Minutes of extra Logic launch time for even a few Melda plugs

[Annabanna]

m1 mac mini
Monterey
Logic 10.7.4
Melda 15.1

Got a new m1 mini this week, and it's been smooth sailing getting most items up and running (at least with Rosetta), but Melda gave quite a few issues trying to validate plugins. I finally just yanked all the ones I don't use regularly and was able to validate my 10 or so go-to's, but the launch time (every time even though they're already validated) goes from seconds without them to minutes with them. As soon as I remove them from the components folder, Logic goes right back to launching in seconds with well close to 100 plugins from other devs validated.

I've only been trying WITH Rosetta since I still have several plugs that aren't m1 compatible.

While it's in limbo during launch, it says: "Updating information about Audio Unig plug-ins."

FCPX launch times have gone through the roof too since it also forces AU validation as well. Between those two, it's become a big enough cumulative PITA that I've stopped using melda entirely until I can find a fix.

Has anyone else found that Melda drags out their Logic launch times 1000x? Is it an m1 thing? A Monterey thing? Something that I can address in some way?

[al808]

Hi Annabanna,

I'm on a mac mini M1 with Big Sur. The set up is workable, but I wouldn't call it ultra stable, nevertheless I don't suffer from the issues you describe. If I were in your position I would start with the standard Logic trouble-shooting procedures, like deleting the Logic and AU preferences files and what not. If you haven't done this before, do a google search and/or checkout the Logicprohelp.com and the Logic apple forums. I haven't been following closely the user feedback for Monterey, but haven't noticed any major horror stories. I'd also see if the beta Melda 16 works any better, and try Logic in native mode (non rosetta).If it's a Monterey issue, you can try booting from an external hd running Big Sur .Let us know if you need more help, and good luck.

Cheers Al.

[Annabanna]

Hi Annabanna,
If I were in your position I would start with the standard Logic trouble-shooting procedures, like deleting the Logic and AU preferences files and what not.

AFAIK, I've done those steps. I've deleted prefs file so Logic resets, rescanned plugs in Plugin Manager, etc. I have not yet tried to start in native mode (though I will need to run in Rosetta anyway for other plugs). I can try that tomorrow.

Alternate boot would take a bit more time to work out since I don't have an alternate os drive handy. I suppose I could give the beta a try too if it comes to it, though I'm still setting up drives and not set up yet for backup / reversioning if it's worse. If anyone has anything else I can try, I'll knock out all suggestions when I get in front of that machine again in the morning.

[Annabanna]

Haven't tried beta yeat, and working on backup drive so I can roll back if that just causes more problems. Will try alternate boot next once I get it all set up.

I have been able to try a few things though that might shed some light. If I have even a single Melda plug (I used mAnalyzer), the launch time is still 50x what it is without that plug. Each successive plug just makes it take longer and longer until even 10 or so plugs is several minutes of waiting every time I launch.

Once finally open, Logic works fine.

That's using Rosetta, mind you. I was also able to try launching without Rosetta. Same wait times, but without Rosetta, launching any Melda plug crashes Logic.

[MeldaProduction]

THat's all quite odd. The thing is, I'm also using Rosetta here for testing, and everything seems just fine. Without it, it's almost instant. Perhaps try sending a simple project (without any audio and other plugins).