that could simulate what the performance of brand A,B,C,D,E , etc etc would be in YOUR pc. Meaning you could download the simulation software , run it, and all the sudden know exactly how crash prone its gonna be with SONAR under a load, even more crucially , the latency you're going to get. That alone is such a critical thing to know but you can't until you buy it! ....I know a driver communicates with hardware, but that's where they could do their engineering magic to simulate the hardware. Of course they'd have to have code from all the major makers, not gonna happen probly, but still, how cool would it be to know beforehand which interface is going to work on your system the best beforehand without trial and  error.

I think you are on to something. Analogue gear wasn't perfect, but when it was gone, software companies started to emulate all the flaws and inconsistencies to the minutest detail. I foresee a new era, where musicians won't need to learn music or hone their skills in a traditional manner, but will just draw patterns and loops and get a song produced and mastered automatically. Oh, wait! Isn't this already happening? You are right, it's time to ask for audio interface emulation.

FWIW, There's a lot of information currently available (online) about various audio interfaces.
If you want a "sure thing", go with an audio interface that's a proven top-performer.
 
It's pretty well known that RME (the entire range) are excellent performers across the board.
Lynx is right there with RME.
MOTU is a close second.
 
 

Or buy a Mac  :) 

The problem is not just the driver, there are a lot of factors that can influence stability and latency.
 
On VGuitarForums there is a thread about audio interfaces. It would make sense to do something similar in the top part of this forum so it would be sticky. People could post what interface they are using, if it is stable, what buffer sizes they are using for tracking/mixing and what OS they are using.
 
Just because some one posts that they have an I/F that is stable and low latency doesn't mean that another person with a different system that is unstable won't have problems, but at least you know the drivers are good.

Interface simulator is extremely hard to write. Even digital part of computer is not easy to simulate (check qemu for example, to have an idea how that goes... you can imagine my frustration when after simulating one ARM based device, checking that the simulator works perfectly with original linux kernel/distribution and writing my own Linux disk driver for newer kernel, I have found that real hardware is refusing to cooperate with my driver ).
 
But there are 2 tests which if implemented will almost solve the problem:
1) the tester which investigate which jitter is acceptable for an interface, with particular driver in particular mode. A kind of audio loop based (already existing) latency utility which fill WDM/ASIO/etc. buffers with jitter and put load on the system at the same time (disk + RAM + video). So people which already have the hardware can run it and publish results
2) a virtual audio interface, which measure the jitter coming from the client (DAW)
 
So, taking the result from latency real live tests (exist in the Internet for almost all interfaces), the result from (1) published the same way and the result from (2) measured on your system with your projects, it should be easy to predict what you are going to achieve with different devices.
 
Hypothetic example: let say an interface is know to produce 5ms loop time with 16bit/64 buffer size, but it tolerate less then 1ms jitter with such settings. 10ms with 16bit/128 and tolerance 2ms, and so on. You measure that Sonar with your project produce up to 1.5ms jitter. Then you know you will be unable to run at 5ms with this interface, but will be able to run with 10ms.
 

Cactus Music
Or buy a Mac  :)

Or PC made to run DAW and tested with particular interface (there are many reports in this forum that works).
Finally a PC for $1000 + RME for $1000 will work not worse then Mac for $1800 + "am interface" for $200
 

I was just kidding, Actually because I do build my own and pay attention to what is said both here and on Computer forums,  I have never had issues like many have. My last issues were 10 years ago when I tried to use a Creative Labs Audigy II card - out of sync,  and next an M Audio Fast Track - kept disconnecting.  
I use 4 different computers - Laptops running Sonar and Home Studio right now and all are 100% stable. 
I have 2 Audio interfaces and one system using on board via WASAPI. 
As far as interfaces go, you get what you pay for. 
Rule #1 only buy brands that seem to have the best drivers. 
I see no point in screwing around trying different systems. It seems straight forward to me, Buy a Motu, RME,  or Lynx. ( sorry if I miss another top brand)  Anything else is going to lower the standards which is fine for many as long as your aware of it. Dont buy a $150 interface and a Laptop of unknown construction and complain. 

rsinger
 
 
Just because some one posts that they have an I/F that is stable and low latency doesn't mean that another person with a different system that is unstable won't have problems, but at least you know the drivers are good.

 
Exactly. Tried and true interfaces on someones elses system is meaningless if you have issues on yours.Plus, how cool would it be to see test results for all the parameters that are important in a side by side comparison of all the major makers, in YOUR system. Very cool, I'd say.

Jim Roseberry
FWIW, There's a lot of information currently available (online) about various audio interfaces.
If you want a "sure thing", go with an audio interface that's a proven top-performer.
 
It's pretty well known that RME (the entire range) are excellent performers across the board.
Lynx is right there with RME.
MOTU is a close second.
 
 

That's nice. But what I have found over the years, is that all the accolades in the world for said piece of gear, are all but meaningless once you install it on YOUR pc, with YOUR type of mobo, memory, peripherals, windows setup, etc,etc et.
 
ps- Why didn't you include the Apollo Twin  Mk II desktop ? Any particular reason, or were you just going with stuff that's reported to work well with SONAR? I ask, because I'm am considering it.

rsinger
 
 
Just because some one posts that they have an I/F that is stable and low latency doesn't mean that another person with a different system that is unstable won't have problems

Exactly. At least a test beforehand could literally show you all the parameters that tests of all makers you are considering would reveal on YOUR system.I think it's an awesome idea.