MOTUnation.com

I have encountered some pretty big problems with Melodyne 4 (plug-in) in DP 9.1.

Here are the issues:

1. Once Melodyne has processed a track, with the Melodyne window open, start and stop playback,
Melodyne's wiper continues to scroll forward 2-4 bars, like it doesn't "know" playback has stopped.
2. Repeated starting and stopping playback intermittently causes "beach ball" and I lose control of DP's transport until the beach ball stops.
3. A MIDI file exported from Melodyne does not line up with my sequence anymore. It's off by anywhere from 2 to 5 bars and an unpredictable number of beats and ticks.

What I think may be one of the causes is that, due to DP 9.1's reduced latency, Melodyne sees a buffer of 512 (the minimum needed for Melodyne to work) as 256. I am going to try setting the buffer to 1024 today, as I have another set of vocals I have to process through Melodyne. I will report back on that experiment.

I have sent tech support emails to MOTU and Celemony.

Please no "I told you so's"...

Ok, I believe I have found the cause of the issue. I set DP buffer to 1024 - Melodyne works
fine. No stutter, no audio dropouts, no beach balls, no wiper continuing to scroll after stopping playback. So this leads me to believe that DP's reduced latency is, in fact, making Melodyne "think" that a buffer of 512 is really 256, and Melodyne struggles at the 512 buffer.

For those of you who use Melodyne, you know that 512 is the minimum buffer that Melodyne needs to work. I recommend setting your buffer to 1024 to do any work with Melodyne for now.

On to the MIDI issue - I tried starting a new project, recording a MIDI kick drum on an external synth (Motif), then recording the result as audio, and then processing that track with Melodyne. This time I did not "select all" notes within the Melodyne window, I went directly to the "Save as MIDI" menu option, and then imported the resultant MIDI track back into DP. The MIDI was late by 20 ticks, but it was consistent, so I shifted it earlier by 20 ticks and it lined up with the audio.

This may have something to do with hardware latency - some synths and drum machines respond differently to incoming MIDI. But at least the MIDI now is not wildly out of sync, nor is it inconsistent. Its actually working like it did in DP 9.02.

For those of you who use Melodyne, you know that 512 is the minimum buffer that Melodyne needs to work. I recommend setting your buffer to 1024 to do any work with Melodyne for now.

Good to know. Thanks!

FWIW, I just received a reply from Andrew at MOTU (damn, I love MOTU's tech support!).
MOTU can reproduce the issues with Melodyne4, are aware of the issues, and are working to address them in the next update.

Thanks for the useful info on Melodyne. I had similar problems and rather than try to figure it out, I've been using it stand alone.

I've noticed some problems recently with Melodyne 4 in DP 9.01.

Auto scroll is intermittent, at best.

And a project that I moved to another drive seems to be about 8 bars off. IOW, DP might be showing bar 100 where I activated Melodyne but Melodyne is showing the material at its bar 92.

The original unmoved project seems to be OK??

Buzzy


Sent from my iPhone using Tapatalk

Having a crashing issue with multiple instances of Melodyne 4 running within DP 9.1... got a ticket into Celemony. If I disable all except one instantiated track things work.

Jumping around to different places in the sequence will bring it down every time with more than one instantiated track.

Digging away at it...

9.12 fixed my issue... thanks MOTU!!!