Jump to content
IGNORED

Wyred 4 Sound Dac2SE Upgrade Revisited & Findings -- The Best Decision Unequivocally!


Recommended Posts

  • 2 weeks later...
Thanks, Tony. I didn't spend a lot of time last night trying to figure out why the i2s wasn't playing properly. The result I got was the left channel only playing and that was incredibly noisy. I am sure it is some configuration issue. I went to the usb rather quickly because I wanted to hear music. I will spend more time this weekend and figure out the issue.

 

Please let us know what you discover. My upgraded DAC2v2SE shipped today, so expecting by the middle of next week. I have an SU-1 and Hydra-Z both with external PS ready and waiting. Hopefully, I can get at least one of them to work :-)

 

BTW, props to W4S for offering this upgrade. I have two other DACs that were replaced by essential the same box with the 9038 chip and neither offered an upgrade. Only a trade-in at less than half the cost of a new model.

Link to comment

Just received my upgraded DAC2v2SE tonight. I still have it burning in but I can comment on a couple things mentioned on this forum. I'm using JRMC 22 running on an AO optimized Win10 SOtM sMS-1000SQ with USB out. I tried these combos:

 

  1. USB direct to DAC2 - works fine in all modes using the W4S ASIO driver
  2. USB to Hydra-Z with i2s to DAC2 - can't get the AudioByte driver to work at all, so unable to test this combo
  3. USB to Singxer SU-1 with i2s to DAC2 - as reported, DSD works fine up to and including 256 (4X), PCM results in noise
  4. Roon Server running on Sonic Transporter over wired network to SOtM sMS-200 connected to the Singxer SU-1 streams all DSD up to 256 with no problem

I haven't had a chance to try Roon via microRendu yet. Will give that a shot tomorrow night. 

Link to comment
On 3/24/2017 at 0:56 AM, ksalno said:

Just received my upgraded DAC2v2SE tonight. I still have it burning in but I can comment on a couple things mentioned on this forum. I'm using JRMC 22 running on an AO optimized Win10 SOtM sMS-1000SQ with USB out. I tried these combos:

 

  1. USB direct to DAC2 - works fine in all modes using the W4S ASIO driver
  2. USB to Hydra-Z with i2s to DAC2 - can't get the AudioByte driver to work at all, so unable to test this combo
  3. USB to Singxer SU-1 with i2s to DAC2 - as reported, DSD works fine up to and including 256 (4X), PCM results in noise
  4. Roon Server running on Sonic Transporter over wired network to SOtM sMS-200 connected to the Singxer SU-1 streams all DSD up to 256 with no problem

I haven't had a chance to try Roon via microRendu yet. Will give that a shot tomorrow night. 

 

I got the Hyrda Z working with Mac and Win 10 this weekend and it plays both PCM and DSD just fine through the W4S DAC2v2SE, I had to use native DSD streaming (DoP disabled) to stream 256 (4X) but other than that there are no issues with DSD through the Hydra. It also plays all resolutions of PCM without issue, except for some 24/352.8 recordings I have. These played but there are frequent drop-outs. They play fine over USB into the DAC, so I assume this is some issue with the Hydra.

 

For those with issues with the microRendu, maybe you want to try the SOtM sMS-200 as an endpoint. Mine streams DSD up to 256 through a SU-1 with no issues.

Link to comment

Ideally, Singxter would issue a fix. However, in lieu of that, I agree more specifics on the capacitor and the pin outs would be appreciated. I ordered a couple different ceramic caps from Mouser but they clearly aren't the right ones, as they were so tiny, I couldn't even see them with 2x magnifying glasses on. No way I could solder them. Can W4S provide a link to the right capacitor and some additional directions for the DIYer?

Link to comment
33 minutes ago, Franatic said:

I just saw this thread over on Head-Fi. SuperDad is aware of the DSD phase issue. I am confused as to firmware status and need to investigate more.

Andrea, if you get info from Singxer, let me know.

http://www.head-fi.org/t/839330/singxer-su-1-owners/165

I read through that thread. My understanding is that the problem being discussed there is that the right and left channel are swapped on the i2s output from the Singxer going into the DAC2 i2s input. I suppose this is another result of there being no "standard" for i2s as a device to device interconnect. To fix this problem, Singxer has issued a new firmware. So there are two version of firmware and you have to try them both to see which one is right for your DAC. I'll need to do some testing today to see if this is even a problem with the DAC2 and, if it is, which of the two firmware correct it. I will post back my findings. As for the signals coming from the SU-1 being out of phase, I don't think swapping the R and L channels will fix that. 

Link to comment

Did some more investigation this morning. First, the PS Audio DSD DAC works fine with the SU-1 with all switches off, firmware 2.02, and the latest Windows USB driver. DSD and PCM all resolutions without problem. No phase issues either. It doesn't support Native DSD but that is probably an issue with the PS Audio DAC and DoP works fine, therefore not really an issue. One thing I did discover is that the HDMI cable length really matters. I use a WW Platinum Starlight 0.3m from the SU-1 to the DAC. When I tested the PS Audio DAC I needed a longer cable so I grabbed a 1m AQ Cinnamon cable from my box. It worked for PCM but wouldn't pass DSD. I re-positioned the SU-1 so I could use the WW 0.3m cable and problem solved.

 

So there is clearly an incompatibility between the SU-1 and the W4S DAC2. As there is no "standard" for i2s each side is pointing the finger at the other. I'm working through Tim at Kitsune, where I bought my SU-1 and their PliXir PS upgrade, and have sent him all the information regarding the capacitor values and Frantic's picture of how it is connected. Tim is at an audio show this weekend, so I don't expect to hear anything back until next week. 

Link to comment
4 hours ago, Ienag said:

It could be also useful if someone could report the iussue also to Kitsune to exhort Singxer to provide a solution.

I have done it with Shentzenaudio because I've bought my SU-1 by them.

Hoping something will happen....

As I mentioned in my previous post, I've already provided Kitsune with all of the details, including pictures. Tim is supposed to be communicating directly with the factory, so we'll have to wait to see what the response is. I know they are at a SoCal hifi show this weekend, so I don't expect to hear anything until Mon-Tue at the earliest.

Link to comment

Thanks, Fran, you made a lot more progress than Kitstune, which is the US distributor. I sent them all of the info from this forum including pictures but they say they have not heard anything from Shenzhen Audio. I appreciate everything you've done. I was getting ready to send my SU-1 to W4S for the cap mod but I think I will hold off until Leter finishes his testing.

Link to comment
3 hours ago, Wizzer said:

On a slightly different topic , I have a 2v2SE and wonder if anyone here have used the Wyred4sound Dac with a PS Audio Perfect Wave Transport ?

I'm having an issue with no signal through the 12s connection however the other outputs on the PWTransport work flawlessly with the 2v2SE .

 

For those whom are currently using this combination or have once paired these components in the past have you experienced any issues with the 12s HDMI connections with either component ?

Is the issue with all formats or just DSD?

Link to comment
2 hours ago, Wizzer said:

Cd playback ,.I haven't tried anything else .

I'd guess it's a pin-out incompatibility between the PWT and the DAC2V2SE. From looking into the issues with the Singxer I know they have one configuration for the PS Audio DAC and a different pin-out (using switches) for other DACs. You'd have to try to get pin specs from each vendor to confirm but that's my guess. 

 

 

Link to comment

I'm not sure anyone can be blamed given the lack of any standards for using I2S between components. Remember, I2S was originally intended for internal connections within a device controlled by a single designer and manufacturer. There are no agreed standards for the pin configuration for using I2S between devices from different manufacturers. However, given the small number of DAC manufacturers with I2S inputs and the limited number of source devices with I2S output, it would seem to be in everyone's best interest, especially the customers, for them to get together and agree on a standard amongst themselves. 

Link to comment
2 hours ago, Franatic said:

I have not heard from any other i2s users that it is working with their DACs without issues. It seems Singxer SU-1 users may be the first to try it. If this is wrong I hope others chime in. :)

Actually, I have been happily using a Hydra Z with the W4S with both PCM and DSD without any issues. So the issue is definitely one of compatibility. Given the lack of I2S standards, it's hard to assign blame to either side. I just wish they would get together and resolve it.

Link to comment
  • 4 months later...
  • 6 months later...
15 minutes ago, rah50 said:

Hi Dom:

 

An alternative to the ultraDigital is the Singxer SU-1 which may be more available to you. I only know I can highly recommend the improvement I got going from usb/DOP/DSD128 to I2S/native/DSD256. Either of these solutions would be an add-on down stream from your excellent SOtM gear, so would probably be an improvement. Only way to know is for you to try one of them out.

 

Bob

Unless Singxer has added a capacitor to their i2S output, it isn't compatible with the W4S DAC. I have one, I know from experience. 

Link to comment

I have no experience with the Linux endpoint you are using but I can tell you that the Sonare UltraDigital works fine with USB fed from SoTM 200Ultra endpoint and feeding a PS Audio DS DAC via i2S. So, whoever said it was designed only to work with Sonore products clearly is wrong.

Link to comment

Supported by Sonore or not, I can tell you it works. I have this exact configuration in my home. I have no idea whether SoTM uses a Linux distribution or not, but I suppose they do, since their devices do not require any type of driver install for USB. 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...