Open Stage Control v1.0.0-beta

Version 1 is getting closer to release than ever ! I finally managed to implement a color scheme that feels legible and consistent (thanks to the great nord theme). I’ve been testing it on rather big sessions, and things are starting to get nice:

(Control surface for Ardour 6)

The actual nord theme is also available (type “nord” in the theme option), it’s just a bit less contrasted than the default one.


1 Like

Hi @jean-emmanuel,

Yes it’s very very nice ! The result of lot of work from you. Thanks for this.

I’ve migrated my template to the beta version. It works splendidly well!
Great job Jean-Emmanuel, you are making my life way easier for two years now :slight_smile:

Great! i did the migration of my old session to v1b5 there was only some graphic resize to do on some nodes.
Thank’s well done!

Hi, first of all thankyou very much for making OpenStageControl. The best touch control creator I have found by far. It’s giving me motivation to learn some code but I am still a rookie on that side of things.

Sorry if this is not the right place to post this… I am using v1.0.0-beta5 running in OSX 10.14.6 and getting a problem that was happening intermittently yesterday but has started happening consistently today. I am not sure it’s a bug with OpenStage Control or my computer so haven’t submitted a bug report yet.

While I am trying to edit all the preArgs in my template, I can edit 2 or 3 widgets (sometimes a few more) and then the next one I try to edit, the value won’t enter. I type [3,45] in the preArgs box and after pressing enter the value won’t actually enter. I can’t change the value of any property of any widget at that point and have to quit and restart the application to get it working again. It lets me modify 2 or 3 more widget preArgs and the process repeats. I am getting this error:
(ERROR, CLIENT) Uncaught TypeError: Cannot read property ‘indexOf’ of undefined
at widget.getProp (src/client/managers/widgets.js:155:54)
at t.onPropChanged (src/client/widgets/common/widget.js:8

Any idea why this is happening?

Thank you all for your feedback it’s very appreciated :slight_smile:

@krisvanlog I think you’ve encountered the same bug I did yesterday ! It’s fixed in the sources already, I’ll cut another beta release soon so that you can check if it fixes things on your side too.

Great news! I’ll keep an eye out for it.

@krisvanlog beta 6 is available