template / dashboard setup

the problem:
i have about 40 CC’s that i commonly map
in FL i have to do this twice [at minimum]
once for mapping the hardware to the dashboard controls
and once to dashboard controls to the instrument/effect
every time i start a new project

it sucks to say the least
i hate spending what time i have for music making
mapping and keeping track of CC# assignments
bo-ring.

now
i know
that cubase and logic and whatnot
will automatically do this once you set the proper midi channel
but fruityloops
not so smart
it requires trickery

the solution:
a project template
which includes a custom two page dashbaord setup
that merges and automatically sends CC#
to and from all three of my controllers
the trigger finger
the mk-249c
and my tablet2midi setup

the data
but first
a couple of analog[pencil & paper] prototypes

and the result…
my new dashboard/template
stock controls mapped
joy
rapture
confusion.

ill attempt to explain in detail
this page that has the cc# from the hardware mapped

then the internal controllers from the first page are mapped to duplicate controllers on page two
these duplicates send CC# to whatever instrument is matched to the master channel of the dashboard.

for example say i want to control a filter in kontakt
the old way i’d have to create a link from trigger finger slider1
to dashboard and then the dashboard to filter parameter in kontakt
i could bypass the dashboard but
that gets messy

so the new way
because i started this project with my new fangled template/dashboard thing
all i have to do is set the CC#in kontakt

score!

questions?
additional hacks?
please
suggest away

---

• 2007-02-26

  J.

  Awesome :) Is this how you get such intricate drum sounds in your work?

• 2007-05-30

  proem

  no.
  i call that magic
  and ALOT of kontakt wankery

Name

http://

E-mail