HISE Compatibility with Windows 11 and Cubase 12

[Casey Kolb]

I received a support ticket from a user who is using Cubase 12 on Windows 11. He can't seem to get any sound out of our plugin, standalone or VST, even after adjusting the audio driver and MIDI input settings. This is the first time we've encountered this issue, so I'm wondering if there is any known compatibility issues with HISE and Windows 11 / Cubase 12.

[tomekslesicki]

@Casey-Kolb I know it may sound like an obvious thing but I'd suggest asking him to re-locate the samples folder and to make sure it's not stored on a location that might be syncing to a cloud.

[Dan Korneff]

My main development rig is Win11 and Cubase 12. No issues here

[orange]

@Casey-Kolb said in HISE Compatibility with Windows 11 and Cubase 12:

I received a support ticket from a user who is using Cubase 12 on Windows 11. He can't seem to get any sound out of our plugin, standalone or VST, even after adjusting the audio driver and MIDI input settings. This is the first time we've encountered this issue, so I'm wondering if there is any known compatibility issues with HISE and Windows 11 / Cubase 12.

Is this issue valid for VST3 versions too?

AFAIK, Cubase (from version 12 and above) doesn't support VST2 anymore.

[d.healey]

You said standalone or vst, so that tells you it's not Cubase related.

[Casey Kolb]

@d-healey Confirming the standalone issue. They might be two separate issues. One might be VST2 in Cubase 12, while the other is a bad audio driver in the standalone version.

[d.healey]

Ask them to test in Reaper, that will confirm if it's a Cubase issue.

[Christoph Hart]

BTW are there any major DAWs left that don't support VST3? It might be a good time to change the default in HISE and fade out VST2.4.

And has anybody made experience what happens if you change the plugin format in an update (so v1.0.0 is VST2 and v1.0.1 is VST3)? Does load old projects with the correct plugin states etc?

[tomekslesicki]

@Christoph-Hart I think only Reason doesn’t support VST3 yet, but they’re working on it. I don’t think it’s possible for VST3 to just replace VST2 in older sessions - in Ableton for example, each plugin format is treated as a separate being. So the older sessions would still use VST2 and the new ones would be able to use the updated VST3 plugins, which is not a bad solution in my book.

[orange]

@Christoph-Hart Some of my plugins were VST2 at the beginning and then I updated them to VST3 and I haven't seen any specific issue/crash with this transition.

But since I've got lots of support tickets from the older DAW users (also from some users who want to demo the plugins) that they can't see the plugin, so I have to provide them with VST2 versions too.

As mentioned, the current Reason version and previous DAW versions will still need VST2 only (also there are lots of users that haven't updated their DAWs yet), maybe a couple of years later VST2 deprecation can be a good idea. But for now, I think VST2 still needs to be on the road, at least a couple of years more.

[Christoph Hart]

Alright, then I'm gonna build both versions. Yay...

[Casey Kolb]

@Christoph-Hart Is there a way to export both VST2 and VST3 at once without checking and unchecking that option in the HISE settings? I'm probably missing something stupid.

[d.healey]

@Casey-Kolb Use a script

-p:{TEXT} sets the plugin type ('VST' | 'AU' | 'VST_AU' | 'AAX' | 'ALL' | 'VST2' | 'VST3' )

[Casey Kolb]

@d-healey My bash scripts are so fickle. Some days they work, other days they don't

[Casey Kolb]

@d-healey I think this type of command will only export either VST2 or VST3 depending on your preferences:

"$hise_exe_macos" export_ci "Presets/$hipFile.hip" -t:instrument -p:ALL -a:"x64"

[d.healey]

@Casey-Kolb

I think this type of command will only export either VST2 or VST3 depending on your preferences:

You can run multiple commands one after another ;) https://github.com/davidhealey/sofiawoodwinds/blob/master/Packaging/OSX/build_mac.sh

I'll be posting a video soon demonstrating a script I use to build my plugins, installers, codesign, and notarize all in one go.

[Casey Kolb]

@d-healey Yup, this much I know.

That's the script I've already modified for my setup :) I just mean the "ALL" command would be helpful if it actually exported all the versions. Maybe it does?

[d.healey]

@Casey-Kolb Meh, just write a few extra lines and you get everything you need.

[Christoph Hart]

I've added a -p:VST23AU flag that builds every plugin except for AAX. Not only it's less code to type in the build script, but it also is 30-50% faster now because it can reuse some object files from the compilations.

[d.healey]

@Christoph-Hart

because it can reuse some object files from the compilations.

Isn't that the same as with the previous build script if you don't run a clean command in between?