charliebuddrocker
Is it possibly to script a custom button to do this?
Effect "Cut" 1/2 beat length 2 times then 1/4 beat length 4 times then 1/2 beat length 2 time and last 1/4 beat lenght 2 times, strenght 50%?
Effect "Cut" 1/2 beat length 2 times then 1/4 beat length 4 times then 1/2 beat length 2 time and last 1/4 beat lenght 2 times, strenght 50%?
geposted Tue 15 Feb 22 @ 2:31 pm
klausmogensen
Something like:
effect_slider 'cut' 1 50% && effect_beats 'cut' 0.5 && effect_active 'cut' ON & wait 1bt & effect_beats 'cut' 0.25 & wait 1bt & effect_beats 'cut' 0.5 & wait 1bt & effect_beats 'cut' 0.25 & wait 0.5bt & effect_active 'cut' OFF
(the new wait action with it's bt option makes live a WHOLE LOT easier in these kind of cases!)
effect_slider 'cut' 1 50% && effect_beats 'cut' 0.5 && effect_active 'cut' ON & wait 1bt & effect_beats 'cut' 0.25 & wait 1bt & effect_beats 'cut' 0.5 & wait 1bt & effect_beats 'cut' 0.25 & wait 0.5bt & effect_active 'cut' OFF
(the new wait action with it's bt option makes live a WHOLE LOT easier in these kind of cases!)
geposted Tue 15 Feb 22 @ 2:42 pm
charliebuddrocker
Super thanks Klaus! It works like i wanted. Now i can script my own "Cut" pad with some groovy cut effect pattern like the beat grid effects settings.
But i have one more question:
Is (effect_beats 'cut' 0.5 && effect_active 'cut' ON) the same as (effect "cut" active & effect_slider "cut" 2 50%)?
If, which is best?
But i have one more question:
Is (effect_beats 'cut' 0.5 && effect_active 'cut' ON) the same as (effect "cut" active & effect_slider "cut" 2 50%)?
If, which is best?
geposted Tue 15 Feb 22 @ 8:39 pm
locoDog
same result but the first is better.
1 it uses the v8 script syntax, [v8 is more capable, and v7 syntax is fading from memory of people who help with script problems]
2 it uses effect_beats, [a v8 verb] no needing to look up how a dial position lines up with a beats measurement.
1 it uses the v8 script syntax, [v8 is more capable, and v7 syntax is fading from memory of people who help with script problems]
2 it uses effect_beats, [a v8 verb] no needing to look up how a dial position lines up with a beats measurement.
geposted Tue 15 Feb 22 @ 8:52 pm
charliebuddrocker
Thanks Locodog!
Now i understand it better.
Now i understand it better.
geposted Tue 15 Feb 22 @ 9:02 pm
charliebuddrocker
Same script that was described in the thread abow but now on a pad:
padfx "cut" 50% 0.25 while_pressed
It doesnt work. Second parameter jumps to 1/8. Needs to write:
padfx "cut" 50% 40% while_pressed
Should it work with 0.25 or?
And is this correct? It works but is it a better cleaner way?
padfx "cut" 50% 50% while_pressed & wait 1bt & effect_beats 'cut' 0.25 & wait 1bt & effect_beats 'cut' 0.5 & wait 1bt & effect_beats 'cut' 0.25 & wait 0.5bt
padfx "cut" 50% 0.25 while_pressed
It doesnt work. Second parameter jumps to 1/8. Needs to write:
padfx "cut" 50% 40% while_pressed
Should it work with 0.25 or?
And is this correct? It works but is it a better cleaner way?
padfx "cut" 50% 50% while_pressed & wait 1bt & effect_beats 'cut' 0.25 & wait 1bt & effect_beats 'cut' 0.5 & wait 1bt & effect_beats 'cut' 0.25 & wait 0.5bt
geposted Thu 24 Mar 22 @ 9:20 pm
locoDog
looks ok, not sure why the last wait is there for.
padfx uses % not beats.
padfx uses % not beats.
geposted Thu 24 Mar 22 @ 9:35 pm
charliebuddrocker
Yes I missed that unnecessary wait 😀
Is it OK to mix padfx and effect beat in the script or should i use only padfx in the whole script?
Is it OK to mix padfx and effect beat in the script or should i use only padfx in the whole script?
geposted Thu 24 Mar 22 @ 10:12 pm
locoDog
no it's fine, no problems with that.
@devs maybe padfx should understand bt params
@devs maybe padfx should understand bt params
geposted Thu 24 Mar 22 @ 10:15 pm
Adion
Indeed useful, will add 'bt' compatibility to padfx
geposted Fri 25 Mar 22 @ 3:30 am