So I'm at the design stage of writing my ultimate controller mapping. This is the stage where decisions now will affect future development. Changing my mind and starting again will require lots of effort. So my question is - what decisions to you mappers make when mapping your brain to your controller?
- deck layout. ABCD or CABD? How does the physical layout of your controls reflect the layout of your software in your head?
- old school or new school? Do you want to lay it out like vinyl/CDJ's with a mixer in the centre? Or have you moved on to a new level where those old paradigms no longer apply?
- to mirror or not to mirror? relates to the above point. Do you want your controls to laid out like (from left to right).
A B C D / D C B A or
A A B B / C C D D
- complex but deep or simple and intuitive? Do you want your mapping to be able to do EVERYTHING in the software at the expense of being easier to use, or do you want it to be rigidly fixed but intuitive. Relating to this; shift or no shift. Is it okay to have to 'play chords' on your controller to access functions.
Thoughts welcome...
Rob
Bookmarks