Jump to content


  • Content Count

  • Joined

  • Last visited

  • Country

    United Kingdom


About louisxiawei

  • Rank
    CA Member

Recent Profile Visitors

5544 profile views
  1. 2006be11 works well on Linux. I’ve been testing it for two days, so far so good. Thanks for the tireless effort. I will spend another few days to see if it goes well on windows and report it back.
  2. @Miska Could you please explain the "Change output stream start/stop handling" in 4.3.3 version? Thanks.
  3. I sense him discouraging the oversampling apporach. Quite a pity he has missed so much fun. 😏
  4. For R2R part, I applied the same filter as SDM: poly-sinc-xtr-lp, new dither: LNS15 and upsampled everything at 1.536M. The sound is very transparent, nothing warm or blur as many said R2R used to be. I believe it's a good and rare thing for a R2R dac? Frankly speaking, I personally think R2R part sound is a bit dull compared to SDM part when using HQplayer. Less holographic and organic. I don't have other R2R dacs to compare with it at the moment because I used to avoid purchasing ladder type dac. I would say DSD512 gives obviously more 3D airy sounding while DSD256 g
  5. Yes, MAY has no volume control in either OS or NOS mode.
  6. Ok, let me make a simpler example: When I dragged the same track time bar (e.g. from 1:20 to 2:45), there is a pop occurred on MAY (or DAC8 on windows). I remember I sent an email to T+A regarding this and they confirmed this pop noise and told me it's normal. Yes, the buffer time was set to be default. Maybe you have a different firmware?
  7. Some subjective listening impressions: To better check any difference MAY could possibly bring compared to my previous DAC8, I applied the same HQplayer settings on MAY as on DAC8 DSD, so only DSD512 part. I will check the R2R or DSD1024 bit later on. MAY just has more fun to explore, needs take some time I'm afraid. In general, I find MAY's sounding is very neutral, transparent and resolving. By comparison, I think DAC8 is obviously warmer while MAY is obviously calmer. This "clam" is not related to "not musical" or "thin" sounding, maybe I should say more neutral.
  8. I also don’t have start/stop pops. The pop I meant only occurres when switching to another track manually. Dac8 used to have this kind of pops and it might still have it on Windows OS.
  9. Another thing I like about MAY is its usb connection. Since it has a quite good USB galvanic isolation internally, I tried not using the USB dongle ISOregen and found the the sound "pure, clean" enough to be satisfied. I’m sure someone can observe some differences/improvement if you plug these ISOregen-ish things back. But for me, MAY itself suffices. I enjoy more of the trouble-free operation. I’m a bit fed up with plugging dongle to the dac and powering the dongle with another LPS and then worrying about their disconnection from time to time. 😂 In my opinion, all DAC nowada
  10. As I said, it’s more a Linux issue. Good to know MAC doesn’t have that hassle.
  11. I will now start with more objective operational stuff and later on towards a bit subjective things. For connectivity, it is a VERY HQplayer friendly DAC. The manual will tell you to install windows USB driver in order to support DSD1024 & PCM 1.536M playback, but it is not necessary. I strongly recommend you use to burn HQplayer NAA ISO image on the USB and plug onto your NAA, then HQplayer will recognize the MAY's end. I believe the ISO image is a customized linux kernal by Miska and allows your NAA to playback native DSD1024 on MAY. As I'm sick of windows OS for audio output
  12. I see people starting discussing the MAY DAC on Spring thread and ASR forum has given some detailed measurements of MAY. As an early MAY user, I feel it‘s necessary to open a new thread to have more discussions for this exciting DAC. I just received it a few days ago and it is still warming up. So bear with me with the listening impressions as I haven’t got too much to say yet. I purchased MAY mainly for the purpose of using its NOS feature with HQplayer (So I don't care other OS features). I used to have T+A DAC8 DSD and guess I might not help myself comparising
  13. I also flashed my dac8 to 2006be10 a few days ago. Boot HQplayer NAA image on my CL100 via USB. Work like a charm in most time. I only detected some distortion one time during turning down volume of my preamp. I'm not sure if I can blame on amanero firmware or something else, will keep an eye on it for a bit more time. Soundwise, it's wonderful. I sense better transparency and there is even no pop when switching tracks. Maybe because of better I/O optimised on HQplayer OS than windows 10, the lyrics timing on ROON syncs correctly to the track. I used to run NAA on Windo
  14. @Miska Thanks for the 4.0.2 update. I see you adding some new features such as 48K DSD and adaptive output rate. Is it possible to add this function: When we greyed the 48K DSD option : upsampling DSD file (DSF) to DSD512 at 48K rate only. Upsampling DSD files to 48X512 does not need too much CPU horsepower since it does not apply the SDM filters. Could you give an example of using greyed adaptive output rate? I'm a little confused about this option. For the case of 48K rate 512 supported DAC like T+A DAC8 DSD, when doing DSD512 upsampling rate at non-2s
  15. @Miska Among windows, linux and mac os these OS, which version of HQplayer you think has been best optimized for running filters in terms of CPU multi-core and GPU cuda offload? I believe mojave cannot support Nvidia graphic card, so cuda offload on that system will be a problem.
  • Create New...