FastBikerBoy



Not to mention the 'expensive' interface you've just bought, only to find out that the drivers are crap..............

Sadly the first thing anyone should do before buying an interface, expensive or not, is check forums like this or the manufacturer's forums, to see what others say about the product especially the drivers.

Unfortunately that's STOP these days.

Of course exceptions exist like when Microsoft introduces new operating systems.
Your great $400 interface that worked great with the current OS, Windows XP could easily be turned into a boat anchor when you move to Windows 7 x64.

For some reason ASIO4ALL really does help laptops if you are trying to use the Laptop's own internal sound.  If I use one of my external audio devices I don't use ASIO4ALL.

wormser

FastBikerBoy



Not to mention the 'expensive' interface you've just bought, only to find out that the drivers are crap..............

Sadly the first thing anyone should do before buying an interface, expensive or not, is check forums like this or the manufacturer's forums, to see what others say about the product especially the drivers.

..........and get so many different opinions you end up more confused than when you started. Unfortunately for me I had a set up that wasn't as good as some but I was also running two interfaces which was another reason for running ASIO4ALL. I did get it very stable with that and when I jumped to Windows 7 x64 the drivers were much improved.

Just dismissing ASIO4ALL is a mistake. It can be a great way to get a stable set up.

I agree with the "sometimes looking for info on the forums can have you more confused than when you started". So with that in mind let take this thread summarize:
 
ASIO4 all is a "good" thing if:
1. If you wish to use your laptop for some editing while away from your main DAW.
2.You are tring to combine 2 different interfaces and wish to use ASIO.
3. The drivers that came with your interface were not updated to Vista or W7.
ASIO4all is "not" a good thing if:
1. Your interface came with the correct drivers but you are having audio problems so you tried ASIO4all  to make things better.

Man, you shouldn't need to use ASIO4All with a RME audio interface! Users here who use RME products attest that RME has excellent support with updated ASIO driver releases which makes RME audio interfaces capable of stable low latency performance.   You probably need to ask some questions here, so you can get your RME product working as well as other RME product users here.

thomasabarnes

Well, my RME HDSP 9652

 
Man, you shouldn't need to use ASIO4All with a RME audio interface! Users here who use RME products attest that RME has excellent support with updated ASIO driver releases which makes RME audio interfaces capable of stable low latency performance.
 
You probably need to ask some questions here, so you can get your RME product working as well as other RME product users here.

Hi Thomas,

I was only trying to get both RME and Yamaha units working at the same time, and as you know, one can only use one ASIO device inside Sonar at any given time. :O)

wormser

Maybe I'm different, but for me I check out the interface I'm considering, ESPECIALLY the drivers.

A quick look on the manufacturer's website, or forums like this are all it takes...
...
I'm referring specifically to the people for which it doesn't give good performance and then who come here and other places and complain about it.

Yes, you ARE different! If it annoys you that people "come hear and complain", how will your "quick look on forums like this" bear any fruit if people DON'T come here and complain?
 
Anyway, I'm not here to troll; I tried it out this weekend and the results were unexpected!
 
I uninstalled ASIO4All and just ran on WDM. I then experienced playback dropouts on projects that had grown large whilst using ASIO4All. I reinstalled ASIO4All and the dropouts cleared.
 
So I have reinstalled ASIO4All and everything works again.
 
Clearly ASIO4All is not just simply a wrapper. There is something going on under the hood, goodness only knows what.
 
Well, I think I'm going to stop fiddling around now. I have two bands that want an album recorded by late January. I have a working rig, so I'm going to leave as is and just get to work.
 
Once again, thanks very much to all for the excellent info and help!

By the way, ASIO4All picks up all WDM devices in its window and you can then record using multiple interfaces in Sonar.

...theoretically, that is.

I tried two interfaces at once (Edirol UA-25EX and Tascam US-1641) and had time shifts between the tracks created by the two devices.

I suppose it would be possible just to cut the time shifts manually. But I don't know what happens over longer recordings when the clocks in the two devices drift apart. Flanging effect?

H'm. Maybe I SHALL fiddle again. If this produces reasonable results over a 3-minute pop song, it would be a cheap way of getting even a greater number of live tracks.

You need to run the two interfaces from the same clock so if possible slave one of the other usually via something like ADAT. Having said that when I was using 2 interfaces running them clocked together via ADAT made my system very unstable.

As soon as I unplugged the digital link it all worked perfectly, including in time even though theoretically that wasn't possible. I must just have been lucky I guess......

Ah. Quick reply! My interfaces do not have ADAT, so I guess that's that.
 
OK, thanks!

wormser


Of course exceptions exist like when Microsoft introduces new operating systems.
Your great $400 interface that worked great with the current OS, Windows XP could easily be turned into a boat anchor when you move to Windows 7 x64.

Wait till more motherboards start using usb3. I've been reading some sound modules do not play well with it.