Anmelden:     

Forum: VirtualDJ Technical Support

Topic: Automated Modular Lightshows using existing Cues
I want to save the work of writing in every song action cues that control the lightshow.
So I use the existing cue-points to call different Scenes in SWEET LIGHT.
Advantage:
Instead of always calling the same scene (action cue “os2l_button XYZ”), you could route the cues to different PRESETS.
So for Tina Turners "Private Dancer" You could choose
PAD1 “Bld in blue” or PAD2 “Romantic red”.
Each of these programs has 8 scenes that are automatically called up when Cue1-Cue8 is reached.

Here is the idea (and the problem as well):
The prerequisite is that VDJ and the SWEET LIGHT software are connected.
The relevant (hundreds of) songs have Cues on
Cue 1 = Intro
Cue 2 = verse 1
Cue 3 = chorus 1
Cue 4 = verse 2
Cue 5 = chorus 2
Cue 6 = Bridge/Drop
Cue 7 = Last chorus/outro
Cue 8 = flexible

Years ago, RUNE and LOCODOC helped me to program different LEDs of buttons that lit up when cue1, cue2 etc were reached:

deck left hotcue 2 exists ? deck left param_add  `cue_pos 2 & param_cast val`  `song_pos & param_multiply -1 `  & param_smaller 0.02 ? param_bigger -0.02 ? cue_countup & param_smaller 4 ? color 'green' : color 10% '#00ffff' : color 10% '#00ffff' : color 10% '#00ffff'


In upper case, the button lights up green for 4 beats when cue 2 is reached.
Now I replace 
color 'green'
with 
os2l_button “green”
but nothing happens in SweetLight.

So the following is NOT working:
deck left hotcue 2 exists ? deck left param_add  `cue_pos 2 & param_cast val`  `song_pos & param_multiply -1 `  & param_smaller 0.02 ? param_bigger -0.02 ? cue_countup & param_smaller 4 ? os2l_button "green" : nothing : nothing : nonthing


I have tested this in PadPages and with controller pads (AKAI APC40) - without success.
Mind you: A button with the simple command 
os2l_button “green”
works well and calls up the right scene in SWEETLIGHT.
Where is the error in thinking? Who can help?
 
geposted Fri 14 Mar 25 @ 11:29 pm
The code provided to you was meant to be used to control a LED.
A LED element, monitors the code and turns on/off or changes color based on the conditions of the code.
However the code used in a LED element can't fire another action like os2l_button
That's why it doesn't work for you.

Simply put is like asking for a LED element to also be able to set the deck on loop. It doesn't make sense, and if it could be done, it would be dangerous.

TBH, I think you approach this the wrong way.
I would use action POIs to trigger os2l buttons.
 
Thanks PHANTOMDEEJAY.
But I don´t want an Idea with this potential to be killed in a minute.

The code we are looking for has not to control an LED but is to be programmed as a PAD or controller button. There must also be some way to trigger a command when a normal cue point is reached (apart from action cues)
I am a “bread and butter DJ”. I don't have time to write action cues for the lights in hundreds of songs.
I'm also more flexible with the above concept. Is there no possibility?
 
This is a DJ software.
Which means that stuff usually happen when you make them happen, and not by their own.

Bare with me as I explain:

In VirtualDJ there are two types of actions.
1) Actions that happen when you push a button/move a slider e.t.c. (inputs) and
2) Actions that monitor the software in order to control LEDs e.t.c (outputs)

Outputs, cannot trigger inputs. That's what I said above.
In VirtualDJ, os2l_button is an "input" action despite the fact that the action then sends a command on some external/other app.
It's an "input" because it fires when you press a button.

Now, the only way to simulate an "output" triggering an input, is to use a repeat script.
The repeat script behaves as firing the same input every X amount of time.
So, if you write an "input" action on a button that checks the current position against a cue position in order to do something and then press it repeatedly every few ms, it will somehow behave as "moniotring" the cue position.
However, technically this solution is different, and there are a few variables that need to be considered (like reseting everything on a new track load)
Repeat scripts code can get quite messy. It needs carefull planning and debugging in order to use on cases like this.
Personally I would avoid that route. However most likely Locodog can come up with a nice 64 lines script that will do what you're after :P
Personally I would go the Action POI route.
Something that's not well known, is that you can write action POIs with the push of a button.
If needed, you can even write a code that will check all your current cues and place APOIs depending on what's present.
I would rather go that way, as it later can be further tweaked very easily. For instance, instead of always turning the lights green on every track's second verse, I can opt for some tracks to have them turn magenta without complex remapping and tweaking of my "repeat" script(s)
 
I've worked with about 20 light show guys, and a few girls, os2l has a meme name of "one second too late", I myself don't know if that's true, but I do know that the punters don't know the difference between a good light show and an world class light show.

I have a skin that makes writing action poi for light shows, it does both os2l and midi.
As is right now it has 256 calls [either os2l or midi] and it allows 1024 action poi per track, let me find a video...

this is an early video, since then I've added a better skin, better LED logic, pois are named and hardware support.
Like I said there's about 20 people using it, the original guy paid a lot but we were working out exactly what he wanted and to start with he wanted to test os2l and midi. [so it does both]
Other users, I've baked this into their skin of choice, a couple of users I put it into their device skins

video demo, all the buttons are nameable and if you want live CC control I can do that too.
 
[This is a DJ software.
Which means that stuff usually happen when you make them happen, and not by their own.]
YES PHANTOMDEEJAY, i totally agree!
Unlike other software with the creators of “my VDJ” I feel connected. In the last years all my dreams with scripts came true with the mighty help of You nice guys. We are all artists and longing to fulfill our dreams. ;-)

Thank You LOCODOC & PHANTOMDEEJAY for Your patience.
Please bare with me as I insist to save a lot of time.
1.) My method wants flexibility. Isn't it easier to be able to choose the routing to different scenes when reaching Cue2 than to rewrite the action cue every time?

I understand Your wish to keep the programming simple and secure but
2.) Action cues with the 
 os2l_button
command monitor the song position and work WITHOUT pressing a button. So why not monitor the cues?

The best and most secure option would be a new script variable 
 os2l_button “…” on_cue (1-99)


OK, this variable should be locked in actioncues. That's obvious. But could work in Pads, Controllerbuttons and Skins.

And with 
on_cue 3 -8beats
we could automatically fire a colorful FILL-IN that leads gently in the Chorus-Scene.
And all the fills, drops and scenes connected to the existing cues can be transformed into a different mood with a different preset button, without having to rewrite the cues each time.

Would it be possible to make such a variable available with an update?
May I ask for this in the WISHES-forum?
I'm not in a hurry, but I want to prepare an automated sound/light show for a concert in June.
Without unnecessary effort and with live intervention options (on the fly change of the moods/presets.