Alternative Xfader script (only echos when the fader is closed, makes for really clean echoed cuts)
Further thinking, other effects like flanger & reverb sound pretty good on the echo and they too can be triggered automatically by the crossfader position (so they only effect echo) all you have to do is add
& deck 2 effect_active 'Name' 1
(after the "deck 2 effect_slider 'echo' 1 80%" bit of the script in code)
& deck 1 effect_active 'Name' 1
(after the "deck 1 effect_slider 'echo' 1 80%" bit of the script in code)
& deck 1 effect_active 'Name' 0 & deck 2 effect_active 'Name' 0
(after the "deck 2 effect_slider 'echo' 1 0%" bit near the end of the script in code)
crossfader & deck 1 effect_active 'volume' ? param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% & deck 2 effect_slider 'echo' 1 80% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% & deck 1 effect_slider 'echo' 1 80% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% & deck 1 effect_slider 'echo' 1 0% & deck 2 effect_slider 'echo' 1 0% : crossfader
Further thinking, other effects like flanger & reverb sound pretty good on the echo and they too can be triggered automatically by the crossfader position (so they only effect echo) all you have to do is add
& deck 2 effect_active 'Name' 1
(after the "deck 2 effect_slider 'echo' 1 80%" bit of the script in code)
& deck 1 effect_active 'Name' 1
(after the "deck 1 effect_slider 'echo' 1 80%" bit of the script in code)
& deck 1 effect_active 'Name' 0 & deck 2 effect_active 'Name' 0
(after the "deck 2 effect_slider 'echo' 1 0%" bit near the end of the script in code)
Posted Sun 16 Nov 14 @ 6:14 am
sorry for the late reply locodog, I'm away now, will be back home maybe on wednesday 19, and will try the scripts... cant wait to give them a try!!
thanks a lot for the effort
thanks a lot for the effort
Posted Mon 17 Nov 14 @ 7:37 am
Thank you for putting it in to a released mapper and also for influencing me to keep pushing at it. I had a system that worked adequately for keyboard use (months ago), but your wish and willingness to test made me rethink, redesign, so that it's a system that almost any controller can use.
I honestly believe that the alternative xfader script is something that no other SW can do (and the HW solution would be bloody expensive), (that's why i love VDJ, scripting is so powerful once you understand it {for me serato is script illiterate, traktor scripts at a junior school level} )
I'm not saying it's perfect, yet, I've found that it isn't fully bomb proof, I need your confirmation that it works with HW, so then I can put the extra tests into the script, so that even if you tried to make it fail (by doing something weird/stupid) the script is smart enough to understand the user. (just lots of little additions/questions to the script)
I urge anyone using a controller/midi|HID mixer to participate.
I honestly believe that the alternative xfader script is something that no other SW can do (and the HW solution would be bloody expensive), (that's why i love VDJ, scripting is so powerful once you understand it {for me serato is script illiterate, traktor scripts at a junior school level} )
I'm not saying it's perfect, yet, I've found that it isn't fully bomb proof, I need your confirmation that it works with HW, so then I can put the extra tests into the script, so that even if you tried to make it fail (by doing something weird/stupid) the script is smart enough to understand the user. (just lots of little additions/questions to the script)
I urge anyone using a controller/midi|HID mixer to participate.
Posted Mon 17 Nov 14 @ 2:49 pm
locodog wrote :
post fader fx button(s)
Xfader script
post fader fx button(s)
crossfader +0% & Leftdeck ? deck 1 effect_active 'volume' ? deck 1 effect_active 'echo' ? deck 2 effect_active 'echo' ? deck 1 effect_active 'echo' 0 : crossfader_disable & crossfader +0% & deck 1 effect_active 'volume' 0 & deck 2 effect_active 'volume' 0 & deck 1 effect_active 'echo' 0 : deck 1 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : crossfader_disable & deck 1 effect_active 'volume' 1 & deck 2 effect_active 'volume' 1 & deck 1 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : deck 1 effect_active 'volume' ? deck 2 effect_active 'echo' ? deck 1 effect_active 'echo' ? deck 2 effect_active 'echo' 0 : crossfader_disable & crossfader +0% & deck 1 effect_active 'volume' 0 & deck 2 effect_active 'volume' 0 & deck 2 effect_active 'echo' 0 : deck 2 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : crossfader_disable & deck 1 effect_active 'volume' 1 & deck 2 effect_active 'volume' 1 & deck 2 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95%
Xfader script
crossfader & deck 1 effect_active 'volume' ? param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : crossfader
this is it! you've nailed it again, PFFX is working again and the Crossfader does not need refresh.
thank you very much locodog
Posted Tue 18 Nov 14 @ 1:01 pm
how do i go about this where do i put this in the mapping and how do i do it.?
Posted Tue 18 Nov 14 @ 1:08 pm
only works if you're using Midi Controllers, just add the PFFX script to a button to turn on/off PFFX, and the script to the Midi Crossfader. and thats it.
Posted Tue 18 Nov 14 @ 1:40 pm
vdj_pARtybOy wrote :
PFFX is working again and the Crossfader does not need refresh.
PFFX is working again and the Crossfader does not need refresh.
Great news! There is one problem that can happen in 2 ways (by doing something illogical) (I spent ages writing about them but I lost the post) I'll have the script amended when I'm not hung over.
Have you tried the alternative xfader script? I'm only using the mouse (and squeezing the script into the skin) but here it sounds first rate.
@angelt99 like partyboy says the audio has to go through the SW crossfader Also you have to have the volume effect installed, then all you need to do is press the button, every thing looks normal but the audio goes through an artificial crossfader and that makes the echo effect post cross fader. The alternative xfader script is smarter that you only hear the echo when the crossfader is closed. Which I can't get over how good it sounds.
Posted Wed 19 Nov 14 @ 7:00 am
Just ironed out the final kinks that caused problems in rare cases.
For anyone just joining this thread you need to have the volume effect installed & your HW Xfader has to be connected to the SW crossfader
This will also work for keyboard/mouse/no HW users.
Post fader fx button(s) Put this script on a button mapping or 2 custom buttons (one for each side).
Action One press on, One press off.
Now pick one of these two scripts for the crossfader (I'd recommend the advanced one).
Traditional Xfader script (apply this script to your xfader mapping or for mouse/keyboard users insert this into the crossfader action inside the skin)
Action: After pressing the button the echo effect becomes post crossfader.
Advanced Xfader script (apply this script to your xfader mapping or for mouse/keyboard users insert this into the crossfader action inside the skin)
Action: after pressing the button the, echo effect is again post crossfader but only when the fader is closed, makes for really clean echoed cuts.
That's it! As far as I can see it's pretty unbreakable. The next phase is 4 decks and an assigned crossfader which is going to be wildly complicated to script as fool-proof as this is now but not impossible.
For anyone just joining this thread you need to have the volume effect installed & your HW Xfader has to be connected to the SW crossfader
This will also work for keyboard/mouse/no HW users.
Post fader fx button(s) Put this script on a button mapping or 2 custom buttons (one for each side).
Action One press on, One press off.
crossfader +0% & Leftdeck ? deck 1 effect_active 'volume' ? deck 1 effect_active 'echo' ? deck 2 effect_active 'echo' ? deck 1 effect_active 'echo' 0 : crossfader_disable 0 & crossfader +0% & deck 1 effect_active 'volume' 0 & deck 2 effect_active 'volume' 0 & deck 1 effect_active 'echo' 0 : deck 1 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : crossfader_disable 1 & deck 1 effect_active 'volume' 1 & deck 2 effect_active 'volume' 1 & deck 1 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : deck 1 effect_active 'volume' ? deck 2 effect_active 'echo' ? deck 1 effect_active 'echo' ? deck 2 effect_active 'echo' 0 : crossfader_disable 0 & crossfader +0% & deck 1 effect_active 'volume' 0 & deck 2 effect_active 'volume' 0 & deck 2 effect_active 'echo' 0 : deck 2 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : crossfader_disable 1 & deck 1 effect_active 'volume' 1 & deck 2 effect_active 'volume' 1 & deck 2 effect_active 'echo' 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95%
Now pick one of these two scripts for the crossfader (I'd recommend the advanced one).
Traditional Xfader script (apply this script to your xfader mapping or for mouse/keyboard users insert this into the crossfader action inside the skin)
Action: After pressing the button the echo effect becomes post crossfader.
crossfader & deck 1 effect_active 'volume' ? crossfader_disable 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% : crossfader & crossfader_disable 0
Advanced Xfader script (apply this script to your xfader mapping or for mouse/keyboard users insert this into the crossfader action inside the skin)
Action: after pressing the button the, echo effect is again post crossfader but only when the fader is closed, makes for really clean echoed cuts.
crossfader & deck 1 effect_active 'volume' ? crossfader_disable 1 & param_bigger crossfader 2% ? deck 1 effect_slider 'volume' 1 100% & deck 2 effect_slider 'volume' 1 0% & deck 2 effect_slider 'echo' 1 80% : param_smaller crossfader 98% ? deck 1 effect_slider 'volume' 1 0% & deck 2 effect_slider 'volume' 1 100% & deck 1 effect_slider 'echo' 1 80% : deck 1 effect_slider 'volume' 1 95% & deck 2 effect_slider 'volume' 1 95% & deck 1 effect_slider 'echo' 1 0% & deck 2 effect_slider 'echo' 1 0% : crossfader & crossfader_disable 0
That's it! As far as I can see it's pretty unbreakable. The next phase is 4 decks and an assigned crossfader which is going to be wildly complicated to script as fool-proof as this is now but not impossible.
Posted Thu 20 Nov 14 @ 1:27 am
Hi locodog, I was so happy with the new working script,I didn't gave a shot to the other scripts,I will try them later on tonight,and post the results.
yes the 4 decks script,would be the final PFFX script.
thanks again.
yes the 4 decks script,would be the final PFFX script.
thanks again.
Posted Thu 20 Nov 14 @ 4:51 am
the new script works fine,like the previous working script, the alternative XF, only echoes when the xf is closed, I dont see me using that alternative xf script,but thanks anyway,nice job.
like you said, the PFFX works for any FX,flanger,reverb,loop roll,slicer,etc... for ex: I can have the flanger FX activated then press PFFX and have Flanger+Echo FX post (x)fader.
looking forward to the 4 decks PFFX (no rush!!)
thanks locodog your PFFX rocks!!!
like you said, the PFFX works for any FX,flanger,reverb,loop roll,slicer,etc... for ex: I can have the flanger FX activated then press PFFX and have Flanger+Echo FX post (x)fader.
looking forward to the 4 decks PFFX (no rush!!)
thanks locodog your PFFX rocks!!!
Posted Sat 22 Nov 14 @ 12:47 pm
When chaining other effects especially the longer length phasing FX (phaser/flanger) The order which you chain becomes important.
If the flanger is on first, the echo effect is sampling a bit of the audio part way through the flanging cycle, but if you turn the flanger on second then the flanging cycle will go all the way through.
So phasing FX can be started before or after, but the results will be slightly different
FX like reverb/distortion can be started before or after and the results might be the same or they might not (if you don't work the dials or do)
Transport FX like beatgrid/slicer/loop roll/backspin have to go first.
I'm looking at 4 decks now and I can get it to work in a basic way, just it's difficult to make it a complete package, the crossfader assign creates lots of ways for it to go wrong.
But if it was easy it would have already been done...
If the flanger is on first, the echo effect is sampling a bit of the audio part way through the flanging cycle, but if you turn the flanger on second then the flanging cycle will go all the way through.
So phasing FX can be started before or after, but the results will be slightly different
FX like reverb/distortion can be started before or after and the results might be the same or they might not (if you don't work the dials or do)
Transport FX like beatgrid/slicer/loop roll/backspin have to go first.
I'm looking at 4 decks now and I can get it to work in a basic way, just it's difficult to make it a complete package, the crossfader assign creates lots of ways for it to go wrong.
But if it was easy it would have already been done...
Posted Sat 22 Nov 14 @ 9:56 pm
Well I've been keeping an eye on this thread and today I applied the needed scripts and effects. I dusted off the NS7 and THIS FRICKING WORKS!!
Now I have yet to try it with my DJM T1 but I am happy with the results on my NS7!!
Thanks a million, we owe you big time for this!! 👏👏👏👏👏👍👌
Now I have yet to try it with my DJM T1 but I am happy with the results on my NS7!!
Thanks a million, we owe you big time for this!! 👏👏👏👏👏👍👌
Posted Mon 24 Nov 14 @ 10:47 pm
Ok so I got up this morning for an early morning scratch session before work and I noticed that when I turn the script on it's only working on deck 1.
So I came back to this page copy the scripts again then went into VDJ and pasted them, closed VDJ and reopened it.
The same problem, would work on deck 1. I had to manually turn the ehco on deck 2 in order for it to work.
Am I missing something here??
So I came back to this page copy the scripts again then went into VDJ and pasted them, closed VDJ and reopened it.
The same problem, would work on deck 1. I had to manually turn the ehco on deck 2 in order for it to work.
Am I missing something here??
Posted Tue 25 Nov 14 @ 7:48 am
Oh, ok erm, you're using HW 2 buttons that share 1 mapping right?
Because it's set up so you can pick left or right (with a left or right button) or both (both buttons)
Although if you only want 1 button that works on the active deck that should work too, I have 2 customs to prove how it would work with a dedicated HW button per side, but I also have the same script on a single keyboard key that works with the active deck (keyboard users hate the mouse too)
*edit* thought occurred if you only wanted HW 1 button, that button can't be defined to a side. (this is why I dislike shared mappings, they're quicker to create but sacrifice/complicate customisation )
Because it's set up so you can pick left or right (with a left or right button) or both (both buttons)
Although if you only want 1 button that works on the active deck that should work too, I have 2 customs to prove how it would work with a dedicated HW button per side, but I also have the same script on a single keyboard key that works with the active deck (keyboard users hate the mouse too)
*edit* thought occurred if you only wanted HW 1 button, that button can't be defined to a side. (this is why I dislike shared mappings, they're quicker to create but sacrifice/complicate customisation )
Posted Tue 25 Nov 14 @ 7:54 am
I mapped a button on my keyboard not on any controllers, not sure if that makes a difference??
Posted Tue 25 Nov 14 @ 8:42 am
Phew! I thought I was in trouble for a second.
Ok for keyboard then it only actives it on the active deck, so if you want it activated on deck 2, deck 2 has to to be the active deck. (that's why you only got deck 1)
Or what you could do is put the script on 2 custom buttons, (left and right) and then map a keyboard key to each custom button (these are the first ones left and right)
custom_button 1
custom_button 6
Ok for keyboard then it only actives it on the active deck, so if you want it activated on deck 2, deck 2 has to to be the active deck. (that's why you only got deck 1)
Or what you could do is put the script on 2 custom buttons, (left and right) and then map a keyboard key to each custom button (these are the first ones left and right)
custom_button 1
custom_button 6
Posted Tue 25 Nov 14 @ 8:53 am
Gotcha 👌
But when I try this with my DJM T1 I will need left/right device........ Etc.
But when I try this with my DJM T1 I will need left/right device........ Etc.
Posted Tue 25 Nov 14 @ 9:23 am
Cool, the good thing about this little confusion it's given me a good idea that I've posted in wishes (an effect that lets you make a effect chain made from existing effects, so you don't need a dedicated button)
Just remember the audio can't go through the HW crossfader.
I have a plan so eventually it can. (for hybrids)
Just remember the audio can't go through the HW crossfader.
I have a plan so eventually it can. (for hybrids)
Posted Tue 25 Nov 14 @ 9:31 am
That's exactly what I was gonna post!! We need a way to save our effects.. 👍
Posted Tue 25 Nov 14 @ 10:01 am
I've actually figured out a way to do the suggestion right now, (skinning mapping and using custom buttons) it's just a shame my skinning progress is so slow.
If you get a chance could you give me your opinion on the advanced xfafader, partyboy wasn't keen but I'm using it so much now.
If you get a chance could you give me your opinion on the advanced xfafader, partyboy wasn't keen but I'm using it so much now.
Posted Tue 25 Nov 14 @ 5:08 pm