Melodyne Essential acts crazy
-[Reaper 5.974 x64]
-Melodyne Essential (4.2.1.003 x64)
My typical setup is as follows: I will have a folder labeled "Vocals" with multiple vocal tracks nested under it. Each vocal track needs an instance of Melodyne. The folder and individual tracks usually have effects on both. Additional both the folder and the individual tracks will have sends to effects tracks.
This has happened to me on numerous projects. Even a fresh project with only two tracks of vocals, loading a second instance of Melodyne can do crazy things.
On to the problems:
If I load an instance of Melodyne Essential on a single track, it works fine. After adding another instance to another track, its kind of a coin toss as to whether I can get it to work right.
There are basically three scenarios that can happen. The Melodyne instance will work as expected, the Melodyne instance will be blank, or the Melodyne instance will have the same blobs as another instance.
Clicking the "compare" button on any instance seems to affect other instances.
Moving blobs in one instance will cause blobs to move in other instances.
It basically makes Melodyne unusable.
Recipe
-create new project
-add two tracks, both with audio on them
-add melodyne essential to one track (works as expected)
-add second instance of melodyne essential to the other track, things go crazy
|