I’m currently setting up my techno/ambient live act with the OT and AR. While preparing loops from Ableton for the OT I run into a couple of Syncing Problems. (might also be the time stretching settings which I haven’t fully understood yet)
I have a lot of loops running on a multiple of 3 bars, 12, 24 etc. Running into looping issues on the OT and obviously on the AR when keeping 64 Bars as a base.
So I’m wondering if I should just move to the base of 48 (or inf.) and keep all loops in that length which both works for 4 bar and 3 bar loops.
I’m curious if somebody works like that or are there any problems with this? Thoughts? thanks!
inf can cause other issues with sample playback you may not want - also it depends on which loops are going to be the “dominant” loops, even if its only in your mind or as a compositional thing… meaning, the more important loop should probably define the multiple, so if that is one of the 3 bar loops, then go with 48 base… but if its a 4 bar loop, maybe leave it at 64 or whatever… and unless you are using direct jump, it will define your pattern transitions so thats also something to keep in mind
also you could use one shot triggers and set the loops at the playback step amount, that way they would loop on their own, detached from the sequencer - they would playback all the way then just loop themselves when they get to end point (set in audio editor)
thanks for the Info! I will try the 48 than… since the 4 bar will fit into that as well. but the one shot triggers sounding good as well. I think thats what im already using without realizing what its called
also slightly off-topic. Im also curious how people prepare their loops. I’ve seen that ableton and OT have a different interpretation of BPM, althought it doesnt seem to make a big difference, but might affect time stretching? e.g having 123 bpm samples from ableton loaded with 113 into OT as base speed, but having the global bpm of the OT project running at 123 bpm
You could use the OT’s sample editor to make the necessary corrections to the reported bpm, via the file or attributes page (can’t remember which one).
yes, but it actually runs at 123 bpm. I’m just not sure if the OT is stretching it from the 113 bpm already or if its just showing the wrong bpm.
if I turn it up to 123 from the 113 in that file or attribute page, it doesnt run in the original speed. might be just not using time stretch whatsoever and just play the sample as is, if thats possible.
i dont think they have a different interpretation… what do you mean by that?
i usually use ableton to process loops and get them very tight and clean and compressed and so forth, before i export to OT
havent had any problems… btw even if you put a bpm in the filename sometimes the OT wont see it (dunno why) and then you have to manually set the file bpm in the audio editor
Very interested in the filename-to-bpm automation. Is there an old thread where the specifics of this has been discussed? Perhaps you need to avoid certain characters in the filename or pad the bpm value with underscores for it to work reliably?
I create all loops in Live at 123 bpm, export via freeze and flatten because I have a lot of them. copy to my OT and all files have the bpm of 113, even though the file name says 123 at the end as well.
The loop length is mostly right, so it might just be a wrong display of the bpm in the OT. The project itself runs at 123 bpm of course. Maybe I can make a little video over the weekend. I cant find any screenshot of those settings.
but yesterday I found out that even those exported loops have a total messed up time stretching and bpm setting if I directly import them back to ableton… so maybe the freeze and flatten option is not the way to go.
how do you export you clips?
googling older or other platforms may be helpful, particularly as the OT is older than Elektronauts
Maybe something in this link to help, besides searches internally
no, you have to fix that - you can manually set the correct BPM for the file in the Audio Editor of the OT… you need to do that to get them to work properly when time stretching and so forth
yeah but the problem is that the loop is running at the correct bpm of 123 even though it says 113. if I put it to 123 in the Audio Editor, its way to slow (or fast, cant remember which way)
@avantronica
I was browsing through plenty of old threads and seems like it doesnt work for most people…
and I guess on the ableton side…
