HISE Compatibility with Windows 11 and Cubase 12
-
Still following. I haven't heard back from my user yet...
-
@Casey-Kolb said in HISE Compatibility with Windows 11 and Cubase 12:
@dustbro I can confirm the VST3 does work in Ableton Live and Cubase 11 on Mac. Must be specific to Windows.
Confirmed. VST3 AAX and AU all working on MacOS
-
Can one of you post a test VST3 that demonstrates the issue, preferably a debug build? Would be good to have the HISE project too.
-
@d-healey Here's a minimal project:
https://hub.korneffaudio.com/index.php/s/2N6A4caaYcFToZ2 -
@dustbro Could you also provide a debug plugin in case the problem is created when you compile it on your system.
-
@d-healey just uploaded the debug vst
-
I checked out a bunch of commits. @Christoph-Hart it looks like this happned when x64 was removed from the plugin name.
-
This is the last working commit:
Commit: 5adca361018f1818111a4747852e58247882a4c6 [5adca36]
-
@dustbro Can you link to the commit? I can't find it using the hash for some weird reason...
-
@Christoph-Hart Heres' the commit that breaks the samplers:
https://github.com/christophhart/HISE/commit/526a10891dea989164607782906237b91c2e7339
-
@dustbro Hmm, that's a fail safe that prevents odd buffer sizes. What audio settings are you using?
-
What happens if you set
HISE_EVENT_RASTER
to 1? (In the ExtraDefinitions).If this is really the culprit, then it should work with a raster size of 1...
-
@Christoph-Hart I'll try that now.
I'm using my internal sound card on this computer. Buffer options are "low, medium, high" hahah -
@Christoph-Hart HISE_EVENT_RASTER to 1 prevents the project from fully loading.
-
@dustbro I think you need to compile your project with that flag, not HISE itself.
-
-
@Christoph-Hart raster size of 1 works
-
@Christoph-Hart Will that extra definition affect anything else? Do we just need to set that in our projects?
-
@Casey-Kolb Yes of course, this vastly increases CPU usage because it will render all modulators at full audio rate.
I just wanted to confirm that it's actually this flag that's causing the problem. Setting it to 1 is not the fix.
-
@Christoph-Hart Noted!