Midi Fighter 3D?

[zestoi]

I believe they are the 20 colours that you can set using the configuration tool. Technically, the leds can do thousands of colours, but most are too similar to be able to tell apart. The colours that DJTT chose for the configuration tool are the ones which they determined to look the best.

cool sure, i suspect 20 different colours will be enough for anyone all i'd need for any mapping is maybe 4 distinct ones tops. being able to change the intensity of any of the colors is more important maybe - but i'm hoping you can do that on this new midi fighter for custom colours and not just the simple on/off colours that are pre selected.

the launchpad doesn't have an exactly awesome range of colors from it's 2 led's per pad but it's nice having 3 intensities for each colour.

[midifidler]

You can only modify the intensity of the Inactive or Active Color - that is how the VU display in the video was programmed.

The flashing states are broken down like this.

(cycle means it fades in and out rather than switching off to on)

Velocity 119 = RGB Color cycle at 1 Hz
Velocity 120 = Red 1 Hz cycle
Velocity 121 = Green 1 Hz cycle
Velocity 122 = Blue 1 Hz cycle
Velocity 123 = Active Color Flash on the beat
Velocity 124 = Active Color Flash on the half beat
Velocity 125 = Active Color Flash on the quarter beat
Velocity 126 = Active Color Flash on the eighth beat
Velocity 127 = Active Color Flash on the sixteenth beat

Obviously there are many many cool aspects of the lighting that could be controlled, however we have to make it easy to map at the same time.

Having to use multiple messages to configure each LED would be confusing for some users.

We will definitely be listening to the community for feature requests once the product is shipping.

Also its worth mentioning that while the utility supports 20 fixed colors/brightness states the more intrepid user can actually program any color they want by editing RGB hex codes in the MF 3D Utility plugin file.

[zestoi]

You can only modify the intensity of the Inactive or Active Color - that is how the VU display in the video was programmed.

fair enough - very nice feature for a vumeter anyway

The flashing states are broken down like this.

(cycle means it fades in and out rather than switching off to on)

Velocity 119 = RGB Color cycle at 1 Hz
Velocity 120 = Red 1 Hz cycle
Velocity 121 = Green 1 Hz cycle
Velocity 122 = Blue 1 Hz cycle
Velocity 123 = Active Color Flash on the beat
Velocity 124 = Active Color Flash on the half beat
Velocity 125 = Active Color Flash on the quarter beat
Velocity 126 = Active Color Flash on the eighth beat
Velocity 127 = Active Color Flash on the sixteenth beat

pretty neat having the buttons cycle as opposed to only flash, very cool.

i presume the "active color flash" is down to midi clock ticks and nothing traktor-specific? not that i guess anything could be totally traktor specific as it's only midi anyway... tho you can't always get an output like the beatphase.

Having to use multiple messages to configure each LED would be confusing for some users.

and impossible to use in many apps probably...

Also its worth mentioning that while the utility supports 20 fixed colors/brightness states the more intrepid user can actually program any color they want by editing RGB hex codes in the MF 3D Utility plugin file.

huzzah! then i am a happy camper... i'd just reprogram those 20 to be 10 different colours with two levels of intensity each. perfect... would be very cool if these 20 preset colours could be exported/imported in some way in case someone wants to share a traktor tsi etc that only makes sense with a different set of colours.

don't suppose there's any chance of there being a uk reseller to avoid custom charges

i have a nasty feeling that this controller, the a&h k2 and the new behringer units are all going to be available around the same time and impact my financial situation

[midifidler]

i presume the "active color flash" is down to midi clock ticks and nothing traktor-specific?

Correct - the MIDI Fighter just looks for a midi clock signal and sync's to that.

i'd just reprogram those 20 to be 10 different colours with two levels of intensity each.

The default for the utility is 10 colors each with two intensities

The plugin config file could be shared between users if you want to share your custom colors, it is just a case of dropping it into the plugin folder.

Also the utility has the ability to import and export color maps, these files can be shared between users. So if a user creates a custom mapping, and has a color map to go with it, that file can be shared with the .tsi so other users can instantly configure the color layout of their unit to match.

Our mappings will control all color via midi, rather than relying on the user having to use the utility to set the colors to match our mapping. But for most people the utility will be the simplest way to go

[synthet1c]

how do the leds receive a signal to light a specific color and flash at the same time? do they receive both messages to do it.

I would be interested in setting it up in vdj but the way things are defined for a note on message I could only send one value at a time eg.

Velocity 66 - 86 = Directly set the color to one of the 20 available settings.

lets say
value = 66 = red = 0x42
Velocity = 123 = Active Color Flash on the beat = 0x7B

So would I define it as two seperate note on messages not just one... Is that how it works in traktor?

<led note="0x00" value="0x42" name="LED 1 red" />
<led note="0x00" value="0x7B" name="flash on beat" />

Although If i can control only the colour then I can make it flash with vdj's native script language anyway... So i guess it's not that important..

Another question any chance of a release without the accelerometers, maybe a mfpro with 4 encoders with led rings would be more useful to anyone but bedroom dj's

[zestoi]

The default for the utility is 10 colors each with two intensities

nice! lol...

Our mappings will control all color via midi, rather than relying on the user having to use the utility to set the colors to match our mapping. But for most people the utility will be the simplest way to go

you're still choosing surely tho from the 20 currently setup for that specific midi fighter via this tho?:

Velocity 66 - 86 = Directly set the color to one of the 20 available settings.

so you're still relying on the user having the same 20 colours setup as you.

being able to share the mapping for those 20 to rgb values as well as static on/off colours will be very handy. which i *think* is what you said will be possible...

Our mappings will control all color via midi, rather than relying on the user having to use the utility to set the colors to match our mapping. But for most people the utility will be the simplest way to go

i'd certainly rather be able to do all config via midi too if possible...

[zestoi]

how do the leds receive a signal to light a specific color and flash at the same time? do they receive both messages to do it.

i don't think you can:

Velocity 0 = No Effect
Velocity 66 - 86 = Directly set the color to one of the 20 available settings.
Velocity 86 - 102 = Uses the inactive color, set to one of 15 brightness levels
Velocity 103 - 118 = Uses the active color, set to one of 15 brightness levels
Velocity 119 = RGB Color cycle at 1 Hz
Velocity 120 = Red 1 Hz cycle
Velocity 121 = Green 1 Hz cycle
Velocity 122 = Blue 1 Hz cycle
Velocity 123 = Active Color Flash on the beat
Velocity 124 = Active Color Flash on the half beat
Velocity 125 = Active Color Flash on the quarter beat
Velocity 126 = Active Color Flash on the eighth beat
Velocity 127 = Active Color Flash on the sixteenth beat

it looks like you can set a pad to flash in unsynched in rgb, red, green or blue or have it flash synched via the "active color" which sounds like it is the colour you preset via the utility - not changeable via midi. unless "active colour" is the last color you sent to it over midi which would be very cool - effectively allowing you to change the preset active colour?

i'm not quite sure why having preset active/inactive colours for each pad is at all useful tho i guess it's kind of like choosing different colour arcade buttons for a midi fighter classic? so in that respect maybe neat if people don't want to worry about what velocities are send over midi,

being able to choose from 20 colours is more than enough, but being able to activate/deactivate them flashing would be very nice.

the launchpad has a neat method for flashing leds in sync with an external source not using midi clock - it (in effect) turns off all leds tagged as "flashing" when you send it a certain CC and on again when u send it another one. midi ticks is probably easier for most things tho...

having said all this i'm not a massive fan of flashing leds tho handy to identify if you have a kill switch enabled or something and i do use it for the play buttons usually.

[zestoi]

Another question any chance of a release without the accelerometers, maybe a mfpro with 4 encoders with led rings would be more useful to anyone but bedroom dj's

i guess it's already cheap enough, just ignore the accelerometers? a lot of people seem to be asking the same question tho...

i'm more excited about the rgb colours and the extra four buttons to switch banks, as it always seemed a waste using four arcade buttons just to select them and i never got round to soldering on some extra ones. the shift buttons are handy too. i just see the accelerometers as being an added bonues.

[dylooooon]

April is going to be a GREAT month, first the kontrol f1 and traktor 2.5, now this?!?! I cannot wait to get all of this sweet gear and take my live performances to the next level! So stoked for this! Great job DJTT! You guys are the best and will forever receive my support as long as you continue to follow your original mission; and this controller has definitely shown me that you guys haven't strayed from it at all.

[synthet1c]

I use flashing leds all the time for things that need your attention eg,

remaining time on track less than 30 secs
effect active
kills
track not loaded
pause
looping

I use different flash rates depending on the importance I give to the action. but really anything that oould adversly affect what you are playing and demands your attention, even using different colours it is an absolute necessity to have blinking leds so you can identify things immediately.

I would use colors for different layers in the mapping kind of like the k2 only this would afford many more possibilities as it's all controlled internally by the software, whereas the k2 and vci400 are controlled externally in the hardware with a simple on/off. It's a bit of a pain to map initially as you have to contend with 20 different led colors but would pay off in the long run as you have much more in depth feedback from the software.

@midifiddler Actually if the 5 accelerometers are sending absolute values, would it be possible to replace them with potentiometers for better more realistic control?