Midifighter Extreme!! mod project!!
Midifighter Extreme!! mod project!! Posted on: 07.04.2011 by Hunter Renslow Ive been working on a midifighter mod project.I am going to do a full build log,the project just took up alot of my spare time so I haven't had a chance yet!Bourns 60mm faders and CD4051B multiplexers. The multiplexers Fatlimey talks about in this thread http://djranking s.com/community /showthread.php?t=23597 The multiplexers set up with 8 inputs into each one(some are being used for buttons so i added pullup resistors at a later stage) case made out of mdf primed up!! button layout! The 4 black buttons on the left are "global banks" the change the midi channels to 3,4,5 or 6.The notes and cc's are always the same just the channels change!! Code:
Bank 1 - browser Bank 2 - loops Bank 3 - deck control Bank 4 - effects(instant gratification) The four black buttons on the top are for decks a,b,c and d (four banks mode) leds on the buttons are controlled by a pic24 | |
| Hunter Renslow 08.04.2011 | Thanks everyone for the supportive comments!! The project is nearly finished except for a few hold ups Cant wait to get it finished!! Have a gig on the 23rd and want to road test it!!
Originally Posted by extraclassic
|
| Janyce Henningson 08.04.2011 | Very impressed mate - great work |
| Louisa Oberc 08.04.2011 |
Originally Posted by Fatlimey
The way you read the two shift registers is ingenious and helped me speed up my button routines 10 fold... Plus being able to emulate 4banks mode correctly is also a plus I don't have the spare buttons at the moment, but if someone wants the midi fighter code ported to an Arduino type chip let me know. It's almost directly compatible out of the box (aside from the MIDI and LUFA code)... |
| Lorelei Przybylowicz 08.04.2011 |
Originally Posted by sidetrakd
|
| Cammy Clegg 08.04.2011 |
Originally Posted by Fatlimey
Originally Posted by sarasin
Originally Posted by sarasin
but tutorials would be great. |
| Louisa Oberc 08.04.2011 | Any chance of posting the PIC code? I've wanted to expand my palate beyond the atmega line of chips. I have a controller in the planning stages that will likely have close to 200 leds on it and was believeing of using a dedicated mcu for the leds so I can give the core atmega chip some breathing time... (over 150 controls--faders, buttons, encoders, pots, xypads on the controller as well) |
| Lilliana Perris 08.04.2011 | I believe its worth an article.... Don't believe its up there with FM1.4.....but its definitely one of the few threads/community members that have coded their own firmware or similar. I would personally like to see more articles/tutorials on this midi device coding. I understand how it works etc...but would like to know more. And I am sure there are others here that would like some advanced stuff like too. Props dude! |
| Shay Wyche 08.04.2011 | Expect a front page write up soon? Some big hitters on the community giving lots of praise here. |
| Lilliana Perris 08.04.2011 | Fucking hell! That was ALMOST geek...i mean greek to me! Badass indeed! |
| robert chanda 08.04.2011 | This is excellent work. You've grokked the expansion ports, you've got an LED controller off a PIC, you're repurposing the source code to get the MIDI model to work how you want, you're multiplexing the analog inputs and you're using the Midifighter something like a USB-MIDI base station for your external hardware. That's exactly how we imagined it being used. Rock on! |
| Adolf Hit 09.04.2011 | Badass dude! That is exactly what we wanted to see happen, and the reason there is an expansion with open source firmware. Cant wait to see it finished! |
| Hunter Renslow 08.04.2011 |
Originally Posted by ToS
I read each of the 32 analogue inputs (8 per multiplexer, one multiplexer on each of the 4 analogue extension pins) into an array of bytes (the ADC gives us 10bit values, so I just right shift it by two bits to drop the 2 least significant bits). The first 12 values are passed to Fatlimeys existing superfader code (the only modification I made to this was to use uint8_t instead of uint16_t for each value, and to extend it from four superfaders to twelve). The rest are treated as buttons and I wrote some code to determine the button state (and transitions, since notes are only sent when the state changes). I do this by checking the current value against a threshold. There is no need for debounce code when using the analogue value. The buttons are split into three groups (and a single specially treated "shift" button): 11 normal buttons, 4 bank buttons and 4 "global" bank buttons. The bank buttons are rigged up so that the existing code for external banks mode reads their state and handles banking the midifighter as if they were connected directly to the digital expansion pins. The "global" banks change the MIDI channel used by all other buttons (including the midifighter buttons), but not the knobs and faders. This is done by adding a global_bank value to the MIDI channel in the send code in midi.c, so if global_bank is 0, then the channel used is the one configured from the midifighter menu mode (3 by default), if global_bank is 1 then the channel is one greater than the selected one (4 by default) and so on. When the shift button is pressed down, and a global bank button is pressed, then the MIDI channel is changed for the knobs and faders and works the same way as the global banks. So, in summary, the code looks something like this (pseudocode): Code:
read MIDI input from USB, unchanged from the latest firmware source
if (analogue expansion is enabled) {
uint8_t adc_values[32];
for (i = 0 to 31) {
select multiplexer
read analog pin one into adc_values
read analog pin two into adc_values
read analog pin three into adc_values
read analog pin four into adc_values
}
select global_bank MIDI channel
static bool button_states[20];
for (i = 12 to 31) {
bool button_changed = false;
bool button_pressed = false;
if (adc_values[i] < up_threshold && button_states[i - 12] == false) {
button_changed = true;
button_pressed = false;
}
else if (adc_values[i] > down_threshold && button_states[i - 12] == true) {
button_changed = true;
button_pressed = true;
}
if (button_changed) {
button_states[i - 12] = button_pressed;
if (i < 24) {
if (i != shift_button) {
// Normal button
send midi note for button i-12, note on/off is button_pressed
} else {
// Shift button
handle shift button
}
}
else if (i < 28) {
// Global banks
if (button_pressed) {
global_bank = i - 24;
}
}
else {
// Banks
set button state bits so the external banks code can use it
}
}
}
send button state information to PIC
select shift+global MIDI channel
existing superfader code
select global_bank MIDI channel
}
existing midifigfhter code for banks, buttons, leds etc
The PIC code is very simple, and our PIC24 is really overpowered for what its used for (we use a PIC24 instead of a cheaper PIC16 because I happened to have an unused one already). All it does is read single bit buttons states on PORTA and set the correct bit on PORTB, which is connected to LEDs. Thats it. The input logic is something like this: Code:
wait for SS to become set wait for CLK to become set read DAT set (or unset) appropriate PORTB bit set ACK wait for CLK to become unset unset ACK repeat Code:
set SS set CLK set DAT to state of next LED wait for ACK to become set unset CLK wait for ACK to clear repeat for each LED unset SS The LED states are determined in two ways: For the normal buttons, including shift button, if the button is down, the LED is on. For the bank buttons, only the LED for the current bank is on, the others are off. The normal buttons could just as easily have been connected directly to an LED, but by having the midifighter control them, we can set them depending on MIDI input (eg, so traktor can control them), though our firmware does not yet do this. There are a few more bugs to iron out, especially in the midifighter-PIC communication code and the midifighter code I wrote needs a major cleanup, but once this is done, we will most likely be releasing the code. Unfortunately I believe we fried our midifighter so it will take a while before we can finish it. |
| Lewis Stumpf 08.04.2011 | That looks sweet. Give us a tour, and a performance, when you're done What's the mapping like? |
| DJ MENSAH 08.04.2011 | Custom firmware? |
| Leeanna Ayla 07.04.2011 | Nice!! |
| Joan Kollmorgen 07.04.2011 |
Originally Posted by sidetrakd
Forgot to ask what's feel like on these faders? smooth, super smooth? Edit: WoW quoted me |
| Matha Obray 07.04.2011 | U should post a how to. Id be interested |
| Hunter Renslow 07.04.2011 |
Originally Posted by extraclassic
http://ie.mouser.com/Search/ProductD...E60-151B-103B2 |
| Joan Kollmorgen 07.04.2011 | Looks so damn sexy Cant wait to see it in action. Where did you get the Bourns faders from? Any chance of a link? |
| Hunter Renslow 07.04.2011 |
Originally Posted by Paulo
|
| Murray Hoffa 07.04.2011 | Thats amazing looking...I wanna see a vid when your finished! :P |
<< Back to Reviews of DJ equipment Reply