FantomXR

Good question! It's hard to see. I think it's about 6. Didn't know that dimming of LED-rings is already possible. I need to check it out. Thanks!

Hey people, another question! Today I had the MIDI fighter twister in my hands. It's a 4x4 encoder box with LED rings. It's a great USB controller... you should check it out. Anyway: When I turned an encoder I realized that the LEDs of the ring are dimmed... so they fade slowly into full brightness depending on the value. As far as I know the LEDs on MIDIbox are just going on and off. But the fades are quite fancy ;-) No big thing but I just want to ask, if this might be able in the future with MIDIbox as well ;-) Thanks, Chris

Great! I'll wait for it then ;-)

Hey people, inspired by another thread I'd like to create a pcb which has 3 RGB LEDs (or 9 single LEDs) on it. This PCB could be stacked on top of a encoder and illuminate it. I could cnc mill the caps for it by myself. My question is now if it's possible to wire each color in series (so, all blue, all red and all green LEDs) or if the current and / or voltage provided by a DOUT (maybe with ULN installed) is not sufficient to light all three LEDs. The reason for this is, that it would be less programming because I only would need to add one string for each color in the NGC instead of three strings. Also it would be less wiring. There is no need to access the LEDs individually. Thanks! Chris

Dear TK, awesome! But the keypad was working flawlessly before anyway :-)

Hey Thorsten, do you have any usecase-examples for inspiration? :)

Hey! I just want to grab this out again. Maybe TK is able to give us a quick "yes" or "no" on this topic :-) Here is another distributor of those displays: http://www.wellbuying.com.tw/UP_pdf/PS007.pdf

You use an LPC-core? Is that right? And what do you mean by distribution-board? BTW: Which kind of buttons do you use? They look great.

Maybe you could provide a few pictures of the board which contains the switches, LEDs and stuff! That might be helpful.

Hi Andy, a short question if you don't mind: Where do you have the layout from (text, symbols, etc.)? I'd be interested in that :-)

I wouldn't recommend that, because by doing this you lower the resolution of the velocity of the keyboard, because more DIN/DOUT have to be scanned. Rotary encoders are also digital. So AINSER64 is not helpful here. For normal pots you want to use AINSER but for encoders you'll need to go with DIN-modules.

@norbim1: Which values do you use for SRIO num_sr= and debounce-cycle?

I discovered a bug in NG! Here is an excerpt of my NGC: And here the NGR: What I try to do is, to activate different channels on the keyboard. If I press BUTTON:17 Chn. 4 should be active and if I press BUTTON:18 also the keyboard should send on two channels (f.e. layersounds). What happens now is that I can set the keyboard with BUTTON:17 to chn.4 without problems. But if I press BUTTON:18 nothing happens. But the strange thing is: If I now delete the whole "BUTTON:17"-part in the NGR file and try again, it works also with BUTTON:18 to set the chn. to 2. I set the debug messages on and with the code I posted it says, that there is no event assigned to hw_id when trying to use BUTTON:18. So it seems that there are some problems with the ID-handling. If you need more informations about the problem, just let me know! Thanks! BTW: Maybe there is an easier way to activate multiple channels on the keyboard?

Okay! Thanks for the code! This is definitely better than before :-) maybe TK will spend a bit time on this and can improve the app if we kindly ask him ;-)

Hey! I checked that and compiled it. I have the problem that no Note Off is send when I release a key. Any suggestions? //edit: Okay. I did "set kb 1 release_velocity on" and it works ;) Thank you very much! I wonder if I can disable the release-velocity because I don't use it. But like I said. If I switch it off, there will be no note-offs generated :( Ah! Now I understand. There are two options: 1.) Set release-velocity on, set make-debounced off: High velocity-resolution but sometimes notes will send a velocity value of 1 when pressed (even when it's pressed much harder). This behaviour is random! 2.) Set release-velocity off, set make-debounced on: Lower velocity-resolution, but all notes play like they should.

Hey, thanks for the file! I'll try to compile the app tomorrow! I'll keep you posted. Best, Chris

This sounds awesome!! Thanks!

Hey! I'm not sure if this is really the reason for the stucking notes because a note is normally not triggered when just the make contact is active. Also the break contact needs to be active to create a note on. I think it's more a problem due to the inverted diodes on the keybed. I need to set din_inverted to 1 if I want to use this keybed (it's an old Fatar TP/8S from a Roland A70). I also discovered, that the velocity-resolution is much lower on din_inverted 1 as on other boards which don't have the inverted diodes. It get's even more dramatic when using NG instead of KB. In NG I have only about 10 velocity steps with this keybed.... I checked the schematic of the keybed and it should be possible to simply cut and turn the diodes so I can use din_inverted 0. Maybe this solve those issues. Thanks, Chris

Hey, sometimes especially when doing a glissando I get stucking notes. I can avoid this by using MIDIbox NG and set the number of shift registers to a higher value f.e. 6 or 8. But this on the other side lowers the velocity-resolution and I normally want to use the KB app for the keyboard. Do you have also those problems? I have that with different keybeds (all FATAR). And another question: MIDIbox KB features an option that is named ain_bandwidth. I can not see such kind of option in NG. May I overlook something? Because: If I connect a expression pedal to my NG, play the keyboard and move this pedal, I get also a lot of stucking notes. I think that the DAW (or the NG-app) is stressed too much because of all this informations. Thanks!

I think he is in denmark ;-)

Sure! I totally agree with you. There is nothing better than a real fader or knob. But I think Lemur could be used more for labeling and feedback than for controllers itself. Envelopes, etc. could be easily displayed there but controlled with your programma ;-) Just an idea. I'll integrate it in my next keyboard for sure.

Hey Peter, what do you mean with bitmap loader? And which ideas to you have for integrating envelopes? I just bought an Odroid mini-computer, running android. Should be here in a few days. I want to try to use lemur on this mini computer. Could be a powerful enhancement.

Congratulations! This is great! ;-) So, you can confirm that 24 OLEDs are working without any issues? I thought there would be a limitation on the hardware side or did you use a separate power supply for them?

Hey! I just took a look at the great midas mixing consoles. They use switches with integrated displays, which is really fancy. After a bit of googling I found out that NKK Switches produces them. They are very expensive (50€ and more). I wonder if those switches are compatible with MIOS! Here is a link to a datasheet: http://www.nkkswitches.com/pdf/IS15EBFP4RGB_Wide64x32LongTrvl.pdf I don't think that it makes sense to put effort into this if MIOS doesn't support it already, because nobody will use them later on... they are too expensive. So I'm just asking ;-) Thanks Chris

But couldn't he do it via a runscript-command that triggers an EVENT:LED dummy, which contains the standard message. The script is called via the encoder after a delay.