Originally Posted by HeatFan12
Well, just installed my NFB-11.32 to a W8 laptop and working flawlessly right now with Foobar (v1.1.16) wasapi event. Still have to test the other renderers. Don't know how many driver versions are now for the 11.32 but I'm on v.1 and all is good and sounding delicious with some Senns....
Wish I could say the same for my NFB-15.1 (TE8802)...lol....The TE8802 does not like W8...It plays lovely with XP, Vistax86 & x64 as well as W7. Hopefully Kingwa will update the drivers for the TE8802.
Ok, to the above picture...
Under Windows 7
I have there only 44,1K and 48K sampling options... those 88,2K-192K are there not even listed.
To the bit depth... I have there all three options, but only 16-bit and 24-bit can be selected.
Under foobar, If I am trying to play anything 88,2-192K, it will fail, and if I am trying to play 32-bit file, it will fail too.
The drivers I am using are v 1.0 and firmware No.1. Well, it seems, that you are using No.1 too, and it is working for you as it should, so I really don't know, where is the problem.
Now, to the random freezes of NFB11.32, during the playing of sounds.
I was able to discover, what is causing this issue. The power. Better said, the shortages in power line. I've noticed, when for example refrigator runs its engine, or printer, or even my table lamp (which is connected to same power slot as computer and NFB11.32), it will cause freezing. So, when some demanding power device will run, it will make a little shortage in power line... the lights dims a little for a bit of second, and they restore... The computer can handle these power line shortages without problems, because it's power supply is quality one (I have Seasonic power supply), but it seems, NFB11.32 not. Maybe, every power line in every house, is other, some powerlines are maybe less sensitive for this. But here, powerline just makes a little shortages with high-demanding device run out...
Well, now interesting point: NFB12.1 has resisted these shortages without problem. But now, NFB11.32 don't. For me, it seems, that this new kind of transport over USB, Asynchronous one, is much more sensitive for power drops-out, and shortages. And the drivers, or firmware, just cannot handle it. Maybe, when some data over USB, was lost, NFB12.1 just played it like white noice, but NFB11.32 is loosing the synchronisation and software cannot handle it. I would say, it can be easily repaired, when firmware is better coded... it just check, when this happen, and will not crash, but handle it.
Don't know, if this is related to Sabre chip, or firmware, but this device simple cannot stand the power-line drops-out, and it's very sensitive. I would say, in state, how it is now, the external power supply is needed... that will make the power to NFB11.32 stable all the time. But external power supplies are expensive, so there need to be something done.
I've tested this both, under Windows XP and Windows 7, and on both platforms, problem occured, so it's for sure related to NFB11.32 itself and asynchonous USB transfer. (I will test it with coaxial transfer too, and let here know)
There are still other problems, like message in Windows, that this device should work better, with USB2.0 Hi-Speed mode... even when Hi-Speed more is enabled, and NFB11.32 is connected to USB port with Hi-Speed. Does anybody have this problem too? (maybe this is related to chipset drivers - I have P5Q Deluxe motherboard with Intel P45 chipset). I have tried all USB ports I have, but same results.
I will try to update Firmware to No.3.
Edited by Warrax - 11/2/12 at 9:07am