Are there any plans to get the OSC API up to speed with muti-cell support, currently the cells are sent using their internal addresses (>510000 - it appears that each cell has a 100000 channel block to identify it but there's not capacity to work out how this block of hidden channels is linked to the master channel.
A simple fix may be to add the master channel number as a note, along maybe with it's index within that channel.
While I am on the subject, has there been any joy fixing the bug which means you can't pull changes observed via /notify/patch - as the index sent doesn't appear to be very useful!
Just to bump this up - there was a note about a change to the patch API in 2.9 but I don't think it's fixed the above. I suspect that I could work out the cells using the start address and the fixtures above 100,000 - but this seems eggy.
Sorry, this is still an open item. I filed a ticket to track its status though -- [EOS-49820] OSC: Patch API (/eos/get/patch) does not handle multicell properly.
We will work on getting it prioritized.
Can you give more details on the notify/patch bug?
Thanks. Regarding notify, when a patch change is made the notify message is transmitted, however it does not return a usable index, meaning that it’s impossible to know what object has changed so a full refresh of patch data is required (I haven’t looked at this for a while but it was definitely the case when I built shift-patch)