Tempo in the file name

[William_WiLD]

Octachainer

OctaChainer v1.2

OctaChainer is a Windows and OS X GUI tool for creating sample chains and slice data for the Octatrack and Analog Rytm. It allows you to arrange samples in the order you want, and then creates a chained .wav file and corresponding .ot file. [image] New in v1.2 Three slice modes: Normal - creates a compact sample chain and a slice for each source sample. Grid - evenly spaced samples. This mode does not create an .ot file. Mainly intended for Rytm users. Use the "Add silent slice" button to…

Don’t sure it will be helpful in your scenario thought …

[Fisto]

as william said…it’s a tool to make Samplechains or Slice-Chains.
I use it to make CUEs for my Dj-Tracks which are all 6-7 minutes long.

They stay right on grid assuming that they are cropped correctly before import. 1.
make sure that they play along with the click in your daw of choice.
2. Cut them up in parts (thinking of intro, build Up, drop, break, 2.Drop. etc…how you like it)
Export those parts as individual files.
3. Load up Octachainer (Octaedit shoud work too, but have not tried this yet for this purpose) and fill it with the “track-part-fragments” from before. Set the tempo in Octachainer to the track-tempo and export (here i put the bpm also to the end of the filename).
4. Load the sample+ “.ot” file into your audiopool. Now you have traktor-like loopable Cues/Slices and can DJ on grid.

Not sure about auto-tempo-mapping of OT for long loops. But in my other 76bpm-case i just imported cropped samples directly into OT with 76 at the end of the filename, and OT recognised 76bpm and put that automatically into the attributes.

[Oblique]

Hi

just want to see what is going on here

as you can see from screenshot all samples have the bpm in the title. however the bpm is not locked to the correct value and you can see on the right side, the first one is correct but the others are all over the place?

How can I fix please?

many thanks

[OverneathTheSkybridge]

Was just doing research wondering the same thing and came across this old thread… bumped! Does anyone know whether the Octatrack reads metadata on tempo info that some DAWs can encode into WAVs? Also wondering if having the BPM in the file name aids the OT in determining tempo?

If Elektron signalled a standard for us to use like “filename 120bpm.wav” where the bpm value is always followed by “bpm” and had the machine seek that string of characters out for BPM data that would seem like an easy fix.

[Blasted_pingin]

More than one time i had loops from an official pack labelled as 80 bpm to realize they were not.
At first i cursed the OT before making a quick calculation in terms of length and the OT was right…

Not sure the guess would be right if the loop was in 7/8 though