PatchWork suggestions

[syra]

Hello, I'm a recent user of PatchWork and it's been great workflow-wise. I'm using it a lot in various situations and wanted to inquire about some possible features.

1) Is it possible to add double-click to open the plugin GUI instead of the little button currently? In all DAWs double-clicking a plugin is the default way to open the GUI. In PW it opens up a menu you'd normally get by right-clicking, all while right-clicking doesn't do anything. Actually neither double-click or right-click does anything. A single click just gives you the menu (while the first press opens the menu and preselects "show editor", it's not fast enough to work as a double-click). Can there be an option that double-click opens the GUI and right-click shows the menu as it's standard in DAWs and computers in general?

2) Can there be a way to fully disable plugins in the chains and PRE and POST columns? I have created elaborate templates but noticed that any inactive plugin in the chain and PRE and POST actually doesn't off load the DSP use. As such I have to keep removing plugins I don't use within my presets but if I need them down the road I have to either reload the preset and transfer any new settings to it, or reload the individual plugins and paste the preset settings. It's not convenient and I have to be constantly aware of what plugins to remove so they are not eating up my DSP. I understand that for delay comp reasons they have to be in place ready to go, but adding the ability to completely off-load them even though re-enabling them wouldn't be instantaneous, is a huge benefit for us with elaborate presets.

3) Can we get a solo capability for the individual plugins (exclusive or with an option like in the rows)? Currently if I have an elaborate chain and need to listen to what a specific plugin is doing, I have to turn off all other plugins to listen to that individual one. (Ideally for me I would love to be able to double-click to see the GUI and make the current GUI button the Solo one but I understand the latter is not very likely).

#2 is obviously the most important one and I hope there is a solution in the works, but the rest would also improve workflow significantly at least on my end.

[syra]

Bump.

Also Lindell plugins are not compensated accurately upon loading a preset or a session in Studio One 5.5.2. Once I change the oversampling, they get calculated correctly. This is the case for ALL Lindell plugins.

[shkr]

+1 on proposed improvements! And #2 is the most important.

@syra as far as I understand you can put plugins in parallel chain and if you disable this chain it will offload all cpu. it works only for disabled parallel chains but it should be an improvement for your needs

Also if Bluecat could introduce "per plugin oversampling" option in Patchwork I'm sure it would sell like hot cakes

[Tj Shredder]

The first hosting plugin that supports AUv3 plugins on M1 will dominate the market. How far did you get with it? A plus would be a CLAP version… (Just curious)
https://developer.apple.com/documentati ... e_auv3_api

[syra]

@syra as far as I understand you can put plugins in parallel chain and if you disable this chain it will offload all cpu. it works only for disabled parallel chains but it should be an improvement for your needs

Thanks shkr, I'm aware of that but it doesn't really do anything for my needs. I need the option to completely off load plugins that are not being used.

[carlca]

The first hosting plugin that supports AUv3 plugins on M1 will dominate the market. How far did you get with it? A plus would be a CLAP version… (Just curious)
https://developer.apple.com/documentati ... e_auv3_api

See the message I've just posted...
viewtopic.php?p=8637818#p8637818