Head-Fi.org › Forums › Equipment Forums › Dedicated Source Components › Audio-gd Digital Interface
New Posts  All Forums:Forum Nav:

Audio-gd Digital Interface - Page 230

post #3436 of 3875
1/21/13 at 7:24am

Hi, have anyone tried DI-V3 with Voyage mpd?

Reply

Head-Fi's Best Sellers

post #3437 of 3875
1/21/13 at 9:11am
Quote:
Originally Posted by Clemmaster View Post

My new NFB-27 came with the firmware #4 already installed. It did not work properly with the Squeezebox Touch. I just got heavily distorted sound (as if the USB receiver was mixing data from left & right channels. Hard to describe but a total mess). I could get it to work only once on several trials and it stopped working after I turn the light off (which always stopped the playback for few seconds with this firmware!?).

I switched back to firmware #3 and everything works fine (the playback still stops when I turn the light off sometimes, but much less often biggrin.gif)

Yes but with firmware #3 it's probably only working in adaptive mode which is supposed to be inferior to asynchronous mode.

It's quite confusing with FIRMWARE #4 referring to the audio-gd chip and KERNEL#4 referring to SBT.

I can't find any kernel installer anywhere other than the one that's included in the EDO applet. And I would like to get it working in async mode with the VT1731 chip.
Edited by SebastianL - 1/21/13 at 11:57am
Reply
post #3438 of 3875
1/21/13 at 2:59pm
Adaptive is not inferior by design. It all depends on implementation. So far I must say I prefere the built-in USB-32 (firm #3) to the Stello U3 feeding the NFB-27 through coax.
Reply
post #3439 of 3875
1/21/13 at 7:01pm
Quote:
Originally Posted by SebastianL View Post

Yes but with firmware #3 it's probably only working in adaptive mode which is supposed to be inferior to asynchronous mode.

 

How do you figure this? The reason I ask is, this kind of casual comment can become false fact fast without confirmation. smile.gif

Reply
post #3440 of 3875
1/21/13 at 11:12pm
Firmware 4 is locked at 48khz async with EDO, and no way to change it. Firmware 3 sounds good enough nonetheless,although in adaptive mode, compared to AP2 async.
Reply
post #3441 of 3875
1/22/13 at 1:49am
Quote:
Originally Posted by Currawong View Post

 

How do you figure this? The reason I ask is, this kind of casual comment can become false fact fast without confirmation. smile.gif

 

I read about it here (at The Well Tempered Computer):

"Asynchronous USB looks to be the perfect solution. You configure your PC for bit-perfect output and the DAC takes care of the timing totally independent of the timing of the PC."

"Asynchronous mode is not better by design but by implementation because you can implement a top quality (low jitter) clock in the DAC."

 

Also I feel it's the general opinion over on computeraudiophile.com

But I understand it depends on the implementation which is why I would like to try SBT async with a DI-V3 which has very little jitter according to Kingwa. Also there are reports that the clock in SBT is nothing to boast about.

 

Sorry if I didn't make myself clear and caused some confusion.

Reply
post #3442 of 3875
1/22/13 at 2:24am
Quote:
Originally Posted by sayh View Post

Firmware 4 is locked at 48khz async with EDO, and no way to change it.

 

Does this apply even with kernel #4 installed? Then it should be added to the notes of the EDO compatibility list.


Edited by SebastianL - 1/22/13 at 6:17am
Reply
post #3443 of 3875
1/22/13 at 3:12am
Quote:
Originally Posted by SebastianL View Post

Quote:
Originally Posted by Currawong View Post

 

How do you figure this? The reason I ask is, this kind of casual comment can become false fact fast without confirmation. smile.gif

 

I read about it here (at The Well Tempered Computer):

"Asynchronous USB looks to be the perfect solution. You configure your PC for bit-perfect output and the DAC takes care of the timing totally independent of the timing of the PC."

"Asynchronous mode is not better by design but by implementation because you can implement a top quality (low jitter) clock in the DAC."

 

Also I feel it's the general opinion over on computeraudiophile.com

But I understand it depends on the implementation which is why I would like to try SBT async with a DI-V3 which has very little jitter according to Kingwa. Also there are reports that the clock in SBT is nothing to boast about.

 

Sorry if I didn't make myself clear and caused some confusion.

 

Sorry, I meant how do you know that firmware #3 is not async and #4 is async? That just strikes me as very unusual. smile.gif

Reply
post #3444 of 3875
1/22/13 at 3:23am
Quote:
Originally Posted by Currawong View Post

Sorry, I meant how do you know that firmware #3 is not async and #4 is async? That just strikes me as very unusual. smile.gif

X2 I thought you needed different sort of clock for asynch and adaptive usb (fixed vs voltage controlled.). Although maybe I have extrapolated too much into wavelength's white paper.
Reply
post #3445 of 3875
1/22/13 at 3:30am

for example, DI-DSP works in adaptive mode if no drivers are installed and in async with them.

Reply
post #3446 of 3875
1/22/13 at 3:48am
Quote:
Originally Posted by kr0gg View Post

for example, DI-DSP works in adaptive mode if no drivers are installed and in async with them.

I have definitely confused myself with wavelengths white paper in this case... DX"
Reply
post #3447 of 3875
1/22/13 at 4:19am
Quote:
Originally Posted by rdsu View Post

DI will not use the power from USB cable, to avoid noise from the source, if we use a PSU?


Any help here?

 

Thanks

Reply
post #3448 of 3875
1/22/13 at 5:16am
Quote:
Originally Posted by Currawong View Post

 

Sorry, I meant how do you know that firmware #3 is not async and #4 is async? That just strikes me as very unusual. smile.gif

 

Again I'm just referring to the EDO compatibility list that was mentioned earlier in this thread. If you read the USB transfer mode column corresponding to "Dac's w. VIA 1731":

firmware #3 Adaptive
firmware #4 Asynchronous

Whether that's correct or not I don't know. I don't even know who made this list to begin with or if it's being maintained. I somehow assumed that Triode kept track of it.

Next to the USB transfer mode column there is the Notes column that states that:

 

(Chip supports up to 384KHz/32bit), with kernel #3 working in adaptive mode, with kernel #4 working in asynchronous mode

 

That's where I got the information. Been trying to locate Triode himself to confirm this but somhow I can't login to the Slimdevices forum in order to contact him.

Reply
post #3449 of 3875
1/22/13 at 11:56pm

Hi! 

 

I recieved my Audio-gd DI V3 yesterday,I bought it as an upgrade to my DI DSP (V2) - which worked perfectly for me to. 



I recieved my V3 with the default firmware chip #4 installed - this did not work in XBMC, only in foobar. 

 

But then i tried to change it to firmware #5 - and now i works perfectly with XBMC (Frodo RC3 with Wassapi ). 

 

I will test it on my MPD server, and i will try to compare it to the V2  and the V1 (Dsp) Which one of my hifi friends has. 

 

Best regards, 

Reply
post #3450 of 3875
1/23/13 at 12:57am

Firmware #5?

Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Dedicated Source Components

Head-Fi's Best Sellers

Head-Fi.org › Forums › Equipment Forums › Dedicated Source Components › Audio-gd Digital Interface