Audio-gd Digital Interface - Page 213

The XO specification is 3,3 v to 5 v,this should be ok,the TCXO of Kingwa is a specification of 5 volts ?

RELEASE ZE DRIVARS!!!!11111!!!11!1!1
 

Kingwa,the driver Tenor is soon available please?

+1 -request for the new drivers!

Well they certainly didn't meet the July 31 deadline... it's August 1st in China right now.

Tenor worker called me yesterday, she inform they have packing the driver and will send to me within few days.

And they have working on a fully new driver applied the full new configuration instead modify on the old driver , can send to me around 15 th Aug.

And plan to release at the end on Aug.

I can't help them work on the driver.

But we can promise if the full new driver still can't fix the problems, we will help users fixed the problems.

Thank for the information Kingwa.The beta driver that you have received a few days ago we would wait until mid August,

Tenor tell me the new beta driver will send me around 3th Aug.

The full new driver will send me at 15th Aug for test .

They tell me I want consider if want to release the beta driver because the full new driver will coming soon.

They expect the full new driver will much better .

They are afraid the new beta driver if can't fix all matter cause users lose their belive.

Kingwa

you want to ask Tenor why they released such a bad driver

hawkhead: It is just about impossible to release perfect software the first time, as it is impossible to test for every possible combination of software and hardware out there that might cause issues. Inevitably issues only come up when the software is released and they see how it performs with customers.

At first we feedback the problems to Tenor, they unbelieve because they claim they have not any issue.

Then they guess maybe the hardware problems? And ask me send two gears to them for test but confirm the hardware without problems.

Still this issue is quite less, in our feedback only less than 2% users encounter the issue .

I asked our Thailand agant, they sell a lot every months and today they replied me only two users have the issue.

I can understanding the first driver have the bugs as some other company also encounter this problems.

So I still waiting their hardwork.

How hard can it be to test 192 playback via WASAPI - does anyone have that working ?

Quote:

Originally Posted by hawkhead 

How hard can it be to test 192 playback via WASAPI - does anyone have that working ?

I am not using a DI , but on my NFB-17.2 (wich use Te8802) , foobar => WASAPI => Stock USB cable get with NFB-17.2 => 24bits/192khz  working flawlessly (just listened 10min right now) . But i mosly use 16/44 ...

Quote:

Originally Posted by Currawong 

hawkhead: It is just about impossible to release perfect software the first time, as it is impossible to test for every possible combination of software and hardware out there that might cause issues. Inevitably issues only come up when the software is released and they see how it performs with customers.

Exactly. I have NO issues whatsoever and my system has everything overclocked (FSB, CPU, GPU, RAM).

One thing you can try, (not sure if AMD chipset has this), is try disabling High Precision Event Timer.  That should lower the DPC latency.

Hi guys, I haven been looking through this thread to and fro and still undecided on 1 thing.. I intend to get the DSP version and have 1 clock upgraded, but does it make more sense to upgrade the clock for upsampling? Since there was discussion that the 12mhz clock upgrade was a tiny improvement? Still, I am not sure how significant the 24.576mhz TCXO clock is since the upsampling is a rather subjective matter too..

Thanks for any advices, really appreciate! :)