• Content count

  • Joined

  • Last visited

Community Reputation

29 Excellent


About FantomXR

  • Rank
    MIDIbox Guru
  1. Control LEDs without HC595

    Hey people, Maybe you can guide me in the right direction.  In my projects I use buttons with integrated LEDs. But I want to get away from the standard HC595. Mainly because it takes a lot of PCB space and it has a lot traces due to the SPI protocol.  Is there another style to control those LEDs? I also work a lot with WS2812. This is great because there is only one single data line from one to the next.  Thanks, Chris
  2. But anyway I'm highly interested what causes this issue... Something seems to disturb the STM when booting... I have no idea. 
  3. I mean the bootloader of the midibox and not the computer. 
  4. I remember that I encountered that a few times too already. All digital signals where inverted after system boot. So also buttons that were connected to the midibox didn't sent 127 when pressed but 0 and the keyboard did the same.  I never solved this. Maybe @TK. has an idea.  Did you try to set fastboot on in the bootloader? I think that was my workaround...
  5. Ainser64 configuration

    You can not set the resolution on a "per input" base. So yes, you'd need a dedicated AINSER module. Please note: MIOS32 only supports two AINSER modules. Although TK shows how to implement a third module in another thread, I was not able to get it running.
  6. IC not available anymore

    Why dont you take those??
  7. IC not available anymore

    Depending on what you want to do you can leave it away completely. What housing do you need? DIP or SMD?
  8. Speed up writing OLEDs

    Well, I hope that it looks better. Now you can really watch the OLEDs build up their text. If this could be speeded up, it would be great. BTW: I send SysEx strings on the displays.
  9. NRPN issues - can't go past NRPN #256

    I can confirm Brunos changes work well! :-)
  10. Speed up writing OLEDs

    Hey people, my setup contains nine 128x64pixel OLEDs in a horizontal layout. I usually print to all of them at the same time. Now, MIOS writes to the displays character by character. So it starts with the first line on the first OLED, goes all the way to the first line of the 9th display and then starts over at the 2nd line of the first display.  Since there is a lot of data, it takes time to print to the OLEDs and you really can see how the characters are printed line by line.  So my question is: Is there a way to speed up that transfer rate? I googled a bit and found this on an arduino forum: Is it possible to somehow adapt this to MIDIbox? Do you have an idea? Thanks, Chris
  11. NRPN issues - can't go past NRPN #256

    I think I ran into this problem also a while ago. Unfortunately I don't have a fix for that issue. 
  12. AINSER configuration (Aftertouch)

    Same here. But it seems to be correct. I've used it a lot already. 
  13. If you set type=cc then it's logical that it only allows values between 0-127. If you want to send highres-midi you have to set the type=pitchbend or type=NRPN.  If you substract 7682 from 8192 you will get 510, which is almost what you set with the range. In this case you have to use MAPs instead of standard ranges. Then it will work. Please refer to the NGC-manual. For testing purposed I'd recommend not to use ranges anyway. 
  14. This should totally be possible. Would you please post the related parts of your NGC file?
  15. Is this possible?

    @latigid on as this might effect the programma too, maybe you can answer this question: Is there any other way to achieve this?