jangeador
I was looking at a custom mapping for a ddj sx3 and the guy in the video is able to switch to the secondary pad mode by pressing the pad mode twice without having to use shift. Every time he presses pad mode it switches between primary and secondary.
This is the video
https://youtu.be/1q35B-IfJcU
How can this be accomplished? Also he has a brake effect assign to a button as well as an echo out. His mapping is truly better than the original imho. Can someone help me do this mapping.
Thanks in advance.
This is the video
https://youtu.be/1q35B-IfJcU
How can this be accomplished? Also he has a brake effect assign to a button as well as an echo out. His mapping is truly better than the original imho. Can someone help me do this mapping.
Thanks in advance.
Inviato Tue 18 Jun 19 @ 4:03 am
Nicotux
Well at 0:31 he start to use shift + mode button
in fact the shift + mode button toggle padpage
mode button:
pad_page "thepadpage" ? pad_bank2 : pad_page "thepadpage"
this is detectable because pad_bank2 pads 9..16 toggle all together
but its map is a little bit different maybe something like this
pad_page "thepadpage" & shift ? toggle 'shiftmode' : var 'shiftmode' ? pad_bank2
in fact the shift + mode button toggle padpage
mode button:
pad_page "thepadpage" ? pad_bank2 : pad_page "thepadpage"
this is detectable because pad_bank2 pads 9..16 toggle all together
but its map is a little bit different maybe something like this
pad_page "thepadpage" & shift ? toggle 'shiftmode' : var 'shiftmode' ? pad_bank2
Inviato Tue 18 Jun 19 @ 5:45 am
PhantomDeejay
If you want to switch pad pages without shift then you need to remap the pad mode buttons
Example for the code needed on HOTCUE pad mode button:
pad_page 'hotcues' ? pad_page 'cueloop' : pad_page 'hotcues'
Repeat the above procedure for the rest pad mode buttons. Do NOT mess with the LED code mapping (leave it as it is)
PS: The default mapper of any device supported by VirtualDJ tries to provide a functionality which is as close possible to the original functionality of the device (with it's original software, or based on silkscreen printing)
Sure we can come up with much more advanced and dynamic mappings if we ignore the way a controller works with it's original software. But then you get hundreds of complaints that this or that doesn't work like it's supposed to
Example for the code needed on HOTCUE pad mode button:
pad_page 'hotcues' ? pad_page 'cueloop' : pad_page 'hotcues'
Repeat the above procedure for the rest pad mode buttons. Do NOT mess with the LED code mapping (leave it as it is)
PS: The default mapper of any device supported by VirtualDJ tries to provide a functionality which is as close possible to the original functionality of the device (with it's original software, or based on silkscreen printing)
Sure we can come up with much more advanced and dynamic mappings if we ignore the way a controller works with it's original software. But then you get hundreds of complaints that this or that doesn't work like it's supposed to
Inviato Tue 18 Jun 19 @ 7:45 am
MrDjLinton
PhantomDeejay wrote :
Sure we can come up with much more advanced and dynamic mappings if we ignore the way a controller works with it's original software. But then you get hundreds of complaints that this or that doesn't work like it's supposed to
Maybe VDJ should add a custom hardware mapping page for the people who like a creative challenge with their controllers. But Stress a HUGE WARNING saying These Mappings are for The LOCODOG Strain of Dj's ONLY! DO NOT USE IN A LIVE ENVIRONMENT
Inviato Tue 18 Jun 19 @ 11:53 am
jangeador
PhantomDeeJay I think that the ir statement will accomplish what I am looking for and in fact it will give me a third layer of pads. Thanks for that.
I appreciate all the effort that the team makes to have the controllers work as originally intended. I guess the controller makers are limited by the software they design the controller for. I wonder what a controller designed exclusively for virtual DJ could do.
I appreciate all the effort that the team makes to have the controllers work as originally intended. I guess the controller makers are limited by the software they design the controller for. I wonder what a controller designed exclusively for virtual DJ could do.
Inviato Tue 18 Jun 19 @ 1:12 pm
locoDog
MrDjLinton wrote :
.. .....But Stress a HUGE WARNING saying These Mappings are for The LOCODOG Strain of Dj's ONLY! DO NOT USE IN A LIVE ENVIRONMENT
Lol, I like to keep it weird, someone's got to do it.
But i sort of agree, we should have the other softwares chasing us. [And they do to an extent, but we could move faster, way faster than them]
Inviato Tue 18 Jun 19 @ 2:18 pm
jangeador
Wow, I am so happy with this thread. I was able to add an extra layer of pad pages to the controller. Plus I just learned that hitting a scratch from the scratch pad page from a cue point does a scratch play. Plus I learned that the pad pages are stored as plain xml allowing me to change colors and actions from a text editor.
Oh the possibilities!
Oh the possibilities!
Inviato Tue 18 Jun 19 @ 3:45 pm
Dj DruFunk
so I can map vdj to hit a button and pull up pad menu. Is there a way to scroll through and select one without using the mouse? example pressing up and down on keyboard to scroll through them?
Inviato Sun 25 Aug 19 @ 10:03 pm
djdad
A keyboard/controller button assigned as .. pad_page, will pop-up the Pad pages list, but then you can only use the keyboard up and down arrows to scroll and the keyboard ENTER key to select.
Inviato Mon 26 Aug 19 @ 10:48 am