Forum: General Discussion
If you need extended support, contact our Support Team.
Forum Guidelines (*) The moderators hold the rights to move or modify posts in order to keep the discussions clear or to facilitate the search.
Topic: Secondary Performance Pad Question.
geposted Wed 10 Oct 18 @ 3:19 pm
Here slicer is the secondary page
geposted Thu 11 Oct 18 @ 11:24 am
geposted Fri 12 Oct 18 @ 2:52 pm
geposted Fri 12 Oct 18 @ 3:01 pm
If your custom mapping was created long time ago (before the default was changed to support pad pages), then it wont work.
So if your Pads are mapped as above, then all u need to do is to change the action for the Pad mode buttons.
Example was given by Phantom above, where the HOTCUE button/key is mapped as ..
shift ? pad_page 'slicer' : pad_page 'hotcues'
This will automatically change the behavior of the pads and the respective Pad page will be also loaded to the GUI , offering Slicer (SHIFT +HOTCUES button) or Hotcues (just HOTCUES button without SHIFT) mode
See here how to map a controller button. http://www.virtualdj.com/manuals/virtualdj/settings/controllers/index.html
Note.. Its the same if you map SHIFT_HOTCUES key as pad_page 'slicer' and leave the non-shift key HOTCUES as pad_page 'hotcues'
Further on this , you may find useful to change the mapping of the LED so to know which mode/page is loaded without looking at the GUI. For the case above, you will need to map the LED_HOTCUES key as ..
pad_page 'slicer' ? blink : pad_page 'hotcues'
where the LED will blink when in secondary mode
geposted Sat 13 Oct 18 @ 8:47 am
geposted Tue 23 Oct 18 @ 11:58 pm
geposted Wed 24 Oct 18 @ 2:37 am