Open Sound Control (OSC) is here

[moss]

I'm probably asking too much now: do you think would sending /track/{1-8}/clip/{1-8}/length and /track/{1-8}/clip/{1-8}/position (fraction of length would be enough) be feasible?

The first would be cheep, while the latter would probably cause too much I/O when the nunber of playing clips becomes relevant. But it would be great for visual feedback on the control surface.

Both is not possible. There is currently no access to any audio/wave related information. For MIDI clips there is the sequencer, which is unlimited in length and the play position is clearly lagging, which you can notice when you check out any of my sequencers.

[giohappy]

For the first one couldn't playStart / playEnd be used? Maybe /track/{1-8}/clip/{1-8}/playstart and /track/{1-8}/clip/{1-8}/playend instead of length, and let the client do the calculations as it wishes.
AFAICS the only case where it is implemented is Push

EDIT: on second thought having the start, end or length without the current position wouldn't be very useful. Forget it.

[NKirn93]

Hey Moss, I've got a question.
I can't get MIDI feedback working with Open Stage Control. The surface faders move my controls in Bitwig but when moving the knob with my mouse it doesn't get updated.
I've tried using the OSC script and using Flexi, as the latter has a MIDI output port selector, just in case. Neither seem to get any MIDI back from Bitwig into Open Stage Control. I've also checked their forum and it seems the software is capable of MIDI feedback so I'm wondering what I'm doing wrong.

I'm also curious why the limitation of 64 user controls is there. Could that number not be higher? It would be really awesome if I could use OSC as a protocol to communicate with my template and Bitwig rather than MIDI. Unfortunately because my control surface has many more than 64 controls that's not possible with the current implementation.

If either of the two mentioned problems I'm having were solved my controller would work fine. As is I can't get all the controls that need bidirectional communication mapped through OSC because the number of user parameters is too low and I can't use MIDI because it seemingly doesn't allow for bidirectional communication. But it does have an appropriate number of CCs to map.

[moss]

Hey Moss, I've got a question.
I can't get MIDI feedback working with Open Stage Control. The surface faders move my controls in Bitwig but when moving the knob with my mouse it doesn't get updated.
I've tried using the OSC script and using Flexi, as the latter has a MIDI output port selector, just in case. Neither seem to get any MIDI back from Bitwig into Open Stage Control. I've also checked their forum and it seems the software is capable of MIDI feedback so I'm wondering what I'm doing wrong.

I'm also curious why the limitation of 64 user controls is there. Could that number not be higher? It would be really awesome if I could use OSC as a protocol to communicate with my template and Bitwig rather than MIDI. Unfortunately because my control surface has many more than 64 controls that's not possible with the current implementation.

If either of the two mentioned problems I'm having were solved my controller would work fine. As is I can't get all the controls that need bidirectional communication mapped through OSC because the number of user parameters is too low and I can't use MIDI because it seemingly doesn't allow for bidirectional communication. But it does have an appropriate number of CCs to map.

I think there is a misunderstanding here. OSC does not require MIDI in any way. If you do not get any feedback in the template check your OSC ports.
The MIDI input is actually not used but necessary to get notes into Bitwig to work around a Bitwig limitation. Watch the OSC videos on my Youtube channel for a better understanding.

[NKirn93]

I think there is a misunderstanding here. OSC does not require MIDI in any way. If you do not get any feedback in the template check your OSC ports.
The MIDI input is actually not used but necessary to get notes into Bitwig to work around a Bitwig limitation. Watch the OSC videos on my Youtube channel for a better understanding.

I understand that OSC is a different protocol altogether. I've build a custom template in Open Stage Control to control my Bitwig template, I'm not using your template to control it.
The problem I'm having is that I cannot map the entirety of the template using the 64 user controls because the number of controls that require bidirectionaly communication is larger than 64.
That would be fine if I could just use Open Stage Control's ability to send MIDI data. 16x128 controls is more than enough. But bidirectional communication seems not to work either when using the OSC control script nor Flexi.

Does that make sense?

[minortom]

Couple of simple additions that would significantly improve working with grouped tracks over OSC:
- An option to work with flat track banks (a config param passed to `hasFlatTrackList`, perhaps?)
- An additional `/track/enter` command that enters the currently selected/cursor track, to complement the `/track/parent`

Without either one of those it's impossible to navigate tracks in TouchOSC without making 8 dedicated controls just to enter tracks. With at least the latter a track navigator could be feasible in TouchOSC with just four simple buttons (next/prev/down/up), with the former it may not even be necessary.

[moss]

Couple of simple additions that would significantly improve working with grouped tracks over OSC:
- An option to work with flat track banks (a config param passed to `hasFlatTrackList`, perhaps?)
- An additional `/track/enter` command that enters the currently selected/cursor track, to complement the `/track/parent`

Without either one of those it's impossible to navigate tracks in TouchOSC without making 8 dedicated controls just to enter tracks. With at least the latter a track navigator could be feasible in TouchOSC with just four simple buttons (next/prev/down/up), with the former it may not even be necessary.

This should work: /track/selected/enter

[minortom]

Couple of simple additions that would significantly improve working with grouped tracks over OSC:
- An option to work with flat track banks (a config param passed to `hasFlatTrackList`, perhaps?)
- An additional `/track/enter` command that enters the currently selected/cursor track, to complement the `/track/parent`

Without either one of those it's impossible to navigate tracks in TouchOSC without making 8 dedicated controls just to enter tracks. With at least the latter a track navigator could be feasible in TouchOSC with just four simple buttons (next/prev/down/up), with the former it may not even be necessary.

This should work: /track/selected/enter

Oops, should have been paying more attention when reading the manual. Thanks.

[NKirn93]

I've just checked again to see if my configuration was wrong and no, it seems it just flat out doesn't work. Of course because the OSC script wasn't designed, I don't think, to handle MIDI. And I know this is not the topic but Flexi also doesn't send any MIDI if I try to use that script as a control surface for my touchscreen rig.

This is a possible show stopper. At this point it becomes a feature request.

Is it possible to allow for an arbitrary amount of user parameters?
So any address with user/[number]/value is received by the script and can be used for mapping?
Alternatively can full MIDI control be implemented where MIDI can be sent to Bitwig for control AND sent back to the control surface for feedback?

And how much would I have to pay you to implement this? I'm serious, it's that important.

[moss]

I've just checked again to see if my configuration was wrong and no, it seems it just flat out doesn't work. Of course because the OSC script wasn't designed, I don't think, to handle MIDI. And I know this is not the topic but Flexi also doesn't send any MIDI if I try to use that script as a control surface for my touchscreen rig.

This is a possible show stopper. At this point it becomes a feature request.

Is it possible to allow for an arbitrary amount of user parameters?
So any address with user/[number]/value is received by the script and can be used for mapping?
Alternatively can full MIDI control be implemented where MIDI can be sent to Bitwig for control AND sent back to the control surface for feedback?

And how much would I have to pay you to implement this? I'm serious, it's that important.

It seems you are looking for something really specific for your use-case. If you cannot code yourself (there are many tutorials on my Youtube channel, if you can) try to ask here in the forum. Myself, I am not looking for any job.

[NKirn93]

It seems you are looking for something really specific for your use-case. If you cannot code yourself (there are many tutorials on my Youtube channel, if you can) try to ask here in the forum. Myself, I am not looking for any job.

Ok, I'll look at your controller API videos. Before I do, is there any way to have bidirectional communication with the Flexi script? I can't get Open Stage Control to respond to my moving the mapped control in Bitwig. In Ableton it does so I know Open Stage Control isn't the problem, I just can't seem to get MIDI out of Bitwig and into OSC.
Again, if user parameters weren't limited to 64 (I'm guessing that's because of 8 times 8 banks) I could make it work.

[moss]

It seems you are looking for something really specific for your use-case. If you cannot code yourself (there are many tutorials on my Youtube channel, if you can) try to ask here in the forum. Myself, I am not looking for any job.

Ok, I'll look at your controller API videos. Before I do, is there any way to have bidirectional communication with the Flexi script? I can't get Open Stage Control to respond to my moving the mapped control in Bitwig. In Ableton it does so I know Open Stage Control isn't the problem, I just can't seem to get MIDI out of Bitwig and into OSC.
Again, if user parameters weren't limited to 64 (I'm guessing that's because of 8 times 8 banks) I could make it work.

I never used Open Stage Control with MIDI, so I cannot comment on that.
In general, my OSC implementation use only OSC and has full feedback for that.
Generic Flexi provides MIDI feedback for CC, see the manual.

[u-u-u]

Just read this news yesterday. New TouchOSC version is out with a lot of interesting features:
https://cdm.link/2021/06/touchosc-next- ... verything/

[carlca]

Just read this news yesterday. New TouchOSC version is out with a lot of interesting features:
https://cdm.link/2021/06/touchosc-next- ... verything/

Looks good. Including "Nested Containers" I notice

[minortom]

Just read this news yesterday. New TouchOSC version is out with a lot of interesting features:
https://cdm.link/2021/06/touchosc-next- ... verything/

Wowzers. I was just recently lamenting TouchOsc's lack of scripting and redoing my experiment in Lemur, only to discover that Lemur ignores some OSC messages at random. WTF, Lemur.

Great news!