[fixed rns 3.5.1] Sandboxed VSTs may show "Plugin not responding Dialog" when browsing patches in some plugins

Help, Support & Bugs
1

Renoise 3.5.0 thinks VST crashed when selecting patch in VST.

  • Start Renoise 3.5.0
  • Load VST (I tried two; Babylon and Performer)
    Open VST and start selecting patches.
    if being in the patch menu for more than a few seconds, Renoise will complain the VST is not responding.

Expected results: being able to browse the menus without Renoise popping up a Not Responding window.

image

1 Like
2

Yeah, I saw that several times too today.
And it’s a bit annoying that it comes up again and again after you close it.

I had it for instance in Vital when I was browsing for the Vital-internal micro tuning file - and the popup and clicking cancel made the file chooser close… :wink:

Later I found that it’s possible to ignore the dialog, but it also did not go away automatically when I was finished browsing…

In Bitwig a plugin not responding shows up in the upper right corner as a notification. That feels less intrusive.

Cheers!

Tom

3

I noticed this when taking a while to choose a preset in the Super Quartet GUI, but hoped it was just an issue with a 25 year old plugin. It’s pretty annoying too, since it interrupts you after only ~10 seconds.

1 Like
4

I’ll get rid of this check altogether and only apply it for plugins that are getting scanned. When those dead-lock, you simply won’t notice and scanning hangs forever.

In other cases it’s difficult, if not impossible, to check whether the plugin has actually deadlocked or is simply waiting for user input.

1 Like
5

In the meantime I had it a lot more, like for instance while browsing presets in Fabfilter ProQ 3, so something that definitely shouldn’t block the audio or throw an error.

I don’t know how Bitwig does it, like I said, they show it in the upper right corner in their notification area and it goes away when the plugin responds again. I also think they wait a bit longer.
During scanning I have a couple of big VSTs that take ages (Pigments, SynthMaster3) and sometimes trigger the warning in Bitwig.

That is one of the great things about CLAP, it does not instantiate the plugins during scan but has a dedicated API to find out it’s parameters, so you can scan 700 plugins in a second.

Cheers,

Tom

6

I have that problem too.
Very annoying
Windows 10

Wondering how that can pass beta testing