HISE Compatibility with Windows 11 and Cubase 12
-
@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.
-
@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.
-
Alright, then I'm gonna build both versions. Yay...
-
@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.
-
@Casey-Kolb Use a script
-p:{TEXT} sets the plugin type ('VST' | 'AU' | 'VST_AU' | 'AAX' | 'ALL' | 'VST2' | 'VST3' ) -
@d-healey My bash scripts are so fickle. Some days they work, other days they don't
-
@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" -
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.
-
@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?
-
@Casey-Kolb Meh, just write a few extra lines and you get everything you need.
-
I've added a
-p:VST23AUflag 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. -
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
cleancommand in between? -
@Christoph-Hart said in HISE Compatibility with Windows 11 and Cubase 12:
I've added a
-p:VST23AUflag 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.Nice!
-
@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.
@Casey-Kolb Hi, One of my user just encountered the same problem. Did you manage to find what was causing this ?
(I'm only offering VST3 + I asked him to check that the samples were at the right place, and they are).Develop branch
Win10 & VS17 / Ventura & Xcode 14. 3 -
This post is deleted! -
@Matt_SF Can you send him a standalone version to test?
-
@d-healey yes, I just got his message today but I'll build it tomorrow to see if it works or not
-
@Matt_SF We were never able to resolve the issue, even with the VST3 version in Cubase 12,
We tried switching the audio drivers in the user's preferences, but that didn't fix anything. It's the only case we've ever had of this, so I'm still wrapping my brain around what could be going wrong. The standalone works fine on the user's machine.
-
@Casey-Kolb Thank you for your response. I don't know how I'll be able to debug this one if you couldn't do it !
I'll try anyway and report back if I stumble upon a solution -
@Casey-Kolb @Matt_SF Have they tried in another host? Have they tried on another machine? What audio interface are they using?
