robinv wrote:
You should bear in mind that there are many many happy users out there - the best feedback a manufacturer gets is in sales and returns. Obviously clever marketing and features can get the sales but if the performance was "unworkable" then they would become quickly aware of that you would think.
Horses for courses, we may have a different client demographic.
You look at performance from a bit of a narrow perspective - from your position of scrutinising latencies of 64 samples and such (and you've been doing it for years) i can totally understand your concerns. My experience in the industry is a bit different and i find that most people i encounter are using buffer sizes of 256 or 512 samples very happily - this is where your tests show a bit more of an even level of performance. I know that there are people for whom this is completely unacceptable and unusable but i would suggest that there are many many more for whom it's completely fine and "real-time" etc etc.
My work over the years in regards to focusing on native low latencies performance was due to direct requests and demands from my client base , and the volumes of traffic across multiple forums that I was active on. You may feel its narrow, but again we have a different demographic.
For those not requiring the lower latencies then the interfaces that are being highlighted as performing badly at those latencies are a non event , but I disagree that the majority of clients working latencies are 256/512, anyone who can actually play would not be comfortable using a VI at those latencies, I know I wouldn't. Also current systems with good audio interfaces can easily be set and forgot at those lower latencies and not have to do the buffer juggle if they decided to go back and do an overdub when mixing , for example. Also many composers process while they compose so again the lower latencies are extremely important.
I did my own tests on some interfaces last year when i was looking for a new laptop and i compared an Edirol FA66, Saffire Pro 24 and Presonus Firestudio and there were marked differences between the Firestudio and Saffire so i'm not convinced that they are the same, at least these models weren't.
Its a constantly moving target, Presonus use multiple OEM FW controllers across the range, its why they have different drivers and not one universal one. Also I did have some variance between the 2 on my notebook testing , so there is some wiggle room in how they tweak the drivers perhaps.
You'll note that the only trouble Martin had in his review is when running your low latency tests - any other test that both he and i did before sending it out using what i'd suggest are more common buffer sizes, it performed fine.
Be very grateful he wasn't using DAWbench VI as a reference test, as the "unnamed" interface would have fallen in a heap at the working latencies anyone would use for live playing of VI's , right up to 256 samples. 512 was O.K in the test without convolution verbs, it stalled with, but seriously Mate , 512 samples is purely for mixing only. You can't play a VI comfortably at that level, you can't use a Guitar Amp Sim, you can't play live MIDI drums into a Drum Sampler , etc, etc.
In short it simply negates a huge potential of the advantages we enjoy using these current uber fast systems.
I think comparing audio interfaces like this is a really great idea and will generate a lot of useful data that will help people chose the right interface for them - good on ya mate.
That's the aim.
Not sure you're going to start a revolution but any improvement to driver performance is certainly a good thing
I'll call and raise ya...
The past work has already resulted in better drivers and multiprocessor performance on some DAW hosts , revolution may be too lofty, but this will grow legs , how hairy will be up to the audio hardware developers.
Lets see where the dust settles.
Yes I have my helmet and armour on..
P.S: you still haven't disclosed the interface used in the review, if its such a non event, then it shouldn't be a problem..
Peace
V: