Sign In:     

Forum: General Discussion

Topic: Filter Color FX Pad Page

This topic is old and might contain outdated or incorrect information.

This is probably one for Locodog!

I'm now having a go at scripting a padpage for the colorfx.... The Script that I have come up with is:

The basic idea is that:
1) If you press a pad it will select the associated colorfx and show the gui for that colorfx.
2) Press again and the gui toggles on/off.
3) If another colorfx Gui was previously selected with it's Gui open, that Gui is closed and replaced with the currently active one.
4) Finally the selected Colorfx can be toggled on/off by double clicking the pad when the Gui is open.

The Script that I have written for this is:
filter_selectcolorfx 'Filter' ? effect_show_gui 'colorfx' ? Doubleclick ? filter_activate : effect_show_gui 'colorfx' : effect_show_gui 'colorfx' : effect_show_gui 'colorfx' ? effect_show_gui 'colorfx' & filter_selectcolorfx 'Filter' & effect_show_gui 'colorfx' : filter_selectcolorfx 'Filter' & effect_show_gui 'colorfx'

With the coloring of the pads set to:
filter_selectcolorfx 'Filter' ? filter_activate? color 'Red' : Color 'Blue' : Off

This seems to work fine in terms of functionality however a couple of questions:
1) Although the pads show the correct colors, in the skin all the pads are highlighted all the time, whereas I would like it that it shows the pads as Off when not selected, Blue but not highlighted when selected but not active, and Red + Highlighted only when selected and active. Is this possible? I still haven't quite got my head around the skin engine and the scripting required to take this into account!

2) All the different colorfx Gui's behave as I would expect them to, showing a green active light when 'active' and with the controls in the Gui responding when colorfx knob is moved...... except the 'filter' colorfx. For some reason the Gui never registers as being active (whether the effect is active or not) and the Gui interface controls do not respond. (There also seems to be a quirk in the colorfx drop down list accessed either directly from the interface or from the command 'filter_selectcolorfx' - the 'filter' on/off switch does not visually respond turning from off to green as it does with all the other colorfxs, though it does register the correct reading next time the drop down list is called.) As the functionality seems to be ok I presume that this is just some little quirk in the skin or in the programming deep under the bonnet of VirtualDJ??

Many thanks for any help with these....
 
Posted Sun 22 Dec 19 @ 6:41 pm
1 - Adding a "off" everytime the gui is open and the effect does not match only the right pad will highlight:

filter_selectcolorfx 'Filter' ?effect_show_gui 'colorfx' ? Doubleclick ? filter_activate : effect_show_gui 'colorfx' : effect_show_gui 'colorfx' : effect_show_gui 'colorfx' ? off & effect_show_gui 'colorfx' & filter_selectcolorfx 'Filter' & effect_show_gui 'colorfx' : filter_selectcolorfx 'Filter' & effect_show_gui 'colorfx'

filter_selectcolorfx 'Cut' ? effect_show_gui 'colorfx' ? Doubleclick ? filter_activate : effect_show_gui 'colorfx' : effect_show_gui 'colorfx': effect_show_gui 'colorfx' ? off & effect_show_gui 'colorfx' & filter_selectcolorfx 'Cut' & effect_show_gui 'colorfx' : filter_selectcolorfx 'Cut' & effect_show_gui 'colorfx'

gui open -> highlight on top of active or selected or none
selected -> blue
active -> red

To get the highlight only when active

2 - look like a bug
the Gui interface controls do not respond with "filter". it seems the filter effect in the gui is not the one used by colorfx :\ maybe a is_colorfx missing
but sliders for other do not work as expected either ... see cut effect

by the way, gui for colorfx bus effect does not title as colorfx - the way aux mix sampler and release do - giving the same name the same plugin in a slot
 
Thanks Nicotux, yes I'd stumbled across that one (sort of copying from something that locodog had written in another thread!) as a way of getting all the non selected pads not to be highlighted, which is a great improvement.

However I would ideally like it to only be highlighted if a particular ColorFX was selected and activated - or at least understand why this is not possible as part of my scripting education! :-)

I tried adding a filter_activate ? on : off and filter_selectcolorfx 'cut' ? filter_activate ? on : off : off right at the end of the script to see if this would work (following the logic that locodog seemed to suggest the Skin Engine followed in the previous post) but it didn't seem to help.....

Still scratching my head... :-D
 
filter_activate is independent of the colorfx slider position, just like mfx active, even with the crossfader closed the "thing" is still active, even with colorfx & 50% it's still active.

filter_selectcolorfx 'cut' ? filter_activate ? filter 50% ? off : on : off : off
 
Hi Locodog,

Returning after a bit of an xmas break. Hope you had a good one if you were celebrating :-)

Once again thanks - another bit of the scripting jigsaw I would never have worked out for myself with the nature of 'filter_activate' readings. Great learning these new things....

However I've tried adding what you suggested to the script (& filter_selectcolorfx 'cut' ? filter_activate ? filter 50% ? off : on : off : off added at the end of the script) and it still doesn't appear to work. I'm still only getting the the highlighting on the interface appearing/not appearing dependent upon whether the colorfx gui is showing or not..... :-(
 
Why bother with the gui? isn't the colorfx dial enough?
 
Perhaps it's just a personal quirk, but I like to have the visuals of the fx gui visible..... however it's also now become a curiosity as to how the scripting might work as a way of learning more about scripting!
 


(Old topics and forums are automatically closed)