Ableton Forum

Hello there. I've got a very interesting question about Ableton and my Launchkey 25...

I've got a DJ setup where I can smoothly transition between songs, but since they are different tempos, I have one of my knobs on my Launchkey mapped to my project tempo so I can smoothly transition into the correct tempo for the songs. I do have one issue however...

I have my knob limited from 105-174 BPM, but I get these gross decimal values such as 160.97 or 139.52 (these are just random numbers, but it's the same idea). Since I have all my clips warped so they are all in beat when I transition, even when I get as close as possible to the original clip tempo, I can hear warping artifacts and it degrades the quality.

I tried both Complex warping mode, and Complex Pro. Both sound the same.

This is a separate but related question, how can I get more resolution out of my pot values? Meaning, how can I get it to jump to numbers less, or how do I get more control out of the values?

Does any of this make sense? Thanks in advance

I think if you map the integer part of the tempo to an encoder with relative midi cc, that will stick to integer bpm values.
Not in front of my computer so apologies if it doesn’t work.

what you're seeing is the tempo range divided by 128 (the resolution of your midi knob)

so 105 > 174 is a range of 69, divided by 128 = 0.54
so your knob is stepping in increments of 0.54 (105 > 105.54 > 106.09 etc.)

chapelier fou wrote: ↑

Wed Mar 29, 2023 1:33 pm

I think if you map the integer part of the tempo to an encoder with relative midi cc, that will stick to integer bpm values.
Not in front of my computer so apologies if it doesn’t work.

I mapped my knob to the integer, but it still gives me decimal values. Any other ideas?

I feel like it should just automatically stick to integers if I've mapped it to the integer part....

Ni other idea than what I already said : use an encoder and relative cc mapping

chapelier fou wrote: ↑

Fri Mar 31, 2023 6:23 am

Ni other idea than what I already said : use an encoder and relative cc mapping

Sorry, I'm not sure what u mean by a relative CC mapping
hahah newbie here, can you tell?

They haven’t mentioned this explicitly but the knob you’re mapping has a resolution of 128 total. Or 0-127. So if your bpm is a range of 128 or 64 total, it Should go in whole bpm or half bpms.