I have my files named as NAME-KEY-TEMPO. The OT never actually reads the proper tempo. On top of that, when I fix it in the file attributes and SAVE SAMPLE SETTINGS, half the time it reloads the sample with the wrong tempo when I rock it in a new project. Any ideas as to what’s going on?
Did you save the files originally as 48k? Make sure you use 44.1 or it the OT will play the samples back at a strange tempo.
Everything is 16bit and 44k
Gonna bump this since I still can’t figure out what’s going on.
If you do a search for “bpm file name” or “bpm attributes” or similar, you’ll find dozens of threads about this…
Cheers…
I wasn’t sure if there was anything new about it beyond those threads.
What about it not reading the already entered in saved settings?
BPM is only able to managed in the arranger, from memory.
OT does not store BPM otherwise. Storing BPM in the filename is for you to use and remember. I don’t think OT uses this in any special way but could be wrong.
So when I save sample settings in the attributes, it doesn’t save the bpm info?
Im not sure, my OT knowledge is fairly basic, I will not comment further as i do not want to misinform you.
Hopefully someone with deep OT knowledge can assist you with your question.
It should be saving the bpm info. that’s weird. If you view the file over usb, does it have a matching .ot? is that file somehow locked or set to read only? maybe you could delete it if you don’t mind reapplying all the settings.
1 Like
Additionally, it might be that your timestretch settings for your track are turned on. double tap playback and set it to off (i think it’s auto by default) – sorry if this is completely off, but might help you think in the right direction, if that makes sense.
1 Like
there are .ot files and i do have timestretch on because i need to be able to match the song tempos to the master tempo. sometimes it works and sometimes it doesn’t. i’ll keep experimenting.
Sometimes, even when resampling internally, my OT still gets the BPM wrong (174.95 instead of 175) even when the machine is already set to that specific BPM.
OT only looks for BPMs within a certain range.
From the manual:
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.
FWIW I’ve never had much luck with putting the BPM in the filename, maybe because I usually work outside of the OT’s BPM range.
The BPM in file name NEVER works for me. All my tracks are labeled NAME-BPM and it never works. My BPMs range from 60-150. Should be within range of the OT.
oh wow, i never knew filename BPM was a thing. or maybe it isn’t anyway by the sounds of it. I’ve not had any problems in the past when i’ve used loops that i wanted to keep in time. Well, no problems that weren’t caused by the usual struggle when doing something with the OT that you aren’t immediately familiar with.
maybe you could upload a couple of examples and see if other people are having the same problem?
I have given up on it and have to do it manually… not sure why its simply not working.
I tried many different bpm’s and most of my samples run in “normal” speed when the bpm on the OT is wrong… e.g. I have my loops on 123 bpm and on the OT its always at 113 to make it play right. Maybe they just forgot the feature and forget to remove it from the manual 
Sounds like your importing 48k. 48/44.1x113=123…
Fwiw I’ve had the bpm in the filename work before, but I haven’t tested to see when in works and when it doesn’t.
Damn. I’ve literally never had it work. I have all my files at 44.1/16bit both to save space and to be read correctly.
I don’t mind setting the tempos, to be honest. The big bitch is when I save the attributes and they don’t get read when I load them into another project.
Bummer. If your saving settings and a .ot file is created, that should always be recalled, so don’t know what’s going on there. Are you shure your saving and loading the sample from the same place, audio pool vs project folder? Perhaps Rusty can help shed some light on this…