OSC output/feedback?
-
James Elliott
I am eagerly waiting for my Enttec OpenDMX Ethernet interface to arrive to start working with QLC Plus, currently I am using DMXIS but want to get more elaborate. I could not tell from the features whether OSC output (for feedback about channel changes) is supported. That would be *huge*, so that the control surfaces on TouchOSC are updated live as chases and presets are invoked. Does this work today? If not, how hard would it be to add?
-
Massimo Callegari
According to the support list http://www.qlcplus.org/features.html
OSC is input only at the moment.
OSC is standard, but unfortunately channels naming is not, so it's not so easy to implement feedbacks.
Output should be easier and it's in the plans. Just need to find the time to add it
OSC is input only at the moment.
OSC is standard, but unfortunately channels naming is not, so it's not so easy to implement feedbacks.
Output should be easier and it's in the plans. Just need to find the time to add it
-
James Elliott
Thanks for responding! I would think that the same mechanism used for learning channel names for input could be used for the output and feedback as well, no? I am not sure what you would need for feedback beyond output; if a DMX channel is assigned to an OSC control, receiving messages from that control would set the DMX channel, and any changes to the DMX channel value from within QLC Plus would generate output messages for the same controller via the OSC plugin.
I’ve got all the developer tools installed on my Macs, so if I get impatient after getting input working right and learning other aspects of working with the application (again, pending the arrival of my compatible DMX interface), I may take a crack at implementing this myself. But realistically I am going to be devoured by the lighting and DJing aspects for the foreseeable future.
I’ve got all the developer tools installed on my Macs, so if I get impatient after getting input working right and learning other aspects of working with the application (again, pending the arrival of my compatible DMX interface), I may take a crack at implementing this myself. But realistically I am going to be devoured by the lighting and DJing aspects for the foreseeable future.
-
Massimo Callegari
QLC+ is quite complex now. 120000+ lines of code. Advanced C++/Qt architecture.
I wouldn't suggest it to newbies.
I'd rather prefer if you can contribute with new fixtures. That would be already a great thing
OSC Output/Feedback will be implemented. Just don't know when, yet
I wouldn't suggest it to newbies.
I'd rather prefer if you can contribute with new fixtures. That would be already a great thing
OSC Output/Feedback will be implemented. Just don't know when, yet
-
James Elliott
Fair enough, and I already submitted my first fixture before you even posted this. I would just as soon stay out of the code; writing software is my day job, DJing and playing with lights is my hobby to get away from that. The area where I may need to jump in and help coding, if it isn’t there yet and I can’t persuade you into prioritizing it, is in building beat-based chases, so that the timing of the fades and changes happens at the right place in a musical measure even as I change the tempo within my DJ controller. But that is a topic for another thread.