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

[Blue Cat Audio]

BTW just to make sure we are not the same page: how to you monitor these CPU spikes? Do they appear in Windows'Task Manger, in Cubase's CPU meter or in PatchWork's real time workload meter (or maybe all at once)?

[rasmusklump]

Windows task manager doesn't show spikes at all, only ultra low cpu.
It's the meter in patchwork. It looks like it is building up until it goes into the red and the sound cracles. Then it falls back to normal and builds up again.

[rasmusklump]

I am using patchwork 99% of the time standalone, so no Cubase involved most of the time

[Blue Cat Audio]

I am using patchwork 99% of the time standalone, so no Cubase involved most of the time

Ah ok, sorry for the misunderstanding! That looks even more strange then!

[rasmusklump]

I still get the spikes with psp Easyverb 2 and the psp EMT emulation (only if the gui of the plugin is visible)
The meters in the ACON plugin do indeed work when I restrict the plugin to 2 channels.

[Blue Cat Audio]

I still get the spikes with psp Easyverb 2 and the psp EMT emulation (only if the gui of the plugin is visible)

Still working fine here . The DSP thread is completely independent from the GUI on our side, so I don't think these changes have any impact on dropouts from the DSP thread directly. Of course the GUI now gets frequent updates due to parameters updates, but this should not impact the DSP thread, which is running in its own world.

I have noticed though that the plug-in is probably using OpenGL or other 3D APIs for its user interface (the GPU usage rises when opening the GUI of this particular plug-in). So I am thinking it may be a related issue specific to your system: it has been noticed in the past that some GPUs could have an impact on audio dropouts because of driver issues causing extra latency during audio interrupts. Have you ever tried the following trick?
https://www.bluecataudio.com/Blog/tip-o ... n-windows/

The meters in the ACON plugin do indeed work when I restrict the plugin to 2 channels.

It's probably worth checking out with them why this is happening. Very nice guy running the company, he should definitely be helpful!

[rasmusklump]

Thanks very much.
Normally I have problems with exe files from the internet but tried it nevertheless. But right after executing the file I got I think access errors, and I didn't want to experiment with my registry and stopped there.
For now I have installed the versions I downloaded in February again.
I can live without the meters for now.
But thanks nevertheless.

[Blue Cat Audio]

Thanks very much.
Normally I have problems with exe files from the internet but tried it nevertheless. But right after executing the file I got I think access errors, and I didn't want to experiment with my registry and stopped there

Yes I definitely agree: it's better to double/triple check them first with something like virustotal.com or anything similar. You may just have to run it as an admin. Sometimes its throws an error message but still works fine. It's an old utility but still quite useful in case you are getting conflicts.

What kind of computer/graphics card do you have by the way?

[rasmusklump]

A 2gb Zotac geforce gt 710
Generally my system doesn't play well with opengl and it's the first thing I switch off if a plugin vendor allows it like softube or uvi.

[Blue Cat Audio]

It could indeed be the culprit here!

[jahpooh]

Thanks for the heads up. Which type of plug-in are you using? VST3? Running PatchWork as a plug-in too or as a standalone app?

Hi there, this happens with the standalone app as well as the VST3. TDR prism is freeware as well so you can check it out. Multiple other plugin developers have cropped GUIs here as well with the latest preview version still from the 14th.