FL Studio 20.6.2 slow tempo automation

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Hey All

Im working on a project where I need to start out at 20 BPM and then switch to 45 BPM. As far as I´ve been able to find out, it is not possible to automate the tempo below 60 BPM, unless you go into the automation settings, and change the minumim value? This technique seems very problematic, and I find it hard to adjust the min / max value knobs in the automation settings panel, so that I can fit the tempo to the exact BPM I want.

Does anyone know a more straight forward workaround?

Thanks :)

Post

You can input exact values (scaled between 0 and 1) at each node in an automation clip via right click and choosing to "Type in value". This could also be done as a mapping formula to restrict your automation clip so that it only operates between the required values. Then you would have 20 BPM as 0 or 0% and 45 BPM as 1 or 100%.

So...

20 BPM = 0.01953125
45 BPM = 0.068359375

"input*0.048828125+0.01953125" will give you full automation clip range between 20 and 45 BPM.

Post

Unaspected wrote: Tue May 05, 2020 2:49 pm You can input exact values (scaled between 0 and 1) at each node in an automation clip via right click and choosing to "Type in value". This could also be done as a mapping formula to restrict your automation clip so that it only operates between the required values. Then you would have 20 BPM as 0 or 0% and 45 BPM as 1 or 100%.

So...

20 BPM = 0.01953125
45 BPM = 0.068359375

"input*0.048828125+0.01953125" will give you full automation clip range between 20 and 45 BPM.
This probably sounds stupid, but I have no idea how you came up with those numbers :-? But thank you very much! Highly appreciated :tu:

I wonder why Image Line made something as simple as tempo changes overly complicated :o
Last edited by 218 on Tue May 05, 2020 3:17 pm, edited 1 time in total.

Post

@Unaspected , You would still have to adjust the min/max values in the automation clip settings right? Typing in the values you wrote does not seem to work.

Post

218 wrote: Tue May 05, 2020 3:15 pm
Unaspected wrote: Tue May 05, 2020 2:49 pm You can input exact values (scaled between 0 and 1) at each node in an automation clip via right click and choosing to "Type in value". This could also be done as a mapping formula to restrict your automation clip so that it only operates between the required values. Then you would have 20 BPM as 0 or 0% and 45 BPM as 1 or 100%.

So...

20 BPM = 0.01953125
45 BPM = 0.068359375

"input*0.048828125+0.01953125" will give you full automation clip range between 20 and 45 BPM.
This probably sounds stupid, but I have no idea how you came up with those numbers :-? But thank you very much! Highly appreciated :tu:

I wonder why Image Line made something as simple as tempo changes overly complicated :o
You're welcome. :)

If you right click any parameter in FL Studio, you can learn its value by copying and then pasting to see it. With third party plugins you will need to either use the browser to work with parameter values or use "last tweaked".

It would be nice to learn parameter values via mouse over events but that functionality hasn't been added yet.

Not sure whether I would say BPM changes are complicated but they certainly are fiddly without either inputting values or restricting the output of an automation clip by first scaling and shifting as we did with my example.

218 wrote: Tue May 05, 2020 3:16 pm @Unaspected , You would still have to adjust the min/max values in the automation clip settings right? Typing in the values you wrote does not seem to work.
You will need for the automation clip to work with it's full range of min/max values for the above formula to operate correctly. Otherwise you are scaling the output once more.

Post

@Unaspected Thank you once again! :tu: I set the min/max to its full and its now working like a charm :)
I noticed that using this function will change the min/max value for all automation clips. I might be overlooking something, but would it not be better if IL made it possible to do this individually on automation clips?

Post

218 wrote: Tue May 05, 2020 3:58 pm @Unaspected Thank you once again! :tu: I set the min/max to its full and its now working like a charm :)
I noticed that using this function will change the min/max value for all automation clips. I might be overlooking something, but would it not be better if IL made it possible to do this individually on automation clips?
Glad you got it working. :)

It is only for that one clip, rather than all. However, the clip based paradigm allows you to edit automation just as you would with patterns and audio. So you can copy sections without having to create new automation clips. Then edits to the same section will be replicated only within that part of the clip. You can just as easily extend the clip and create new automation for that parameter if required. Slicing the clip doesn't create a new clip - just a section of the same clip that can also be replicated.

And you could indeed have two or more conflicting sources of automation being read to control a single parameter.

This might help: http://www.theflipsideforum.com/index.php?topic=29148.0

Post

Unaspected wrote: Tue May 05, 2020 4:12 pm
218 wrote: Tue May 05, 2020 3:58 pm @Unaspected Thank you once again! :tu: I set the min/max to its full and its now working like a charm :)
I noticed that using this function will change the min/max value for all automation clips. I might be overlooking something, but would it not be better if IL made it possible to do this individually on automation clips?
Glad you got it working. :)

It is only for that one clip, rather than all. However, the clip based paradigm allows you to edit automation just as you would with patterns and audio. So you can copy sections without having to create new automation clips. Then edits to the same section will be replicated only within that part of the clip. You can just as easily extend the clip and create new automation for that parameter if required. Slicing the clip doesn't create a new clip - just a section of the same clip that can also be replicated.

And you could indeed have two or more conflicting sources of automation being read to control a single parameter.

This might help: http://www.theflipsideforum.com/index.php?topic=29148.0
Thank you for the link :tu: Will check it out later tonight:-)

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”