the new elastic tempo identify -wtf !?!

[dominikkolendo]

i've been struggling with this since 7.4 and have only found the same advice on forums as in the PT reference guide.

all i am trying to do is sync the protools tempometer to an audio file i imported.
i have tried identify beat but i must be missing something... this has to be a simple procedure, i know it does, so maybe i am overthinking it.

i highlighted the first 2 bars, hit ctrl+i, and it just gives me the 120 default tempo again. with beat detective i can split up the audio into correct bars, but i dont need to do that, that's not the "official" method anyways.

can someone give me a step by step of what i am missing here?
i know this must be a fairly common problem, but i just cant figure it out.
it must be something really tiny and basic and i know i will slap my forehead when i figure it out, but as of right now i am too frustrated to work on any audio.

thank you so much in advance!

[audiogeekzine]

you need to turn on the tempo ruler (conductor on in transport)
if the selection starts on bar 3 and its 2 bars long it ends on 5. Make sure your identify beat selections match this.

[dominikkolendo]

yes, i have "him" on, i have view in samples i have 2 bars selected with slip mode and in identify beat i have the correct start and end points, still 120.

[audiogeekzine]

and the song is indeed not in 120 bpm?

the main timescale view should be in Bar|Beat to see the correct grid.

[dominikkolendo]

the audio i imported is NOT 120, it's about 108... however the "new file" defaults to 120, so protools thinks it is 120 right now... all i want to do is change the main tempo ruler to the 108.xx, and find out what the (about)108 really is via identify beat hopefully

[dominikkolendo]

ok, i see conceptually what is going on...
pro tools is telling me the 120 +/- .1 figure based on the selection i highlight, as if it doesn't actually read the audio... if i use beat detective it will split up the audio at the correct beat markers but still give the 120ish figure for all bars.
i am SURE the file is about 108 as doing the tap tempo along with teh music verifies this approximate figure.
i have the view in samples, i tried going back and forth between ticks jsut in case, i've reread teh reference guide step by step again... oivey.

[audiogeekzine]

you have the view in samples? Does not compute.
The tracks are in samples or ticks?

Tracks can be in either ticks or samples.
-In samples changing the tempo only effects the grid lines
-in Ticks, changing the tempo moves the start each region to stay in the same spot relative to its bar|beat position.

The main timebase can be either Min:Secs, Bar|Beat, or Samples
This is what you choose for your grid lines, nudge values and counters.
---------------
OK, so you know how to do tap tempo so use that.

Take bar 11, drop in a timechange (+ sign on the tempo ruler) and set it to 108.

Tab to transient to get to the first downbeat of the song.
push A to trim the left of the region.
grab the region and snap the start to bar 11
trim the left edge of the region back to its original length.

[dominikkolendo]

in the workspace window it analyses it as about 108!
how can i conform the session tempo to match my files?

[dominikkolendo]

sorry, i meant to say i went back and forth between ticks and samples to see if it would affect the measurements (which i have in bars/beats)

where did you get bar 11 from?
you lost me

yes, i can tap tempo but that is obviously not how to analyze audio, i cant do this for the rest of my protools career when there is an identify beat function that i simply cant figure out.

[dominikkolendo]

and thank you so much for your help, i just figured out the stupid mistake i was making on another thread.