Fruity Limiter sidechain input number changes when new mixer track is routed in

[artmast]

I sometimes use fruity limiter for sidechaining. I route in all my main instruments from their individual mixer tracks to one dedicated mixer track, and route my kick track in at 0%, then sidechain to the kick.

However, I've found that when I later go to add an additional mixer track for a new instrument I also want to be sidechained, the sidechain input selection doesn't adjust its value to keep the kick as the selected track to sidechain to. Instead, it maintains the relative position the previously selected track had.

Let's say I have instruments on mixer tracks 1-3, and my kick on track 5. Once I route them to my dedicated mixer track for sidechaining, they display in the fruity limiter sidechain input drop down like this:

(1) Mixer track 1
(2) Mixer track 2
(3) Mixer track 3
(4) Kick (track 5) <-- I have this one selected right now

If I then route in an instrument on mixer track 4, the sidechain input in fruity limiter adjusts relative to the mixer track positions, like so:

(1) Mixer track 1
(2) Mixer track 2
(3) Mixer track 3
(4) Mixer track 4 <-- Now this one is selected, even though the kick was selected before!
(5) Kick (track 5)

That's not what I want. I selected mixer track 5, not mixer track 4! Why should it change like that?

I feel like the sidechain input number should maintain the specific mixer track as its selection.Any time that I rearrange or reroute to a mixer track with fruity limiter, that sidechain input selection could potentially get reassigned while the limiter isn't even visible! I find this design very unintuitive, and there have been several times that I have to redo a bunch of work because I was sidechaining to the wrong thing for an hour.

[XAngeled]

it's such a quality of life change, it happened...

[Audiobusters]

XAngeled wrote: ↑Tue Sep 10, 2024 2:46 pm ...th...

[vertexguy]

I've seen the fruity limiter sidechain ID chang...

[imps]

Bumping this one up as it's one of my worst nig...

[timhagman]

Can't see anything about this being fixed in FL...

[Spaces]

timhagman wrote: ↑Tue Oct 21, 2025 12:13 pm Can...