[barretp]

Can someone help me out with my NFB-28? I'm on Windows 8.1 x64. I think I've installed the drivers correctly, however whenever I installed them, it said driver version 1.2 (Is that the latest version?). When I select playback device it says SPDIF Interface. I thought SPDIF was only the optical chord.
 
 
I can get audio through Foobar2000 and Windows system sounds, but that's all. Is there any way to hear audio from Spotify or Chrome, Firefox? 
 
Edit: I think I've found my issue, I had the default sample rate set too high. I changed it from 2 channel, 32 bit, 384000Hz to 2 channel, 32 bit, 192000Hz.

 

[conquerator2]

Just a heads-up, the issues I've had with the DI's USB... Seemed to have been resolved by installing the latest drivers. I've been using the previous revision drivers and they seemed to work fine but those new ones seem to solve lots of issues people have had with their Audio-gd DACs [blue screens, etc.]
Well, I'll keep watching for a few days and if things stay fine, then I guess all's good.

 

[max785]

  Just a heads-up, the issues I've had with the DI's USB... Seemed to have been resolved by installing the latest drivers. I've been using the previous revision drivers and they seemed to work fine but those new ones seem to solve lots of issues people have had with their Audio-gd DACs [blue screens, etc.]
Well, I'll keep watching for a few days and if things stay fine, then I guess all's good.

I got the lastest driver and I get alot of bluescreens !!

 

[conquerator2]

 
I got the lastest driver and I get alot of bluescreens !!

Sorry to hear that... Maybe it won't solve every issue 

 

[SpirosG]

 
I got the lastest driver and I get alot of bluescreens !!

 
what's your OS ? win7, 8 or earlier ? 

 

[max785]

   
what's your OS ? win7, 8 or earlier ? 

Win 7 sp1

 

[SpirosG]

that' s a little bit peculiar ... I, -with win7-, dont' have bs any more, since I installed the latest driver ...

 

[max785]

  that' s a little bit peculiar ... I, -with win7-, dont' have bs any more, since I installed the latest driver ...

The driver from here ? http://www.audio-gd.com/Pro/dac/USB32/USB32EN.htm the version 1.

 

[conquerator2]

 
The driver from here ? http://www.audio-gd.com/Pro/dac/USB32/USB32EN.htm the version 1.

No from the home website - http://www.audio-gd.com/En%20audio-gd.htm
There's a version 2 in the top center part.

 

[max785]

  No from the home website - http://www.audio-gd.com/En%20audio-gd.htm
There's a version 2 in the top center part.

wow it worked ! I can even see asio in the output pannel of foobar !!!! THANKS

Is it normal that wasapi ( event ) sound better then asio : via ks direct asio ??

 

[conquerator2]

 
wow it worked ! I can even see asio in the output pannel of foobar !!!! THANKS

Is it normal that wasapi ( event ) sound better then asio : via ks direct asio ??

Should be the other way around technically...
But it doesn't matter :]
Both are exclusive modes.
As long as it works now, don't worry about it :}

 

[SpirosG]

what a relief ! I was becoming nervous that -even with the latest (version 2) - the blue-screens will apear again ... 

 

[Gloomy Moonie]

So to confirm, as of now, there aren't any issues with the drivers, correct?
About to pull the trigger on the NFB-15, so if there's anything I need to know - do tell.

 

[Honkytime]

  So to confirm, as of now, there aren't any issues with the drivers, correct?
About to pull the trigger on the NFB-15, so if there's anything I need to know - do tell.

Buy it you wont be disappointed 
 
Cheers

 

[Anda]

Has anyone tried the USB-32 with the new Raspberry Pi 2? I'm using a SA-1.32 recognized as SVB-202D in Linux.
I have a Lenovo T500 and Raspberry Pi 2, both running up-to-date Arch Linux.
The SA-1.32 works fine on my Lenovo, but I'm having some issues with the Pi 2. Below are some results from a simple speaker-test.
It seems my problem has something to do with the buffer handling. The samples are played around 4 times faster on Pi2 (that's also what I hear).
 
I also did some tests with aplay which resulted in "underrun!!!" errors.
 

Spoiler: Warning: Spoiler!

Raspberry Pi 2:
 
[anda@alarmpi ~]$ speaker-test -l 5 -t wav -c 2 -D hw:1,0 -b 1000000
 
speaker-test 1.0.28
 
Playback device is hw:1,0
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 48 to 262144
Period size range from 24 to 131072
Requested buffer time 1000000 us
Periods = 4
was set period_size = 12000
was set buffer_size = 48000
 0 - Front Left
 1 - Front Right
Time per period = 0.584356
 0 - Front Left
 1 - Front Right
Time per period = 0.750027
 0 - Front Left
 1 - Front Right
Time per period = 0.749841
 0 - Front Left
 1 - Front Right
Time per period = 0.750216
 0 - Front Left
 1 - Front Right
Time per period = 0.750286
 
 
 
Lenovo T500
 
[anda@copperhead ~ ]$ speaker-test -l 5 -t wav -c 2 -D hw:1,0 -b 1000000
 
speaker-test 1.0.28
 
Playback device is hw:1,0
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 48 to 262144
Period size range from 24 to 131072
Requested buffer time 1000000 us
Periods = 4
was set period_size = 12000
was set buffer_size = 48000
 0 - Front Left
 1 - Front Right
Time per period = 2,251276
 0 - Front Left
 1 - Front Right
Time per period = 2,999977
 0 - Front Left
 1 - Front Right
Time per period = 2,999963
 0 - Front Left
 1 - Front Right
Time per period = 3,000034
 0 - Front Left
 1 - Front Right
Time per period = 2,999969

 
Does anyone know if there are some issues with VIA VT1731 on RasPi or similar hardware. Any suggestions on how to resolve this?

EDIT: I have no issues with my Gustard U10 (XMOS)