Singxer SU-1 Owners

Discussion in 'Dedicated Source Components' started by t bone, Mar 7, 2017.
First
 
Back
21 22 23 24 25 26 27 28 29 30
32 33 34 35 36 37 38 39 40
Next
 
Last
  1. gvl2016
    The absence of the 32bit is puzzling as the SU-1 supports 32-bit over I2S, hmm.
     
  2. gvl2016
    Interesting, does this mean one can use a XMOS driver from another device? I thought the drivers were locked to hardware, after all you can't just get a generic full driver directly from XMOS.
     
  3. LoryWiv
    I can't speak to other XMOS drivers but the current HOLO driver is compatible with SU-1 running latest firmware. Works flawlessly for me.
     
  4. T Bone
    I agree. I installed the latest Holo driver for Windows - Version 4.35 - this morning without incident.
    Even though the Singxer SU-1 is the "first" device in the USB signal path, the Holo driver is able communicate with the XMOS based SU-1.
     
  5. gvl2016
    Thanks folks, good to know unlocked XMOS drivers do exist.
     
    Last edited: Jan 3, 2018
  6. taxman2
    Singxer have made their own driver 4.36 and it sounds much better than any other drivers I've tried so far (DIYINHK, Holo). It also has even 8 packets in the buffer (which means very low latency). So far I could only had 64 packets with the Holo driver.
     
  7. gvl2016
    Is there a 16-bit setting on the "Format" tab in the driver control panel, if there is the "Format" tab at all?
     
  8. taxman2
    Yes, you've got the choice of 16 and 24bits.
     
  9. gvl2016
    Thanks, but no 32 bits? Odd as it is spec'd to support 32 bits over I2S. My Marix X-SPDIF 2 has 24 and 32, but no 16. It sounds like these devices should have all 16, 24, and 32 listed to be able to restrict capabilities based on the downstream hardware.
     
  10. bflat
    There are no commercial audio recordings at 32 bits, nor any DAC in existence that can resolve 32 bits. Even if there were, the minimum listening level would be 192 dB. Of course you could say, I just want more than 24, but that would mean you are listening at more than 144 dB which would literally make your ears bleed. With 16 bit, you may get some short bursts of sound that exceeds 96 dB so you want a few more bits for headroom, but still well below 24.

    If you look at the specs of your DAC, you are likely to see something in the 120 dB dynamic range so well below 24 bits even though it may be spec'd for 24 bits. Schiit will tell you that their flagship Yggy "only" resolves 21 bits. Chord Dave is spec'd at 127.5 dB which is also about 21 bits.

    Of course for native DSD the bit depth is 1 so the resolution increases with just the sampling rate.
     
    T Bone likes this.
  11. gvl2016
    I get it, but if the device is spec'd at 32 bit I want to be able to send 32 bit to it, after all there are DS dac chips that can take 32 bit words and digital filters that can produce them. I'm more frustrated because of the missing 16-bit mode on my Matrix however.
     
  12. bflat
    It can be done. Under Windows, I can use JRiver to upsample to 32 bits and use the ASIO driver to output 32 bits to the SU-1. But as I said, there is no point to it.
     
  13. taxman2
    In my case I use forced 32bits in Jplay settings.
     
  14. bflat
    Dumb question - what do I need to connect the optical output on the SU-1? I have a standard toslink and mini (looks like a 3.5mm jack from Fiio) cable.

    Thanks!
     
First
 
Back
21 22 23 24 25 26 27 28 29 30
32 33 34 35 36 37 38 39 40
Next
 
Last

Share This Page