I think I have found the bug that causes Melodyne lost data! (FIXED)

[prorenzo]

Originally Posted by ferropop

I'll put this here because it's all Melodyne people reading -- I've been having MADDENING issues with crossfades not playing properly!

Especially with lots of splits/takes, the crossfades will randomly click/blip and sound like either a bad crossfade or none at all. If you hit stop and revisit the click/blip area, it'll play fine! If you let it keep playing then Some Other Random Crossfade will then click/blip! Stop and revisit that one, that That one is now fine!

In a project with potentially thousands of crossfades, this is lunacy

Devs is there some interaction with buffer settings and ARA/Melodyne integration not playing nice? Anything we can try? Something related to Anticipative FX?

Yeah I am experiencing the same issue now. I guess the workaround will be to render the take without melodyne engaged first, and then plop melodyne on top. I just learnt it the hard way as I put melodyne on the track with the multiple stitched vocal takes and having the same issue as you. However if I were to render it and copy over the melodyne, Melodyne will forget all the edits you made and you have to start tuning from scratch again!

[ferropop]

Originally Posted by prorenzo

Yeah I am experiencing the same issue now. I guess the workaround will be to render the take without melodyne engaged first, and then plop melodyne on top. I just learnt it the hard way as I put melodyne on the track with the multiple stitched vocal takes and having the same issue as you. However if I were to render it and copy over the melodyne, Melodyne will forget all the edits you made and you have to start tuning from scratch again!

Yeah this completely defeats the purpose of ARA also, which is to let you hot-swap the takes in realtime. Having to render everything down like this, you might as well not use ARA honestly.

[Burnsjethro]

"Yeah I am experiencing the same issue now. I guess the workaround will be to render the take without melodyne engaged first, and then plop melodyne on top. "

That's not a bad idea to render the track then mute the original track.rather than glue it.

[ferropop]

Originally Posted by Burnsjethro

"Yeah I am experiencing the same issue now. I guess the workaround will be to render the take without melodyne engaged first, and then plop melodyne on top. "

That's not a bad idea to render the track then mute the original track.rather than glue it.

You lose 98% of the purpose of ARA doing this though.

My workaround has been to render to a new track, and created a script that lets you razor edit a section of the original takes and it "bumps it down" to the rendered track...a sort of half-baked middle ground where things Mostly sound ok because there's less crossfades, and gives you Some freedom to audition takes when needed.

...but by no means a solution.

[ferropop]

This is a bit ridiculous to have to run though just because of clicky crossfades.

[ferropop]

Originally Posted by prorenzo

Yeah I am experiencing the same issue now. I guess the workaround will be to render the take without melodyne engaged first, and then plop melodyne on top. I just learnt it the hard way as I put melodyne on the track with the multiple stitched vocal takes and having the same issue as you. However if I were to render it and copy over the melodyne, Melodyne will forget all the edits you made and you have to start tuning from scratch again!

We should continue at the other thread -- this one is titled "FIXED" and might not get the devs' attention.

https://forum.cockos.com/showthread.php?t=266411

[maxdis]

So this bug has really been "FIXED" as in the title? I'm using Reaper 6.42 with Melodyne Essential (latest version) and I'm losing edits all the time, wasting hours of work. Upgrading to Reaper 6.70 will solve this? I'm in the middle of a big project so I'd prefer not to upgrade, but if it would solve this huge problem I'll do it gladly.

[ferropop]

Originally Posted by maxdis

So this bug has really been "FIXED" as in the title? I'm using Reaper 6.42 with Melodyne Essential (latest version) and I'm losing edits all the time, wasting hours of work. Upgrading to Reaper 6.70 will solve this? I'm in the middle of a big project so I'd prefer not to upgrade, but if it would solve this huge problem I'll do it gladly.

It has absolutely not been fixed, I'm also losing edits regularly.

Usually when doing things like :

-trimming edges of items with Razor
-duplicating items with razor (the duplicates sometimes will not have the edits)
-recording onto a track that has Melodyne edits already (later on the track on empty space, previous edits disappear)
-adding/removing time to the project
-inexplicably

[maxdis]

Originally Posted by ferropop

It has absolutely not been fixed, I'm also losing edits regularly.

Usually when doing things like :

-trimming edges of items with Razor
-duplicating items with razor (the duplicates sometimes will not have the edits)
-recording onto a track that has Melodyne edits already (later on the track on empty space, previous edits disappear)
-adding/removing time to the project
-inexplicably

This is really bad, I'm trying to render/glue the stems just after the edits (and this alone is a workflow killer) and often Melodyne forget the edits while rendering, so I have to check again the rendered file with Melodyne to see if the notes are in tune. And if I need to change something? Total nightmare.