Thats the point.mcallegari wrote: ↑Sun Oct 14, 2018 4:54 pm Alright, then I'm missing something about this VDJartnet plugin architecture.
I thought VDJ exposes some kind of hook when a button is pressed/knob rotated/etc.
If that is the entry point, then ArtNet or OSC is just a different incapsulation of the message into a network protocol.
And for our purposes, OSC would be richer than ArtNet.
If we have a look on VDJ, there are for example some free buttons to give actions. VDJ has an own scripting language to do any mappings of VDJ functions to the button. Easy things are in the pad editor to do by click some dependences together.
For DMX lighting in VDJ with OS2L they included some OS2L-Messages and merged it into the script code. (my meaning). The user can choose in pad editor a main function as DMX and then to "button push action" there comes for example a simple "os2l_button 'blackout' " . That should activate in lighting software the button called "blackout". Thats all.
Same in the Poi Editor of a track. You can set same simple message. I dont know if next time the button or same Cue is set, if the function will stop. Cannot test it.
For DMX lighting in VDJ with VDJArtnet its the same way, but other workaround. Instead of main function DMX you choose Custom and then to "button push action" you set a variable to a value (set artnet 1). You can use var names you wish. In the VDJArtnet in presets is var "artnet" included but also you can use as example "dmx_button".
In VDJArtnet plugin is only a list. Here line = artnet-channel. In a loop the list lines were read. The code in the lines is also the VDJ Script. Is in one line the dependency variable artnet = value 1 then the code will be executed. In this case it will set an artnet value of 255 to artnet channel else value 0.
In DMX Software you only catch the artnet channels , best as profile where you set the names of functions as used in VDJ.
At this point the VDJArtnet plugin gives you more functions because you can set buttons in VDJ to DMX or Pois in VDJ to DMX or only executing VDJ script code such as "every Beat" or "only first beat of 8" in dependencies you wish. This is an advantage !
The only thing what is to do if you use variables is to set them back to value 0. Means that once the var artnet =1 it never stop the code of that line. So in pad editor you can use more VDJ buttons with other values to switch from function to another. Or you simple set one button as "reset" with value 0.
In poi editor the same. First Cue you set artnet 1 and in Cue2 you can set to value 2 to start other function over other artnet channel. Or you simple set artnet 0 in Cue2 to stop the activated script code / Artnet channel.
What do you think ? Which things are with OSC possible ? And how should the plugin work to get the OSC commands directly to QLC+ and also the possibilities of self executing VDJ Script code to OSC command. What expects QLC+
regards ralf
) 
