No products in the cart.
Using a new Mac Studio M1, with OS 12.6.1 and Logic Pro X 10.7.4 and its takes up to 5 minutes to load up projects where I have EZbass or SD3, or both.
Normally SD3 and Ezbass are not loaded by default when I open the project, and once I click on the e.g. Ezbass channel it starts loading and I can make a coffee while it takes forever to load. Then the same thing with SD3. What am I missing? Thought my Mac Studio would make things faster and not the opposite
Hi,
this sounds strange indeed. When I create a test Project in Logic with a 6,7GB kit in SD3 and EZbass, it takes a few seconds to load on my M1 Max MacBook Pro.
The interfaces open right away when I click the plugins in the mixer.
Where are your libraries located? Internal or external drive?
Are you running Logic natively or via Rosetta 2?
BR,
John
John Rammelt - Toontrack
Technical Advisor
Hi John
Library is on a local SSD disc and I am not running in Rosetta mode
Worth noting here:
EZbass and SD3 used to be installed on an external slower disc when these projects were created. Since then I have relocated both EZbass and SD3 to the faster SSD drive.
When the projects finally open, I can see they are pointing to the right path but could this be part of the issue?
No,
What happens is that I can start a project from scratch using Logix Pro X, and it works fine to add SD3 or EZbass. But later, when I open up the same project again it takes forever.
I am not sure if this is only these old projects, where upon creation the path to Sd3/EZbass was different, and is now changes to a faster SSD disc. Or if it’s a common problem. I will try creating a few new projects and see if it still happens.
If I move the path to SD3/EZbass and a project was created using the old path, could that create this problem? It’s like logic is searching for something for 5 min every time, going through thousands of files. And eventually it finds what its looking for and opens up project.
No, it shouldn’t be connected to moving sound libraries, since the paths to sounds are stored in the plug-in settings.
I am a bit puzzled by the inconsistent behaviour.
Have you tried opening Logic’s Plug-In Manager before opening your Project and perform a Reset & Rescan on the Toontrack plug-ins?
Perhaps clearing the AU cache, just to have one more thing to have checked off the list, if you need to create a Support Ticket?
To clear the AU cache, please open a new Finder window, click ‘Go’ and press the ‘Option’ key. Now you will see a ‘Library’ entry in the list, click it.
Open the ‘Caches’ folder, followed by the ‘AudioUnitCache’ folder. Delete the files in there and reboot your Mac.
BR,
John
John Rammelt - Toontrack
Technical Advisor
I performed both of your suggestions, and now it loads super fast !
Will test to open and close a bunch of projects back and forth, but looking good so far.
Huge thanks John.
No, it shouldn’t be connected to moving sound libraries, since the paths to sounds are stored in the plug-in settings.
I am a bit puzzled by the inconsistent behaviour.
Have you tried opening Logic’s Plug-In Manager before opening your Project and perform a Reset & Rescan on the Toontrack plug-ins?Perhaps clearing the AU cache, just to have one more thing to have checked off the list, if you need to create a Support Ticket?
To clear the AU cache, please open a new Finder window, click ‘Go’ and press the ‘Option’ key. Now you will see a ‘Library’ entry in the list, click it.
Open the ‘Caches’ folder, followed by the ‘AudioUnitCache’ folder. Delete the files in there and reboot your Mac.BR,
John
I have a similar slow-loading issue in Windows 10/VSTs — is there a similar fixit for that OS? Thanks.
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.