Midifighter Features

DJTT Gear & Custom Mods Midi Fighters
,
1

Midifighter Features

Features of the Midifighter v1
20091230: post created by Fatlimey
20110510: edited to reflect the current firmware

  • The Midifighter is a Class Compliant USB device, so it can plug and play to produce MIDI over USB on Mac, PC and Linux without additional divers needed.

  • High performance key scanning, with keys read at 1000hz giving 1ms response to keydowns and 10ms response to keyups (use to the 10-entry debounce buffer). We send the MIDI events to the host as fast as we capture them.

  • Bootup menu system sets allows you to alter system settings, which are written to persistent storage and reused at every subsequent reboot. Hold down the top-left key (nearest the USB socket) while powering up to enter Menu Mode. See the Menu System HOWTO post for more.

MIDI Implementation

  • The keyboard generates the 16 notes from C2 to D#3 (assuming the standard numbering that “Middle C” = C4, note 60), to line up with the default window of an Ableton Live 8 drum map.
C3  C#3 D3  D#3
G#2 A2  A#2 B2
E2  F2  F#2 G2
C2  C#2 D2  D#2

or as MIDI note numbers:

48  49  50  51
44  45  46  47
40  41  42  43
36  37  38  39

The base note of this group is selectable through the menu system allowing the 16 note window to be placed anywhere in the MIDI map.

  • The Midifighter generates NoteOn (0x90) and NoteOff (0x80) events to signify a note finishing instead of using a zero velocity NoteOn event.

  • MIDI notes have a selectable velocity, which defaults to 127 (0x7f). The velocity is also used for the NoteOff events.

  • MIDI notes are generated on a single channel, which defaults to MIDI channel 3 (0x2)

  • Sending MIDI events out to the Midifighter on the same channel and note numbers as the keys controls the LEDs. NoteOn lights the LED, NoteOff turns it off. By default pressing a key also lights the LED on that key, but for total control over your LEDs this feature can be turned off using the menus system.

Open Source Resources

  • The Midifighter is an open source hardware project. All schematics, firmware, source code and other support documentation are openly available and licensed under Creative Commons (hardware) and GPL (firmware).

  • Source code and documentation is available at Midifighter download | SourceForge.net

  • Programming potential: program memory is only 35% full, plenty of space to add new features!

2

Dude… You might actually start a wiki just for this controller? :eek:

3

not to be a d.i.c.k but i noticed resources is spelt wrong on the main page.

4

Same here… But before handling that one, I need to be sure that they meant resources instead of recourses.

5

Done. :wink:

6

do you ship this worldwide?

damn i’d like to buy 2

7

Check the shops… This is a world wide thingy. :wink:

8

Availability is a bigger issue. :wink:

9

hey people, i’m still new at mapping and setting up midi controllers, even though i’m use a vcm100 with and mpd24. if the default midi channel is 3, (vcm00 is 1, mpd24 is 4) could i use just use the midi learn in traktor to map the midi fighter?

10

Why not?

11

i used midi learn in serato to map my controller, so I can only assume the same would apply in traktor

12

somewhat off topic .. i wish we would start getting a proper doc page for all the DJTT controller/modifications. like the other day i was searching forever to find the video where Ean explains how to switch between FW 1.2 and 1.3 on the VCI-100 SE. to yeah .. lets move stuff like this out of the forum.

13

+1.. otherwise the same questions will rise up again and again..

14

d.i.c.k. lol

15

You mean spelled? Fail lol

16

Hagging on old posts fail! :stuck_out_tongue:

17

Why isn’t there an option (4 little extra buttons) to switch between different midipages? I’d like a Midifighter that can be setup for different pages.
For me 16 Buttons just isn’t enough.

18

4 bank mode is coming, just needs some polishing and thorough testing I believe, but Ill let Fatlimey tell us an ETA

19

I’m, in the middle of a major overhaul of the main loop. I’m moving from a reactive “Someone pressed a button, I must immediately light an LED and generate a MIDI event…” style design to a “Someone pressed a button, let me immediately generate a MIDI event and make a record of that so we can see later whether we want to change the LEDs in some way once we’ve checked out in the MIDI input stream and the expansion ports…” state based design.

Essentially it’s in pieces all over the living room floor, each piece on a separate piece of newspaper, but they’re a lot cleaner and working better than they used to. It should come together quickly.

20

What does this have to do with mapping different pages?

I’d like one page / 16 buttons for the sampler in Torq.
Another page for cuepointjuggling.
One for effects and loops, …
I did this with different (groups) pages on my NI Maschine super easy, even my Korg nanoPad let’s me change between four banks/pages.

But the Midifighter doesn’t have these little extra buttons to make a switch between different pages. It’s the only feature I really want in a Midifighter.
Maschine needs more space while travelling and I’d love to buy a Midifighter and play around with these dope arcadebuttons.