Midifighter Extreme!! mod project!!

[sidetrakd]

Here's a quick sneak preview!!!

http://www.youtube.com/watch?v=zvvS3nsrv3Y

[ToOntown]

this is glorious... the thought of attempting to do this to mine makes me break into sweats, but yours is glorious.

[DjWindzOne]

:eek:

HOLY. . .FRIKKEN. . .JEEBUS!!!!!

:eek:

[V-Hoff]

Man, you rock! I'm loving every aspect of your mod!

Good work!
DJTT is hiring and they may have a job for you

[DjWindzOne]

@GuyWithKnife or SideTrakd
Stupidly n00b Question, but could I get away with using this Mux? http://www.sparkfun.com/products/9056

Or would using the chips mentioned have to do?

[guywithknife]

Looks fine to me. Note that I don't know anything about its operating characteristics (eg crosstalk issues and such), but then, I don't really know about the ones we used either, except that they seem to work fine for us in practice.

To get it working with Fatlimeys firmware (you will have to recompile it yourself with the MULTIPLEX_ANALOG define selected -look around line 195 in the Makefile and uncomment (remove the #) from the line mentioning MULTIPLEX_ANALOG), you would connect pins S0, S1 and S2 to digital 0, 1 and 2 and connect pins C0 through C7 to your analog input devices. Then connect the SIG to the Midifighters analog 0.
(Note that the photos, the schematic and the datasheet use slightly different labelling: Cn drawn on the circuit board is labelled In in the datasheet (where n is 0 through 15), SIG is labelled common I/O (and COM in the schematic))

To make it work with all 16 multiplexed pins would require some modification of the firmware (similarly, using more than one of these together, for a maximum total of 64 analog inputs, requires more firmware modding still). Its not terribly hard (and we do it in our modded firmware, you could take a look when I release it - though we use some of our inputs as buttons, complicating the code a little more).

[DjWindzOne]

^ Thank you. . .Time to go research and back to my own project (only a year and a half behind ). . .I have some help on the coding, and a plan. . .

. . .but now. . . back to work. . .

[cmcgonag]

How are you doing the scrolling lights around the rim of the controller? I assume that it is tied to midi clock?

[Glen]

this... is awesome, nice job

[guywithknife]

Thats our "demo mode" You can drop into and out of it by pressing a six button combo (six buttons so its not likely you will press them all in a gig).

Its actually insanely simple - nothing advanced at all: I keep an index into a table. The table tells me which led to light up. Then, every iteration of the "do stuff" loop, I light up the correct led and delay for 100 milliseconds. You notice this if you press a button while in demo mode: if you press a midifighter button and demo mode is also lighting up a midifighter led, the led for the button you press flickers as demo mode clears all other leds, while pressing one of our extension buttons will not light up any leds. Syncing with the midiclock, or implementing it without a delay wouldn't bee too difficult.

I am actually working on something right now which I may use to create all sorts of cool light shows. If I do that, I may even back-port the code to work with unmodded Midifighters, we'll see - no promises just yet.

In any case, we are still perfecting the Traktor mappings (well, Sidetrakd is), which is slow going, since the Traktor UI is a bit of a pain to use. After thats done, we will release some proper videos, more pics, the source code and some kind of build log.