Quote: As for question 1: yes, no problem. Question 2: since it seems possible via scripts, I can't see why not. 3: sure.
The problem is - how effective will this be? What's the CPU/memory cost. How fast will it be? Could it crash Reaper in unfortunate situations?
--- (sorry, cant figure out right now how to quote - still want to write c++
I dont see OSC as a protocoll for doing timing and performance sensitive stuff at all.
Although of course there may be many things people might like to develop that are exaclty that: Timing and performance critical.
In my case iīm really just interested in getting info into lemur about track color, folder state, number of channels shown in mixer.
I will try to dig into beyond reaper or the c++ plugin development. Both seem far away right now...
Am i correct that the C++ extention is the more direct, maybe robust and "up to date" solution?
Sorry for highjacking this thread, but the title subject seems non specific enough.
And at this point:Sorry for my bad spelling, i know i have a problem
Then, to adress the problem of the OP about adressing a speciffic track id via OSC:
Have you considered binding a lua script to (any) OSC-command that selects your track by ID?
A second script could be used to assign any track to an external variable to be used by the first script.
Not great, i know, but maybe a workaround to at least get you going.
Your usecase seems rather special, so i really hadnīt thought about stuff like that. (I do "traditional" composing and multitracking).
But thatīs what Reaper is all about most of the time: Making stuff possible to cover any usecase and provide a perfect workflow in the end, no matter what you are doing.
Only with OSC (and propably some other stuff (midi feddback)) itīs not going sooo far. I totally get your desire.
If you design your perfect workflow, start setting up reaper, doing scripting, building controllers... and then maybe months into doing so you realize that you have hit a wall you would never have expected to be there... thats not nice.
I guess in one way or another we have all been there...
Another thing about building your own devices, just a side note for those who are interested: Your solution using that library you linked looks great. Another excellent option is the Midibox project.
Its over at ucapps.de
German site, but itīs all english.
It provides a framework for handling OSC and Midi and itīs a modular Hardware solution.
The MidiboxNG project is especially usefull for doing OSC handling. It can have itīs own Control elements, translate and process data and next to having midi ins and outs it can also be a USB Host, so you can hook up your (USB) midi devices directly without the need of going into the computer first and thaen routing it back using some fuzzy tool.