|
Home | Forums | Rules | Articles | diyAudio Store | Blogs | Gallery | Wiki | Register | Donations | FAQ | Calendar | Search | Today's Posts | Mark Forums Read | Search |
exaDevices World-class audio devices for do-it-yourself projects from exaDevices |
|
Please consider donating to help us continue to serve you.
Ads on/off / Custom Title / More PMs / More album space / Advanced printing & mass image saving |
![]() |
|
Thread Tools | Search this Thread |
![]() |
#1201 | |
diyAudio Member
Join Date: Feb 2011
|
Quote:
Regards, exa065 Last edited by exa065; 22nd October 2012 at 08:26 PM. |
|
![]() |
![]() |
#1202 |
Can you say Audio?
diyAudio Member
|
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?
Last edited by MisterRogers; 22nd October 2012 at 08:46 PM. |
![]() |
![]() |
#1203 | |
diyAudio Member
Join Date: Apr 2003
Location: MA
|
Quote:
Are there measurements for the exaU2I after the upgrade? Or before and after comparison? |
|
![]() |
![]() |
#1204 |
diyAudio Member
Join Date: Oct 2004
Location: NRW
|
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. |
![]() |
![]() |
#1205 |
diyAudio Member
Join Date: Feb 2011
|
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.
|
![]() |
![]() |
#1206 |
diyAudio Member
Join Date: Apr 2008
|
YES! YES!
![]() |
![]() |
![]() |
#1207 |
Can you say Audio?
diyAudio Member
|
Thanks for the clear answer George. We'll not expect DSD support for the current device.
|
![]() |
![]() |
#1208 | |
diyAudio Member
Join Date: Feb 2011
|
Quote:
|
|
![]() |
![]() |
#1209 | |
diyAudio Member
Join Date: Feb 2011
|
Quote:
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 |
|
![]() |
![]() |
#1210 |
diyAudio Member
Join Date: Feb 2011
|
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. |
![]() |
![]() |
Thread Tools | Search this Thread |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Ultimate USB to I2S interface | sampler | Digital Source | 206 | 30th January 2012 03:45 PM |
High Resolution Multi-Channel Digital Interface | Brian Brown | Digital Source | 34 | 15th January 2008 06:48 PM |
interface I2S with USB | mermoz | Digital Source | 0 | 21st February 2003 10:34 AM |
New To Site? | Need Help? |