OB-Xf by Surge Synth Team

[EvilDragon]

That is strange, because we explicitly changed the mode of operation so that OB-Xf does NOT expose all its presets to the host... And we did that a few months ago!

If you've used the old alpha, maybe the Rosetta-ran Cubase is still using some older cached version of the plugin somehow? Although, the preset menu inside OB-Xf would not have looked like that back then...

Bizarre.

Maybe worth attempting to clear Cubase's plugin cache then reinstalling OB-Xf from scratch.

[Weasel-Boy]

Maybe worth attempting to clear Cubase's plugin cache then reinstalling OB-Xf from scratch.

I am well versed in the whereabouts of Cubase's Preferences and Caches. I deleted all the preset caches rebooted and let Cubase rebuild and ran the test. Same problem. I also keep safety copies of my Preferences that are generated once a week. I went back to when I first installed C15 and didn't have a copy of OBXF on the machine. Reinstalled OBXF 1.0.1. Same problem.

I'm done mucking with my system based on blind guesses.

[baconpaul]

Yes I’m also suspecting it’s a conflict between the vst3 edge presets and the state and the cubase state machine

But I’m not quite sure what to do about that yet

[baconpaul]

That is strange, because we explicitly changed the mode of operation so that OB-Xf does NOT expose all its presets to the host... And we did that a few months ago!

If you've used the old alpha, maybe the Rosetta-ran Cubase is still using some older cached version of the plugin somehow? Although, the preset menu inside OB-Xf would not have looked like that back then...

Bizarre.

Maybe worth attempting to clear Cubase's plugin cache then reinstalling OB-Xf from scratch.

No we still expose them we just made them not break. The breakage with edge presets came from bank stuff

My guess is the answer is to not expose them at the edge in cubase for now and see if that fixes it. I’ll prep a build which does that in the nightly next time I’m in there

[EvilDragon]

But Reaper and others show just one preset instead of the whole list? So it seems we're not exposing them after all...

[baconpaul]

The VST3 and AUv2 both show a full preset list for me here in reaper and logic with 1.0.2. Are you using the CLAP instead?

Anyway I have a theory - I'll try and get a nightly together and will let you know @Weasel-Boy. And if that doesn't work will try and drum up a cubase 15 NFR. (Edit: Oh they have a free 60 day trial. Let me see if I can replicate with that)

[baconpaul]

OK in good news @Weasel-Boy, I was able to reproduce this with 1.0.2 and cubase 15.0.10 trial on apple silicon

So I guess i have 60 days to find this. I'll look.

[EvilDragon]

Hah, touché, I was loading CLAP, whoops!

[EvilDragon]

Ohhhh this now rings a bell, actually. @baconpaul, see this post from Blue Cat Audio that sounds like it is quite relevant to this topic.

Basically... Cubase made a really "interesting" choice there, that is not really all that logical. Just actively discouraging any attempt to use the preset lists...

[baconpaul]

that matches what i'm seeing yes.

i'll poke this afternoon/evening and will either turn off edge presets in an if cubase or do something else or not, and report here.

[EvilDragon]

The timer idea from @wrl there is good, I guess.

[baconpaul]

That's exactly it. If I modify the VST3 to not support edge programs at all in Cubase, it all works. It is definitely calling setProgram again after setState and thats just .... ugh. wrong.

It will take me a bit of time today to get it merged and cubase-only but I'll get it done and push a 1.0.3 today or tomorrow.

[baconpaul]

The timer idea from @wrl there is good, I guess.

meh. i'll just turn off edge presets in cubase for now. lower risk.

[teilo]

That's exactly it. If I modify the VST3 to not support edge programs at all in Cubase, it all works. It is definitely calling setProgram again after setState and thats just .... ugh. wrong.

It will take me a bit of time today to get it merged and cubase-only but I'll get it done and push a 1.0.3 today or tomorrow.

But it's Steinberg, and they obviously will use VST3s properly, right?

Right?

[EvilDragon]

You'd think, hah.