iZotope VST3 plugins don't show UI


#1

Hi
There is a compatibility issue between Juce and iZotope vst3 plugins.
The createEditorIfNeeded() returns nullptr.
Tested with Tracktion 7 so it is not just my code.

Now you are going to say that this is an issue with iZotope, and yes it is probably a good idea to let them debug as well.
But from their perspective their product works in all other hosts but Juce based… so

While on the topic what happened to the idea of keeping a list of these type of issues.
There was a post here:
https://forum.juce.com/t/collaborate-document-for-host-specific-behaviour/17424


#2

Interesting… it seems as if the entire edit controller part of the plug-in doesn’t load. For example, the plugin does not return any parameters or programs either. The plug-in returns nullptr when JUCE asks for an editor.

Any iZotope guys on the thread?


#3

Yes, it is really “dead”. Don’t think iZotope frequents this forum.
Would you like to conntact them or should I? you might have bigger influence than me. :wink:


#4

OK I dropped them an e-mail.


#5

Fantastic, thank you
Will be interesting, the will among plugin developers to look into these things is very varying.
Lets hope iZotope are among the "good guys"
Now if only every plugin developer would use the Juce framework, life would be a lot easier for us host developers.


#6

I also found out that the izotope plug-ins all fail Steinberg’s vstvalidator - they even crash.


#7

OK this is fixed on the latest develop branch. Thanks to the iZotope team!


#8

Thank you for the quick response! I’ll check this soon.
Thanks also to iZotope, they make great plugins, now we know they are also nice, helpful people.:clap:


#9

Had me a laugh, especially seeing that I recall doing the exact same thing when I was first developing the VST3 wrapper.