OSC -> LUA -> MIDI

[RedStoneRanger]

Hi All,
Since a few weeks I am struggling with a very specific task, which is all about routing MIDI messages between VST plug-ins in Davinci Resolve. I tried everything out there including Patchwork, Connector, Bidule, and others but there's no elegant solution. My best approach was with ElementFX but this is now hitting some memory constrains. Long story short, I am now planning to do all my internal communication via OSC and finally convert this stream to MIDI before its send to my controllers. This way I only need a few ElementFX, which saves me from the memory issue.
Inside ElementFX I want to use "OSC Receiver" -> "LUA Script" -> "MIDI OUT Device" (Or vice versa). The LUA node takes the OSC messages and an adress to work on and outputs MIDI commands, which are then fed into the MIDI Out node.
Is this the right approach? I have some experince with C++, Lua and other stuff but never touched LUA inside Element. Not even sure how to declare an OSC input. Maybe someone has worked on a similar topic and can get me started.

[mfisher31]

That could work. The OSC receiver will translate all incoming OSC as MIDI though.

[RedStoneRanger]

You mean I can directly connect an OSC Receiver to a MIDI In device?? This would immediately make all my headaches go away.
From what I can get from the code, the OSC adress has to be
"/** /midi/{command} or /midi/{deviceName}/{command} */"

What I send is
/midi int32 xxx, int32 yyy, int32 zzz
but I get nothing on the midi monitor. Is it the missing "/" after "/midi" ? Can't add a "/" in Bidule :(

EDIT: Did some more investigation and yes, it looks like the rightmost "/" should not be there. If I look at the code for the function "parseOscAddressPaths " in utils.hpp line 85 it looks like the delimiter is also used between the adress and the payload.
If I am right, any chance to fix this in 1.0b?
Its also not used in other apps that use OSC like Touch OSC or Bidule.

[mfisher31]

For raw midi its /midi/raw {data}

[RedStoneRanger]

Thanks Michael!

[mfisher31]

No problem. There definitely could be issues with these OSC nodes. They were contributed years ago. If you find any problems with that format, let me know. They might need changed as I'm not sure all clients are capable of blobbing raw data as parameters. e.g. we might need to add another endpoint which is "raw" but the data is an array of int32's or something.