[Fixed] css is still buggy, sry guys!
As much I love the new updates there are lots of bugs in there.
For e.g. I have two sets of pads. So, I have pad 1-16 another group pad 1-32. If I’m selecting PAD1 from the second group, as soon I leave that option and selecting anything else and then get back, the selection goes back to the PAD 1 from the first group.
I’ve attached a video to better explain things
there are more but I think I’ll wait for another update.
as a feature request: custom name for every controller input type and also the option to change the type. with this new feature, I wanna change the controller input from knob to endless enconder.
Are you sure that isn’t a row from your other set of pads sticking out the bottom?
I don’t see them anywhere else on the MIDI Controller.
Hi Dan,
Good news, in version 2.5.3 (released today 6th July 2020) we have fixed this issue where a the pads contained in a second pad group is not selectable in your script.
With this update, when you add the second pad group, the name+number of pads inside it will take into account other pad groups in the controller. For example, if you have 1 pads group containing pads 1 – 16 inside it. If you then add a second group of 16 pads, they will be named ‘pad 17’ up to ‘pad 32’.
This fix means that you will now be able to select all pads in you script without issue! 🙂
(Note this will be the same for keys also).
We also fixed an issue where changing the rows & columns settings of a pads group, the visual in the midi controller panel would not update correctly.
Thank you for your patience and hopefully the update works correctly for you.
John
Sign up
User registration is currently not allowed.