HISE Compatibility with Windows 11 and Cubase 12

[Casey Kolb]

@Christoph-Hart said in HISE Compatibility with Windows 11 and Cubase 12:

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.

Nice!

[Matt_SF]

@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).

[d.healey]

This post is deleted!

[d.healey]

@Matt_SF Can you send him a standalone version to test?

[Matt_SF]

@d-healey yes, I just got his message today but I'll build it tomorrow to see if it works or not

[Casey Kolb]

@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.

[Matt_SF]

@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

[d.healey]

@Casey-Kolb @Matt_SF Have they tried in another host? Have they tried on another machine? What audio interface are they using?

[Matt_SF]

@d-healey I'll ask

[Matt_SF]

@Matt_SF
So I just compiled a standalone version of the plugin, adding to it "Settings", "MidiSource" and "MidiChannels" panels, and no problem on my computer (as expected).
I tried it first on my computer of course and it turns out that it's impossible to select the MIDI source or the MIDI channels, they are greyed out. Therefore I can't use my MIDI keyboard to play it but the sound is playing when I use the plugin's keyboard.

I compiled a simple SineGen standalone app to test this and the MIDI is working fine.

(The reported problem in Cubase is that the MIDI messages are not recognized or received by the plugin)

[Matt_SF]

...Another great moment of solitude for me as we say here...
Turns out the greying out of the options was caused by an error in my LAF script :man_facepalming: :man_facepalming: :man_facepalming:
The MIDI options does work.

So, I've sent the standalone version to my user to see how that goes. I'll wait for him to respond and I'll try to debug things up with him.

[Dan Korneff]

Ok... It's happening here too. Can't get my newly exported samplers to work on C12 PC. Standalone, Reaper, and PT all work properly.
PT not working either. I'm thinking routing matrix issue

[Casey Kolb]

@dustbro Good to know I'm not crazy! You're using VST3 right?

[Dan Korneff]

@Casey-Kolb yes

[Dan Korneff]

It appears to be Cubase in general. Cubase 11 no workie. PT no workie. Seems like Reaper is the only one functioning

[d.healey]

@dustbro Can you recreate the system on your machine?

What are the audio settings he is using in Cubase, Pro-Tools, Reaper?

And does the standalone version work?

[Dan Korneff]

@d-healey It's happening on MY machine :)
I'm using internal sound drivers for all tests.
Gonna double check standalone after I do a little debugging.
EDIT:
Standalone works fine

[Casey Kolb]

@dustbro Strange, maybe the VST3 is messed up in general. Spooky because we're about to launch the VST3 version of our plugin in a week.

[Dan Korneff]

I'm getting an error when activating outputs on my test instrument.
"the current layout you supplied is not a valid layout".
I would think that's the main reason it's not making any sound.

>	TEST Debug.vst3!juce::AudioProcessor::Bus::isLayoutSupported(const juce::AudioChannelSet & set, juce::AudioProcessor::BusesLayout * ioLayout) Line 1073	C++
 	TEST Debug.vst3!juce::AudioProcessor::Bus::getBusesLayoutForLayoutChangeOfBus(const juce::AudioChannelSet & set) Line 1136	C++
 	TEST Debug.vst3!juce::AudioProcessor::setChannelLayoutOfBus(bool isInputBus, int busIndex, const juce::AudioChannelSet & layout) Line 191	C++
 	TEST Debug.vst3!juce::AudioProcessor::Bus::setCurrentLayout(const juce::AudioChannelSet & busLayout) Line 1005	C++
 	TEST Debug.vst3!juce::AudioProcessor::Bus::enable(bool shouldEnable) Line 1049	C++
 	TEST Debug.vst3!juce::JuceVST3Component::activateBus(long type, long dir, long index, unsigned char state) Line 2939	C++

deactivating channels:

-		this	0x00000000294518b0 {owner={deactivatedBecauseOfMemoryLimitation=false updater={suspendState=false parent=...} ...} ...}	juce::AudioProcessor::Bus *
+		layout	{channels={heapAllocation={data=0x0000000000000000 {???} } preallocated=0x00000000294518c8 {6, 0, 0, ...} ...} }	juce::AudioChannelSet

[Casey Kolb]

@dustbro I can confirm the VST3 does work in Ableton Live and Cubase 11 on Mac. Must be specific to Windows.