Audio-GD Reference 5.2 (New Balanced 4x PCM1704UK DAC)

[HaVoC-28]

There is no "hardware issue" with TE8802 , there is an driver issue depending on many things , not all user will have problem some only , and it's a minority . But even if it's a minority there is many complaining about it , enough to switch to "usb 32" 

 

[preproman]

Quote:

There is no "hardware issue" with TE8802 , there is an driver issue depending on many things , not all user will have problem some only , and it's a minority . But even if it's a minority there is many complaining about it , enough to switch to "usb 32" 

 
 
 
Agreed but...
 
Why not take it offline and not offer the product until the issue is resolved or until a new product is tested and produced.
 
It doesn't really matter if it's the minority or not.  It's still a potential issue for any new adopter of this product.
 
As a new customer I'll stay as far away from this as possible until I see a resolution or a new product.

 

[HaVoC-28]

Hum When Audio GD released TE8802 based products they had done numerous test on various computers , and TE8802 was used in other brand before Audio GD like for the ILTW DAC from Firestone Audio (taiwan) they have been using TE8802 , almost one year before Audio GD etc .
 
Audio GD hardware Djob on TE8802 is done , and supposedly well done . But for some their is driver problem , and Audio GD can't help about it , they can just advice "to Wait for tenor ... "  i don't think that probems popped out directly it grew up slowly 
 
Now they switched to USB32 that seams more mature for the driver side but you will see .
 
 
Custom Drivers can be risky 

 

 

[tme110]

though the users who had the tenor issues were very vocal, I never got the impression that many people (percentage wise) had any issues at all. It could have been issues with thier computers for all anyone knows. Plus you can just use the DI as a coax reclocker which is what I wanted it for. I just ignore USB all together and don't have to deal with any of these issues.

 

[Rodzt]

Hello! 

 
Anyone had the chance to compare this DAC to Wadia's 121? 

 
Impressions would be much appreciated. 

 
Thanks! 

 
Rodrigo

 

[stoutblock]

This is the note I got from Kingwa about upgrading my 5.2:
 
"We will offer the upgrade for users, for the Reference 5.2 ,users even without solder can replace the USB input.
But now we wish can sale more gears and get more users feedback to confirm the driver have not matter.
Do you mind waiting some days for the driver confirm?"
Kingwa
 
I have mixed success with my current tenor chip...
 

 

[stoutblock]

I bought a USB32 board for my 5.2.  I removed the TE8802 drivers from my PC, installed the board, down loaded the USB32 drivers (but did not install), plugged in the DAC (USB), but PC does not detect the DAC.  Drivers fail to install.
 
Anyone done this successfully?
 

 

[FauDrei]

Few things...
 

1. check wire connections to/from USB-32
2. check whether USB firmware chip is seated properly in the socket
3. change USB cable

 

[stoutblock]

Yes, the cable is connected correctly.
Chip is installed as received. How would I know which way is correct?
Tried a different USB cable with no luck.  TE8802 works fine with both cables.

 

[jrjhoe]

Quote:

Yes, the cable is connected correctly.
Chip is installed as received. How would I know which way is correct?
Tried a different USB cable with no luck.  TE8802 works fine with both cables.

Which cable did you use to connect the usb-32? Mine came with a cable that was 'cross' wired compared to the original cable in the dac. Using the cable that came with the usb-32 it didn't work, while it works perfectly fine with the dac's original cable (the one the TE8802 was connected with).

 

[tme110]

how did you know it was cross-wired?
 

 

[FauDrei]

Chip is installed as received. How would I know which way is correct?

 
I did not suggest that chip was installed in wrong direction. If this would be so - the chip would be killed in a few seconds after power on.
 
I suggested to "check whether USB firmware chip is seated properly in the socket" - which simplified read as: "While NFB-11.32 is not powered on, carefully push USB firmware chip with one finger into the socket where it resides.". There is a possibility that chip has weak contact with the socket due to mechanical shipping stress.
 
BTW, proper installation direction of the USB firmware chip in NFB-11.32:
 

 

[FauDrei]

...also - the good quality looking USB cable that came with my NFB-11.32 had certain connector (mis)tolerance problem(s) which caused that computer was not properly detecting USB-32 interface or USB-32 was abruptly disconnected from the computer after slighest movement of the computer, cable or NFB-11.32.
 
Worth (re)checking.

 

[jrjhoe]

how did you know it was cross-wired?

 

I don't know which of the two is cross-wired, but one of the connectors is mounted on the cable the other way around compared to the original... I don't know if this was accidental and I got the wrong cable, or if this is always the case.

 

[stoutblock]

Quote:

Which cable did you use to connect the usb-32? Mine came with a cable that was 'cross' wired compared to the original cable in the dac. Using the cable that came with the usb-32 it didn't work, while it works perfectly fine with the dac's original cable (the one the TE8802 was connected with).

Bingo!  Cable that comes with the USB-32 board has the pins connected in the opposite sequence on one end compared with the TE8802 cable.  Don't know if this is an error or if the cable is for another application?  In any case, using the original cable the DAC now sounds perfect with absolutely no latency problems running on my little ASUS EeePC.  Now I have Reference 5.32