I had a few, and those I also had them send units to had a few. We were aware of the first batch problems (doesnt mean 100% that the replacements we all got still werent first batch). Which is another issue, Presonus' QC, which I doubt you or anyone else will deny, is quite shady. We gave this an epic going thru, with a huge variety of test systems. If it could have gotten stable, then the 64 msec latency would have been acceptable.
I'm not kidding when I say I secured some driver writers for this thing but was denied. You can hopefully guess the names on that list were none too shabby
But back to the latency. Jim Roseberry just confirmed, theres no way those numbers could be correct and the original ones I posted are what he sees as well. I think some of the signal is going thru the DSP mixer. That happens, it also makes it hard to accurately measure the maudio stuff
Now Im not saying you are wrong, just that its tricky to get it right when theres a DSP mixer in the loop. I still cant get an accurate line6 driver measurment because of this issue even when I turn off the tone direct thing
One thing he did say though, was that Focusrite is now letting you change the size of the "safety" buffer. Let me quote his post
"Those figures aren't even possible with the best PCIe hardware. ;-)
The ASIO input/output buffers alone will account for 2.9ms.
What about the A/D D/A converters... and the infamous hidden safety buffer? No matter how small... they're still present.
Presonus needs to do what Focusrite is doing on their new drivers... which is allowing you to tweak the size of the safety buffer. I believe they're calling it the "Firewire Buffer".
Your figures jibe exactly with what I've measured"
So its worth a try probably of running the focusrite drivers.
The only time we got our Firestudio close to stable was when I ran
the Alesis IO26 drivers on it...not sure if any damage could happen though