Hi, I was wondering if anyone could point out how to add on of the downloaded FX to one of the four custom buttons? I figure out where the code is. I would like to learn how to do this for other effects (eg morbius etc) as well. Not much in documentation.
Thanks in advance
Thanks in advance
Posté Fri 29 Nov 24 @ 5:31 am
[deck specifier] verb [params] [while_pressed]
deck specifier not needed custom_buttons already have an implied deck,
verb = effect_active in this case
params available (in order) for effect_active;
slot number/stem (optional)
effect name (optional if you have already decided slot, *not optional for stems)
effect state to change to (BLANK|on|off|toggle|1|0|-1) (also allows `get_* actions to determine state)
so params = effect name (inside " " or ' ' if the name contains a space)
Posté Fri 29 Nov 24 @ 5:50 am
Loco, still trying to figure out the custom buttons. You mentioned they have an implied deck.
I added a shortcut key "V" to one of the buttons (its for the abt extension):
var '@$abpmt_source' 1 ? auto_bpm_transition 'source_original' : auto_bpm_transition
When one side is playing and I hit "V", the opposite deck turns on the function vs the deck that is actually playing. When I did this with a padfx, VDJ figures out which deck is active and applies the button to the correct side.
Any thoughts on why the logic seems different for the abt extension?
I added a shortcut key "V" to one of the buttons (its for the abt extension):
var '@$abpmt_source' 1 ? auto_bpm_transition 'source_original' : auto_bpm_transition
When one side is playing and I hit "V", the opposite deck turns on the function vs the deck that is actually playing. When I did this with a padfx, VDJ figures out which deck is active and applies the button to the correct side.
Any thoughts on why the logic seems different for the abt extension?
Posté Wed 04 Dec 24 @ 11:43 pm
with keyboard shortcuts the selected deck is implied.
Posté Thu 05 Dec 24 @ 2:04 am