Multiple instances of PatchWork as standalone, different preset databases possible?

[Vaultnaemsae]

Hi Blue Cat Audio legends,

Possibly a weird info request…I want to create “virtual” standalone apps for some plugins that don’t have standalone versions . e.g. u-he Diva, Helix Native. The idea is that I could open them as individual app instances and funnel their outputs to a DAW via Loopback or Dante Virtual Soundcard only if recording.

In macOS I know how to duplicate the PatchWork app, relabel it etc. but when I launch the various PatchWork instances they always open the default patch from the preset database. Of course, this is great when running Patchwork as it was intended

Is there some workaround to somehow change the database per-app instance? The idea is that each instance would have a different default patch so the plug-ins would be active immediately from startup.

Thanks in advance for your help!

[Blue Cat Audio]

Hello,

You cannot do that BUT there is another way: the standalone app accepts a preset path as a first argument.

So you can either drag and drop your preset on the app icon to launch the right preset, or write a small shell or script that calls the app with the right preset, that you can launch directly. Something like:

Code: Select all

open /PathTo/PatchWork.app --args pathToYourPreset.preset

No need to duplicate the app, it's just a shortcut - much easier and cleaner

[rasmusklump]

That could be done very well with quick access popup.
I launch all my programs with it

[Vaultnaemsae]

Hello,

You cannot do that BUT there is another way: the standalone app accepts a preset path as a first argument.

So you can either drag and drop your preset on the app icon to launch the right preset, or write a small shell or script that calls the app with the right preset, that you can launch directly. Something like:

Code: Select all

open /PathTo/PatchWork.app --args pathToYourPreset.preset

No need to duplicate the app, it's just a shortcut - much easier and cleaner

Thanks for your informative response. That’s very useful. The reason for duplicating the app is to allow specific channel allocation in virtual audio transports.

So I just created some presets that live on the desktop and launching them opens the respective instances of the app based on the default launch app.

The only issue I’m having now is with Helix Native, though I suspect that it has nothing to do with PatchWork. When I launch the preset (causing the app to open), Helix throws up a DSP error. Closing the plug-in (Audio Unit) and reopening it fixes the issue but forces the plug-in to return to its default setting. Also, opening the PatchWork app first and then launching the preset from the desktop works as expected — just adds an additional step. This doesn’t happen with other plugins so I think I’ll need to check in with Line 6. Might be time to get back to working with Axiom for guitar stuff

I’ve never written or used a script before. I’ll have to give it a shot.

[Blue Cat Audio]

That's odd that you get this error! There should be no difference compared to loading a regular preset.

Axiom could indeed be the solution to all your problems