Ableton / Melodyne Studio
Posted: Sat Jun 16, 2007 1:30 am
I've been experiencing many Ableton / Melodyne problems.
This is by far the most frustrating.
I'm on the latest version of Melodyne Studio 3.1.2.0 and Ableton 6.0.7.
We use Nuendo at work, I use Ableton for home use.
I experience none of these problems using Nuendo.
Firsly, I have melodyne set up on ableton audio track 1, I've sent the audio on that track (a pretty simple guitar loop) to melodyne and melodyne is now set to "playback" mode. Easy stuff. (I just want to change the pitch of that guitar loop now on the fly using melodyne).
Secondly I have a MIDI track on ableton track 2. I'm sending MIDI to melodyne on this track to control the pitch of audio its now playing back. I'm doing this via MIDI Yoke NT channel 3 port 1. melodyne is set up to monitor the incoming MIDI on the above port and transpose the audio on track 1. These are the options I have ticked in the melodyne MIDI options to do this:
MIDI in transposes track from C3=0
MIDI channels to track numbers
Here's a screen print.
http://www.picoodle.com/view.php?srv=im ... 58d3ec.jpg
Now its about time someone REALLY looked into this issue, cause it seems to cause problems ACROSS the board in all kinds of plugins/rewire and why Ableton really can't be considered a major contender at the moment with regard to being a full blown sequencer. It's a major bug and a real pain.
1) It all works well and good when I play the track back. HOWEVER, when I come to MIX DOWN, the pitch changes I am sending to melodyne via MIDI Yoke NT channel 3 port 1 are now (for some reason) completely ignored and all I hear is the sound coming from melodyne but in the original pitch.
2) I have to press stop on the transport on Ableton AND melodyne to reset the track counter position MANUALLY to zero, ready for the next shot. Ableton doesn't seem to be bothered about resetting track parameters on stop (it only does this "on transport start"). To "fudge" this I've had to start on bar 2 and reset melodyne to the original pitch by sending a C3 note (See screen print). This resets the pitch from the previous pitch it was when I stopped play on the transport. If I didn't do this the pitch would be set at whatever the pitch was when I pressed stop on the transport. It seems I'm always having to compensate for an 1/8th note lag between the two applications.
Point 1 is just not on.
Point 2 is "OK I can live with that in playback mode, but I really hope it doesn't do it at mixdown - (assuming I could get it to mix down with pitch changes - see point 1)"....
None of these problems with Nuendo 3 at work and a substantially slower computer than the one I'm using at home.
Anyway, if anyone has any kind of solution for this behaviour it would be much appreciated. This feature in melodyne is very useful one for making changes on the fly "without" having to constantly switch between applications to make pitch changes.
Cheers, Davin.
PS.
1) Point 2 is a timing issue obviously, when I press stop on the Ableton transport and switch to melodyne, I notice the transport on melodyne is still at the Bar where I stopped it. This means that when I press play on the Ableton transport, melodyne (in the background) has to reset its transport position, reset its pitch information AND ONLY THEN can it start, this (in audio terms) causes a substantial delay in the melodyne playback start (i'm already an 8th note into the Ableton track before melodyne actually starts playing). I cannot do anything to alter this behaviour as a user other than start on Bar 2. Celemony or Ableton need to do something to change this. I notice exactly the same behaviour in Reason using ReWire because of this exact same problem. In Nuendo when I press stop on the transport, the melodyne transport is also reset back to bar 1 so its ready to go for the next time. Once this is resolved maybe melodyne should have some form of MIDI read ahead or (more realistically) plugin delay compensation to account for the OTHER "pitch" warping anomalies caused by these delays both at the start of the track and when pitch is changed during playback. Again, even during playback I notice an 8th note difference between me sending a MIDI pitch change signal and the pitch in melodyne actually changing and being sent back to the ableton audio track. What's more annoying is that sometimes there's a delay on one of the pitch changes and sometimes their isn't (probably because its already buffered the change previously in memory). That's an impossible situation to account for as an End User.
Anyway... that's obviously for Celemony (I don't mean to bug your forums with their issues), but I would imagine you (Ableton) have more power to request these changes than I would. I just want to use the stuff without having to consider these issues in the first place.
This is by far the most frustrating.
I'm on the latest version of Melodyne Studio 3.1.2.0 and Ableton 6.0.7.
We use Nuendo at work, I use Ableton for home use.
I experience none of these problems using Nuendo.
Firsly, I have melodyne set up on ableton audio track 1, I've sent the audio on that track (a pretty simple guitar loop) to melodyne and melodyne is now set to "playback" mode. Easy stuff. (I just want to change the pitch of that guitar loop now on the fly using melodyne).
Secondly I have a MIDI track on ableton track 2. I'm sending MIDI to melodyne on this track to control the pitch of audio its now playing back. I'm doing this via MIDI Yoke NT channel 3 port 1. melodyne is set up to monitor the incoming MIDI on the above port and transpose the audio on track 1. These are the options I have ticked in the melodyne MIDI options to do this:
MIDI in transposes track from C3=0
MIDI channels to track numbers
Here's a screen print.
http://www.picoodle.com/view.php?srv=im ... 58d3ec.jpg
Now its about time someone REALLY looked into this issue, cause it seems to cause problems ACROSS the board in all kinds of plugins/rewire and why Ableton really can't be considered a major contender at the moment with regard to being a full blown sequencer. It's a major bug and a real pain.
1) It all works well and good when I play the track back. HOWEVER, when I come to MIX DOWN, the pitch changes I am sending to melodyne via MIDI Yoke NT channel 3 port 1 are now (for some reason) completely ignored and all I hear is the sound coming from melodyne but in the original pitch.
2) I have to press stop on the transport on Ableton AND melodyne to reset the track counter position MANUALLY to zero, ready for the next shot. Ableton doesn't seem to be bothered about resetting track parameters on stop (it only does this "on transport start"). To "fudge" this I've had to start on bar 2 and reset melodyne to the original pitch by sending a C3 note (See screen print). This resets the pitch from the previous pitch it was when I stopped play on the transport. If I didn't do this the pitch would be set at whatever the pitch was when I pressed stop on the transport. It seems I'm always having to compensate for an 1/8th note lag between the two applications.
Point 1 is just not on.
Point 2 is "OK I can live with that in playback mode, but I really hope it doesn't do it at mixdown - (assuming I could get it to mix down with pitch changes - see point 1)"....
None of these problems with Nuendo 3 at work and a substantially slower computer than the one I'm using at home.
Anyway, if anyone has any kind of solution for this behaviour it would be much appreciated. This feature in melodyne is very useful one for making changes on the fly "without" having to constantly switch between applications to make pitch changes.
Cheers, Davin.
PS.
1) Point 2 is a timing issue obviously, when I press stop on the Ableton transport and switch to melodyne, I notice the transport on melodyne is still at the Bar where I stopped it. This means that when I press play on the Ableton transport, melodyne (in the background) has to reset its transport position, reset its pitch information AND ONLY THEN can it start, this (in audio terms) causes a substantial delay in the melodyne playback start (i'm already an 8th note into the Ableton track before melodyne actually starts playing). I cannot do anything to alter this behaviour as a user other than start on Bar 2. Celemony or Ableton need to do something to change this. I notice exactly the same behaviour in Reason using ReWire because of this exact same problem. In Nuendo when I press stop on the transport, the melodyne transport is also reset back to bar 1 so its ready to go for the next time. Once this is resolved maybe melodyne should have some form of MIDI read ahead or (more realistically) plugin delay compensation to account for the OTHER "pitch" warping anomalies caused by these delays both at the start of the track and when pitch is changed during playback. Again, even during playback I notice an 8th note difference between me sending a MIDI pitch change signal and the pitch in melodyne actually changing and being sent back to the ableton audio track. What's more annoying is that sometimes there's a delay on one of the pitch changes and sometimes their isn't (probably because its already buffered the change previously in memory). That's an impossible situation to account for as an End User.
Anyway... that's obviously for Celemony (I don't mean to bug your forums with their issues), but I would imagine you (Ableton) have more power to request these changes than I would. I just want to use the stuff without having to consider these issues in the first place.