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

Audio-gd Digital Interface - Page 237

post #3541 of 4054

Just as a piece of information, for any who wish to use it with Winamp like I do (I'm used to it, you can go bit perfect with it like foobar, and I never found any difference in ABX tests between foobar and winamp using wasapi on both):

 

adionSoft WASAPI plugin: doesn't work (V1 did)

Maiko WASAPI plugin: works but channels reverse at each music play, and sound signature changes a lot for whatever reason (worked correctly with V1)

KernelStreaming plugin v3.63: doesn't work

 

With otachan ASIO plugin 0.70 and ASIO4ALL 2.10 installed:

 - VIA DirectKS ASIO device choosen in ASIO output settings: doesn't work

 - ASIO4ALL v2 choosen in ASIO output settings: OK

 

With otachan ASIO plugin 0.71 x64 (Intel) and ASIO4ALL 2.10 installed:

only ASIO4ALL v2 available in ASIO output settings: OK

 

Issue now is that I can't get rid of the ASIO-related problematic gaps between tracks...


Edited by Pacha - 2/13/13 at 6:23am

Gear mentioned in this thread:

post #3542 of 4054

As I stated before, I have a similar experience with Foobar 1.2.2 and DI-V3 under Win7 64-bit:

 

WASAPI output 3.2.1 doesn't work (but worked with DI-V1)

Kernel Streaming  1.2.2 works (but didn't work well with DI-V1)

 

> So I use Kernel Streaming instead of Wasapi in Win7 64 now.

post #3543 of 4054

I am using my DI-V3S with Win7 64bit:

 

1/ Foobar work fine with KS, ASIO4ALL v2, WASAPI and JPlay ASIO. Yup my VIA DirectKS ASIO also doesn't seem to work on foobar either - the sound bars graph moves but no sound;

2/ With JPlay mini, both KS and WASAPI work just fine. I have to set buffer to 128 samples, any lower I get drop out. I guess this is pc performance dependent.


Edited by SleepyOne - 2/13/13 at 1:53pm
post #3544 of 4054

If the driver source folder have move or rename, the ASIO can't work .

Release the driver source in the Driver: C and install the driver, keep it in the Driver :C .

post #3545 of 4054
Quote:
Originally Posted by Pacha View Post

 

 

I switched connectors inside the DI to have current technolgy going through RCA instead of BNC.

This was not that easy as Audio-gd put some glue on the connectors to prevent them from unplugging during transport, but I managed to switch them.

 

 

 

what is the difference between current technology and class technology and how much of a difference does it make?

post #3546 of 4054

I think Kingwa answers your question best here: http://www.audio-gd.com/audio/ACSS.htm

post #3547 of 4054

This is NOT the problem

 

I have left the source folder exactly where it was:

 

 

 

Please fix this

 

 

Quote:
Originally Posted by Kingwa View Post

If the driver source folder have move or rename, the ASIO can't work .

Release the driver source in the Driver: C and install the driver, keep it in the Driver :C .


Edited by hawkhead - 2/14/13 at 2:26am
post #3548 of 4054

Some more information on the VIA ASIO issue (v1.22 drivers)

 

The VIA ASIO control panel WILL NEVER WORK inside Foobar because the driver is looking for the wrong name - control.exe

 

If you make a copy of VIA ASIO ControlPanel.exe and call it that control.exe it will load - but still no sound

 

 

post #3549 of 4054

Thanks hawkhead for the inform!


Edited by SleepyOne - 2/15/13 at 2:25am
post #3550 of 4054

I just received my DI-V3 w/PSU yesterday. It seems to be working great but I have a question. When I switch on the PSU the blue light comes on but the light on the DI doesn't light up until I plug the USB cord into my PC. Is the light on the DI a link light or a power on indication? Before anyone asks, yes, I have the cord connecting the two boxes. My concern is that the PSU isn't actually powering the DI but instead it is getting power from the mac's usb port.

post #3551 of 4054
Quote:
Originally Posted by Erieg View Post

I just received my DI-V3 w/PSU yesterday. It seems to be working great but I have a question. When I switch on the PSU the blue light comes on but the light on the DI doesn't light up until I plug the USB cord into my PC. Is the light on the DI a link light or a power on indication? Before anyone asks, yes, I have the cord connecting the two boxes. My concern is that the PSU isn't actually powering the DI but instead it is getting power from the mac's usb port.

 

Try turn the other switch at the back of the DI. It switches the power between PSU and USB.

post #3552 of 4054

Both switches are in the on postion. I guess the best question is .. is the light on the DI supposed to light up when is attached to the powered on psu but not the computer?

post #3553 of 4054

The switch has three positions.

 

1. DC in -  The front light will up when you have a PSU connected

 

2. Mid position - The front light will off and DI is off as well

 

3. USB - The front light will up if you have a USB connected to a computer and the computer is on

 

Hope this help.

post #3554 of 4054

It's a power indicator light.

post #3555 of 4054

Thanks Jimmychan. I will take a look at it when I get to work on Monday. I figured I was doing something wrong.

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

Gear mentioned in this thread:

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