If you can't get it in melodyne try the RealBand ACW method.
Success!!A ton of thanks Musocity. I shut everything down, started from scratch and followed "Captain Gregor's" instructions and it worked like a charm.
A common occurrence (for me) in doing a new set of tasks with unfamiliar software (Melodyne) is not knowing what to expect at each step, clearly I bungled something up.
What these 2 tools did was analyze an arbitrary audio waveform to determine what the tempo in BPM is at each point in time; to no less than 4 decimal places! This "tempo map" can vary wildly throughout the song especially if the band is playing live. [I happen to know something about this from experience when playing in a church band and listening to a recording of us. Almost without exception, we would all speed up during the high-energy chorus and then slow down when the softer parts came. Playing to a clicktrack is not easy and our drummers couldn't do it.]
Back to S1: With the software having a knowledge of what the map is, the user can then alter it at will and the audio will then follow your new map. For me, I just want a static BPM for the whole song.
I don't know what you think, but I'm blown away by the sophistication of the algorithms that have been programmed to accomplish this.
Very impressive from a computer science perspective.
I wonder if at least a high-level description of how they pulled this off is available to the public. I don't think AI is involved in any way and I'm guessing that somewhere there is a public domain paper written by a grad student or musicologist/researcher on the subject.
Thanks again for the videos . . . this is good stuff!