-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VST3: Element FX not Loading in Wavelab #805
Comments
Hi Michael, I have some spare licenses of the WaveLab LE 11 version, valid for Windows and Mac. I could send you one of them for free if that helps you out in some way for testing. Would you be interested? |
Yeah, I'd be interested. I mean... I won't use it for anything but fixing this bug though: note to self: downloads: https://o.steinberg.net/en/support/downloads/wavelab_11/wavelab_112_latest_version.html |
Ok, got it running. I can load the VST2 but not the VST3. Not sure what the problem with the "layout" is since that is shared code across all formats and part of the JUCE plugin client api. Does VST2 work for you? |
the code below is saying "if there is at least one input and at least one output channel, then accept the layout as valid. Really not sure how to resolve this. This layout config basically supports any channel configuration with the exception of 0 ins or 0 outs. case Effect:
// require at least a main input and output bus
supported = layouts.inputBuses.size() > 0 &&
layouts.getNumChannels (true, 0) > 0 &&
layouts.outputBuses.size() > 0 &&
layouts.getNumChannels (false, 0) > 0;
break; |
Yes, I hadn't tested it before because I'm almost not using VST2 these days, but it seems to be working fine in WaveLab Elements 12. If I remember well, this issue arised first around Element builds 23x-24x. At some point something broke the Element FX plugin, which wasn't even recognized by the hosts, and you fixed it except for WaveLab, which started showing the message above, until now. |
Yeah... that was due to changes in JUCE (from updating it). |
Could it be related to what is mentioned here? The fix specifically talks about VST3 and WaveLab 11.1: |
This ChangeSet is already in use by element. There is a suggestion on the forum to set latency samples async. Element isn't doing that, so gonna give it a go and see. |
async latency setting does not work, FYI. Not gonna be a quick fix today unfortunately. |
The text was updated successfully, but these errors were encountered: