Quick Sign In:  

Forum: General Discussion

Topic: Controler Mapping Ideas?

This topic is old and might contain outdated or incorrect information.

NuzzletPRO InfinityMember since 2015
I have a bunch of faders/sliders, buttons, nobs, ect on a bunch of midi controllers that aren't doing much. I wan't to get the most out of my hardware, so ive started building defiitions/mappings for these controllers and virtualdj. But it seems I have run short on new functionality to add.

So, if you had an unlimited number of Sliders, Buttons, Leds, Pads, what would you map them to do? Just desperate to give my controllers something to do!

I will try to make every idea a reality, and I will post the definition/mapping code here! Looking for any ideas, ones you have used, seen, tried, thought of, thought weren't possible, or don't even know. Thanks!
 

Posted Sat 01 Apr 17 @ 4:45 pm
I would use the pad pages that were introduced in v8.2
So I would mapped it to the 8 pads, the 2 sliders, and to directly change current pad page to specific pad pages on the fly
Then I would download all interesting pad pages from the download section
Finally I would create more pad pages myself for just about any function or combination of functions I could think of
That way the possibilities are endless
 

Posted Sun 02 Apr 17 @ 9:31 am
locoDogPRO InfinityModeratorMember since 2013
One way to really make pads accessible is to make a pad page to index pad pages, have one button to call the index and then you have 8 (16 if you include shiftpads) one button press away

Here's how
 

Posted Sun 02 Apr 17 @ 10:31 am


(Old topics and forums are automatically closed)