jjLOAKS

That did the trick, thank you! It seems the file is now named: com.apple.logic10.plist

Hi David, bumping this old thread because I am unable to find the file at this location. Is there an updated place Apple Loops Favorites are stored?

Have you had experiences with Logic not being able to properly retrieve a patch setting on an older project file (that has gone through multiple computer migrations, for example), even if the plugin was still available on your current system?

Bumping thread, how does everyone else save patch information?

Nice, does this mean I should throw out my 16 pad drum pad and get a launchpad?

I've had bad experiences in the past with other DAWs where I'd migrate computers, then completely break plugins information and couldn't find out what the original plugin's patch was. Lately I've just been renaming all my library saves as "Plugin - Patch", but I'm hoping there's a better way to do this as this doesn't allow me to simplify the track name to something like "Bass, Pad, Drums" for the mixing process.

How feasible would MainStage for the iPadOS be? Rumors have recently been circulating that Xcode, Final Cut Pro, and Logic Pro will be coming to iPadOS within the next year, and if true logically MainStage would make the most sense in that mix as a performance tool.

Would this allow for multiple instances of the Reason AU preset in Logic? Ex. if I wanted to save an Echo version, Reverb, Chorus, etc.

There are some plugins that require a bit of menu diving to access effects available. Two examples are: Reason Studios effect rack (image below), and Reaktor 6's effect module. Ideally I would like to save an effect setting (ex. Reason Studios w/ "The Echo" plugin enabled) to be recalled under my Audio FX panel when selected. 1. One way I've seen a possible (but not preferable) way of doing this is saving the entire rack with just the effect loaded on into my library, and then using the patch merging feature to only load in the "Audio Effects" portion of the rack. However, this still seems to overwrite the pre-existing track's name and icon, which is not ideal. 2. Another way is to save the settings under the plugin library itself, which would require an additional step after loading in the plugin in the Audio FX module to then access the library and load a selected state. I am hoping to bypass this additional step entirely.

That worked! I would have never thought of doing that, so happy it recalled correctly.. Thank you so much for the help! And yes I'll be contacting the plug-in manufacturer with this info as it does seem to be reporting it wrong.

Good catch, didn't notice that. I tweaked the envelope before saving the patch this time, unfortunately still replicating the same issue. Here's the video: https://streamable.com/72j01a

Sure, please see linked video: https://streamable.com/1h27kb

Saving from the setting pop-up menu in the plug-in header doesn't seem to replicate the problem, thankfully. The plug-in company is FutureAudioWorkshop, the plug-ins this issue is affecting are Circle2 and SubLab (https://futureaudioworkshop.com). I've uploaded a video replicating the issue I'm facing, and also how the setting pop-up menu doesn't cause the same problem: https://streamable.com/pifq69

Thanks for the quick reply. The channel strip is empty aside from the loaded plugin. I just saved these plugins this morning by browsing the plugin's library and saving sounds I liked (with no modifications). Then loading them back in a different project they loaded in like this (still with an empty channel strip/only plugin loaded in). I remember this same issue happening to me in the past on a different laptop running Logic. EDIT: This same issue is not replicating from the same company's plugins in Ableton Live.

I've been recently saving my favorite plugin presets from my 3rd party plugins to my library and whenever I load them to a new track from the library selection window the plugins aren't loaded in correctly. This happens with multiple different company plugins, so it's not isolated to any particular plugin.* I've attached 2 audio examples (one loaded from library after being saved, another being loaded directly from the plugin) to show the differences in what I'm hearing. Plugin loaded from saved library preset (incorrect sound): https://clyp.it/qc4bcrcm Plugin loaded directly (correct sound): https://clyp.it/pm0ygls1 *EDIT: This does seem to be isolated issue to a particular company's plugins.