ok, this is what the manual says:
"The tempo guessing algorithm analyzes the sample filename for tempo figures, checking if the initial guess is off by a factor 0.5 or 2.0. The ”normal” BPM range the Octatrack uses to make its initial BPM guess is 85 BPM-170 BPM. If you have loops with tempos outside this range, it might be a good idea to put the BPM value in the filename. Typically, a 70 BPM loop is initially loaded as 140 BPM loop, but if the number 70 is found anywhere in the filename, the octatrack will use 70 BPM instead. Similarly, if 280 is found in the filename, the BPM of the sample will be 280. "
so it should read my sample that is 126bpm as 126 when that number is in the file name. Obviously numbers as low as 01, 10, 30, etc should be ignored, I’m sure they would have thought about that.
As it happens, my long samples (entire songs) have been prepared in Ableton to be a duration of exact multiples of 4, as this makes it easy to slice them correctly in the OT if needed.
I’ve been running OS 1.25D as it happens, and I see that I’ve missed a few updates by now, but no mention in the OS update log of any fix of this between 1.25D and the current OS 1.25H
Seems I need to get onto Elektron directly to sort this out, but it’s always worth running it by the community here first right?
I just thought anyone who has tried to DJ with the OT would be feeling the same problem.
By the way, the OT is AMAZING as a DJ solution, and particularly brilliant when used with a pair of turntables, as a third deck that can simultaneously be used to take on-the-fly samples from your records. If you haven’t tried this out you’re missing some fun!
Thanks for the input anyway. Lets hope 1.25I may be the one! Will report back 
