Hi SONAR forum!
 
There's a project I'm working on where Melodyne seems to have gone out of sync since I upgraded to Melodyne 4 Studio a few days ago. The Melodyne timeline seems to be a couple hundred msecs ahead of the actual SONAR timeline, i.e. the blobs hit the ruler before they are heard. It seems fine in all the other projects I've checked!
 
Suggestions?
 
Sven

Sorry Sven.  I've not seen that one.
 

try turning all FX off by pressing the FX button before creating a Melodyne clip.  that seems to be the current workaround for Melodyne timing issues

Hmmm. I just upgraded to Studio 4 Wednesday and I am experiencing this timing issue. I did turn off the FX but the sync is definitely off kilter. Awaiting additional ideas.

Do you perhaps have a tempo change mid-clip? Melodyne often gets confused by this. It will also get off over time on very long clips, probably due to rounding the bpm value. I stick to short clips with Melodyne, often splitting longer clips when necessary, usually to avoid including a tempo change.

bitflipper
Do you perhaps have a tempo change mid-clip? Melodyne often gets confused by this. It will also get off over time on very long clips, probably due to rounding the bpm value. I stick to short clips with Melodyne, often splitting longer clips when necessary, usually to avoid including a tempo change.

Hello Bit - enjoyed your posts for many years!
 
Nope, no tempo changes - but I will double check just to make absolutely sure. I agree with sticking to shorter clips.

wetdentist
try turning all FX off by pressing the FX button before creating a Melodyne clip.  that seems to be the current workaround for Melodyne timing issues

Thanks, turning off master FX did indeed sync me back up! And I identified the culprit as Ozone 7 running on the master buss! Furthermore, bypassing the different modules inside O7 did nothing, while deleting them one by one gradually reduced the offset until Melodyne became sync'd again. I'm pretty sure this was not the case with the Melodyne 2/Ozone 5 combination I ran for years (seems like I would've come across it)! 

Apparently it's not Melodyne that gets out of sync with SONAR, but rather the other way around. Ozone does incur a great deal of internal latency. I've always wondered how Melodyne could know about PDC on busses - maybe it can't. 

I have just noticed the same problem. It seems to have started in the last month or so for me. I have tried shorter clips too but it still is an issue when running Melodyne 4 as a region FX in Sonar Platinum. Work perfectly in the past.
Makes editing on the fly almost impossible due to the melodyne time line running ahead of Sonar's. 
 
Also experiencing some delay now between hitting the stop button (with the mouse) on the transport console and the track actually stopping. Feels like I just got sent back to the sync days of the 90's. Puzzling - what changes are causing this?
Mike