pharohoknaughty
I must be a special case, when I track the band I record virtual instruments as MIDI tracks and also have audio tracks. We don't use a click track, so the timeline has no relevance to the beat. Since the tempo map changes when you apply Melodyne, the relative midi notes are moved to the new tempo instead of being re-calculated in a manner that preserves the tempo. Any midi track is now at the wrong tempo. I think the only solution is to bounce the midi clips to audio, but then you loose the ability to edit the MIDI.
Unless I am doing something wrong, which is often the case, this feature has value only for projects with no MIDI clips.
Hi! I don't think you're doing anything wrong per se. Remember, Melodyne does not affect the audio or MIDI data (with regard to tempo). It instead rearranges the beat and measure lines so that they match the musical content of the source track (the track you dragged up to the timeline). Since Sonar displays the beats in the timeline in a linear evenly spaced fashion, the effect of the tempo map is manifested by the speed at which the playback cursor moves and changes with tempo changes. The source audio will sound exactly the same as before, even if you draw in a crazy tempo map going from 20 bpm up to 200 bpm. Try it with a simple audio track.
Likewise, Melodyne doesn't change MIDI data. So, if you had MIDI data recorded
before you applied the Melodyne tempo mapping, since the MIDI data remains the same (notes will play at their previous times, not at the new tempo), it will be out of sync with the tempo and therefore audio tracks.
I'm not sure what can be done about this, as I haven't had to tackle this situation yet. What you need is some way to stretch the MIDI tracks to abide by the new tempo map. Perhaps someone more knowledgeable than I knows how to do this.
Good luck with it!