Range recall anomaly 4303

I’ve been experiencing this issue for a little while but have only just been able to nail it down.
In two states, the first limits the range to a synth. C4 and above FWIW. The second removes the limit - or it’s supposed to. The second route shows the limit removed but nothing is getting to the synth below the previous limit.
The route has been renamed to allow discrete actions, and is filtered for notes only. I can go to a different state which also employs that synth, no problem.
If I hit the binding which mutes the route and then re-enable it, it works.
To recap, approaching state 2 from state 1 always fails to remove the range limit. Disabling and re-enabling the route kicks it into life.
This was occurring in other recent versions too.

@brad

Hi @Ade,

Thanks for reporting this. Can you send me a copy of a song or rack that demonstrates this issue along with some steps to reproduce it and I’ll check it out.

Brad

DM’d you.
Thanks @brad

Sorted - it was a hangover from a old, purposely, misspelled name which snuck in when aliases were introduced. Still confused as to why the direction of approach made it work or not, but at least all is good now. Thx @brad

Thanks for the update - glad you got it sorted.