Melodyne 5.1.0 HELP

[adamdavid]

I'm trying to demo the trial version of Melodyne 5 in Reaper v6.70 but am having some issues. I can open Melodyne as a stand alone program outside of Reaper, but I cannot open it as a VST3 FX inside of Reaper. I keep getting the message "Melodyne 5.1.0 (b 016) has encountered a problem that prevents it from loading properly." I tried setting it to run as "Native Only" after reading someone's suggestion to try that, but that didn't change anything. Any help would be much appreciated. Thanks!

[Bumble Bee]

I'm having a similar issue.

Plug-in works as a Stand Alone but not within Reaper.
Both Dexed and Sitala exhibit the same behavior.

I've never encountered this before. Other effects are working as they should.
Dexed was uninstalled and reinstalled, on the C Drive. To run as both Standalone and VST.

I'm running REAPER v6.70/OSX64 rev 309480

Error message:
The following effect plug-in could not be loaded

AUi: Dexed (Digital Suburband)

(effect configuration is preserved)


Any help would be appreciated.
Kind regards.

[mabian]

Isn't now Melodyne up to version 5.3?

- Mario

[Bumble Bee]

Originally Posted by Bumble Bee

I'm having a similar issue.

Plug-in works as a Stand Alone but not within Reaper.
Both Dexed and Sitala exhibit the same behavior.

I've never encountered this before. Other effects are working as they should.
Dexed was uninstalled and reinstalled, on the C Drive. To run as both Standalone and VST.

I'm running REAPER v6.70/OSX64 rev 309480

Error message:
The following effect plug-in could not be loaded

AUi: Dexed (Digital Suburband)

(effect configuration is preserved)


Any help would be appreciated.
Kind regards.

Solution discovered.
1. Go to Preferences
2. Go to Plug-ins
3. At the bottom, "Only show FX matching filter string:"
4. Press Soft button that says, "reset to recommended default:
5. This statement in the white rectangle should say this,

NOT ("AU"(Waves)")

6. Save and close Reaper
7. Open Reaper again, it should now all function as it should.

[Bumble Bee]

The "solution" posted did not actually help once Reaper was closed and reopened.

With both Sitala and Dexed, they seem to only function properly when Plugin behavior preferences get adjusted, and then only for that session.
This process has to be repeated when another session is launched, and then only "hit or miss". Sometimes those Plugins will not load at all.

[Gopherhawk]

Originally Posted by adamdavid

I'm trying to demo the trial version of Melodyne 5 in Reaper v6.70 but am having some issues. I can open Melodyne as a stand alone program outside of Reaper, but I cannot open it as a VST3 FX inside of Reaper. I keep getting the message "Melodyne 5.1.0 (b 016) has encountered a problem that prevents it from loading properly." I tried setting it to run as "Native Only" after reading someone's suggestion to try that, but that didn't change anything. Any help would be much appreciated. Thanks!

I too am having a similar problem after updating my rig from a laptop to a brand new desktop machine. I can load the program from Windows Explorer, but it won't appear in my VST list. I'll try one of the solutions above, as I am away from my home computer at the moment, but this is the last thing I am trying to sort out after transferring all of my programs. Stressful!

[Stella645]

Originally Posted by Gopherhawk

I too am having a similar problem after updating my rig from a laptop to a brand new desktop machine. I can load the program from Windows Explorer, but it won't appear in my VST list. I'll try one of the solutions above, as I am away from my home computer at the moment, but this is the last thing I am trying to sort out after transferring all of my programs. Stressful!

Your issue isn't remotely the same thing. The solution posted is an OSX thing so not going to help you on WIndows.

You need typical fixes for plugins not scanning.

1. Check if it's in the failed to scan list...If not you probably messed up the install somehow.
2. If it's there then Reaper is rejecting it....which is most likely either going to be wrong location of install or missing runtimes in Windows.