Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

5 points

Older Sessions Not Loading Plug-ins

Since installing Logic Pro X, when attempting to open a session created in Logic Pro 9 I now get this pop up window and my instruments don't load. They all have the ⚠ on them. But i can go thru the sub menu's and re-insert the same exact plug-in on the channel, but it will not load the preset/patch that it should. Its either blank, or the first "default" patch like your inserting a new instance. I did not move any folders, all my plug-ins are installed correctly, because as I said I can re-add them just fine. Any ideas?? I'd hate to think that GBs of previous sessions and projects are totally gone and a waste. PLEASE don't tell me that...

My software is up to date, everything worked fine before I installed the new version of Logic….

Posted on Jun 28, 2014 10:18 PM

23 replies

Jul 12, 2014 12:14 PM in response to Mr609

Bingo...

That's the problem.. Its Automap.... I've seen this before...(which is why i added it to my last post..) and the only true solution was to unwrap them... and stop using that software... or at the very least unwrap and then update Automap to the latest version and try again but so many people report issues with Automap that frankly, I think it's a waste of time to try and use it once you start getting such problems..

I'd certainly try updating Automap first but again, I'd recommend not using it at all...... as it is often that cause of many different issues under various different DAWs... though I do understand thats why you bought Novation gear in the first place.

Mr609 Author

Level 1

5 points

Jul 12, 2014 7:26 PM in response to The Art Of Sound

man thats crazy...

so i've unwrapped them and loaded the session, still saying they're missing which would make sense in this case as they were ACTUALLY missing since i un-wrapped them and rescanned my AU library.

were u able to have ur settings/presets load in the non-automap version of the plugin once you crossed back over??

Jul 12, 2014 7:40 PM in response to Mr609

No.. because the names of the plugins have changed... when you unwrapped them and so Logic cannot find them...

As I said, you can try updating Automap to the latest version and then re-wrapping the plugins..and see how that goes... but frankly, I think it's a mistake to use Automap at all given the issues it can cause. However, not using Automap and unwrapping the plugins... means you will have to reload manually each of the plugins you used in older projects that you used Automap with.. as Logic (nor any other DAW for that matter as its not a Logic issue) won't be able to locate them... because their names will have changed.

Note: New projects after unwrapping... wont be affected....

Oh.. and in case the thought crosses your mind.. I believe you cannot simply rename the 'Unwrapped' plugins yourself back to their 'Wrapped' names...... There is more to it than simply the file's name change I gather... as others tried this and again, it created more problems than it ever resolved.

Sorry... I know this isn't what you wanted to hear.... but all i can suggest is, if updating Automap and rewrapping the plugins doesnt help.. then stop using it altogether.. bite the bullet and go through your older projects manually reloading the plugins and presets yourself. At least that way you wont have the problem possibly reoccurring in the future...

xfggfx

Level 2

217 points

Jul 12, 2014 9:58 PM in response to Mr609

Just worth a quick look ...check you preferences > audio...is core audio still enabled (ticked)...?

I had a similar problem to this recently.

geoff

Mr609 Author

Level 1

5 points

Jul 13, 2014 7:14 PM in response to xfggfx

yes core audio is still enabled…but thanks

Mr609 Author

Level 1

5 points

Jul 15, 2014 1:34 PM in response to Mr609

So i finally fixed the problem, and actually it was Automap themselves who finally reached back out to me with the answer.

so apparently, that box bottom right that says "Use Logic 9 64-bit friendly AudioUnits" was checked and needed to be UN-checked…smh

hey, whatever allows me to re-open all my previous sessions. I'm currently verifying in logic pro X now, since the older sessions wouldnt even open in that either. I'll confirm in the next few minutes...

I've also attached the reply email from Automap...

"...

It sounds like you having issues with having your older wrapped plugins being recognized by Logic Pro. There was a issue when Logic Pro began being offered as 64-bit, which caused the DAW to scan plugins every time it was loaded. To adjust to this we did an update to Automap which would prevent users from having to do this.

In order to have your older plugins load in older sessions you will need to uncheck the "Use Logic 9 64-bit friendly Audio Units" box which can be found here:

Automap > Preferences > (Bottom right corner of Preference box)

After doing this, restart Logic Pro.

Were you successful in loading your Automap plugins in your older sessions?

Also please note that, for newer sessions you want to check the "Use Logic 9 64-bit friendly Audio Units" to make sure that you don't experience the plugin scan as I previously stated.

Please let us know if you need any further assistance, we will be happy to help further.

Best Regards,

David Joyner // Novation Technical Support"

Jul 15, 2014 1:53 PM in response to Mr609

Im glad Novation helped you sort this out....

But, take note and be very careful before you update Logic (or any other DAW/OS X System/component) again as these kinds of incompatibility issues are well known after doing so, when a company like Novation uses a method of 'wrapping' the plugins to provide compatibility/functionality with their own hardware.. as often such methods 'break' after updates and then you can be stuck for a lengthy period of time waiting on the company to update or provide a workaround for their own 'wrapping' software before you can use your DAW and older projects once more...

This is the reason i avoid hardware that uses such programming 'tricks' to provide such functionality with their hardware...because these kind of annoying issues happens all too frequently I've found...

However, this is just a personal opinion and so, it should be taken as such 🙂

Cheers..

Nigel

Mr609 Author

Level 1

5 points

Jul 15, 2014 2:16 PM in response to The Art Of Sound

I can confirm it also works in Logic Pro X after rescanning…im just happy its working.

You are right about wathcing out for future updates. One of the reasons Im still on 10.8 and not 10.9 because of my Pro Tools software….

Thanks again for all the help and to all those that took the time to help, i truly appreciate it.

Older Sessions Not Loading Plug-ins