bpm reseting on 6.4 ??

[Dzz]

Hey everyone,
New to the board, hope this question hasn't been asked too many times, but I'm finding that I change the BPM in the transport window, but when I finish and save, and re-open, it has changed back to standard 120bpm.....thus throwing any midi parts in the song....
Running V.6.4
Any ideas?
Thanks all,
Darren.

[Bazzle]

Have you tried setting the tempo in the MIDI menu and do you have the conductor clicked?

[Rail Jon Rogut]

Manual tempos are saved in the session.. but if you switch the transport to conductor - it'll default to the conductor tempo of 120bpm. I suggest once you have the right tempo for a session.. create a tempo event/object in the conductor track (in the MIDI menu).

Rail

[tele_player]

Also - is Reason being used? If it is, the BPM set in the Reason sequence can change the BPM in the ProTools session. So, if the song has no tempo changes, set the BPM to same value in the ProTools session AND the Reason song.

[Dzz]

Yes, Reason has been running.....I'll try setting it to the same as protools,
thanks very much.
Darren.

[Roy Howell]

I must say, I've had this happen a few times myself in 6.4, most recently in a jingle, which had to be just under 60 seconds total. Initially, I had written it at 164bpm, but had to bump it up slightly to 168bpm for a perfect fit...and although I would save both Reason and PT at 168bpm upon closing the session, it would come back as 164bpm when I'de open the session again. Unfortunately, the first time this happened, I didn't notice the slight difference in tempo, and the singers sang it at the too-long 164bpm, so the audio was off at 168. I didn't notice because I was using all midi tracks as a reference at the time. So after they'de gone, I had to use Sound Shifter to pull the vocals in to 168 (although it worked great).
So my point is, it seemed not to have to do with Reason's bpm, since I was saving settings on both PT and Reason at 168 before exiting the session. So hmmm...just possibly a minor bug, maybe?
-Roy