Jump to content

FantomXR

Members
  • Posts

    1,035
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by FantomXR

  1. Hey people,

    everytime I switch on the MIDIbox, all LEDs will light up for a fraction of time. Is there any chance to avoid this behaviour? 

    I think it has something to do with the initialization-process. I already tried to put a capacitor (100uF) between VDD and GND, but this didn't change anything...

    Thanks,
    Chris

  2. Okay! I got it! 

    This code works great:

    EVENT_RGBLED	 id=1 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP1
    EVENT_RGBLED	 id=2 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP2
    EVENT_RGBLED	 id=3 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP3
    EVENT_RGBLED	 id=4 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP4
    EVENT_RGBLED	 id=5 type=cc cc=16 rgb=8:5:0 dimmed=1 range=MAP5
    EVENT_RGBLED	 id=6 type=cc cc=16 rgb=5:0:0 dimmed=1 range=MAP6
    
    MAP1/BYTEI  0:0 21:127
    MAP2/BYTEI  0:0 21:0  42:127 
    MAP3/BYTEI  0:0 42:0  63:127 
    MAP4/BYTEI  0:0 63:0  84:127 
    MAP5/BYTEI  0:0 84:0  105:127 
    MAP6/BYTEI  0:0 105:0 127:127 

     

  3. Hm okay. But if I have a strip of 6 LEDs and I want them to show the status of a fader or encoder like a led-bar or led-ring which sends f.e. CC16, how to do that? Or isn't it possible yet? Maybe I could assign different ranges to the LEDs...this is the only workaround I could think of at the moment  

    i have another idea for lightning the encoders. So no need for PCBs or encoders. Will share it as soon as I've tested it. ;-)

  4. Does someone know if it's possible to use the WS2812 as matrix? I'm afraid that there is no parameter called EVENT_RGBLED_MATRIX. So there might be a workaround that I don't know? 

    I'm looking for a replacement for the classic encoder led rings and those WS2812 seem to be a great alternative. 

    Thanks!

  5. I think it all depends on the time you want to invest. From my experience I can tell that it needs more time as you might plan ;) 

    Also it depends on what kind of PCBs you have available. Faders are quite easy to solder even without a PCB. Buttons are more crucial especially if you want to use buttons that are not able to be mounted on the frontpanel directly and need a PCB. 

    I think the most time consuming work will be to solder the LED-rings. As far as I know there is no ready-2-go solution at the moment and no PCBs are available for 16 LED rings. Some time ago there was a bulk order for those:
    http://www.midibox.org/dokuwiki/doku.php?id=mb-lre8x2cs_pcb

    But I think Jerome is not active in the forum anymore.

    Anyway: If you have good soldering skills and you are able to solder SMD than I can help you out. I have some SMD-LED-Ring PCBs a while ago. But those are 0603 SMDs you need to solder by hand... and it's 16*16pc = 256 LEDs = 512 pads ;)

    What do you mean by scribble strip?

  6. I don't know if you still need help on this and if it even helps what I've found. In app.c of the NG you will find 

    		// create the default files if they don't exist on SD Card
    	  MBNG_FILE_CreateDefaultFiles();
    	}

    So at least it seems that you can disable the creation of the default file... I haven't tested it yet...

    And to load your dedicated ngc.-file you can use an NGR-script and the "load" command. 

    Should look something like this:

    if ^section == 0
     load xxx
    endif

     

  7. I made a bit of process here. I discovered in the changelog of NG, that NG supports to control terminal commands from a DAW via SysEx. So if I create a syx-file and send this to the STM, it works f.e. this stream

    F0 00 00 7E 32 00 0D 00 73 65 74 20 64 65 62 75 67 20 6f 6e 0A F7

    sets the debug mode on.

    Now I try to set up a button in the NGC file that sends this command to the terminal. So I added 0x to every byte and I end up like this:

    EVENT_BUTTON id=23 type=SysEx  stream="0xF0 0x00 0x00 0x7E 0x32 0x00 0x0D 0x00 0x73 0x65 0x74 0x20 0x64 0x65 0x62 0x75 0x67 0x20 0x6f 0x6e 0x0A 0xF7" button_mode=toggle

    What happens now is, that the terminal prints the command "set debug on" but that's it... its just printing this text without activating this function. So I guess that the NG-firmware somehow filters out the sysex message. I think I need to send this command to "USB0" or "UART0" but those ports aren't available afaik.

    Does anybody have a hint on that? I looked into the code but for now I couldn't find the function that I need to disable or to change.

    Thanks!

  8. Hey people,

    what is the meaning of the RC1 and RC2 lines on digital modules? I wonder that the official schematic of the DOUT-module uses only one select line:
    http://ucapps.de/mbhp/mbhp_doutx4_r5.pdf

    the DIN-module uses both
    http://ucapps.de/mbhp/mbhp_dinx4_r5.pdf

    and the DIO-module also only uses one:
    http://ucapps.de/mbhp/mbhp_dio_matrix.pdf

    I ask because I made a PCB that works perfectly when connected to the core directly but stops working as soon as a DIO-module is between the PCB and the core. If I put the DIO behind the PCB it works also... but not the other way around... on the PCB I have addressed RC1 to HC165 and RC2 to HC595. As the DIO doesn't seem to forward the RC2 this seems to make sense...

    Can anybody confirm that?

    Thanks,
    Chris

    //edit: I checked the LRE-PCB and he also addressed RC1 and RC2 like me.
    http://jeromebo.free.fr/Wiki/MB-LRE8x2CS_Rev4.6/Schematic_MB-LRE8x2CS_Rev4.6.pdf
    But I wonder how the DIO can work with both HC165 and HC595 connected to the same RC-line...

  9. Hi Zam,

    I'm not talking about MB_NG only. For me it's more interesting, to have access to the parameters of MB_KB without the editor / computer. So I can not use any EVENTs and BANKs...

    I'm not a coder... but for me it doesn't sound that complicated to get control over some (not all) configuration parameters.... :) 

  10. Hey guys,

    at the moment I try to dive deeper into the code of MIDIbox. One thing that I'd like to know if it's possible to implement a "simple" function, that allows to use a MIDI-Controller to control internal configuration-data f.e. delays of a keybed, break-is-make-function, etc. This would help to take control over the keybed "on the fly" without using the MIOS.

    Does anyone has an idea?

    Thanks,
    Chris

  11. Hey people,

    I have a question regarding the pins of a DIO. I mostly use the DIO for scanning keybeds. Sometimes a keybed needs another configuration and I'll need to build an adapter for that. 

    Is there an option to change the assignments of the pins on the firmware side? For example "inverting" break and make contacts (break = make, make = break)? Or changing the layout / counting of the rows?

    thanks!

    chris

×
×
  • Create New...