I am in the process of programming eventbased control of my dmx through VDJ.
One candidate is to use QLC+ with a pure SW based solution with APOI's.
The other way I am thinking about is to simply use my lighting desk which I have in use today which accept both OSC and ArtNet as external triggers, so my question is:
Is there a way to direct the APOI's to generate OSC or ArtNet messages?
Thanks
One candidate is to use QLC+ with a pure SW based solution with APOI's.
The other way I am thinking about is to simply use my lighting desk which I have in use today which accept both OSC and ArtNet as external triggers, so my question is:
Is there a way to direct the APOI's to generate OSC or ArtNet messages?
Thanks
Posted Sun 07 Jan 24 @ 1:43 pm
Not really, not in an easy way.
Your best bet would be to create a Virtual MIDI device (so that APOIs trigger MIDI messages) and then use a MIDI to OSC converter/translator app.
It can be done, and it's a bit of a mess to setup, but once it's working there are no "unstable" variables that could brake it.
Your best bet would be to create a Virtual MIDI device (so that APOIs trigger MIDI messages) and then use a MIDI to OSC converter/translator app.
It can be done, and it's a bit of a mess to setup, but once it's working there are no "unstable" variables that could brake it.
Posted Mon 08 Jan 24 @ 6:52 am
previous skin sent is set up for the virtual device angle, I've a mapping and definition already wrote, I just need the driver name of the virtual midi cable.
Posted Mon 08 Jan 24 @ 6:58 am
Thanks Loco, do you mean the driver for the lighting console of mine ?
Or:
https://www.tobias-erichsen.de/software/loopmidi.html
Or:
https://www.tobias-erichsen.de/software/loopmidi.html
Posted Mon 08 Jan 24 @ 10:19 am
loopmidi
Posted Mon 08 Jan 24 @ 7:06 pm
Mobile Zombie wrote :
I am in the process of programming eventbased control of my dmx through VDJ.
One candidate is to use QLC+ with a pure SW based solution with APOI's.
The other way I am thinking about is to simply use my lighting desk which I have in use today which accept both OSC and ArtNet as external triggers, so my question is:
Is there a way to direct the APOI's to generate OSC or ArtNet messages?
Thanks
One candidate is to use QLC+ with a pure SW based solution with APOI's.
The other way I am thinking about is to simply use my lighting desk which I have in use today which accept both OSC and ArtNet as external triggers, so my question is:
Is there a way to direct the APOI's to generate OSC or ArtNet messages?
Thanks
I Used QLC+ on raspi as my OSC/Artnet target /gateway, The raspi just had a generic rs485 adapter and QLC+ was programmed with the DMX devices as output and ArtNet on QLC+ would do the translation layer , Input wise QLC+ has all the basics set (blackout,strobe, colour select , beat via QLC, beat VIA DMX devices onboard etc)
This setup gave me great flexibility as a lot of newer programs can use ArtNet/osc as outputs to my old DMX devices without the user needing to do a massive setup each time they use the system or knowing a single DMX address and data value, they just point to my IP and retrieve the panel layout.
I didnt have access to Lighting desk's in the time I had so this proved to be a working and very cheap solution as the pi also had a touch screen and would boot into my QLC+ profile ready to go so users could also control the light from that and lots of space saved as well as the age old issue of drinks damage on the control panels as the pi was mounted eye height and off to the side so they could see the effects as they hit buttons and not be looking down.
I think the hardest two parts was first adding in profiles for my no name brand DMX tech and then designing a easy to use layout in QLC that made sense to the user (colours, gobi spotlight positions etc)
This solution again came in very handy as on one event that was not DJ's but a band they needed specific lighting for the song and wanted to mount ,cable and program their lights the day of the event, as it turned out we had the lights they needed installed and setup and connecting their Ipad to QLC+ instantly provided the control profile and they just played back the control sequence and the only change they needed to make their side was recording a new walking path for the artist's walk in solo.
So while not easy to setup initially that was overshadowed by it's flexibility for me.
Bonus story , I used to carry one round as a spare for the work I did and one occasion I was DJ'ing at a event and their panel had failed , i was able to program the DMX channels real quick and have my normal layout.
darkspr1te
Posted Tue 09 Jan 24 @ 9:57 am
locodog wrote :
loopmidi

Posted Tue 09 Jan 24 @ 10:06 am
darkspr1te wrote :
I Used QLC+ on raspi as my OSC/Artnet target /gateway, The raspi just had a generic rs485 adapter and QLC+ was programmed with the DMX devices as output and ArtNet on QLC+ would do the translation layer , Input wise QLC+ has all the basics set (blackout,strobe, colour select , beat via QLC, beat VIA DMX devices onboard etc)
This setup gave me great flexibility as a lot of newer programs can use ArtNet/osc as outputs to my old DMX devices without the user needing to do a massive setup each time they use the system or knowing a single DMX address and data value, they just point to my IP and retrieve the panel layout.
I didnt have access to Lighting desk's in the time I had so this proved to be a working and very cheap solution as the pi also had a touch screen and would boot into my QLC+ profile ready to go so users could also control the light from that and lots of space saved as well as the age old issue of drinks damage on the control panels as the pi was mounted eye height and off to the side so they could see the effects as they hit buttons and not be looking down.
I think the hardest two parts was first adding in profiles for my no name brand DMX tech and then designing a easy to use layout in QLC that made sense to the user (colours, gobi spotlight positions etc)
This solution again came in very handy as on one event that was not DJ's but a band they needed specific lighting for the song and wanted to mount ,cable and program their lights the day of the event, as it turned out we had the lights they needed installed and setup and connecting their Ipad to QLC+ instantly provided the control profile and they just played back the control sequence and the only change they needed to make their side was recording a new walking path for the artist's walk in solo.
So while not easy to setup initially that was overshadowed by it's flexibility for me.
Bonus story , I used to carry one round as a spare for the work I did and one occasion I was DJ'ing at a event and their panel had failed , i was able to program the DMX channels real quick and have my normal layout.
darkspr1te
Mobile Zombie wrote :
I am in the process of programming eventbased control of my dmx through VDJ.
One candidate is to use QLC+ with a pure SW based solution with APOI's.
The other way I am thinking about is to simply use my lighting desk which I have in use today which accept both OSC and ArtNet as external triggers, so my question is:
Is there a way to direct the APOI's to generate OSC or ArtNet messages?
Thanks
One candidate is to use QLC+ with a pure SW based solution with APOI's.
The other way I am thinking about is to simply use my lighting desk which I have in use today which accept both OSC and ArtNet as external triggers, so my question is:
Is there a way to direct the APOI's to generate OSC or ArtNet messages?
Thanks
I Used QLC+ on raspi as my OSC/Artnet target /gateway, The raspi just had a generic rs485 adapter and QLC+ was programmed with the DMX devices as output and ArtNet on QLC+ would do the translation layer , Input wise QLC+ has all the basics set (blackout,strobe, colour select , beat via QLC, beat VIA DMX devices onboard etc)
This setup gave me great flexibility as a lot of newer programs can use ArtNet/osc as outputs to my old DMX devices without the user needing to do a massive setup each time they use the system or knowing a single DMX address and data value, they just point to my IP and retrieve the panel layout.
I didnt have access to Lighting desk's in the time I had so this proved to be a working and very cheap solution as the pi also had a touch screen and would boot into my QLC+ profile ready to go so users could also control the light from that and lots of space saved as well as the age old issue of drinks damage on the control panels as the pi was mounted eye height and off to the side so they could see the effects as they hit buttons and not be looking down.
I think the hardest two parts was first adding in profiles for my no name brand DMX tech and then designing a easy to use layout in QLC that made sense to the user (colours, gobi spotlight positions etc)
This solution again came in very handy as on one event that was not DJ's but a band they needed specific lighting for the song and wanted to mount ,cable and program their lights the day of the event, as it turned out we had the lights they needed installed and setup and connecting their Ipad to QLC+ instantly provided the control profile and they just played back the control sequence and the only change they needed to make their side was recording a new walking path for the artist's walk in solo.
So while not easy to setup initially that was overshadowed by it's flexibility for me.
Bonus story , I used to carry one round as a spare for the work I did and one occasion I was DJ'ing at a event and their panel had failed , i was able to program the DMX channels real quick and have my normal layout.
darkspr1te
Thanks for providing this info.
But how did you output data to the QLC+ raspi from VDJ? OS2L?
Posted Tue 09 Jan 24 @ 10:34 am
I had it working via Both OSL and the dmx-artnet plug in if i recall right (has been a few years)
i mostly used dmx-artnet plugin though as OSL translation layer at the time would have a delay in there, it would not update clients for changes made via dmx-artnet unless you made a change in OSL at least thats what i found on the ipad app i had at the time.
mst of the issues i cafed are ment to be fixed in the later versions of qlc+ , at the time the last v4 was coming out and anything after would be v5, which i never checked out.
darkspr1te
i mostly used dmx-artnet plugin though as OSL translation layer at the time would have a delay in there, it would not update clients for changes made via dmx-artnet unless you made a change in OSL at least thats what i found on the ipad app i had at the time.
mst of the issues i cafed are ment to be fixed in the later versions of qlc+ , at the time the last v4 was coming out and anything after would be v5, which i never checked out.
darkspr1te
Posted Tue 09 Jan 24 @ 1:52 pm