BUG: Melodyne ARA Timing When There Are Tempo Changes

[Dizzi45Z]

I've discovered a couple bugs with how Melodyne ARA gets off when you have tempo changes in a project. Melodyne playback and MIDI visuals will mismatch the waveforms on the clips and will playback according to the MIDI visuals, not the waveforms.

This video demonstrates what I'm talking about:

Melodyne ARA Bug in Pro Tools 2022.10

The current best workaround I have found to avoid this bug is.

1. If there are already time changes in the project, the track should be in Sample Mode when you turn on Melodyne. If you make any further tempo changes where the clip exists, the audio will get off. Don't render it with Consolidate Clip as you will get unexpected results. Commit with Melodyne-Render or removing Melodyne from the track and choosing commit.

2. If you haven't made any tempo changes where your clips are going to be Melodyned and you plan to make tempo changes, then Melodyne needs to be Tick Based, then turn on Melodyne on the clips. After this, you shouldn't switch the track back to sample based or Melodyne will mismatch your clip wave forms.

Can others confirm this bug?

[Dizzi45Z]

I just wanted to mention that this is not fixed in the latest 2022.12 update.

[Ray Lyon]

I have not upgraded yet but someone should make a little manual that documents all these workarounds and put it in a sticky until the bugs are worked out. I can't imagine using ARA Melodyne in a professional situation where esp. the dock cannot be disonnected and tempo changes can render audio files worked on are corrupted. My .02

[Vadym]

Originally Posted by Dizzi45Z

I just wanted to mention that this is not fixed in the latest 2022.12 update.

This bug is happening when user consolidates (opt-shift-3) a partially (middle or right part) selected MD-edited clip placed on the tick-based track. To avoid the issue select the whole clip before "consolidating" or use any other method of Melodyne render (Track commit, freeze, clip select Melodyne->Render etc.)

Hope it will be fixed in the next release.

[Vadym]

Originally Posted by Vadym

This bug is happening when user consolidates (opt-shift-3) a partially (middle or right part) selected MD-edited clip placed on the tick-based track. To avoid the issue select the whole clip before "consolidating" or use any other method of Melodyne render (Track commit, freeze, clip select Melodyne->Render etc.)

Hope it will be fixed in the next release.

The above only applies to the "consolidate" issue.

Originally Posted by Dizzi45Z

Melodyne playback and MIDI visuals will mismatch the waveforms on the clips and will playback according to the MIDI visuals, not the waveforms.

Most likely the result of the issue with tick-to-sample track with ara clips conversion. If you can confirm and/or clarify the steps when this happens, please do so.

[Dizzi45Z]

Originally Posted by Vadym

Most likely the result of the issue with tick-to-sample track with ara clips conversion. If you can confirm and/or clarify the steps when this happens, please do so.

Did you see the link to the video in my original post? That shows you steps on how to reproduce the bug every time.

[Vadym]

Originally Posted by Dizzi45Z

Did you see the link to the video in my original post? That shows you steps on how to reproduce the bug every time.

Yepp, all the cases from the video are the focus of our attention. One of them (ARA clip(track) tick-to-sample conversion when session tempo changes are present) is pretty tough since some specific nature of the Melodyne plug-in implementation.
The case when the user changes the session tempo over the ARA clip on the sample-based track is a UI issue only, it plays correctly and any clip move or edit in the Melodyne Tab will update the appearance of the blobs in the correct place over the ARA clip.

[Dizzi45Z]

Unfortunately this still exists in 2023.3.

I hate the fact that Melodyne now analyzes every clip on Tick based tracks too. Hopefully that wasn’t the intended solution for this bug.

I don’t like Melodyne automatically analyzing every clip as this creates lots of ARA data to be saved contributing to more Saving ARA data hanging. For now, I’ll just have to make sure tracks are sample based before I use Melody. This adds an additional step now.

This bug has existed since 2022.9. Is this in the que to be addressed and fixed? Almost half the music I work on has tempo changes which makes this bug a very annoying issue.

[audiogamble]

Originally Posted by Dizzi45Z

Unfortunately this still exists in 2023.3.

I hate the fact that Melodyne now analyzes every clip on Tick based tracks too. Hopefully that wasn’t the intended solution for this bug.

I don’t like Melodyne automatically analyzing every clip as this creates lots of ARA data to be saved contributing to more Saving ARA data hanging. For now, I’ll just have to make sure tracks are sample based before I use Melody. This adds an additional step now.

This bug has existed since 2022.9. Is this in the que to be addressed and fixed? Almost half the music I work on has tempo changes which makes this bug a very annoying issue.

Does it do this regardless of whether melodyne ARA is active on the track or not?


Sent from my iPhone using Tapatalk

[Vadym]

Originally Posted by Vadym

Bug is happening when user consolidates (opt-shift-3) a partially (middle or right part) selected MD-edited clip placed on the tick-based track. To avoid the issue select the whole clip before "consolidating" or use any other method of Melodyne render (Track commit, freeze, clip select Melodyne->Render etc.)

Hope it will be fixed in the next release.

This one should be fixed in PT 2023.3.