Melodyne assistant 2.1.0 >original/edited sync fail
- Thread starter FIXXXER
- Start date
The StabbinCabin
Member
Isn't there some sort of buffer setting that does that? I remember having the same issue when I was bouncing stuff between FL Studio and Cubase...
JeffTD
Senhor Testiculo
This is a common issue with Melodyne. Timing is not preserved perfectly, especially in large chunks (entire songs, for example). Your best bet is to use the standalone app (which helps with this a bit but does changing timing slightly) or to use another program (AT Evo, Waves Tune, etc).
i have tried all possible settings with no effect. the files and project settings
match also, i am really frustrated right now becuase the software does not work as it should and it was damn expensive.
time to write another hate mail...
i am running it in standalone already. i have also tried to edit small clips instead of the complete DI track. unfortunately it fucks up the timing in
both files.
it's also not just optical, i can hear the variation clearly. first i thought that it was just latency but aligning one part makes the other even worse.
btw. whenever i import a sound file into melodyne it "calculates" the wrong tempo.
i have a track in 260 half time, melodyne sees it as 139.833...which seems completely illogical and way to unprecise to me.
maybe this is what is causing the problems. i can set the tempo manually to 260 (130) but it doesn't seem to do anything at all
i have a track in 260 half time, melodyne sees it as 139.833...which seems completely illogical and way to unprecise to me.
maybe this is what is causing the problems. i can set the tempo manually to 260 (130) but it doesn't seem to do anything at all
