🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

[Fixed] css is still buggy, sry guys!

Submitted by danicroitor on Tue, 07/02/2019 - 19:21
danicroitor
Pro User
Control Surface Studio User

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.

https://youtu.be/VRLc4fTCap0

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.

Topic Category: 

7 Responses

Comments

danicroitor
Pro User
#1

https://youtu.be/Ye4Bi0fl_yo midi value wont update when midi monitoring. what I found out is that I have to click on an empty space or just to move the mouse around :O

JohnC
Forum Admin
#2

Thanks Dan!
We will check these issues out.

danicroitor
Pro User
#3

missing pads...
I've setup 2 rows for pad, sometimes it shows 3. I could write a book with al the bugs.! CRAZY!

danicroitor
Pro User
#4

controller manager: one click on a input type and it moves it (no drag) https://youtu.be/_AeN70G7wUw

JohnC
Forum Admin
#5

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.

danicroitor
Pro User
#6

I'm centrally. Also sometimes they just disappear.

JohnC
Forum Admin
#7

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