Mapping beat phase monitor to maschine leds

DJ Software & Apps Controller Mappings
1

Mapping beat phase monitor to maschine leds

Hello all,

I mapped up my maschine to show the beat phase monitor for all 4 decks and it works pretty well.

The problem is that the leds are moving quite fast and was wondering if there is a way to slow this down? Maybe using a modifier or something?

I am trying to prevent midi message overload - my MBP only has a few USB ports which is starting to get a bit loaded with all this LED activity.

Thanks in advance!

2

adjusting the midi range will help with that. i have mine set to min=0 and max=15 so i only get 16 ticks per beat - which is more than enough for most synching etc - and certainly enough to use to drive led’s.

3

Fantastic! Thank you!

4

I made this change and its still going really fast. Do I need to adjust the midi controller range as well?

I have 4 mappings setup for each deck ranging from -0.5000000 → -0.3000000 and then , -0.2000000 → -0.0000000 etc..

5

possibly. the controller won’t loop any faster from it’s overall min and max values, changing the midi range just affects how the controller values are mapped to the midi min and max and traktor won’t send out duplicates.

for me midimasher does the translation of midi output from traktor to changing led status etc so i only have one mapping in traktor and (i think) have the midi range set from 0 to 1.

it could be that you need to have different max and min midi ranges in for each of your controls? easiest way would probably be to run something like midi ox to dump out what traktor is sending so you can debug.

could be i’m missing something as i haven’t tried to add more than one mapping in traktor per beatphase before.

6

I have been looking for a reason to get started with your midimasher lua software and this might be the perfect start…

7

this kind of stuff is a lot simpler… this example is going to look like giberish - but its the only code needed to create a shift button that toggles and create a virtual yfader on a set of buttons that is used to control the overall level for deck A (with feedback from traktor) and when the toggle is pressed (toggled :stuck_out_tongue:) it then switches to displaying the monitor level (on a launchpad - but is a generic):

toggle_modifier("lp", "vol", 4, lp_hi_yellow, lp_lo_red, "lp_vu_toggle")

virtual_yfader("lp", 7, 3, 4, "traktor", "volume_fader_a", 0, 8, lp_hi_yellow, lp_lo_red, 0, 127, true, "traktor", "monitor_deck_afl_mono_a", 0, "lp_vu_toggle")

probably not the best first example - but does show how much u can do with very little code in a config file.

also reminds me i need to write some/any actual documentation for the core functions sometime…