Set clip notes with OSC

[giohappy]

I don't know much the Bitwig API but I guess it offers a way to set the notes in a clip with a single method call. Does it?
If it's possible, do you think the OSC interface provided by DrivenByMoss could be extended with a method that accepts a list of notes (relative time, duration, pitch and velocity) for a clip?

[Kirkwood West]

if you create a CursorClip in your bitwig extension you have a lot of options for programming manipulating notes in Bitwig. There is a great class for OSC nativily in the bitwig API so you can hook it up.

As far as modifying DrivenByMoss OSC... I wouldn't unless you are next level programmer. Its extremely well coded to work for both Reaper and Bitwig so it can be a bit overwhelming following the code structure, it is truly a work of art and labor of love.

[Anchor]

In theory, the OSC interface provided by DrivenByMoss could be extended to accept a list of notes for a clip by defining a new OSC message type and extending the codebase.

Implementing such a feature would be a non-trivial task requiring a deep understanding of the Bitwig API and OSC interface, as well as careful consideration of conflict resolution...

[giohappy]

Yes, it wouldn't be trivial but my main concern was to understand if the API supports this.
I've digged a bit into the API docs during the weekend and it seems everything is there.

Jurgen's work is a masterpiece. I've played with it for a while, recompiled it to tweek some parts for my own needs. However, extending it while maintaining all its abstractions is not an easy task!

What I suspect is missing instead is the possibility to write automation. This is also missing from Live API, and I guess because ir's quite a complex topic...

[Kirkwood West]

Yes, it wouldn't be trivial but my main concern was to understand if the API supports this.
I've digged a bit into the API docs during the weekend and it seems everything is there.

Jurgen's work is a masterpiece. I've played with it for a while, recompiled it to tweek some parts for my own needs. However, extending it while maintaining all its abstractions is not an easy task!

What I suspect is missing instead is the possibility to write automation. This is also missing from Live API, and I guess because ir's quite a complex topic...

I'm pretty sure you can do at least clip automation in the live python api. That be very welcome here