Skip to content
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

Open
mfisher31 opened this issue Jul 26, 2024 · 9 comments
Open

VST3: Element FX not Loading in Wavelab #805

mfisher31 opened this issue Jul 26, 2024 · 9 comments
Assignees
Labels
3rdparty Relates to a third party plugin or host bug Something isn't working vst3

Comments

@mfisher31
Copy link
Member

Captura_de_pantalla_2024-07-26_190916

@mfisher31 mfisher31 added the bug Something isn't working label Jul 26, 2024
@mfisher31 mfisher31 added this to the 1.0 milestone Jul 26, 2024
@mfisher31 mfisher31 moved this to Ready in Element 1.0.x Jul 29, 2024
@Sahul-GitHub
Copy link

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?

@mfisher31
Copy link
Member Author

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

@mfisher31
Copy link
Member Author

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?

@mfisher31 mfisher31 self-assigned this Sep 30, 2024
@mfisher31
Copy link
Member Author

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;

@mfisher31 mfisher31 added the 3rdparty Relates to a third party plugin or host label Sep 30, 2024
@mfisher31 mfisher31 removed this from the 1.0 milestone Sep 30, 2024
@mfisher31 mfisher31 changed the title Element FX not Loading in Wavelab VST3: Element FX not Loading in Wavelab Sep 30, 2024
@mfisher31 mfisher31 added the vst3 label Sep 30, 2024
@Sahul-GitHub
Copy link

Sahul-GitHub commented Sep 30, 2024

Does VST2 work for you?

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.

@mfisher31
Copy link
Member Author

Yeah... that was due to changes in JUCE (from updating it).

@Sahul-GitHub
Copy link

Could it be related to what is mentioned here?
https://forum.juce.com/t/bug-juce-7-0-2-error-loading-vst3-in-wavelab-11-mac-win/53729/12

The fix specifically talks about VST3 and WaveLab 11.1:
juce-framework/JUCE@78a0fc6

@mfisher31
Copy link
Member Author

Could it be related to what is mentioned here? https://forum.juce.com/t/bug-juce-7-0-2-error-loading-vst3-in-wavelab-11-mac-win/53729/12

The fix specifically talks about VST3 and WaveLab 11.1: juce-framework/JUCE@78a0fc6

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.

@mfisher31
Copy link
Member Author

mfisher31 commented Oct 1, 2024

async latency setting does not work, FYI. Not gonna be a quick fix today unfortunately.
I notified the forum, maybe somebody will jump in with suggestions:
https://forum.juce.com/t/bug-juce-7-0-2-error-loading-vst3-in-wavelab-11-mac-win/53729/15?u=kushview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rdparty Relates to a third party plugin or host bug Something isn't working vst3
Projects
None yet
Development

No branches or pull requests

2 participants