I have saved patch files for all of my third party libraries. In my template. I use patch merging to load instruments into pre-existing 'empty' tracks that have the template's routing, FX inserts, and group settings pre-made. With this workflow, I don't face the issue of templates with hundreds of loaded tracks, saving me from large file sizes, navigation time, and clutter when many tracks go unused.
The patch-merging needs to be enabled because, without it, loading a patch will at a minimum replace all of a track's plugins, group settings, and sends, which I need retained.
As mentioned, Logic Pro 10.5.1 followed this desired behavior (where the patch merging toggle remains active for the duration of the project work). This was changed in subsequent versions of the program, for reasons unbeknownst to me as it now makes working in any newer version of Logic more tedious.
Hope that helps and please let me know if you have other questions.
It would be remiss of me not to ask whether you've tried loading your full templates with all instruments pre-loaded in these more recent versions of Logic Pro.
This is separate to the issue that is bringing me here though; My aim is to keep a minimalist template and add needed tracks only while writing. Even adding deactivated tracks to a template will boost project file size, as well as navigation burden without a 'search track' function.
'Instrument' patch merging is the most efficient approach I've found to accomplish this in my scenario. As mentioned above, there are complications when loading the entire patch, hence merging the instrument only.
Unless an alternative is discovered, my goal is to find a way to make the patch merging window in newer versions of Logic remain constantly active, as it did in Logic 10.5.1.
In that case, I suggest you have a look at PlugSearch, which now has a Track Search function and is an essential purchase for Logic users, in my opinion.
Thank you but again this isn't going to solve all my issues (project file sizes, unused track clutter while working, etc). I do have PlugSearch and I agree it is useful but I am still looking for a solution to keep the Enable Patch Merging window open. Would this be possible?
P.S -- in the latest version of PlugSearch I do not see a "Track Search" function, could you specify how you got this? Regardless, I have used other 3rd party tricks for this and while handy, it again sadly is not the all-out fix I am looking for here.
Perhaps I'm not following you, but PlugSearch will load an instrument for you very quickly. Isn't that what you're trying to achieve with Patch Merging? In terms of programmatic preset recall, this can easily be done via the plugin's UI menu after the plugin has been inserted.
Opening it is obviously possible, but keeping it open isn't as straight-forward. How would you trigger it? I'm averse to constant polling for image or UI Element states, but it seems like the only feasible option, unless you consistently use the up and down arrows for track selection. That could be an option.
Ah. I'm a beta tester so I've had it for quite a while, but it's possible that he's yet to make that feature publicly available. I know v4 is in the works, and it will be part of that.
As far as I can tell, your best bet is to manually turn on Patch Merging by doing something like this whenever you change tracks (which causes the Library to lose focus):
Somewhat but there is the added step that you just mentioned -- having to recall the preset from within the instrument. Many extra clicks, and problematic if you have multiple instrument types across various VSTs; if you want your Violins, you actually can't think 'Violins' in PlugSearch, but you HAVE to think, 'Kontakt 5 or Kontakt 6 or Spitfire App or PLAY?" etc. Using patches means you can save all your violins from all your players into the same folder, which is really great! And with "Enable Patch Merging" active, you can just slip the instrument right onto the track without it impacting plugins, sends, group settings, etc.!
Oh how exciting! How did you get on the beta?
Yeah... this is one of the many I've tried as well, been through and dumped, as the "manual" need to do this each time is just too time consuming or something I'll forget to do, since it was so sigh automatic in Logic 10.5.1. I cannot think of the argument for why they changed this, but maybe there is/was a good reason.
I've alternatively tried macros that quickly click onto the library window's "search" bar and run the custom key commandâthis both activates patch merging AND activates the search field, which is rather nifty. Again though, this requires a manual trigger.
I was mostly curious if you had any insight on the apple script side (something I am far less versed in), specifically something that can at least trigger the UI elements in a cleaner way without having to click around or press tab, etc. But I understand if this is also too tricky.
Any speedy way to load in an instrument preset (from any VST/player) and have the track be renamed accordingly would be awesome. Patches with "enable patch merging" was simply my best workaround.
I don't remember exactly, but it was the result of an initial conversation with Rinus (the dev) about some suggestions/bug fixes a few years back.
I tried this, but had no luck I'm afraid.
activate application "Logic Pro X"
tell application "System Events"
tell process "Logic Pro"
set tracks_window to title of first window whose title contains "- Tracks"
click text field 1 of group 2 of splitter group 1 of group 1 of group 1 of group 3 of window tracks_window
end tell
end tell
Now that I understand your goal a bit better, I think it probably still is. Sorry I can't be of much further help here; I think some manual triggering is going to be hard to avoid.
Hi, I have SD with KM and plug search - great combo. However, I can't work out how to Load, say Kontakt with a specific library/patch. Or Omnisphere with say, the Hollywood strings patch. Is this possible? TIA
For this, I would suggest having a look at the Strip Search macros near the top of the thread. You can save Kontakt/Omnisphere/whatever with the desired patch loaded as either a channel strip setting or a Library patch and recall them at will.
I also have a dedicated Kontakt library loading macro, but it's quite particular to my way of organising Kontakt libraries, which relies on aliases, so probably won't be applicable to many others.
Hi, I've tried the "strip search" macros you mentioned and nothing happens. I've tried doing my own, whereby I'm recalling a CST and using the KM recording function. But, it doesn't recall that patch reliably. Sometimes I have to press the SD button (assigned to that macro in KM) up to 7 times to get the patch to load. I wonder what I'm doing wrong? See screen=grab of KM
Did you read the macro notes in the thread? Many of the macros here will need a bit of tweaking if they involve found images etc. I'm not by my mac right now so I can't confirm this is one of them, but usually any coloured actions require user attention.
Hi, I've looked at the macro notes in this thread and some almost work and others don't at all. For example>
I run the âStrip search - sendâ macro
But: 1-It only activates if a track or instrument doesnât have a send already. It wonât insert a new send on slot 2 for example.
But: 2- Only gives send 1 on bus 1 and if this is already taken nothing is inserted.
I can't see which aux bus is selected and why only send 1 and aux 1 is activated?
Thanks
Just putting a word in that there are always multiple ways to accomplish these things, and of my 443 macros, only one uses Applescript, and that's because it needs to quit and relaunch Keyboard Maestro itself!
Also, the latest Keyboard Maestro's Press Button capabilities (namely, identifying available buttons in a given app window) helps with some, but not all, buttons in Logic.
As an example, here is my macro for creating a new track with Retro on it:
That looks good. I'm achieving the same thing using plug search but I've only got so far. I'd like to be able to get a macro that add sends to a track and routes the new aux to where the existing track is routed (eg vocal is routed to a "vocal" group). Do you think this could be accomplished without using apple script? Thanks
HI, I've looked at your macro's more and have had very mixed results. I can aunch the strip search set called âstrip search - sendâ - This does bring up a list of random things Iâve saved as bus routing in the past, but also only chooses send 1. If I select say âLV Verbâ it inserts this in send 1 bus 1, but this if this is already taken so creates a conflict.
How is this macros organised/ controlled ? How can I change the Aux from always selecting Aux/bus 1?
Thanks
