icontakt
Hi, this will probably help me more in choosing the right audio interface than the thread I posted earlier. Questions here are very simple.
 
Did any of the audio interfaces you purchased NOT work very well with SONAR? If so, which manufacturer/model was it? Which OS were you on at that time?
 
Thanks

Usually these are not related to a DAW. If one does not work with Sonar it usually wont work with other DAWs.  The only issue I had was with a Terratec EWX2496.  This card was discontinued after XP yet the developers created beta drivers for Vista 64.  They worked with W7.   The only issue I had was Sonar and Reason would not recognize the Terratec's ASIO drivers.  It worked with WDM drivers. 
 
 The only "audio interface" that does not work well is usually onboard sound.

chuckebaby

pwalpwal

chuckebaby
Here is a list of Audio hardware:
http://www.cakewalk.com/Support/Knowledge-Base/2007013101/Open-Audio-Hardware-Guide
 
This might be helpful to just see a bunch of them all in one place.

indeed useful, although some devices are recommended to use mme drivers! (maybe needs updating?)

Well it would be nice if you helped the OP out by listing some ?
or are you here simply for your morning debate ?

listing some what? i've never had an audio interface that didn't work with sonar, plus, being a cheapskate non of my current ancient ones are available to purchase any more
 
and (and!) it's already tea-time here

Side topic advice here. If replacing an audio interface, be sure to get one from a store which has a 30-day return policy so that you get the opportunity to test drive it on your system. Just because something works for others does not mean it will be ideal for you and vice versa.
 
Typically, a model with good ASIO drivers should not have issues. The machine itself can insert some issues due to its setup and how much it is tasked during use. Some VST/is are heavy handed, and no AI will fix this, so low latency when the CPU is already choked won't happen.
 
Again, being able to return it if it doesn't suit you is paramount.

Tale of two interfaces here, well actually the same one. My friend has a Focusrite 18i20 which worked wonders on his system. When it was time to upgrade I got one based on his success. It was nightmare for me, but it turned out to be a bad unit which I had to return. Still waiting for a few days to get a new one, but I will say when it worked, it was awesome. I was able to get down to .7 ms of latency and my system was stable even with big projects.
One word of advice, when in the desktop environment it's really a good idea if using usb to make sure the device is not only on its own ports and not sharing, but that the port is matched with it's own internal hub on the MB. You get great results that way at low latency and slightly less CPU overhead.
 

emwhy
 
One word of advice, when in the desktop environment it's really a good idea if using usb to make sure the device is not only on its own ports and not sharing, but that the port is matched with it's own internal hub on the MB.
 

 
Em,
What's the best way to determine possible port and hub issues and or reassign them?
 
Thx,
Freq

Tricky way is to look in device manager and see what device is on what port/hub. You may have to unplug various devices to do this. Also, when connected to a usb 3.0 port it will be on the xHCI controller as opposed to the eHCI controller for 2.0 devices. It would help if you have a block diagram of your motherboard to see how things are connected.
 
I cheated....went and got an Inantech pcie to usb card strictly for my usb audio stuff. All the usb number crunching is done on the card and passed along the pci buss to the chipset. On some computers and laptops the usb hub is part of the main chipset. This can cause some bandwith issues.
 

I was able to get down to .7 ms of latency and my system was stable even with big projects.
 
I'm sure you meant 7ms, not .7ms.. or your not talking Round trip latency , right?  
 
That's interesting that Cakewalks list of audio interfaces contains a lot of devices I and others would never recommend  and even some pathetic USB mikes, and RME is not even on the list??? What's with that. Pretty pointless list.  It tells you some basic specs and importantly ASIO support, but then that said it shows Creative as having asio drivers ( har har) 
 

It was in fact .7 but you're correct that it was not the round trip latency. Also had to have nothing running in the background. I will go on record as highly recommending Focusrite as soon as my replacement arrives. mentioned up thread that I had one that was defective. 
 
 
 
 

chuckebaby
Here is a list of Audio hardware:
http://www.cakewalk.com/S...n-Audio-Hardware-Guide

This might be helpful to just see a bunch of them all in one place.

 
I didn't know such a list existed on the CW site. The list actually helped me easily identify which model (i.e. 2 audio inputs+MIDI posts) I should check out on the manufactuer's site. 

MacFurse
M-audio FTP, then M-audio mobile pre, then Mackie Onyx Black Jack.
~~~
Then I changed to a Focusrite Scarlett 2i2 to trial first, then to my current 18i20. They started on 8.1, then moved onto win 10. Both have been rock solid, though occasionally I have to delete and re-install the driver for 18i20, always after a win update.

emwhy
Tale of two interfaces here, well actually the same one. My friend has a Focusrite 18i20 which worked wonders on his system. When it was time to upgrade I got one based on his success. It was nightmare for me, but it turned out to be a bad unit which I had to return.

 
Thanks for the info, and for sharing your experience with the Scarlett interfaces.