Open Sound Control (OSC) is here

Post Reply New Topic
RELATED
PRODUCTS

Post

There is a new update available.

To make my life a bit easier I decided to centralise the info in one thread:
http://www.kvraudio.com/forum/viewtopic ... 8&t=502948

You can keep posting in this thread or in the new one, whichever you prefer.

Post

Hi Moss,

Since no script yet exists for the Faderfox UC4 (if you feel like making one, that would also be great), and I've never done anything in javascript, (and am proficient in Max Msp) I've decided to make a max patch that maps the UC4 to bitwig through OSC.

I've got everything working except one thing: I would like to select the parameter banks of the currently selected device in an absolute rather than relative manner. I can currently bank up and down through the devices parameters with /device/param/+ and /device/param/-, but how to I select bank 1, 2, 3... directly?

Thanks for your great work.

k

Post

For now I've found a work around in max using the relative parameters, but please let me know it there is a way to call the parameter banks absolutely.

thanks.

Post

This is working nicely!
Thanks so much for this Moss.

One thing I still can't figure out:

How do you control the return volumes with your implementation?
I can control the send volumes on each track, but what about the volume of the returns?

k.

Post

ke10g wrote:This is working nicely!
Thanks so much for this Moss.

One thing I still can't figure out:

How do you control the return volumes with your implementation?
I can control the send volumes on each track, but what about the volume of the returns?

k.
/track/toggleBank Toggles between the Audio/Instrument and Effect track bank

For selecting a device page use:
/device/page/selected {1-8}

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
I have made a workaround for bi-directional clients on other hosts than 127.0.0.1: https://github.com/sorl/DrivenByMoss/re ... 4-touchosc (https://github.com/sorl/DrivenByMoss/releases/tag/6.4-touchosc)

Post

Hi Bitwigers ! Hi Jürgen ! (thanks once more for this extension I'm still discovering)
I need to use Bitwig as a VST host and I would like to create an instrument selector monitor in OSC.
Then, I need to receive a text information from an instrument selector, how to make that?
In Bitwig, my OSC control script is locked on the right track and on the right device.
I tried a lot of combinaison around "/device/layer/selected/name/..... " but nothing works.

It would be even better, If possible, to retreive to full layer list in order to see what's next, and what's before.

Is something similar possible?
Thanks,
Have a nice day

Post

Mathiross wrote: Mon Jul 08, 2019 9:10 pm Hi Bitwigers ! Hi Jürgen ! (thanks once more for this extension I'm still discovering)
I need to use Bitwig as a VST host and I would like to create an instrument selector monitor in OSC.
Then, I need to receive a text information from an instrument selector, how to make that?
In Bitwig, my OSC control script is locked on the right track and on the right device.
I tried a lot of combinaison around "/device/layer/selected/name/..... " but nothing works.
It would be even better, If possible, to retreive to full layer list in order to see what's next, and what's before.
Is something similar possible?
I am not sure if I fully understand what you try to achieve. In such a specific use-case it might be easier to implement your own OSC protocol. In my Bitwig API development tutorial series on my Youtube channel I discuss that, too.

Post

Ok, thanks for your answer,
I created an exemple to explain what I'm trying:

Image

It's just a clone of the "instrument selector" device in Bitwig in order to be able to check which sound is selected while I'm changing them with a midi foot pedal. The main bitwig window will be on another track so I can't see what instrument I'm changing.

Is there actually a solution? I can't code myself, then I'll have to wait, maybe you find this function usefull and you integrate it in your next version of the Bitwig plugin.

Post

Mathiross wrote: Tue Jul 09, 2019 4:52 pm Ok, thanks for your answer,
I created an exemple to explain what I'm trying:

Image

It's just a clone of the "instrument selector" device in Bitwig in order to be able to check which sound is selected while I'm changing them with a midi foot pedal. The main bitwig window will be on another track so I can't see what instrument I'm changing.

Is there actually a solution? I can't code myself, then I'll have to wait, maybe you find this function usefull and you integrate it in your next version of the Bitwig plugin.
So, the problem is that selecting a layer is not working? If you post your template, I can have a look.

Post

Thank you very much for your help.
This screenshots were just false examples, it was just to show you the idea. I could not make it like that and working because I don't know what to write in the address field in order that OSC retrieves directly the name of the selected layer.

For the moment, I found an alternative but it's far from being perfect :
1) I rename every first remote control page the same as the layer name
2) I create a text field with the address: /device/page/1/

Image

I don't change remote control page, so that it's working fine for the moment. But it's long to rename each first remote control page of each layer.

The best would be that your OSC script send direclty the name of the selected and active layer to the widget and also, the previous and next layers (to see where we are in the list) like what I imagined in the first screenshot, like in the natural environnement of bitwig.

Actually, it's planned that my instrument selector is controlled by a foot pedal but why not to have also the arrows to be able to change it from a touch screen, but it's not a priority, for the moment I just need to monitor what layer I'm selecting in bitwig.

Is there a simple solution or is it not yet implemented?

Post

Mathiross wrote: Thu Jul 11, 2019 11:44 am Thank you very much for your help.
This screenshots were just false examples, it was just to show you the idea. I could not make it like that and working because I don't know what to write in the address field in order that OSC retrieves directly the name of the selected layer.
I just released DrivenByMoss 7.02. With that it should now be possible to do what you are trying to achieve.
See the included Open Stage Control template, it has now a new layer tab. This should show you all the necessary commands. Note that the strip on the right is not the master track but the selected layer.

Post

Hi Jürgen,
great job ! it's now possible to list the layers, and to know wich one is selected.
Thanks a lot
Maybe you planned to make it, but one important thing is still missing for people who use Bitwig as VST host to play live, the sending of the "Active" layer. (which is different from "activated" or "deactivated")

In this exemple, the layer 3 is selected, but the layer 2 is "active"
Image

Beyond the fact that now we can list the layers, there is still no way to create a LED in front of each layer in order to show which one is "active". In bitwig, the concerned field is called "index", maybe it helps you to find the command.

The address messages could look like:
/device/layer/active/name
/device/layer/active/... Same attributes as for a layer

Thanks again to share your skills ! I'm really thankfull.
Beside that, I'm a fan of progressive rock and I wish you all the best with Arilyn. :wink:
Do you use Bitwig in the band?
Last edited by Mathiross on Thu Jul 18, 2019 9:30 pm, edited 1 time in total.

Post

Mathiross wrote: Thu Jul 18, 2019 2:47 pm Maybe you planned to make it, but one important thing is still missing for people who use Bitwig as VST host to play live, the sending of the "Active" layer. (which is different from "activated" or "deactivated")
The problem is that this is only available via a mapped parameter (and a user could map it to anything (or not at all)).
I did not try but I think it is possible in Open Stage Control to monitor the value of e.g. the first parameter and compare it to a layer.
Mathiross wrote: Thu Jul 18, 2019 2:47 pm Beside that, I'm a fan of progressive rock and I wish you all the best with Arilyn. :wink:
Do you use Bitwig in the band?
Thanks! Currently not. I use a host coded in Max/MSP, which is very specialised to my needs. I am trying for some time now to write a similar setlistmanager for Bitwig but I am still running into too many problems.

Post

moss wrote: Thu Jul 18, 2019 3:39 pm The problem is that this is only available via a mapped parameter (and a user could map it to anything (or not at all)).
I did not try but I think it is possible in Open Stage Control to monitor the value of e.g. the first parameter and compare it to a layer.
Humm, I don"t know if I was clear. Concerning mapping, as far as I know, you can map the arrows next and previous of an instrument selector (arrows up and down) to change the active layer, ok, this is what I've made with my midi foot pedal.
Then, I understand that OSC could not "control" the next or previous layer buttons (exepted maybe with a midi message command as explained here https://openstagecontrol.ammd.net/docs/midi/)

But my main question is: could your OSC script send just the information of which layer is active? As a text widget (exaclty as this address: /device/layer/selected/name but with active layer, not the selected one), or as a led widget (layer n is active: 1 or 0)
moss wrote: Thu Jul 18, 2019 3:39 pm Thanks! Currently not. I use a host coded in Max/MSP, which is very specialised to my needs. I am trying for some time now to write a similar setlistmanager for Bitwig but I am still running into too many problems.
With these musics, it can be a serious advantage to be able to code ! I hope I'm right to try what I need in Bitwig. Maybe it's simplier if I explain a bit my project:
The laptop is on a keyboard played by another musician who can monitor his actual settings directly on bitwig. The keyboard sound presets are in an instrument selector on track 1.
A second 10" screen is pluged in the same laptop and placed next to my foot pedal where I play a midi wind controller. My sound presets are in an instrument selector on track 2. While playing live, I would like to keep an eye on my actual settings via this screen thanks to OSC.
This is why I need to monitor the active layer, and why not, to know which are previouses and nexts layers to appease my brain while a live performance :)

Post Reply

Return to “Controller Scripting”