Mapping beat phase monitor to maschine leds
Mapping beat phase monitor to maschine leds Posted on: 26.10.2011 by Rosina Steinkuehler 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! | |
| Chasidy Heckenbach 26.10.2011 |
Originally Posted by GeekGod
Code:
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")
also reminds me i need to write some/any actual documentation for the core functions sometime... |
| Chasidy Heckenbach 26.10.2011 |
Originally Posted by GeekGod
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 believe) 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. |
| Rosina Steinkuehler 26.10.2011 |
Originally Posted by zestoi
|
| Rosina Steinkuehler 26.10.2011 | 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! |
| Chasidy Heckenbach 26.10.2011 |
Originally Posted by GeekGod
Code:
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")
also reminds me i need to write some/any actual documentation for the core functions sometime... |
| Rosina Steinkuehler 26.10.2011 | I have been looking for a reason to get started with your midimasher lua software and this might be the perfect start... |
| Chasidy Heckenbach 26.10.2011 |
Originally Posted by GeekGod
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 believe) 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. |
| Rosina Steinkuehler 26.10.2011 | 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.. |
| Rosina Steinkuehler 26.10.2011 |
Originally Posted by zestoi
|
| Chasidy Heckenbach 26.10.2011 | 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. |
<< Back to Post and find Controller MappingsReply