Pro Tools 2022.10: Melodyne Edits Missing After Relinking Clips

[psycho]

In a session, all Melodyne (ARA2) edits were lost! Was some hours of work and client was present. He was not amused.
"Expert Plus Support" was unable to help ("Trash preferences" blah blah, you heard it before ).
So I investigated myself and found that it was caused by moving audio data to a different drive (and relinking again).

Steps to reproduce:
1. Do some Melodyne edits
2. Save and close session
3. Move audio clips to a different drive
4. Open session and relink missing audio clips
5. All melodyne edits are lost! "Melodyne notes" are still visible as clip overlay! A new analysis will run automatically (eventually).

"Some Melodyne track data can't be found. Melodyne edits on affected tracks may not playback correctly." might be reported if you are lucky but in most cases nothing is reported.

Watch here: https://youtu.be/4OQv-egClxA

To even further verify relinking success, I also did some clip effects and, as expected, those were still present after relinking.
If you move the audio files back to their original location, everything will be fine, unless you did a save session in the meantime.


I am using Windows. Maybe some Mac user can verify if this happens under Mac OS too.

[midnightrambler]

Can confirm I’ve had the same issue.

[albee1952]

This makes a good argument for committing early, especially if you plan on moving or copying the session to another drive(although I don't know why you had to relink).

[lesbrunn]

Originally Posted by albee1952

This makes a good argument for committing early, especially if you plan on moving or copying the session to another drive(although I don't know why you had to relink).

Yes Dave. I've experienced this issue, so I do my ARA edits in little chunks and commit as soon as I'm done, one small clip at a time.

[psycho]

Originally Posted by albee1952

This makes a good argument for committing early, especially if you plan on moving or copying the session to another drive(although I don't know why you had to relink).

The point is that when moving sessions from desktop to notebook (where the file-paths start with a different drive-letter (Windows), thus (auto-) relinking required), committing doesn't help. I would not be able to continue Melodyne editing on the notebook as un-committing with different file-paths reveals the bug.

[Tweakhead]

wow. that's outrageous. and having to commit is not a solution.
what if there's some minor adjustments you need to make with fresh ears the next day ? C'mon Avid - get it together.

In the meantime, can we have an option to hide ALL these now utterly useless TABS eating up all that space at the bottom of the Edit Window ? and/or a preference to move them to the top near the timeline.

[midnightrambler]

Originally Posted by lesbrunn

Yes Dave. I've experienced this issue, so I do my ARA edits in little chunks and commit as soon as I'm done, one small clip at a time.

You see now I think I would argue the opposite - it's better to work from one consolidated file, rather than a number of different files on the same track. This is certainly the case for Elastic and it would appear that I'm also getting fewer errors this way using ARA. (I appreciate this is not exactly a rigorous scientific test though :))

[[email protected]]

this happened to me and i didn't move anything. this is freaking outrageous. I've lost hours of work. it's utterly unacceptable that avid hasn't sent out a warning telling people about this.

[[email protected]]

fwiw I went to an autosaved version and found one prior to the session being corrupted. I save the last ten versions every 5 minutes.
fwiw, I also save as each day with the date, so that the worst case scenario is I only lose today's work.

[psycho]

Update:
I opened a new support case after my investigation.
Once again i was told to trash (Melodyne) preferences, which of course had absolutely no effect.
Finally today someone from global support in Poland answered. He said:

I am suspecting a known bug here. Just need to run some tests to verify if your workflow matches the issue we are already aware of and it shall be fixed with the upcoming Pro Tools release.
I will contact you after I am done with testing.

I will keep you updated.