CSS 2.8 is now available!

393 viewsGeneral
0

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

admin Changed status to publish May 22, 2024
Attached Files:
1 2 3 10 11
0

Is there a newer tutorial for parameter banking for version 2.8 or higher? I am not seeing a mapping for parameter banking in version 2.8 like you do in 2.7. Also an updated tutorial for modifiers would be great. Both of these mappings failed to import properly to 2.8 when I migrated.

admin Changed status to publish May 22, 2024
0

found!

admin Changed status to publish May 22, 2024
Attached Files:
0

I don’t find the “Selected Track” mode. Only “Selected Device”. Am I missing something?

admin Changed status to publish May 22, 2024
Attached Files:
0

I wanted to let you know I remapped everything in the 2.8+ app. Took a bit of time but it was totally worth it. I love the new mapping system; much more intuitive. Also the app is way more stable. Thanks guys!

For everyone thinking of purchasing CSS, do it! I have so much control over Ableton for my Liveset its insane.

admin Changed status to publish May 22, 2024
Attached Files:
0

Hi Aqenra,

The upgrade is indeed mostly in the interface, which means that there is no new added script functionality. So if your scripts are already done, there is no need to convert them to 2.8+. If you want to update your existing script with minor (or even major) changes, you can still use an older version of CSS (2.7 or 2.6.3) to adapt your script. All mappings and reactions still have the same functionality.

If you do want to convert your script to CSS 2.8+ then you will have to assign a mode to each mapping, which can take some time but nothing excessive. If you run into the problem that you don’t remember which mapping is assigned to which mode, you can run both CSS versions next to each other.
I had a problem with a script that had many parameter banks that did not translate well when I imported the script to v2.8+. I redid the parameter mappings entirely by having both CSS versions open, which made it really easy. Sure it took ‘some’ time, but to be honest, I never finished a working script so swiftly 😉

Sure if there was to be a script or program that translates older scripts to 2.8+ without having to reassign modes or redo some mappings, I would use it too. But that is not so high on my wish list. Anyway, for now, I use CSS 2.8+ for all my new scripts (I prefer it mostly for the bigger screen estate you get for making Reactions and the ability to export selected mappings), Older scripts get modified by CSS 2.7-. That way I don’t lose functionality or time 😉

admin Changed status to publish May 22, 2024
Attached Files:
1 2 3 10 11