I didn’t know there was a ‘out of range’ on the G/U/D commands Ledger, I would’ve not applied any limit on those as they seem to accept a range as 00-FF is valid?
Glide goes from 1 to 16 (hex =10) then FF is for instant glide, so anything between 10 and FF is junk data (or at least all those values do the same thing). The thing to do with this tool I guess is to just treat them all as 16. I`ll have to do a bit more experimentation/ research on each command to get it all working right, and not having big areas of the sliders that seem to do nothing.
EDIT: works as expected see posts below
However I just did a quick test of this and there seems to be an unexpected difference with 16,17 and 18 in Glide:
In a render of this (16, 17, 18 used at the end of each note/ run of Glides), the middle render17 seems to come out different from 16 and 18??
Couldn’t think of a Richard Branson backlash Ledge
No, I can`t imagine there being a Branson Backlash, unless anyone just got stuck late on one of his trains
backlash would be conversations about the merits of limiting instrument numbers to tracks and fx commands to particular columns (mirroring the concept of the automation lane). I`m not a fan of trackers “anything anywhere”, not just from a scripting point of view but from a composing view aswell. These conversations open a bit of a can of worms though due to conflicting workflows/ habits people have…