The bizarre behaviour of automation clips and certain other aspects

[dboot]

Bought FL some years ago and every few months I try to get into it again, because I love it's different and more modular approach and think it's
actually much better in almost all aspects than a traditional DAW.

But I never manage to fully switch to FL from Ableton/Bitwig/Logic/Renoise, because of some (at least to me) really bizarre behavior patterns within the program, that are just being overlooked for years.

How, for example, is it not possible to stretch automation clips (from both sides) in the playlist with a modifier key? This really makes no sense to me and even when I double click it to get into the automation editor, it's impossible to just stretch (expand/compress) a whole automation curve. The only way to do this, as far as I can see, is to increase the range value of the clip and than use the time knob.

I take it FL Users are just so used to this behavior, but as a user of a lot of other DAWs and considering all the options within FL, this really seems like such a basic and almost bizarre oversight to not have been fixed by now.

Same goes with not being able to have a shortcut to quantize/snap clips in the playlist. Once you shorten (or drag) a clip off grid, it's impossible to snap it's end to the grid again. Like how has this not been fixed? Because weirdly you can actually make a clips end snap to a marker by setting the snap setting to "Markers", but once you've done that, you can't snap a newly created marker to the grid. Just another bizarre loop of just not letting you do something very basic.

I really think FL is more than great, has first class synths and features, but it's really mind boggling how some very basics things in the playlist just are not being fixed for years.

[levendis]

i like how FL Studio stretches Automation Clips...

[dboot]

levendis wrote: ↑Fri Jun 14, 2024 1:03 pm i lik...

[jbarkerhill92]

I agree that certain aspects of FL Studio are u...

[levendis]

dboot wrote: ↑Fri Jun 14, 2024 2:35 pm about qu...

[dboot]

levendis wrote: ↑Fri Jun 14, 2024 5:54 pm For m...

[dboot]

jbarkerhill92 wrote: ↑Fri Jun 14, 2024 5:20 pm ...

[levendis]

dboot wrote: ↑Fri Jun 14, 2024 8:22 pm Exactly ...

[jbarkerhill92]

dboot wrote: ↑Fri Jun 14, 2024 8:34 pm jbarkerh...

[pararealist]

jbarkerhill92 wrote: ↑Fri Jun 14, 2024 5:20 pm ...

[jbarkerhill92]

pararealist wrote: ↑Sun Jun 16, 2024 5:29 am jb...

[DjNotSo]

dboot wrote: ↑Fri Jun 14, 2024 12:34 pm Same go...

[DjNotSo]

jbarkerhill92 wrote: ↑Sun Jun 16, 2024 3:40 pm ...

[jbarkerhill92]

DjNotSo wrote: ↑Mon Jun 17, 2024 9:14 am jbarke...

[DjNotSo]

jbarkerhill92 wrote: ↑Mon Jun 17, 2024 4:00 pm ...

[jbarkerhill92]

DjNotSo wrote: ↑Mon Jun 17, 2024 5:57 pm jbarke...

[DjNotSo]

jbarkerhill92 wrote: ↑Mon Jun 17, 2024 6:46 pm ...

[jbarkerhill92]

DjNotSo wrote: ↑Mon Jun 17, 2024 7:09 pm jbarke...

[levendis]

jbarkerhill92 wrote: ↑Mon Jun 17, 2024 7:37 pm ...

[DjNotSo]

jbarkerhill92 wrote: ↑Mon Jun 17, 2024 7:37 pm ...

[jbarkerhill92]

DjNotSo wrote: ↑Mon Jun 17, 2024 11:40 pm jbark...

[DjNotSo]

jbarkerhill92 wrote: ↑Tue Jun 18, 2024 5:21 pm ...