The o'l CPU overload/increase H/W Buffer Size (error AAE-6101)

[xrekcor]

Originally Posted by Sardi

At some point, they made it so that when you launch PT, it creates the factory plugins if you have removed or deleted them.

I don’t know when they implemented this, but it caught me off guard too. Maybe v2018... maybe v12. I don’t recall this being the case in v11.

I’ve been getting some CPU errors that have become repeatable, so I’m trying to figure out if it’s a rogue plugin and was perplexed when I noticed the reinstallation of the stock plugins.

IMHO - it’s not a good thing. There’s probably only a handful of stock plugins I use. If I don’t want the rest there, that should be my choice.


Sent from my iPhone using Tapatalk

It is all your choice now bro.... especially where that particular plug is concerned and any of the others.... I have been deleting it right after PT loads and as long as it was deleted I had no probs but a pain to have to do every start up.

[Sardi]

Originally Posted by xrekcor

It is all your choice now bro.... especially where that particular plug is concerned and any of the others.... I have been deleting it right after PT loads and as long as it was deleted I had no probs but a pain to have to do every start up.

No offence, but what you were doing was not a solution for me. There’s no way in the world I would be doing that after every launch of Pro Tools.

Removing files from the .pkg file is a decent workaround if it works and doesn’t alter anything. It’s always a bit scary doing that. Who know what checks they’ve put in place.


Sent from my iPhone using Tapatalk

[the.engineer]

Forgive the potentially stupid question...

What do you guys use for a click track now you've removed it??

[Emi]

Originally Posted by the.engineer

Forgive the potentially stupid question...

What do you guys use for a click track now you've removed it??

Good questions, you could do your own click track by importing a click sound copy it for a measure and than duplicate that measure for the length you need it.

[the.engineer]

Originally Posted by Emi

Good questions, you could do your own click track by importing a click sound copy it for a measure and than duplicate that measure for the length you need it.

I would sure miss being able to press 7 on the keypad to turn it off!!

[ferrerh]

Create some intrument track (Structure for example), In the transporter double click on the metronome icon, in the output box select Structure and enter the corresponding notes for accented and unaccented, velocity and duration, for greater convenience save as a Track Preset

[xrekcor]

Originally Posted by Sardi

No offence, but what you were doing was not a solution for me. There’s no way in the world I would be doing that after every launch of Pro Tools.

Removing files from the .pkg file is a decent workaround if it works and doesn’t alter anything. It’s always a bit scary doing that. Who know what checks they’ve put in place.


Sent from my iPhone using Tapatalk

Who meantioned removing files from the .pkg? As I mentioned previous I was killing the click plug from the plug-in folder after every start.... and by doing so allowed me to work error free.

As for what was described by ferrerh all your doing is removing a file the .pkg looks at when PT loads. I would say there is a lil macro that runs checks the plug-in folder against the list core plugs it has in it contents package folder named “core plug-ins” and throws a copy in if one is missing. All you are deleting in there is a copy of the click plug itself..... “Clickll.aaxplugin” the very same file you kill in the plugs folder.... it’s cool if you’re uncool with that.... all good mate.

Actually I’m willing to bet you could place any plug in that core plug folder and it will then be a core PT plug on your system.

[xrekcor]

Originally Posted by the.engineer

Forgive the potentially stupid question...

What do you guys use for a click track now you've removed it??

Yeah like ferrerh said create an instrument/midi loop.... and you can use real drum sounds, save as a preset.... and they’ll stretch or shrink with what ever tempo where an audio won’t without sounding crappy.

[Sardi]

Originally Posted by xrekcor

Who meantioned removing files from the .pkg? As I mentioned previous I was killing the click plug from the plug-in folder after every start.... and by doing so allowed me to work error free.

As for what was described by ferrerh all your doing is removing a file the .pkg looks at when PT loads. I would say there is a lil macro that runs checks the plug-in folder against the list core plugs it has in it contents package folder named “core plug-ins” and throws a copy in if one is missing. All you are deleting in there is a copy of the click plug itself..... “Clickll.aaxplugin” the very same file you kill in the plugs folder.... it’s cool if you’re uncool with that.... all good mate.

Actually I’m willing to bet you could place any plug in that core plug folder and it will then be a core PT plug on your system.

I didn’t state you said it. I was merely commenting on the solution you responded to.

I’ve done package modifications before for many years, but not being a coder, I still stand by that we don’t know exactly what may or may not be happening. I’m sure it will be fine, but it’s still a risk.


Sent from my iPhone using Tapatalk

[the.engineer]

Originally Posted by ferrerh

Create some intrument track (Structure for example), In the transporter double click on the metronome icon, in the output box select Structure and enter the corresponding notes for accented and unaccented, velocity and duration, for greater convenience save as a Track Preset

You are a GENIUS


Sent from my iPhone using Tapatalk