BUG: Melodyne ARA Timing When There Are Tempo Changes

[Vadym]

Originally Posted by Vadym

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.

This one is not fixed yet, but the workaround is pretty simple, hope it will help you.
Apply "Copy Song Data To Note Assignment" over the messed ARA-clip from the Melodyne Tab → Edit top menu.

Originally Posted by Vadym

The case when the user changes the session tempo over the ARA clip on the sample-based track is a UI issue only

Same, not fixed(we tried honestly), but we have a workaround on hand.
Any DnD, trim or any other action over such a buggy(shifted blobs) clip and UNDO should fix the position of the blobs for you.

[Dizzi45Z]

Thank you for fixing what you have so far. Please continue to pursue getting this completely fixed for us.

Please also consider giving us a preference to choose whether all audio on a tick based track needs to be analyzed by Melodyne (when Tick based).

Since Melodyne requires the pauses to save ARA data which is so abrasive (freezing everything for a couple seconds). It is crucial to keep ARA data as low as possible. To do this, I always render the exact sections I want to use Melodyne on before I have it analyze the data. This new change is going to create TONS of ARA data right away when using tracks that are Tick based.

I don't even care if the preference is "on" by default to analyze all tick based Melodyne clips. I just want a way to turn it off. I know changing the track to sample based turns it "off", but it definitely feels like a workaround and another thing to have to keep track of.

[audiogamble]

Originally Posted by Dizzi45Z

Thank you for fixing what you have so far. Please continue to pursue getting this completely fixed for us.

Please also consider giving us a preference to choose whether all audio on a tick based track needs to be analyzed by Melodyne (when Tick based).

Since Melodyne requires the pauses to save ARA data which is so abrasive (freezing everything for a couple seconds). It is crucial to keep ARA data as low as possible. To do this, I always render the exact sections I want to use Melodyne on before I have it analyze the data. This new change is going to create TONS of ARA data right away when using tracks that are Tick based.

I don't even care if the preference is "on" by default to analyze all tick based Melodyne clips. I just want a way to turn it off. I know changing the track to sample based turns it "off", but it definitely feels like a workaround and another thing to have to keep track of.

I agree that constantly analyzing after recording passes is overly invasive and ends up just trading one problem for another. Thanks for trying to address the problem, but for now 2022.12 combined with non-ARA melodyne is a more seamless workflow for me in large sessions with multiple tempos. Happy to provide additional feedback and details if it’s helps inform future implementations of this feature.


Sent from my iPhone using Tapatalk