So I have this month's latest Sonar Platinum and I'm trying to match a track's tempo to the project without much success.  I've tried matching the tempo by dragging a stem of the drums to the timeline.  I've also tried using a bounced down track of the entire project consisting of a vocal, guitar and drums but the calculated timing is off by quite a bit.  Sonar runs the calculation and creates a tempo map that changes measure to measure.  However, the resultant project tempo doesn't coincide with any transients or beat of the referenced track.
 
I've opened up a new project and tried the same with other finished mixes with the same results so I must be missing something.  I've tried clipping the track's beginning so they start right at beat one.  These are all basic 4/4 songs with high crest factor transients so I would think they'd be recognized properly. 
 
I have the most updated release of Melodyne 4 installed so I didn't install Melodyne essentials within Cakewalk's installer.  Could that be the issue?   For reference I'm using the exact steps shown in cakewalk's demo.  In the past I've had to change the project's tempo manually, measure by measure so I'd love to get this working.

Hi, and welcome to this forum. Have you tried to change the Melodyne algorithm? IIRC I used the percussive algorithm. I have successfully made a tempo map with freehand recordings, and I only have the Essential. The "bigger"versions should give you more options than the Essentials version. Hope it helps.
All the best.

Melodyne Studio and Editor allow making corrections to the detected tempo as in addition to choosing the detection algorithm, which is all you get with Essential - see Melodyne's documentation. I only have Essential, so I can't give you any more detailed guidance. But based on my few experiments with Essential, the default detection will often need tweaking. The most common issue I've seen (and seen other users report) is that the detected tempos are 2x what they should be. Other than that, it seems to do a reasonable job with tempos that just 'wander' a bit, but is likely to have issues with more variable/rubato material.

Gregkonji
So I have this month's latest Sonar Platinum and I'm trying to match a track's tempo to the project without much success.  I've tried matching the tempo by dragging a stem of the drums to the timeline.  

Hi gregkonji.
I could be mistaken, but when you drag a track into the time line,  you are creating a tempo map to match the projects tempo to that track, not the other way around. 
 
Not installing essentials if you have a more advanced version certainly should not be an issue. 
 
 

Zargg71
Hi, and welcome to this forum. Have you tried to change the Melodyne algorithm? IIRC I used the percussive algorithm. I have successfully made a tempo map with freehand recordings, and I only have the Essential. The "bigger"versions should give you more options than the Essentials version. Hope it helps.
All the best.

That's another issue I'm having.  When I do the steps of creating a melodyne region fx, changing the detection algorithm and then applying the tempo to the project, the tempo is reset to a static 120bpm.  The only method that at least does something is dragging the track to the timeline.    
 
The project was recorded to a click track but I'm wanting to use this functionality to further improve the timing grid so edits and adding virtual instruments are more inline with the recorded music.  Using this melodyne method is killing it altogether and I'm not seeing a doubling or halving effect.  Going through tens of measures I'm not seeing any transients coinciding with the newly created tempo. 

Gregkonji

Zargg71
Hi, and welcome to this forum. Have you tried to change the Melodyne algorithm? IIRC I used the percussive algorithm. I have successfully made a tempo map with freehand recordings, and I only have the Essential. The "bigger"versions should give you more options than the Essentials version. Hope it helps.
All the best.

That's another issue I'm having.  When I do the steps of creating a melodyne region fx, changing the detection algorithm and then applying the tempo to the project, the tempo is reset to a static 120bpm.  The only method that at least does something is dragging the track to the timeline.    
 

Did you drag the clip onto the timeline until it (the timeline) turns blue? This is how I have done it.

tenfoot

Gregkonji
So I have this month's latest Sonar Platinum and I'm trying to match a track's tempo to the project without much success.  I've tried matching the tempo by dragging a stem of the drums to the timeline.  

Hi gregkonji.
I could be mistaken, but when you drag a track into the time line,  you are creating a tempo map to match the projects tempo to that track, not the other way around. 
 
Not installing essentials if you have a more advanced version certainly should not be an issue. 
 
 

Yes my wording is wrong.  I'm trying to do what you just said.  I want to create a project tempo map that follows the recorded music.  The video demos I've seen are exactly what I'm trying to do.

Zargg71

Gregkonji

Zargg71
Hi, and welcome to this forum. Have you tried to change the Melodyne algorithm? IIRC I used the percussive algorithm. I have successfully made a tempo map with freehand recordings, and I only have the Essential. The "bigger"versions should give you more options than the Essentials version. Hope it helps.
All the best.

That's another issue I'm having.  When I do the steps of creating a melodyne region fx, changing the detection algorithm and then applying the tempo to the project, the tempo is reset to a static 120bpm.  The only method that at least does something is dragging the track to the timeline.    
 

Did you drag the clip onto the timeline until it (the timeline) turns blue? This is how I have done it.

I tried that procedure before creating the region but not after.  I clicked on the melodyne region and then selected from the drop down menu to map the tempo.  I'll instead try dragging the melodyne fx region to the timeline.

Try to drag the file / clip you want SONAR to follow to the timeline (until the timeline turns blue), and then drop. You should have the new tempo map calculated by Melodyne / SONAR.

Zargg71
Try to drag the file / clip you want SONAR to follow to the timeline (until the timeline turns blue), and then drop. You should have the new tempo map calculated by Melodyne / SONAR.

I tried this method after creating the melodyne region fx. With the Percussion Algorithm it resets the tempo to 120. With the Universal Algorithm the timing is somewhat ok the first 30 measures but the rest of the song is off by a full beat.