Open Stage Control (Tutorial) - An alternative to Lemur and TouchOSC

Grizzlymv

Active Member
As promised. here's the revised version.

There's some minor changes in the UI since I started to work quite a lot with Track Presets, I wanted to have access to the media bay more easily, and display/hide the left/right bars more quickly. Rest is the same. bug free. Enjoy
 

Attachments

Gefionsong

New Member
Hi Grizzlymv!
I have a stupid question. I wonder where did you put your Articulation, buttons? idnt you have those in your template as well? I cant find them. Or did I just dream this. Think it was Ciematic studio in my dream.... :)
 

Grizzlymv

Active Member
Hi Gefionsong. I used to have that in a previous version of the template. Got rid of them since I switched from the expression maps to a 1 articulation per track. It wasn't an automatic screen though. It was a manual process. So you did not hallucinated. But it's also no longer in my latest version unfortunately.
 

Grizzlymv

Active Member
Did you try CubaZen, anyone?

Nope. first time I hear about it. Did have a quick look, and it seems interesting espcially with the fact it cover a lot of the Cubase shortcuts and you get it all, out of the box, for a small fee (70$). But I haven't seen anything else then button in the presentation. the UI seems to be locked down, and it doesn't seem to support faders/sliders or other type of controls than buttons.

In OSC, I love the fact I can add as many faders as I need to control my CCs (ModWheel, Expression, PitchBend, Breath, etc.). Also the fact I can personalize the screen to fit what I use/need and get rid of what I don't/barely use keeps the UI clean. Personally, I just feel that OSC is more flexible and offer more, especially for the price (0$).

I have to admit that OSC is probably less user friendly to install/make it works than a paid solution that just works out of the box like CubaZen seems to be. I guess it all come down to what's best for you. And since we each have different workflows, it's good to have choice. To each their own. ;)
 

FantomXR

New Member
Hey people,

this thread is really really helpful. The tutorial is great and it worked immediately.
Anyway: I struggle with midi feedback loops. I set up a really simple layout with a fader that sends CC7 over a virtual midi port. I use the software "Cantabile" and assign this command to master volume. This works great.
Now I want to have it bidirectional. So I tell Cantabile to send out the value of the master volume out to the same MIDI port and back to OSC. This obviously creates a midi loop.

How to prevent that? I read through the thread but the solutions some people come up with aren't clear to me. Can someone help me?

Can I somehow tell the fader to listen and send on two different ports?

Thanks,
Chris
 
OP
Manaberry

Manaberry

Senior Member
Hello @FantomXR

I'm very happy that you are enjoying this software and this tutorial.

Regarding your project, you can set multiple midi ports in OSC. But first, let's understand the values.

-- midi MIDIPORTNAME: 0,1

As you can see, there is two values. The first one (0) is the incoming midi port, the second one (1) is the outgoing midi port. You can create another port with value 1,2.

-- midi MIDIPORTNAME: 0,1 MIDIPORTNAME2: 1,2

By doing so, you can allow more ports to be used in the same instance of OSC. You can split the data on those two ports now. It should be easier to handle data to avoid loops.

I'm explaining some data logic with XY pad and faders here. I hope it will help!
 

FantomXR

New Member
Hello @FantomXR

I'm very happy that you are enjoying this software and this tutorial.

Regarding your project, you can set multiple midi ports in OSC. But first, let's understand the values.

-- midi MIDIPORTNAME: 0,1

As you can see, there is two values. The first one (0) is the incoming midi port, the second one (1) is the outgoing midi port. You can create another port with value 1,2.

-- midi MIDIPORTNAME: 0,1 MIDIPORTNAME2: 1,2

By doing so, you can allow more ports to be used in the same instance of OSC. You can split the data on those two ports now. It should be easier to handle data to avoid loops.

I'm explaining some data logic with XY pad and faders here. I hope it will help!
Excuse my late reply. I now checked and something really seems to be strange. I set "--midi Control:0,1" and it worked great. Now I have removed that command and the fader still sends commands to that MIDI ports. How come? I of course saved everything a few times. Is there any kind of cache?

And BTW: How do I change the color of an element? I have a meter which I address via midi and I don't want it to be blue. I tried "--custom-color: red" and "--custom-color FF0000" and "--custom-color #FF0000". But that's not working. I can't find informations about the correct syntax.

Thanks,
Chris
 
OP
Manaberry

Manaberry

Senior Member
Hi there!

Open Stage Control 1.0 is currently in alpha state. Jean-Emmanuel needs some feedback and alpha testing. Feel free to install it and give your feedback and result of your testing HERE.



That being said, remember that it is an alpha. This version must not be used for production.
Feel free to share about it here also. I will take care to take important information to Jean-Emmanuel.


---


Excuse my late reply. I now checked and something really seems to be strange. I set "--midi Control:0,1" and it worked great. Now I have removed that command and the fader still sends commands to that MIDI ports. How come? I of course saved everything a few times. Is there any kind of cache?

And BTW: How do I change the color of an element? I have a meter which I address via midi and I don't want it to be blue. I tried "--custom-color: red" and "--custom-color FF0000" and "--custom-color #FF0000". But that's not working. I can't find informations about the correct syntax.

Thanks,
Chris
Did you change those values in the Default.scss file?
 

infinitecool

New Member
Added more working buttons and improved some buttons by changing them from toggle to tap, included the logical presets for cubase so the velocity and note length buttons work, you need to place the cubase logical presets folder "Open Stage Control" in:

Mac: /user/Library/Preferences/Cubase X/
Win: C:\Users\your_user_name\AppData\Roaming\Steinberg\Cubase 10.X.X\Presets\Logical Edit

Enjoy!
 

Attachments

infinitecool

New Member
If anybody knows howto change the BPM in Cubase with midi messages or with logical editor or macros through OSC please let me know, so I can make the red BPM buttons work :)