jima12
Hello,
I am trying to learn how I can code to pads to increase volume slowly rather than instantly.
I have 3 pads set up Levels at 100% 50% 15%. I want the volume to increase/decrease slowly.
I am not an expert at coding this but only thing I have is levels set.
I found something for button mapping repeat_stop 'test2' & repeat_start 'test' 60ms 85 & deck left volume -1% & deck right volume -1% & repeat_stop 'test' but if the key is pressed twice the volume goes to 0. Is there way to stop the code so it doesn't repeat again on the same key press
I am trying to learn how I can code to pads to increase volume slowly rather than instantly.
I have 3 pads set up Levels at 100% 50% 15%. I want the volume to increase/decrease slowly.
I am not an expert at coding this but only thing I have is levels set.
I found something for button mapping repeat_stop 'test2' & repeat_start 'test' 60ms 85 & deck left volume -1% & deck right volume -1% & repeat_stop 'test' but if the key is pressed twice the volume goes to 0. Is there way to stop the code so it doesn't repeat again on the same key press
Mensajes Mon 27 Jan 25 @ 4:50 pm
locoDog
repeat_start fadeUp ? repeat_stop fadeUp : repeat_stop fadeDown & repeat_start fadeUp 33ms -1 & param_equal `level` 1.0 ? repeat_stop fadeUp : level +1%
repeat_start fadeUp ? repeat_stop fadeUp : repeat_start fadeDown ? repeat_stop fadeDown : param_smaller 0.5 level ? repeat_start fadeUp 33ms -1 & param_smaller level 0.5 ? repeat_stop fadeUp & level 0.5 : level +1% : param_bigger 0.5 level ? repeat_start fadeDown 33ms -1 & param_bigger level 0.5 ? repeat_stop fadeDown & level 0.5 : level -1% :
repeat_start fadeUp ? repeat_stop fadeUp : repeat_start fadeDown ? repeat_stop fadeDown : param_smaller 0.15 level ? repeat_start fadeUp 33ms -1 & param_smaller level 0.15 ? repeat_stop fadeUp & level 0.15 : level +1% : param_bigger 0.15 level ? repeat_start fadeDown 33ms -1 & param_bigger level 0.15 ? repeat_stop fadeDown & level 0.15 : level -1% :
repeat_start fadeUp ? repeat_stop fadeUp : repeat_start fadeDown ? repeat_stop fadeDown : param_smaller 0.5 level ? repeat_start fadeUp 33ms -1 & param_smaller level 0.5 ? repeat_stop fadeUp & level 0.5 : level +1% : param_bigger 0.5 level ? repeat_start fadeDown 33ms -1 & param_bigger level 0.5 ? repeat_stop fadeDown & level 0.5 : level -1% :
repeat_start fadeUp ? repeat_stop fadeUp : repeat_start fadeDown ? repeat_stop fadeDown : param_smaller 0.15 level ? repeat_start fadeUp 33ms -1 & param_smaller level 0.15 ? repeat_stop fadeUp & level 0.15 : level +1% : param_bigger 0.15 level ? repeat_start fadeDown 33ms -1 & param_bigger level 0.15 ? repeat_stop fadeDown & level 0.15 : level -1% :
Mensajes Mon 27 Jan 25 @ 6:28 pm
jima12
@locodog Thank you so much!
I tried this one and it doesn't seem to work
repeat_start fadeUp ? repeat_stop fadeUp : repeat_stop fadeDown & repeat_start fadeUp 33ms -1 & level 100% ? repeat_stop fadeUp : level +1%
Another issue I am having is when I set the 50% and 15% to the pads they work fine. But if I button map it to a key, only the right deck goes down never both the decks go down at once. Do you know why this is happening?
I tried this one and it doesn't seem to work
repeat_start fadeUp ? repeat_stop fadeUp : repeat_stop fadeDown & repeat_start fadeUp 33ms -1 & level 100% ? repeat_stop fadeUp : level +1%
Another issue I am having is when I set the 50% and 15% to the pads they work fine. But if I button map it to a key, only the right deck goes down never both the decks go down at once. Do you know why this is happening?
Mensajes Mon 27 Jan 25 @ 6:53 pm
locoDog
try this instead
& param_equal `level` 1.0 ?
pads have a deck implied due to there being pads on either side, keyboard keys use the selected deck as the implied deck
& param_equal `level` 1.0 ?
pads have a deck implied due to there being pads on either side, keyboard keys use the selected deck as the implied deck
Mensajes Mon 27 Jan 25 @ 6:55 pm
jima12
@locoDog
Thank you that worked.
repeat_stop 'test2' & repeat_start 'test' 60ms 85 & deck left volume -1% & deck right volume -1% & repeat_stop 'test'
this is code I found which is working for both decks once but assume I press the key and volume is at 15%, If I press is again it goes down to 0.
Your code works flawlessly but I'm not sure where I would add deck left and right for key mapping and make sure the pad code doesn't collide with button mapping code. Sorry if I am asking for too much, I am still learning. Also if you know any guide for the future to keep learning that would be great.
Thank you that worked.
repeat_stop 'test2' & repeat_start 'test' 60ms 85 & deck left volume -1% & deck right volume -1% & repeat_stop 'test'
this is code I found which is working for both decks once but assume I press the key and volume is at 15%, If I press is again it goes down to 0.
Your code works flawlessly but I'm not sure where I would add deck left and right for key mapping and make sure the pad code doesn't collide with button mapping code. Sorry if I am asking for too much, I am still learning. Also if you know any guide for the future to keep learning that would be great.
Mensajes Tue 28 Jan 25 @ 12:21 am
locoDog
When you specify a deck it is carried to all further verbs, until you specify another deck, so this case specify at the start will be enough.
if you want both decks to act then specify
deck all
but if you wish to expand the script take note of
https://www.virtualdj.com/forums/223743/General_Discussion/Script_School.html?page=45.70
because deck all starts several script threads.
if you want both decks to act then specify
deck all
but if you wish to expand the script take note of
https://www.virtualdj.com/forums/223743/General_Discussion/Script_School.html?page=45.70
because deck all starts several script threads.
Mensajes Tue 28 Jan 25 @ 12:30 am
jima12
@locoDog
Thank you, sorry going to bug one last time as I ran into an issue.
I have deck all set up as 1-9 keys which works flawlessly.
I have a key set up V which follows the following code - mic_talkover 20% 1800ms & mic_volume 95%
When V key is used the code for deck all doesn't work as the volume sliders will try to go up but doesn't.
I took you code and added (mic_talkover 20% 1800ms & mic_volume 95%) at the end, the code does work but only when the volume goes the the set % and while the key is pressed.
Can you help me with your code to add mic talk over?
Thank you, sorry going to bug one last time as I ran into an issue.
I have deck all set up as 1-9 keys which works flawlessly.
I have a key set up V which follows the following code - mic_talkover 20% 1800ms & mic_volume 95%
When V key is used the code for deck all doesn't work as the volume sliders will try to go up but doesn't.
I took you code and added (mic_talkover 20% 1800ms & mic_volume 95%) at the end, the code does work but only when the volume goes the the set % and while the key is pressed.
Can you help me with your code to add mic talk over?
Mensajes Tue 28 Jan 25 @ 7:54 pm
locoDog
mic_talkover sets some internal variables when switched on, deck levels and the speed it was told to move, when mic_talkover is switched off these "hidden" variables are used to reset.
You're starting a fightyou I can't win... ( ...reliably, 3 out of 5 is worse than 0 out of 100 )
we've pretty much already recreated mic_talkover with the script above, so don't use mic_talkover,
I could work it all out but we're talking about 1:1 technician levels of support.
You're starting a fight
we've pretty much already recreated mic_talkover with the script above, so don't use mic_talkover,
I could work it all out but we're talking about 1:1 technician levels of support.
Mensajes Tue 28 Jan 25 @ 9:31 pm