ASIO problems with Logic 5.5 and Scope 4.5

pacificband · Post by **pacificband** » Fri Oct 27, 2006 11:34 pm

I had to reinstall eveything and when started up again I took a war for me to open Logic. I can see that it is the ASIO contact that takes time.
What kind of ASIO driver is the best in SCope 4.5,?
-righ now I am using: ASIO1 24 bit , in my set up.
regards Claus

valis · Post by **valis** » Sat Oct 28, 2006 4:00 am

The audio engine in Logic is directly bound to the audio driver you're using, in this case the ASIO driver. This means that scanning all of your plugins occurs under the ASIO driver initialization process. At first you'll see it just load the driver, then it will scan all of your plugins. This takes some time if you have a lot, especially the very first time you scan your plugins or if you've recently installed several it can also potentially take a bit.

You can disable directx plugins (especially those that might be problematic) by running PlgEnabler2a.exe from within your logic dir, or from the emagic>tools start menu folder.

ASIO1 or ASIO2 24bit drivers are both fine, asio2 adds the ability to send sync to external sources (and a few internal optimizations that aren't critical). If you have a large number of inputs &/or outputs defines for your scope drivers this might also slow the initialization down.

All of the above is normal for any of the soundcards I have here, Scope takes no longer than my RME or my other firewire interfaces.

pacificband · Post by **pacificband** » Sat Oct 28, 2006 4:17 am

Thank you very much I appreciate you answer.
- and then I must wait these 5 - 10 min. it takes, still I think it´s a long time. Longer than I ever have had to wait? Maybe it´s another thing I have to find out?
Cheers, Claus

miguel · Post by **miguel** » Sat Oct 28, 2006 6:29 am

maybe a midi loop? midi feedback will eat your cpu and make everything crawl.

In the file C:\WINDOWS\win.ini logic stores what midi ports are available. By default it sends sync data through all outs and listens to sync on the inputs too. That's bad if you've got an output wired (by cable or through software) to an input and logic opens both.

valis · Post by **valis** » Sat Oct 28, 2006 1:51 pm

5-10 mins is definately excessive, lol. Sorry I didn't realize it was THAT long. I think you should do some basic troubleshooting. First & foremost insure that you have ONLY the ASIO driver selected in Logic (audio driver page 2) and also insure it's using the Scope ASIO driver. Check your asio settings (24bit checked, only a reasonable number of audio tracks & ASIO channels, etc).

I would also move your vstplugins directory temporarily so that Logic can't find it (this will remove plugins from the initialization process) and see if this changes things. If it does and restoring the vstplugins dir brings back the long load times, then you have to figure out what plugins causes the issues.

If it turns out to NOT be plugin related & you're using the correct ASIO driver etc, and the midi ports (as in the above post) are all correct, then I would begin to suspect possible harddrive issues, perhaps a thermal issue during load (causing the cpu to slow down) or perhaps other issues. I doubt it's Scope related, as once the Scope project is loaded there should be no reason that it affects Logic's load times at all.

pacificband · Post by **pacificband** » Tue Oct 31, 2006 10:21 pm

valis wrote:5-10 mins is definately excessive, lol. Sorry I didn't realize it was THAT long. I think you should do some basic troubleshooting. First & foremost insure that you have ONLY the ASIO driver selected in Logic (audio driver page 2) and also insure it's using the Scope ASIO driver. Check your asio settings (24bit checked, only a reasonable number of audio tracks & ASIO channels, etc).

I would also move your vstplugins directory temporarily so that Logic can't find it (this will remove plugins from the initialization process) and see if this changes things. If it does and restoring the vstplugins dir brings back the long load times, then you have to figure out what plugins causes the issues.

If it turns out to NOT be plugin related & you're using the correct ASIO driver etc, and the midi ports (as in the above post) are all correct, then I would begin to suspect possible harddrive issues, perhaps a thermal issue during load (causing the cpu to slow down) or perhaps other issues. I doubt it's Scope related, as once the Scope project is loaded there should be no reason that it affects Logic's load times at all.

As soon as I am back in my own studio, I will try some of theese things you told me. I had to go to another studio, for working more safe and not waisting time.
Thank you for what you send to me I apreciate your help. I will send a message, when I have something to tell.

Cheers Claus