🔥 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.

CSS UI/UX problems & suggestions thread

Submitted by tmp on Wed, 12/20/2023 - 16:17
tmp
Control Surface Studio User

Hi together!

I wanted to start a thread that collects suggestions that could make the control surface studio more user friendly.

What I experienced so far:

1) When adding new pads to a controller template, the matrix could be automatically named with the schema "PAD column/row" where columns are numbers and rows are letters. For example "PAD 1A", "PAD2A", .. and so on. This makes it easier later to select Pads since PAD4C is more meaningful than PAD182

2) It would be nice to delete all current Midi Message Settings for a pad matrix with one button. Right now I cannot use the midi learn feature because some pads where pre-initialized with wrong values already and CSS prevents me from using Midi values twice. So I have to manually change midi mappings to other channels first and then I can use the midi learn feature again.

3) In general the GUI elements are way too big for my taste. Especially when creating reactions it is really hard to to keep track of everything. So I would decrease GUI element sizesand also use more horizontal space if possible (right now almost everything is ordered vertically what unnecessarily eats lots of space).

4) After a bulk action has been performed on selected items in the list of mappings/modes it would be nice to deselect the items again.

Topic Category: 

10 Responses

Comments

tmp
Control Surface Studio User
#1

Next suggestion:

- Please let me auto-login. Typing the password every new startup of CSS costs time

tmp
Control Surface Studio User
#2

- In reactions -> loops & actions you can restrict the selection via the button with the hand symbol on it. This button isn't recognizable as a button and the content that it hides should always be visible when editing loops & actions.

tmp
Control Surface Studio User
#3

- It would be really helpful to have the possibility to deactivate mappings instead of deleting them if you don't want to use them (for testing purposes)

tmp
Control Surface Studio User
#4

- It would be great if mappings could be grouped and collapsed for a better overview

JohnC
Forum Admin
#5

"- It would be really helpful to have the possibility to deactivate mappings instead of deleting them if you don't want to use them (for testing purposes)"
A simple way to do this is to add a mode which you don't use (I add one called 'unused mode')
You can then set the mappings to this mode, which is the same as deactivating them.

tmp
Control Surface Studio User
#6

Yeah but that is from UX side of view a hack and needs a lot of time (in comparison to a checkbox next to the mapping)

tmp
Control Surface Studio User
#7

After some time of writing scripts by far the biggest UI problem is the size of actionblocks.
It is nearly impossible to have a good overview. Collapsable rows that can be dragged and dropped would really improve the creation of reactions a lot!

tmp
Control Surface Studio User
#8

Next suggestion: It would be nice to have the possibility to globally set custom names for modifiers and custom lists.

tmp
Control Surface Studio User
#9

Some feedback from the developers would be really nice!
Are there plans to redesign/develop the GUI? There is so many room for improvements. Already small changes (especially the size of the modal elements!) would improve the UX a lot!

Fluxiia
Control Surface Studio User
#10

I agree with some of the above points:
the GUI is too big and I was really struggling scrolling up and down many times just to see a few lines of settings in reactions. I would have liked to have a one page view to understand what I was doing.
It would also be nice to be able to group bunch of settings (ie 8 volume assignments, 8 mute assignments etc) so that we can free up space in the main page.
I am not sure if there is a way to have "take over mode" in reactions, but I could not find it.
Saying this I would like to say that this is a great application and has enormous potentials, enabling people like me with no knowledge of Python to write scripts for Ableton. It's quite impressive, so congratulation to the developers for that.
I found the tutorial video informative but there is a lot that is not in the video or the documentation and some times I find things that don't work for me and I cannot find information anywhere on how to make the work.
I think in terms of priorities I would put GUI size and organization, and documentation on top of the list.