Yeah that’s a good idea… I haven’t tried to split the file yet…
But still - if I told OT that the sample is 174 and the project tempo is 174, why would it timestretch? Why would the same sample sound differently on OT and on the computer even the timestretch is off? 
try using a different program to convert the mp3.
audacity may be of use, try doing a 16bit and a 24bit version.
1 Like
I suggest verifying the sample rate using a computer one way or another…
On a Mac in finder you can click “get info” I think it is and a window will pop up that says…
It’s the only thing that really would make sense…
The OT can tell you too in the place where you load samples to the slots…
There’s a little face that will smile if it’s right and have a straight line mouth if it’s not…
1 Like
Sounds like a 48khz file. Played slower.
1 Like
yes - although the Digitakt and AR will handle 48khz natively, OT only goes to 44.1khz
whereas Nigel’s guitar amplifier goes to 11.
2 Likes
Just checked - OT sees both files as 44.1k, 24b, 2ch. Even the source files are 44.1k.
Did anyone hit the same issue with the project I uploaded?
This is getting more and more weird… I did another round of experiments and created a new empty project.
Into this project, I loaded only one file and assigned this file to the static machines on T1 and T5. I changed no setting of these tracks but only set them to play free so I can trigger them manually… Guess what - the same file sounds different on T1 and T5… On T1 I hear a slight timestretch and the sample is pitched differently. On T5, it plays as expected. If I load the same sample to T2, it also plays nicely and the pitch and the overall sound is the same as on T5 - its only and always T1 having this issue…
Even if I load the project I uploaded here earlier and assign the same sample as in T1 to T2, it works fine…
I am not getting it… - Am I hitting some bug? Is there any setting in the OT which I could possibly changed, causing that the T1 sounds different even on a clean project?
Seems I am an idiot ladies and gentleman! The correct answer is…tadaaaaa…p-lock!
Thanks for all your input its really appreciated and sorry for taking your time with such an user error… Lesson learned 
5 Likes
For a newbie getting used to the OT. Can you explain how p-lock can affect imported sample rate for future reference. Cheers!
2 Likes
I had one trigger on each track which fires the sample when I start the track.
Even all the parameters were set as expected, I realized that it might be that one trigger having different settings so what I did was I enabled the step recording mode and held the trigger pressed down. It was immediately obvious that the trigger in one of my projects was pitched up and in the second project (the one I uploaded here earlier) had a different rate (like 57 instead of 64).
tldr; any of the parameters you can set in any of the pages can be set per-trigger. In the step record mode hold the trigger pressed and you will see
(manual page 67, section 12.5)
2 Likes
Thanks. Good to know.
P-locked trigs are flashing, if that helps spot them in situations like this
1 Like
An idea about perfect tempo like 123.456 bpm with Octatrack :
Load a sample with 123.456 bpm in a Pickup machine, as master sync.
Didn’t tried. Just do it! 
1 Like
I got the same problem, I was absolutely certain that my sample had a sample rate at 44100 hz turned out it was 11000.
I basically consolidated (a kind of export) it in ableton with the destination tempo I wanted to work with on the OT and it fixed the problem after importing it. Hope it help those who have the very same problem.
How about loops exported to have specific BPMs like 110.03, is it possible to edit the sample’s BPM to have something so fine? Or is there a naming format I can use that the OT will assign its real BPM to it automatically?
When I edit the BPM in ATTR (and hold FUNC) the values it jumps by are sometimes in increments of 0.04bpm and sometimes 0.05bpm, seems random, so I can’t set its real BPM. I suppose I gotta go back and export them all to whole numbers?
Edit: Oh god, I just found this, so even if I manage to set the sample to the right BPM it’s not correct 
You can set loops accurately with sample values, not Attributes Tempo.
The problem is to sync a loop not matching real sequencer tempo values I mentionned.
The Untold Truth About Octatrack Tempo
1 Like
I’d like to understand why you’d need such a tempo on OT, unless you don’t use the sequencer and loop at that tempo…
0.04166 increments precision doesn’t suffice ?
Can you hear a timestretch difference between 110.03 and 110.04166 ?
1 Like
Ok it clicked after reading your post again. After realising how it works now I’m gona stretch my loops to whole bpms in Ableton.
I’m not sure if I’d hear the difference but here’s an equivalent scenario, I’d never set Ableton’s master bpm to let’s say 100.06bpm if my loops are playing unaltered at 100bpm just cuz I’d hardly notice, I’d rather set it correctly. So that’s why I’m happy to go back and stretch them so the OT plays them back bang on, feels icky otherwise.
1 Like
Better than using OTs timestretch.
1 Like