Q PatchWork 2.6

[DarkStar]

I am just trying out PatchWork and have a few questions.

Q1 How do I create the custom plug-in view? As in:

I cannot find out how to hide the other panels,

Q2 In such a view, wouldn't a much simpler tool bar be better, as most of the tools are not then relevant?

Q3 Can I set a default zoom level (rather than having to do it each time I open a new instance)?

Q4 i would prefer not to have the ~3,500 files (67 MB) of VST Data in my plug-ins folder. How can I move them?

Q5 If they cannot be moved they would be better in (on Windows) to ...\AppData\Roaming\Blue Cat Audio\BC PatchWork VST (where the global.xml file is)

Q6 Do we really need two sets of VST Data folders and files (for effect and synth editions)? Their contents seems almost identical.

[Blue Cat Audio]

Hi,

Thank you for your interest in our software. Please find below our answers and comments:

1. Just hide the plug-ins view by clicking on the little plug icon in the toolbar (6th icon in the second row).
2. All tools are actually still relevant. You may indeed not SEE all the changes on the screen, but they are still active.
3. Yes, you can set the default zoom value using the save as user default command.
4-5-6. We are indeed thinking at ways to move these files and share them as much as possible. Now that people seem to have finally stopped moving VST files manually, it seems like a reasonable option.

I hope this helps!

[DarkStar]

Thank you for the clarifications, they all help

1 Found it I saw that before but the tool-tip said "Show plug-in slots" when they were currently displayed. Can I suggest that, when they are displayed, the tool-tip says "Hide plug-in slots?

2 Understood, but i think that some of the active buttons may be a little confusing.

3 Got it - it would be worth adding that to the User Manual.

4-6 Just to add that if those files were somewhere-else, then they would not be scanned for possible plug-ins each time my DAWs start.
(u-he has a neat solution - with a single shortcut file alongside the plug-in file, pointing to the folder where all the plug-in data is installed. And the user can choose the location of that folder during installation.)

More info:
The Macro names show up in Reaper 6 and Waveform 12, using the VST edition. That is a great plus.

The Patchwork GUI is 25% bigger in Waveform 12 than in Reaper 6; maybe it is applying the Windows-scale of 125%??? Third-party plug_ins loaded in PatchWork and directly into the DAWs are all the same size.

Can we have double-click to open a plug-in editor? That seems better to me than clicking the menu line,

[Home Studio 87]

Can it be possible to have the "Tempo" on the bottom toolbar (on the left) in the "standalone" Patchwork application ?

[Blue Cat Audio]

Can it be possible to have the "Tempo" on the bottom toolbar (on the left) in the "standalone" Patchwork application ?

You may want to download the latest preview!

[Obsolete187521]

[DELETED]

[Blue Cat Audio]

Thanks!

[neverbeeninariot]

[...]
4-6 Just to add that if those files were somewhere-else, then they would not be scanned for possible plug-ins each time my DAWs start.
(u-he has a neat solution - with a single shortcut file alongside the plug-in file, pointing to the folder where all the plug-in data is installed. And the user can choose the location of that folder during installation.)
[...]

If you can be bothered with a manual (temporary**) workaround for this, LinkShellExtension (windows only) can create links and junctions with a simple drag and drop.

I have another folder 'VSTData' that sits next to my VST3 folder. I move the Blue Cat data directories into VSTData, then select them all and right-click-drag back to the VST3 folder, then select 'Drop-as-junction' from the LInkShellExtension submenu.

But yeah, it would be much better to not have to do this in the first place...as you say, u-he has a decent solution using regular shortcuts.

**temporary because updating the plugins overwrites the junction [sigh]