Wyred 4 Sound

Correct that we don't closely monitor this thread but please note the following: DAC upgrades for MQA will require more than a firmware update - it will also require hardware unless it can be implemented in the USB interface itself and at that time, that can be USB updated but not the front panel firmware of the DAC. We originally designed the I2S for our DAC to be used with our own music servers and modded components we offered at the time. It also was compatible with PS audio before DSD was implemented where the lines are now multiplexed for DSD and cause the phase issue as noted before. We can only do so much to make sure our unit works well with gear others design after the release of ours but once we heard about this - with your help - we were eager to learn about what we could to to make it work and did. In the near future, we will release such product in our line to properly work with our gear right out of the box. Thank you EJ

Hello and thanks for the interest in our Recovery unit. The iFi iPower does indeed work fine with our unit. We appreciate all of the feedback we get on our Recovery. It is almost universally praised and we feel the finest of the USB reclockers available.

I am not familiar with the AudiophileOptimizer so I can't give an honest opinion, sorry.

The primary differences with the 10th anniversary DAC (besides our spiffy special edition case ) is that the 10th includes a newly redesigned digital board, Hand-matched custom Vishay Z-Foil resistors, Custom 10th Anniversary lathed aluminum footers, and Custom 10th Anniversary red LED display. All of which extends the performance slightly above our highly rated DAC-2v2SE model.

We hope everyone had a nice long weekend! Fran and Minor sure were busy. Jeez...between their dogpiling it got a little hard for us to breathe under here! Guys, we frankly don't have time for the drama that some of you seem to enjoy stirring up publicly instead of reaching out to us directly. We're not huge fans of forums largely for this reason. As we've stated before, if anyone wishes to get direct answers instead of making assumptions, accusations and insults, contact us. For this reason, this will be our last post here. It's tiring monitoring some of the peanuts in this gallery. Below are our 'official' responses. If anything else is needed, please contact us. 'Openly straighten out the issues'... How would we do this beyond publishing the correct diagram, which we did? There was no attempted 'cover up', there was a realization. And once we realized this we gave you the correct diagram. This is news to us. The last time we had any communication with Leter, we had no reason to think he didn't have what he needed, including the info for DSD. We've received NO communication from Singxer that reflects what you say. As we've stated, the chart we posted here is accurate, and then later, we affirmed the chart by vortecjr was good. Thus, it's already been published twice. See the above 2 responses. Everybody can post the same sentence. It has no meaning unless stated by W4S officially. We've already done this. Broken record... see last 3 responses. Cheers, Wyred 4 Sound

@JohnDonaldson and others interested -- In the past, we've partnered with others who have made our USB drivers and firmware. This worked fine for the original project scope and goals, but the flipside is that it's kept our hands tied to their capabilities (and willingness of those parties) to support future, unforeseen implementations not part of the original project. Moving forward, we would like to move away from relying on third parties for these things due to an inevitable bottleneck and lack of adaptability (and sometimes cooperation or availability) on their end, and integrate our own autonomous solutions. This will be a bigger initial challenge for us, but better in the long run to hopefully eliminate situations like these. We're working to make the current circuit operate with Linux in this way. At the same time, we're developing a new solution in-house to have full control. Should we not be able to get the current design working, we'll have two options: 1) to get the new circuit in the DAC, or 2) an upcoming external interface that will also work. Your patience is appreciated, this may take some time.

Yes, this has inspired us to look into this. I don't have a clear timeframe at this point, though.

Agreed. At the time I wasn't aware of that live doc, and we had an old and erroneous one. Posters on this thread were wanting the config so we posted the image, which is accurate. It should have been clearly understood in the context of the post that this was our DAC configuration, thus 5v out. The reason for the 5v out is to power the DAC of the isolated source. If it's not needed, that pin can simply go unused.

We spoke with JR yesterday and his pin configuration chart should be updated and correct. What "misleading information" are you referring to? We posted the correct pin configuration early on in this thread, it has not changed.

Regarding the phase, that is correct. Our fully balanced design took advantage of a former feature on the ESS chip that inverted output polarity. On the new chip, that feature was removed. For the setup menu, the discrete setting is at the 'bottom' of the menu (refer to the manual for the complete menu tree). Once there, hit the up button to get back to previous settings. We believe Leter has everything he needs from us for the update. We've enjoyed very open communication between each other so I expect if anything further from us is needed, he would reach out. I would inquire with him for any ETA-related questions.

We have given Leter our pin configuration and he emailed that he is working on a firmware update.

As we've said many times here and elsewhere, PS Audio PWT. Our server board is our music server, which works perfectly with our I2S, i.e. no noise, phase issues, etc. Our collective thanks. We're working with Singxer on it as well. This is why we're working with Singxer. You're welcome. However, once the Singxer fix is implemented, we expect the fix we did for your unit to be irrelevant for future users. Enjoy the weekend.

John, we wish there was. But the noise is related to a timing problem within the provided I2S signal and we are hoping that the changes Singxer is making will correct this. To see the firmware version, turn the DAC off in the back, then turn it back on. The firmware version will flash on the display.

Look, Fran. Our DAC has never had any PCM noise via I2S with any other device that we know of over all the years that we've implemented it. The Singxer is the first, and like we said, it's possible that the changes we are working with Leter on to make will correct the I2S timing to alleviate the issue. So we're doing more than 'wishful thinking'. As far as testing goes, we test with both a PS Audio device and our own server board without issue.

Attached please find our I2S pin configuration. Based on PS Audio’s model, pins 1 and 3 need to be addressed from Singxer to fix the phase issue. We have reached out to Leter of Singxer about this and are awaiting his reply. FYI, there are no other variations of our pin configuration; we’ve been doing it this way since the beginning. Regarding the PCM noise issue, putting the cap fix on either side accomplishes the same result. The reason we fixed the Singxer instead of our DAC is that our other I2S sources do not exhibit any noise issues. In addition, we had Fran’s Singxer here, not his DAC. There is a chance that if Singxer is able to update their I2S, the noise issue could also go away due to the improved clocking. Our theory is that it’s caused by isolation jitter on the Singxer output. We’ll post more once we hear back from Singxer.