Thanks you two.
I’m confused by this. As you suggested Joule, removing the server code and just using the user-options OSC server allows me to play a note from a script. But the opposite does not work. I cannot play a note purely from the scripted API OSC server with the options server shut down.
I was using as much info as i could find from the forums and documentation. I even copied this class you wrote for Raul: [Solved] Help, code for play/stop specific note of a instrument, is po which uses the same syntactic setup as my code above, but has a tool() call which doesn’t work in the scripting editor of course.
The OSC docs are using functional notation to explain the trigger messages eg. “/renoise/trigger/note_on(number, number, number, number)” which is not valid if taken literally, as Renoise is looking for a table of tables for the arguments and they have to be passed outside of the selector string, more like a list. It’s a mess tbh. Danoise’s tools and libraries are mental, and way too complicated to be useful as a ‘meta-API’ in my opinion if that’s what they’re for, and he’s doing exactly the same, with the table construct, just in a more extreme way.