PatchWork 2.71 Released: MIDI Sync, SysEx, Presets Navigation & More!

Official support for: bluecataudio.com
RELATED
PRODUCTS
PatchWork$99.00Buy

Post

I have to add that my studio is strictly offline and I work with a windows 10 version from 2021 if that is of any interest.

Post

Just tried it again.
VST3 of multiply version 1.3.1: the output metering directly left beside the eq doesn't work. Patchwork 2.71.
I installed the vst2 version, here the metering works.

Post

rasmusklump wrote: Mon Mar 17, 2025 2:06 pm Just tried it again.
VST3 of multiply version 1.3.1: the output metering directly left beside the eq doesn't work. Patchwork 2.71.
I installed the vst2 version, here the metering works.
Confirmed! It seems that I stupidly loaded the VST2 version the first time! :dog:

Post

Thanks for confirming.
The same happens with several psp plugins I own.

Post

rasmusklump wrote: Tue Mar 18, 2025 7:23 am Thanks for confirming.
The same happens with several psp plugins I own.
That's probably the same root cause. Will look into it!

Post

Hi,
With the newest preview version the metering works now but with psp Easyverb I now get massive cpu spikes that I didn't have with the previous version (standalone and vst3 version of patchwork in Cubase, win 10 )

Post

It's much better when the gui of the hosted plugin is closed....

Post

Another update: while the meters on the psp plugins work with the newest preview version of patchwork the meters in acon multiply still don't work.

But thanks very much for the progress so far.

Post

rasmusklump wrote: Sat Apr 12, 2025 1:18 pm Hi,
With the newest preview version the metering works now but with psp Easyverb I now get massive cpu spikes that I didn't have with the previous version (standalone and vst3 version of patchwork in Cubase, win 10 )
Thanks for the heads up. I could not reproduce those spikes here, does this happen in CPU-heavy session, or when doing stuff in Cubase's (or plug-ins') user interface? In this case, there may indeed a bit of potential extra CPU usage in the main thread (thanks to VST3's suboptimal threading design). An update to the preview is in work. It will add extra guards to avoid main thread contention in case it's already too busy. It will hopefully fix the problem.

Post

rasmusklump wrote: Sat Apr 12, 2025 4:45 pm Another update: while the meters on the psp plugins work with the newest preview version of patchwork the meters in acon multiply still don't work.
With multiply, I have noticed that the meters won't be displayed if the plug-in's I./O configuration is set to more than 2 channels. It seems to be an internal problem to the plug-in, I don't know why. Anyway, since PatchWork may have some extra channels, you may want to double check the number of I/O set (and maybe override them) on this plug-in. Just click on it and select Audio I/O. Try to force it to stereo. It always work fine here.

Post

Regarding Acon, that's true, I have 4 channels configured.
Regarding CPU load.
Not heavy at all, just a instance of Patchwork standalone with one instance of Easyverb 2 loaded to process a input channel of my RME Fireface with some reverb.
The other project is just one old Superior EZ librariy with 60 MB size that doesn't tax cpu at all and one instance of Easyverb 2 (also standalone)

Thanks very much.

Post

A new preview has been uploaded. I hope it will help with the CPU issue. Unfortunately as it does not happen here it's hard to reproduce. Also iLok-protected plug-ins prevent developers from using a debugger, so it's a bit longer to find out what may be going on.

Post

Thanks.
Will try it in three hours.

Post

Btw, Easyverb 2 has a free brother, PSP Chamber.
I don't know if it happens there as well but I think so, as the EMT plugin is also affected.
And this free plugin is completely without ilok.

Post

rasmusklump wrote: Mon Apr 14, 2025 11:48 am Btw, Easyverb 2 has a free brother, PSP Chamber.
I don't know if it happens there as well but I think so, as the EMT plugin is also affected.
And this free plugin is completely without ilok.
Oh nice, will check it out. However since this CPU hit does not happen on our systems (yet), it is going to be difficult to track. Anyway, with the additional fix in the new preview, it should avoid any contention in the main thread due to potential too high refresh rate of the parameter for the level meter. You may still get high CPU usage if refreshing the GUI of the plug-in takes time on your system for whatever reason.

Post Reply

Return to “Blue Cat Audio”