Search the Community

Showing results for tags 'leds'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 3 results

  1. DOUT with pro tools

    I'm having trouble getting leds to work properly with pro tools At the moment I have the leds responding when I press solo in pro tools, but the problem is, when I press solo on any channel it will turn on all leds I have assigned. I know that the problem is in the way I'm coding because it is only doing this in pro tools. The code I am using is this, which are the cc equivalent values to sysex zone select/port on: EVENT_LED id=  1 type=cc chn=1 cc=12 range=0:0 EVENT_LED id=  1 type=cc chn=1 cc=44 range=67:67 I can't get them to respond with sysex messages, whereas it does work for buttons. For example, this was not working: EVENT_LED id= 1  type=sysex stream="0xb0 0x0c 0x00 0xb0 0x2c 0x43" I have the buttons configured in a similar way as shown before with cc messages with ranges and they work, so I thought maybe this could work for the leds, but it appears that is wrong What would be the right way to do this?     
  2. I am brand new to midibox, I don't have any modules yet, as I am trying to figure out which ones to get exactly, I haven't found a sure answer to what I'm looking for specifically by looking in the forums and the general information on the ucapps site, maybe someone could help. I'm trying to make a controller for Pro Tools using 3 MF_NG modules , for 20 channels/faders total since it would be installed in an existing 20 channel console, but I'd also like to have buttons and leds for record enable, channel automation, as well as transport controls and automation selectors (read, write, latch, etc.) as well as leds for the record lights, which for me would be about 60 buttons, and 20 leds at least for the record enable lights. at least Ideally it would use mackie HUI, but I would be fine with using MotorMix if that works better.  I'm trying to find someone here who has successfully made a controller with both motorfaders AND buttons/leds who could let me know what modules I would need My first thought was to get a STM32, and then connect the MF_NG modules and DIN and DOUT modules, but in the MF_NG thread there was a post that made me think that might not work. I posted the quotes below, they are from 2012, maybe this is dated? Would it be different since I am only using 3 MF_NG modules? Could I use just a STM32 or would I have to use an LPC17 and MIDIO128? If I did need to use the MIDIO128, would I have to use the LPC17 or could I use it with a STM32? My understanding is that the STM32 is an upgrade in a lot of ways to the LPC17, and doesn't require an external burner. My goal is to keep everything as simple as possible since i'm completely new to midibox. But since it's Pro Tools we are talking about, things can't be so easy..    Sorry for so many questions, any help is greatly appreciated!! Even if i had to use older modules, that would be okay! I just don't want to get/build the wrong components.. I also wanted to make sure this kind of configuration is something other people have gotten to work in pro tools   Here are the quotes:
  3. Hi all,   I'm trying to configure my MIDIbox to work with FL Studio, and so far I've successfully mapped outputs from the box to control knobs and switches in FL. However, I haven't had any luck in sending feedback to the box to trigger LEDs to light up.   FL has a plugin called 'MIDI out' which allows you to send CC, RPN or NRPN bytes to an external MIDI device. My firmware has only been configured to switch LEDs in response to note events. Does anyone have any suggestions how I can take CC, RPN or NRPN bytes being sent from FL and translate them into note events so the LEDs light up on my MIDIbox?   Ideally, I'd like to configure FL so it sends out a separate CC for each LED (on channel 2, as 1 is used for my pots and encoders). A CC value of 0 would turn off the LED, while 127 would turn it on.   Thanks