Absurd plugin loading time in Protools 11

jeam25

Member
Hi my system is taking too much time loading a session with UAD plugins OR in the session loading the first UA plugin ..is taking like a minute or more ...is a crazy thing.. Ive formated my PC so is a new installation and installed 8.3 version of UA ..what is wrong ? Does it have to do with the UA control panel settings ?? ..by default i have checked mark on Enable CPU Optimization , Dsp lock and Extra Bufrering ,Limit dsp is set tp 100% andUad bandwith is on 85%.

Thanks ..
 

Uadsat2

New Member
Yep had that problem since forever and UAD never address it. Open the first instance of a plugin you'll sit there twiddling your thumbs waiting for the darn plugin in to load. Open the second plugin loads immediately . Switch on my PC start pro tools is quicker than waiting for a UAD plugin to open. Dear UAD not everyone has time to waste ,waiting for one of your plugins to grace us with its presence.Zzzzzzzzz huh has it loaded yet
 

DanButsu

Administrator
Forum Admin
Moderator
Has always loaded normally for me in PT10&11. Just sayin'

It's not fun to hear and please don't take it the wrong way; but you might have to check your system "cleanliness". See what's running g in the background, calling home et al.
 

jeam25

Member
Has always loaded normally for me in PT10&11. Just sayin'

It's not fun to hear and please don't take it the wrong way; but you might have to check your system "cleanliness". See what's running g in the background, calling home et al.
No problem at all thats what im here ..trying to find what is causing it . I have to mention that in Protools 10 the loading time is fine like always the problem is with PT11 . Yes i have my background process clean with just only the must services for PT and UAD . As i can see here with other users too im not alone with this issue :) . Not shure but apparently is Windows bug related !? All the people here that have fast loading times are o mac os ?
 

yluko

Active Member
I keep a fairly clean and high powered custom built PC. I have this issue but not as extreme. I would say like about 10 seconds for the first. Just something I got used to. It does something for sure when first instancing the uad. As for loading a session, I have noticed that as well. I wasn't sure if it was uad plugins or not as they are in every track I use pretty much but it takes a minute or two at least to load full sessions.
 

jeam25

Member
I keep a fairly clean and high powered custom built PC. I have this issue but not as extreme. I would say like about 10 seconds for the first. Just something I got used to. It does something for sure when first instancing the uad. As for loading a session, I have noticed that as well. I wasn't sure if it was uad plugins or not as they are in every track I use pretty much but it takes a minute or two at least to load full sessions.
Hi ..thats correct i noticed the most loading time when they are in the master fader but is just a little more time not a dig difference in my case ...

Thanks
 

UniversalAudio

Official UA Representative
Hi ..thats correct i noticed the most loading time when they are in the master fader but is just a little more time not a dig difference in my case ...

Thanks
Hi Jeam25,

I've been trying to remember what we did to correct this in some systems - it's a matter of fixing the caches. Anyway, here is a set of steps to get rid of the bad prefs and start again. Give it a shot and let us know if it solves it for you.
___________________

1. Uninstall UAD software: Uninstall & Firmware (Windows 7) (make sure to manually delete device drivers from Device Manager)

2. Trash Pro Tools prefs: How do I trash my Pro Tools preferences? | SweetCare

3. Reinstall UAD software

4. Perform win 7 aax initialization procedure:

Initializing AAX 64 for Windows 7

Important: To use Pro Tools 11 or Pro Tools 12 with UAD AAX 64 plug-ins under Windows 7 and UAD v8 software, the following steps are required. The procedure must be performed each time an updated version of UAD software is installed (once for UAD v8.0.0, once for future UAD releases, etc):

1. Install the UAD v8.0.0 software software. Be sure to restart the computer after installation.
2. Open the Pro Tools application. The UAD AAX 64 plug-ins are automatically scanned during launch.
3. Click "No" when Pro Tools displays a message indicating some UAD AAX plug-ins failed to load. This message can be safely dismissed.
4. After all plug-in scans are complete, QUIT Pro Tools. The UAD AAX 64 plug-ins are now properly initialized and ready for use the next time Pro Tools is opened.

If Pro Tools is not quit after the initial plug-in scan, Pro Tools AAE error -14018 and/or other anomalies may occur.
______________________

Hope this helps!

-GK
Gannon Kashiwa
 

DanButsu

Administrator
Forum Admin
Moderator
Thanks Gannon. I'm going to sticky this post. Thanks for sharing! Cheers
 

jeam25

Member
Hi Jeam25,

I've been trying to remember what we did to correct this in some systems - it's a matter of fixing the caches. Anyway, here is a set of steps to get rid of the bad prefs and start again. Give it a shot and let us know if it solves it for you.
___________________

1. Uninstall UAD software: Uninstall & Firmware (Windows 7) (make sure to manually delete device drivers from Device Manager)

2. Trash Pro Tools prefs: How do I trash my Pro Tools preferences? | SweetCare

3. Reinstall UAD software

4. Perform win 7 aax initialization procedure:

Initializing AAX 64 for Windows 7

Important: To use Pro Tools 11 or Pro Tools 12 with UAD AAX 64 plug-ins under Windows 7 and UAD v8 software, the following steps are required. The procedure must be performed each time an updated version of UAD software is installed (once for UAD v8.0.0, once for future UAD releases, etc):

1. Install the UAD v8.0.0 software software. Be sure to restart the computer after installation.
2. Open the Pro Tools application. The UAD AAX 64 plug-ins are automatically scanned during launch.
3. Click "No" when Pro Tools displays a message indicating some UAD AAX plug-ins failed to load. This message can be safely dismissed.
4. After all plug-in scans are complete, QUIT Pro Tools. The UAD AAX 64 plug-ins are now properly initialized and ready for use the next time Pro Tools is opened.

If Pro Tools is not quit after the initial plug-in scan, Pro Tools AAE error -14018 and/or other anomalies may occur.
______________________

Hope this helps!

-GK
Gannon Kashiwa
Oh thanks im gonna try and let you know :) !
 

jeam25

Member
Umm another question my satellite quad had never asked for a firmware upgrade :-/ is that ok ?! i have it and use it since v7.0
 

jeam25

Member
Umm another question my satellite quad had never asked for a firmware upgrade :-/ is that ok ?! i have it and use it since v7.0
OK I HAVE AN UPDATE !!

I found that the problem is the UAD plugins .!! Let me explain .. I cannot make the first PT launch because an error that im receiving in PT during thet first UAD launch into PT . I tought that error was PT 11 or another plugin but after proper troubleshotting i saw that the problem was caused by the UA pluguins itself .
The error make me close hard trough Task manager during that first launch so I was everytime jumping that step . AND I can not resolve it :-/ ! Beucase I don't know what is causing it within the UAD plugins !

This what it says :

Microsoft visual C++ Runtime Library
Runtime error !
C:\ ProgramFiles \ Avid \Protools \ Protools.exe
- R6016 - not enough space for thread data



Attached is the error screenshot .

Thanks again !
 

Attachments

Last edited:

Kcatthedog

Hall of Fame Member
ah you do know that Gannon is not providing formal customer service support here; right ?

I don't understand why you think this is ua problem as the script is referencing a pro tools problem ?
 

UniversalAudio

Official UA Representative
ah you do know that Gannon is not providing formal customer service support here; right ?

I don't understand why you think this is ua problem as the script is referencing a pro tools problem ?
Thanks, Kcatt -

Jeam25, sorry for the lapse in communication!

From the looks of the error message and the fact that you can run plug-ins in the console without issue leads me to believe that it's an issue with Pro Tools. As Kcatt suggests, this isn't a formal customer support channel and you will get a faster resolution by contacting UA Customer Support directly.

I did a little poking around and there are quite a few threads on R6106 errors, so you might a few of them out, there appear to be some patches and solutions on the Windows side.

How to fix runtime error R6016 on windows 8 - Fix PC Errors
https://support.microsoft.com/en-us/kb/126709
http://www.justanswer.com/computer/5ioi0-i-m-using-windows-64bit-days-ago-internet-explorer.html
Runtime Error R6016 Not enough space for thread data-Pro Tools 8- - MajorGeeks Support Forums

In the meantime, call Customer Support and get a ticket going - that's going to be the best way to resolve your issues.

Cheers!

-GK
Gannon Kashiwa
 

jeam25

Member
Thanks, Kcatt -

Jeam25, sorry for the lapse in communication!

From the looks of the error message and the fact that you can run plug-ins in the console without issue leads me to believe that it's an issue with Pro Tools. As Kcatt suggests, this isn't a formal customer support channel and you will get a faster resolution by contacting UA Customer Support directly.

I did a little poking around and there are quite a few threads on R6106 errors, so you might a few of them out, there appear to be some patches and solutions on the Windows side.

How to fix runtime error R6016 on windows 8 - Fix PC Errors
https://support.microsoft.com/en-us/kb/126709
http://www.justanswer.com/computer/5ioi0-i-m-using-windows-64bit-days-ago-internet-explorer.html
Runtime Error R6016 Not enough space for thread data-Pro Tools 8- - MajorGeeks Support Forums

In the meantime, call Customer Support and get a ticket going - that's going to be the best way to resolve your issues.

Cheers!

-GK
Gannon Kashiwa
Sorry i didnt knew ..i think that you chime in more frequently as a moderator or simething like that :-(..

im gonna make contact with CS thanks again !!
 

UniversalAudio

Official UA Representative
Sorry i didnt knew ..i think that you chime in more frequently as a moderator or simething like that :-(..

im gonna make contact with CS thanks again !!
No worries - I do my best to help people out here, but sometimes the issues require deeper troubleshooting and the public forums aren't really suited for that kind of problem solving.

Check out the links I posted earlier - there is a lot of information about runtime errors that might be helpful to you.

Good luck and let us know how it gets resolved!

-GK
Gannon Kashiwa
 

shopson1984

New Member
Hi everyone,

New to the forum as well as UAD. Just wanted to send a quick note and say that I am having this exact same problem. I'm running PT 10/12 and an Apollo Quad through FW on a Windows 10 system (I know W10 isn't supported, but this doesn't apear to be strictly W10 based on other's experiences). I've tried Gannon's suggestion earlier in the post, as well as optimizing my system for PT and UAD. The plugins load perfectly fine in the Console. Once I let a single plugin load in PT (which takes about 3-4 minutes!) then I can load as many plugins as DSP will allow. It seems to be some process that initializes during the first DAW plugin load, because it also takes a while to unload the last UA plugin in PT. Did anyone ever find a solution to this problem? I just got this Apollo, and while it seems great, I am none too pleased with the absurd load times for plugins. Any help would be greatly appreciated. Thanks!
 
UAD Bundle Month
Top