The new Pigments plugin from Arturia crashes when you try to open its editor window. This is completely reproducible with the JUCE Audio Plugin Host. How can this be fixed? It’s very odd that the Arturia plugins all run perfectly fine with non-JUCE hosts but break with any JUCE host, as far as we can tell.
Help would be appreciated.
This crash is happening in Arturia’s code, so there’s nothing we can do other than send another email to their tech support to let them know about the issue which I’ll do now.
We’ve also emailed them - but I’m much more concerned as to why their plugins (and Korg Gadgets as well, it now turns out) work perfectly fine with hosts that are not JUCE based. Korg is using JUCE (it’s proudly on your discover page) and I think Arturia is as well. I realize the crashes appear in their codebase but is it possible that something is wrong with the way those plugin editors are being invoked from a JUCE host?
It’s impossible to know without having access to their code and being able to step in and see exactly where the crash occurs. Although given that there are thousands of JUCE based plug-ins out there which don’t crash or show a blank UI when using the JUCE hosting classes, and the JUCE plug-in demos using the latest code don’t either, I’d say the odds are more likely that it’s an error in their code.
I’m having a lot of trouble with Pigments 3 in AudioPluginHost (JUCE 6.1) on Windows.
Firstly, it opens with the wrong window size. The window is too big for the plugin UI, and there’s a lot of black space on the right/bottom.
Secondly, I get a stack overflow when I click the little ‘gear’ settings icon on the far right of the toolbar. This method is being called recursively:
AudioPluginHost.exe!juce::VST3PluginWindow::resizeView(Steinberg::IPlugView * incomingView, Steinberg::ViewRect * newSize) Line 1540
Looks like the call to view->onSize() on line 1538 of juce_VST3PluginFormat.cpp causes it.
Thirdly, I get asserts in VST3HostContext::beginEdit() and VST3HostContext::endEdit() when I click the ‘FX’ button in the toolbar.
I’m sure there are other issues too. It’s generally very flakey indeed. It seems to work fine in other hosts I’ve tried.
I realize it may be down to the plugin, but it warrants investigation on the JUCE side to make sure the host isn’t misbehaving in some way.
Not sure if relevant, but I have two 4K monitors @ 150% (recommended) scaling in Windows display settings. Maybe that has something to do with the plugin window being the wrong size. I see the same with FabFilter plugins too (window too big for plugin UI, empty black areas on right/bottom of window).
This is what Pigments and all of the FabFilter plugins look like when I open them in AudioPluginHost. Again, I’m using a 4K display at 150% scaling, which may be related.
Edit: I spoke too soon. FabFilter Pro-C 2 and Saturn 2 display at the correct size. Pro-G, Twin 2 Micro and Simplon don’t. Happy to break this particular issue out into a separate thread if you prefer.
@ed95 Just to confirm that Pigments is behaving nicely now. Thanks again for the quick turnaround.
Unfortunately, many of the FabFilter plugins still look like the screenshot above. Would appreciate a fix if it’s a JUCE issue.
