DJJamieFox
Is there a way to adjust the 'Voc Reverb' in this pad mode to make the reverb a little less? I just want to adjust this only on "Voc Reverb' and not across the deck.
Posted 6 days ago @ 1:13 pm
DJ VinylTouch
Just edit the vdjscript for that pad for the Stems+FX page in the
Pad Page Editor
Pad Page Editor
Posted 6 days ago @ 1:20 pm
DJJamieFox
Man you are a lifesaver! I was pulling my hair out but knew there was an easier way. Still learning the features and script.
Can I control parameters of the reverb rather than just strength?
Can I control parameters of the reverb rather than just strength?
Posted 6 days ago @ 4:35 pm
DJ VinylTouch
Yes. Readup on the padfx verb on the vdjscript verb page
Parameters come after the name of the effect in quotes, and are positional, as displayed in the config UI for it (when you click the "gear cog" next to the effect, the sideview shows the parameters UI for the effect - the first param to the verb = the first configuration parameter you see in the UI and so on).
The default Stems+FX mapping for that pad button you asked about is an example of using stength and length with the Echo Out effect.
Parameters come after the name of the effect in quotes, and are positional, as displayed in the config UI for it (when you click the "gear cog" next to the effect, the sideview shows the parameters UI for the effect - the first param to the verb = the first configuration parameter you see in the UI and so on).
The default Stems+FX mapping for that pad button you asked about is an example of using stength and length with the Echo Out effect.
Posted 6 days ago @ 5:20 pm
DJJamieFox
Can the 'script verbs' be used in a skin XML file or is it just better to do these on the controller mapping. I use a Rane Four and the Vanced GT skin. I have modded the menus in that skin and was wondering about that. So much to learn...
Posted 17 hours ago
DJ VinylTouch
Yes. Read here:
https://www.virtualdj.com/wiki/Skin%20SDK
Most elements take an action attribute for vdjscript that is meant to perform some action and a visibility attribute for a vdjscript check that controls whether or not the element is visible or not.
Some elements I believe may have additional actions specifiable in vdjscript as well - like a button can have left click, right click, middle click and double click actions.
What is better for you only you can decide, but remember, what you do on the skin is normally accessible from interaction with the skin. If you do it as a controller mapping, it's only available if you connect the controller. If you do it as a pad mode button, that pad button is accessible from the skin, but the pad mode (and hence the button), could also be mapped to a controller with pad mode support too. If you make a keyboard shortcut, it's most likely always available (as long as a keyboard is comnected, which is the norm with laptops).
I tend to keep the last 2 for general mappings as I can always use them with or without a controller, and use the skin only for visual confirmation of things/mappings I don't use frequently, such as custom buttons. I only make controller level mappings for special cases, like deck move functionality on the DJM-S11.
https://www.virtualdj.com/wiki/Skin%20SDK
Most elements take an action attribute for vdjscript that is meant to perform some action and a visibility attribute for a vdjscript check that controls whether or not the element is visible or not.
Some elements I believe may have additional actions specifiable in vdjscript as well - like a button can have left click, right click, middle click and double click actions.
What is better for you only you can decide, but remember, what you do on the skin is normally accessible from interaction with the skin. If you do it as a controller mapping, it's only available if you connect the controller. If you do it as a pad mode button, that pad button is accessible from the skin, but the pad mode (and hence the button), could also be mapped to a controller with pad mode support too. If you make a keyboard shortcut, it's most likely always available (as long as a keyboard is comnected, which is the norm with laptops).
I tend to keep the last 2 for general mappings as I can always use them with or without a controller, and use the skin only for visual confirmation of things/mappings I don't use frequently, such as custom buttons. I only make controller level mappings for special cases, like deck move functionality on the DJM-S11.
Posted 17 hours ago