There is a disconnect for me on the very cool auto temp map creation method of dragging a clip in the timeline. I see that it is using Melodyne to create the map but the track does not actually turn into a region fx. So once the tempo map is created, can it be modified? How?
 
I also tried tempo creating by creating a region fx and just using the Melodyne interface create the temp map. I can view the graphic showing the tempo. I can also edit it but the tempo does not change once it is created.
 
What am I missing? How do I change a tempo map?
 
Thanks

Try dragging the clip back up to the timeline after editing the tempo map in Melodyne (as Region FX).

PeteL
Try dragging the clip back up to the timeline after editing the tempo map in Melodyne (as Region FX).

Unfortunately, that did not work. I really thought it would and seemed obvious, after you said it. :-)
 
I watched a video on Melodynes website and it looked so easy lol
 
I will watch more videos and re-read the help a few times.
 
Thank you for the suggestion!
 
--Edit--
BTW I should have added that I can change the actual tempo map in Sonar. The midi track (AD2 in this case) follows the changes but of course the audio track, that was used to create the tempo map, does not change. So I would have to do this in Melodyne and get them to sync. In Melodyne, nothing changes when I edit the map. Like I said above, I have more reading to do. :-)

I figured it out, partially anyway. I added Melodyne as a region fx to an audio track. Then in Sonar, I edited the tempo map. I right clicked the audio track again and selected "Follow host tempo". It certainly tried to follow it but it did not stay in sync. This was just a test. Perhaps a more subtle change would have worked better. 
 
Thanks

Hmmm ... that's odd.  That's the way I do it.
 
I really debated whether to actually post what's below, because I fear I may make things less understandable for you.  But here it goes:
 
I don't know which version you have, but I'm using Melodyne 4 Studio.  I just tried it my usual way to make sure I'm not insane and it worked.  I loaded a wav file into an audio track, dragged it up to the timeline, and saw the effects of the tempo detection.
 
Then to modify the tempo map, I created a region FX for the clip using Melodyne.  When the Melodyne window pops up in the MultiDock, I switch to Melodyne's Note Assignment mode, Show Tempo Map, and dragged one measure line in the tempo map in Melodyne way to the right, thereby decreasing the tempo.  Note that more notes (blobs) will fall now within that dragged, expanded measure.  Went back to Melodyne Edit mode (not sure if this is necessary), dragged the Clip back up to the timeline, and now the clip displays in the clip pane with the measure I drew out further looking "contracted", and the overall length of the clip decreasing by a measure or two.
 
How do you know it didn't work for you?  Did you check Sonar's tempo map and listing under Views?  Also be aware that the tempo mapping will not alter the speed of audio clip playback (the audio clip will sound the same as the original). One way of thinking about it is that Melodyne's Tempo Mapping allows you to slide the beat and measure lines around with the audio being the constant reference.  Depending on your adjustments, some beats/measures will be longer than others, and Melodyne will compensate tempo to make it so ... and thus the resulting audio remains the same.  In Melodyne, the result is manifested in the tempo map expanding and contracting.  Since Sonar uses an evenly spaced Time Ruler, the result is the playback line will speed up and slow down according to the tempo map (turn on the metronome for playback!), since the audio waveform has contracted/expanded but is still displayed on a linear time grid (MBT).
 
I hope I haven't done more harm than good in attempting to explain this.  It can be very confusing to explain.  It's better experienced by doing.
 
I don't recall exactly how I finally figured out the tempo mapping in Melodyne, but I'm pretty sure it was a YouTube video, but not from Melodyne.  The videos from individuals I found are often more helpful than the Melodyne produced videos.  I also found that it's important to understand the tools corresponding to cursor placement within the various locations in the Melodyne tempo plot.  It's not always straightforward.
 
Hopefully this helped in some respect without making matters worse.
 
Gulp ....
 
Press Submit ....

Hey Maxpower,  I just read your edit.  And yes, MIDI (and the metronome WILL follow the tempo map), but as I hopefully explained in my previous post, audio will not change.  If you're trying to change the speed of the audio, you may want to do it in the Sonar tempo plot with audio transients visible in the clips pane.  When you draw the change in tempo you'll see the time compression in shades of red in the audio clip, and expansion in blue, and the audio will speed up and slow down.
 
Oh, and remember to render using the Radius algorithm.  When you check it with the real time algorithm (groove clip), it will sound pretty nasty but still useful.  Just "Bounce to Clip after you're done to render.

PeteL, I followed your directions and the tempo map did change. What I had in my head is that if I created a tempo map from an audio track (so that a midi drum track would follow my poor timing) and then later changed the tempo, the audio would change to stay in sync. That is why I thought it wasn't working. 
 
Following your instructions, above, I was able to change the tempo map as you said it would.
 
Thank you for taking the time to spell it out for me :-)

maximumpower
Thank you for taking the time to spell it out for me :-)

No problem! :-). I'm glad I was able to help. I was really worried that I'd confuse things so much you'd be totally confused.

Now if you do want to change the tempo of the audio track, take a look at AudioSnap. Or you can just take the whole audio clip and just stretch it to where you want it (effectively increasing or decreasing the tempo). It will sound a lot better when you Bounce to Clip with the Izotope Radius algorithm after the stretch. For some types of content, the results are remarkably good. If your intent is to even out a performance that undesirably wanders in and out of tempo, a simple stretch won't do it. Editing individual transients would, but that can get quite tedious.