FantomXR

You are right. It should work this way. I have several keybeds connected like this. You used a twisted cable for connection DIO to J8/9?

Hey TK, in the past two weeks I ran pretty much into the problem, that the keys of the keybed do not react equally...some are more sensible than others and vice versa. I could go and create a velocity-map for every key but as you can guess this would be a lot of code and a lot of stuff to do. I'd like to ask you if you think it might be possible to somehow control delay_fastest / slowest for every key instead of the whole keyboard. Or does that require a lot of changes / addons in the code? Thanks!

You can of course easily adopt my breakout-board to fit four displays instead of just one. No, it's not 0,5mm, which is the problem. It's 0,7mm and I wasn't able to find a fitting socket.

Well... it would be possible. But you would need to send A LOT of MIDI messages on patch change. I had no idea yet how to get around this... And finally: The distance between each LED is not the same as the keys... so not every key has it's LED. I have 71 LEDs on the lower board and not 88 :-) Anyway... it's already such a nice feature... I LOVE IT!! :-)

Thanks for making some things clear ;-) It looks awesome... :-)

I did some more testing: 1.) Using a shielded cable doesn't help. I'll try to experiment with aluminium foil to shield the pots of the mod/pitchwheels 2.) The LED-strip seems to be directly connected to the AINSER-command. Create an empty NGC and put this code in: now run ngr exec_meta rgbledrainbow:9:20. Now look at the speed of the LEDs changing. Now create another NGC and paste this code: The rainbow effect should still go on when you change between those two NGC files. But you an see that the speed differs. Is this meant to be like this? And also changing the number of num_sr=x will change the speed drastically.

Hey people, maybe this is just an easy thing... but I have a problem when I connect two midiboxes to my computer (Windows). I'm just able to access one MIDIbox only via MIOS Studio. The other one appears in the MIDI-ports list and I can click it and it seems, that MIOS Studio also connects to it. But when I switch to the file browser I see the exactly same content as on the MIDIbox before. Both MIDIboxes run NG. Is there anything one could do? I tried to change the device-ID of one of the controllers... also without success. Any help? :-) Thanks, Chris

And btw: Is there a chance so control the LEDs with the internal MIDI clock so it can act like an visual metronome? :-) //edit: just discovered another "bug". When I set the rainbow on and run after that RGBLedClearAll not always all LEDs will go off. Sometimes (random) a few of them are still on in different colors (no rainbow effect). I'd need to use the command twice in this case to shut off all LEDs. :) //edit2: And finally I recommend to use a shielded cable which goes from the output of J4B to the strip. I didn't use one and I wonder why my pitchwheel outputs values all the time. I found out that it behaves normal when I disconnect J4B. I'll try the shielded cable tomorrow.

Dear TK, there is a little error message, which the terminal outputs as soon as I start the midibox: Do you get the same message?

Works perfectly! :-)

Thanks for the explanation! I'll do that ;-) But I'll need a few days to complete the build!

Ah, thanks! Today I found a power supply, that has 2A and I connected it to a 2m strip with 60 LEDs / m. Every LED worked also if I set them to full white. But I didn't control it with STM but with another RGB controller. I expected that not all LEDs will work with 2A... do you think that the LEDs will be even brighter with a more powerful power supply? They were already very bright ;-) My strip has 120 LEDs but I will cut it to fit an 88 keyboard. So it will be around 90 LEDs. Will then only 64 LEDs work? Thanks! ;-) Can't wait to see it in action.

Whooohoooo! Awesome!!!! :-) My strip came today but I don't have a power supply that is strong enough. So, in theory every LED could be adressed individually... right? The meta only says LED 1-64... that's why I ask. Thanks TK!

I finally found the problem... there was a short on the EncoderPCB... now everything works fine :-)

I checked now with original Midibox PCBs... same problem. So it seems there is a mistake in the encoder-PCB... but I don't see it...

Thanks for the reply! Then I will try that tomorrow... Anyway... here are the files. The 2x DOUT is not equipped with ULN but with 220Ohm resistors.

Hey people, I have some trouble with self designed PCBs. I have three DOUT SRs which power 8 LED rings perfectly. The first SR is equipped with a ULN2803 as driver. This works as expected. Now I want to connect the encoders and switches to it. I add a DIN-PCB but as soon as I connect the 10pin IDC of the switches to the DIN, the LED-rings go off. There is just one LED, that is still bright. If I disconnect the ULN-PCB, nothing changes. Still this LED is on. BTW: The switches are working! If I set debug modus on I see that the PCB works as expected... just that the LED-rings go off is really not clear for me. I'll add the schematics here later on. Just a question: Are RC1 and RC2 are supposed to be soldered together like in this schematic: http://ucapps.de/mbhp/mbhp_dinx4_r5.pdf I have them seperated (DOUT got RC1, DIN RC2). Maybe somebody has a hint for me? Thanks, Chris

Whoopwhoop! I'm very curious about it ... I also just ordered such a strip (2m but I just need 1,30m). It should be here tomorrow. I didn't plan to control it with the MIDIbox... but if it would be possible..... awesome... But: Keep in mind that those strips draw a lot of current. In purewhite they draw 60mA each which makes 3,6A per meter with 60 LEDs. So be sure your power supply is sufficient. :)

The core is designed by myself and normaly has no parts for LCDs on it. The intermediate board contains all parts for the LCDs (J15A/B, 74HC595, potentiometer, etc.). This is because I wanted the core to be as small as possible and I don't need displays for every build :)

Did you tried to disconnect the displays (J15A/B) for now and only use J8/9 for testing?

Okay... I kicked this idea. It's really too much work to get this working. So I created something else. This is a simple breakout-board, which can be used with the core directly (pay attention of the voltage-selector). Every output of this breakout goes to another little PCB, that is stacked directly behind the OLED. This PCB contains a resistor and a cap... currently THT, but will be SMD in the next version I think. OLED_Breakout_8pin.sch OLED_Breakout_8pin.brd OLED_Breakout_Displayboard.brd OLED_Breakout_Displayboard.sch

Dear TK, thanks for the conclusion. Maybe 4 or 5 brightness levels are enough to give a bit of a fade-effect. I will check that with some of my led-rings. But I'm not sure how to program that into the NGR... Thanks!