Okay, so backwards compatibility for the range bug was awkward and ugly so I decided against it. If you made a track with 1.10 using value ranges and you need to preserve the incorrect value range behaviour, all you have to do is put an equals sign before the second value in the range definition eg. "R:%10-=50". Doing so will force the second value to be treated as a normal integer value, which will recreate the effect of the broken code.IXix wrote: 2020.01.23 - IX Magic 1.11 - x86
+ Fixed note off being triggered by full velocity when using velocity to control note params.
+ Corrected documentation of chord definition in Note Sequence Reference
+ Fixed value range parsing broken by 1.10
+ Machine version 1.11 (still file version 11)
Sorry for the inconvenience.