Originally Posted by
muffintop
Page 3 will have the deck A deckalized mf on top of the left and deck B on bottom of the left side
4 columns will be in this order... deck A volume (all 8 buttons) deck A filter (Top button filter on/off...lower 7 are the fader)...and repeated for deck B
that's a pretty cool idea... nice use of 2 virtual midi fighters like that so you can also use virtual faders on the same page
I'll upload the tsi soon so you can take a peek if you want
cool, cheers
i thought i wouldn't be using the virtual midi fighter feature now that i have a real one - but i still prefer the led feedback on the launchpad.
btw you can customise the "off colors" for virtual midifighter pads by defining a list of colors like this:
Code:
mf_colors = { lp_lo_orange, lp_lo_red, lp_hi_red, lp_hi_red,
lp_lo_red, lp_lo_green, lp_lo_green, lp_lo_green,
lp_mi_green, lp_mi_green, lp_mi_green, lp_mi_green,
lp_lo_orange, lp_hi_orange, lp_hi_orange, lp_lo_orange }
and then pass that in along with a single 'on' color:
Code:
virtual_midifighter("lp", 1, "midifighter2", 1, 4, lp_hi_yellow, mf_colors)
the list should go 1st row, 2nd row etc but i think at the moment it's going 1st col, 2nd col, i'll change that for the next release if it's wrong.
a previous version of my code used x,y instead of row,col for grid controls which is what caused issues with the midi fighter functions i just fixed. still not sure which way makes more sense, but too much is now row,col to change probably.
Bookmarks