I upgraded my laptop from Windows 10 to Windows 11. Melodyne 4 doesn't work in Windows 11 unfortunately. So I had to install Melodyne 5. And now when I open the Ableton project including Melodyne 4 it shows me "The Plugin Is Not Found". It doesn't load v5 as v4. Probably they have different IDs. How do you open edits from v4 to v5 in Ableton? Is there any option for importing or saving? Or moving data from the old machine?

I have just noticed that the latest v5 is VST3 and not VST2 as v4.

Another thing I noticed is the presets' extensions have changed from .fxb to .vstpreset. So the preset saved in v4 as .fxb can't be opened in v5 which uses .vstpreset

 

Last edited: Jul 6, 2024

Your best bet is to email Celemony. I've found them quite helpful.

 

I am here not there because... It is obvious

 

System requirements
For Melodyne 5 essential, assistant, editor and studio
- Interfaces Plugin operation via VST3, AU or AAX. ARA operation with compatible DAWs, as specified in the DAW compatibility overview.

Ableton Live
We have tested the current versions of Melodyne 5 in the following configurations.
Live 12.0 (VST3) under: Windows 11

You shouldn't actually do any updates at all if you have important projects.
You should have saved in VST3 in your previous project. I don't think they can produce that anymore.

 

Has anybody got any good news about the issue by now?

 

I am on Windows with Ableton. V4 crashes or so Ableton in Win11. I will probably be forced to buy cheap editions of Melodyne v4 and v5 to get the guide from Celemony. They say it is possible, but don't say how...

 

That's a very good point. You're right, I didn't do that. I didn't use the standalone version, but a VST plugin that doesn't save projects, right? I can't even open those plugin sessions in the standalone versions, can I?

 

Last edited: Jun 25, 2025 at 4:06 PM

If you left Melodyne open with an audio file transferred into it, and saved your DAW project; when you re-open that project your work in Melodyne should still all be there. It is saved as part of the DAW session, but not separately.

So, no. Standalone will not help.

 

Need to correct something of mine here. You can load/save melodyne projects when you use it as an external editor like Wavelab or SoundForge which is standalone, the plugin doesn't have the option of saving projects, all is saved within the main daw project. So you are correct, you can't open those plugin sessions in standalone.
Compatibility mode maybe the only option or going back altogether if nothing works.

 

They usually call it saved state generally, but that can be one of those terms they come up with different terms for each individual DAW. You can save the device state within the plugin as a new preset, for example. That way it can be used in other DAW or standalone too. But you always have to deliberately do it, otherwise you would be creating new preset junk in every new project you create with that plugin.