exaU2I - Multi-Channel Asynchronous USB to I2S Interface

[exa065]

Originally Posted by labjr

I'd just like to see an end to the perpetual upgrades.

DSD256 should be the highest DSD sampling rate needed since the quanitzation noise is out of the audio band. Same with PCM sample rates. Really no need to go beyond DXD/384.

We provided several free upgrades for the exaU2I at no charge:

• 384 kHz sampling rate was a free software upgrade
• dsd64/dsd128/dsd256/dsd512 was a free software upgrade
• OSX drivers
• We released a second generation ASIO drives and the Dashboard
• We also upgraded the clocks with 1ps crystals without changing the price
• The devices with upgraded clocks have a new firmware with lower jitter

At this time we are discussing a new device, not an upgrade.

Regards,

exa065

[MisterRogers]

To be clear - do you still plan on having a new OS X driver available soon that will work with the current board and Audirvana; providing DSD support?

[labjr]

Originally Posted by exa065

We provided several free upgrades for the exaU2I at no charge:

• 384 kHz sampling rate was a free software upgrade
• dsd64/dsd128/dsd256/dsd512 was a free software upgrade
• OSX drivers
• We released a second generation ASIO drives and the Dashboard
• We also upgraded the clocks with 1ps crystals without changing the price
• The devices with upgraded clocks have a new firmware with lower jitter

At this time we are discussing a new device, not an upgrade.

Regards,

exa065

Thanks for the info. I was not aware of the upgrades.

Are there measurements for the exaU2I after the upgrade? Or before and after comparison?

[DUC985]

not working means that Audirvana is for example not outputting any sound Amarra is unstable and crashing from time to time under Mountain Lion.
This is not the problem with other USB devices so its a driver / OS problem.

I'm happy to go back to Snow Leopard if that would solve the issues, but so far i have not heard any statement if this would solve the issues, you only promised updated drivers a few posts. I'm also not the only one having issues with Mountain Lion. So either way updated drivers are needed or an older OS.

[exa065]

Originally Posted by MisterRogers

To be clear - do you still plan on having a new OS X driver available soon that will work with the current board and Audirvana; proving DSD support?

The current exaU2I supports DSD in a twisted way. Our e20 DAC and the new to-be-developed USB to I2S interface support DSD natively. I don't like half measures, new driver without hardware support won't make anybody happy. It is time for a new device.

[Forane12]

YES! YES!

[MisterRogers]

Thanks for the clear answer George. We'll not expect DSD support for the current device.

[exa065]

Originally Posted by DUC985

not working means that Audirvana is for example not outputting any sound Amarra is unstable and crashing from time to time under Mountain Lion.
This is not the problem with other USB devices so its a driver / OS problem.

I'm happy to go back to Snow Leopard if that would solve the issues, but so far i have not heard any statement if this would solve the issues, you only promised updated drivers a few posts. I'm also not the only one having issues with Mountain Lion. So either way updated drivers are needed or an older OS.

What version of the OS X drivers are you using? Have you reported the issue to customer service on our website? I don't thing we left any request sent to customer service unanswered, and we don't have any open cases on OS X. I use Audirvana Plus, and I recommend it to customers. What is your user name on our website? I would like to check the customer service logs.

[exa065]

Originally Posted by labjr

Thanks for the info. I was not aware of the upgrades.

Are there measurements for the exaU2I after the upgrade? Or before and after comparison?

Here are the measurements on our website: www.exadevices.com > exaU2I > Measurements

I also did a quick search on this thread for measurements:

exaU2I - Multi-Channel Asynchronous USB to I2S Interface

exaU2I - Multi-Channel Asynchronous USB to I2S Interface

[exa065]

I admit that lately we've been busy with the e20 DAC, and this thread was neglected. I don't know if the world needs another exaU2I, that's why I am asking.

Two years ago there wasn't much choice. We were waiting for the USB to I2S interface from TPA. Now there is a healthy competition. We have the WaveIO, but it has been reported that it has 2 ns jitter because of the internal XMOS re-clocking. My customers have told me that they have bought it, tested it, and sold it because "it is not in the same league with the exaU2I". There is no DSD support either. I know that the use of standard drivers is a big convenience and it opens the door to new platforms, like iPad and Android, but priority must be given to the sound fidelity.

Then there is the new USB to I2S 384Khz - DSD Converter. I am reading on their thread that it cannot pass the bit-perfect test of the Audio Precision APx525 system, and it doesn't sound as good as WaveIO. You get what you pay for.

Asynchronous I2S FIFO device is another alternative. It can provide very good results, but I think it is a partial solution. Perhaps I am wrong, here is my issue with it. The I2S buffer has no way to control the computer. Even if it is attached to an asynchronous USB interface, it has no way to ask the computer to speed-up or slow-down the USB stream of data. Computer timing is horrible. The FIFO board uses its own clocks for re-clocking, so the two clocks will go out of sync. After a while the FIFO buffer will skip, if the computer clock is faster, or it will get empty if the computer clock is slower. It is just a matter of time. For a 100 ppm computer clock the chance is let say 1:10,000 on the bit-clock frequency. Depend on the sampling rate and the FIFO buffer size this can be after 15 min or after an hour. Perhaps it is OK to have one FIFO buffer error per hour. I continue to believe that the top solution is asynchronous USB to I2S, nor asynchronous I2S to I2S.