CSS 2.8 is now available!
Hi all,
We’re super excited to announce that version 2.8 of Control Surface Studio is now available. Based on feedback from our amazing community of users, we’ve rebuilt the entire User Interface from the ground up with a focus on making the workflow more clear and simple to use…
Full details here: https://remotify.io/introducing-control-surface-studio-28-whole-new-user-interface
@mj (and others): OK, that wasn’t polite. I’m sorry about that.
But anyway, thx for your support with the point.
I agree that the old user interface of 2.7 is much more intuitive and organized than the new 2.8 UI for all the same reasons mentioned in this thread. But I’m hopeful that these are developmental growing pains for now. Some ideas/suggestions for improvement that immediately come to mind are:
– The potential of allowing some form of nesting mappings/reactions (like in folders voluntarily created by the user).
– The potential of at least displaying the Mapping Name in the header of the mapping edit window instead of hiding it in a collapsed section of the window after moving on to the additional parameters of each mapping. (perhaps allow users to chose whether or not they would like to collapse the different sections of the pop-out window).
– The potential of integrating a separate window for the controller display so you can easily identify the names/midi info associated with each controller object whilst editing a mapping/reaction.
I also agree that getting rid of all nesting in 2.8 makes working on elaborate scripts completely chaotic and subject to erroneous mistakes.
I have attempted to import a script built with 2.7 into 2.8 and it did not go very well. After a few hours of carefully assigning the right modes to each of my mappings in 2.8, I’m receiving an error message that is preventing me from installing the script to Ableton using 2.8. I’m not sure what could be throwing it off, as I made no significant changes to anything other than assigning the right mode to each mapping.
The error message states the following:
“Script generation error
get_device_chain_target error:
we cant currently handle device selections of type: . Called by config_module”
czechball: the missing midi controller images should now be displaying.
I tested 2.8 out on a Mac Intel but couldn’t reproduce your issue with the app settings. Could you check it again please?
dok.ryconn: Thanks for reporting those issues with the Pads and Keys breaking and the tooltips displaying behind inputs. We will investigate this a priority.
MartinJ: We will investigate this issue with device parameter feedback, thanks.
ewersk:The cleaner is for fixing an issue with Midi controller templates only, as it specifically says on the page!
With regards to scrolling, are you aware that we now have filtering and a tagging system which you can use?
2.7 can still be used independently of 2.8 if you want to stick with that for now.
MartinJ & ewersk: we will be using the dialog/overlay for settings forms going forward, so if you have any suggestions on how this can be improved we’re all ears.
I’d like to present a different perspective than the angry user above – I left Ableton for Bitwig maybe a year ago and therefore I have not been using Remotify at all in this time, so I could care less about the previous version, as well as for some new version bugs (that are gonna be fixed). What I actually do care about and the reason why I’m here now and still interested in this project, is that the Remotify Control Surface app was one of the reasons why I didn’t want to leave Ableton and kept using it maybe for another year, and improving and developing this app might very well tip the balance back to Ableton for me – because it is a big of a deal and my major problem with Bitwig (not being able to use my controllers like with Remotify in Ablik). So just for the developers – don’t get intimidated by the haters, take a deep breath and carry on. We love what you’ve done and are doing. ❤️
Sign up
User registration is currently not allowed.