Melodyne revisited

[Burnsjethro]

By coincidence I came across this passage in relation to Logic. I wonder if this has any relevance for Reaper:


""""First thing after loading a song: Hit “Play” at least once

Due to the different architecture of Logic and Melodyne, there might occur a problem, so we recommend the following procedure:

After opening an existing Logic project, the first thing to do is to hit “Play” once. Because even if this project contains Melodyne edits, which you saved some other day, Melodyne will – upon loading today – first show the notes in their original, non-edited state. As if Melodyne “forgot” its edits, but don’t worry: A “Play” command will update the Melodyne display to the state you had, when you saved the edited song the other day.

However, if after loading a song, you work too long with the song being stopped, this may lead under special circumstances to the loss of Melodyne edits. Therefore, take this as a golden rule to avoid any loss of data:
Load > Play > Stop

This is especially true for the following scenarios:

You open a song and want to save a copy of it with the “Save As”-command. Then you need to press Play once, before using “Save As”, otherwise the new project would contain wrong Melodyne information.

You open a song, realize that this is not the song you intended to work with, and open another song right away. So far, no problem, yet. But if you open a song AND change anything in Logic (e.g. renaming a track) AND you never ever hit “Play” AND you close the song again AND you answer the following dialog with “Save”: Well, then you may have lost important Melodyne edits (which you then need to restore with Time Machine or other backup strategies).

The row of actions described above seems to be pretty much unlikely. But if you make use of the “Auto Save” function in Logic, this could have a similar effect. Therefore always remember: Load > Play > Stop, then you are always on the safe side. And, of course, deactivating “Auto Save” is an additional safety net""""