OB-Xf not showing AU in DaVinci Resolve

[usegitterhub]

Can't choose AU bc. it doesn't show up in "Instrument" menu, instead it shows up in UNCATEGORIZED:

[usegitterhub]

ED, are you going to post on VI-Control when the update to 1.1 is available?

[mkruselj]

Of course!

[usegitterhub]

Great, thank you!

BTW., your Surge XT shows the same behavior as OB-Xf, crashes when clicking in Data fields, not showing up under AU but UNCATEGORIZED. Should I open a new issue or are you taking care of it?

[mkruselj]

When you say data fields, what do you mean? But yeah we're not guarding VST3 host menus against Resolve in either Surge nor Shortcircuit - that it doesn't work is news to us. And this should also be reported to them, so they can fix it on their end.

[baconpaul]

The bug report to give then is:

Plugins which use the VST3 host param context menu api crash on unpacking the menu.
If youa re using JUCE 7 for your hosting, this is a bug fixed around Juce 7.0.9 or so in the JUCE reference counting of this hosting API
If you are building your own VST3 hosting, then it looks like you forgot an addref on a host param menu
You can test this with Surge 1.3.4 or OB-Xf 1.0 among other synths.
The latest versions of Surge and OB-Xf have excluded Davinci resolve from their host menu list so won’t crash

[mkruselj]

Next Surge nightly should also be fine in Resolve.

[usegitterhub]

When you say data fields, what do you mean?

Sorry, I don't know the right terminology, click on Status off Waveshaper:

[mkruselj]

Right, so that's going to open a context menu. Same issue as the one baconpaul fixed, now also fixed in latest Surge nightly.

[baconpaul]

But the bug is in resolve to be clear
It is handing us a wrong thing

[mkruselj]

And now back to actual report. So we're not categorizing for AU properly, it seems.