• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About roberto

  • Rank
    MIDIbox Newbie

Profile Information

  • Gender
  • Location switzerland
  1. seq-productsheet-two.jpg


    thanx! no problem. this is what this forum is for!

    yes, the screen is plugged into the internal intel nuc which is hosting the software. the screen is working flawless with win 10. 14 ms response. no luck with osx - there are no decent touchscreen drivers... (shame on bitten off fruits :)

    thank you very much master TK! without all YOUR efforts you did the past decades for this platform i couldn't do something like that...

    thanks guys. @engineer this is all a question of the software you use. in the video i use stagelight who is capable to host vst's. then there are two moogs controlled also by stagelight and routed back to the software via audio-interface... as example one could use vcvrack (freeware!) as a "touchable" virtual modular synth controlled also with the hardware knobs and encoders... the screen is a planar screen

    many thanks peter! the same to you!
  7.   after 6 months of blood. sweat and tears, 20m of ribbon cable, a ton of parts soldered, screwed and glued -  it’s (almost) done! this midibox build-up is intended to use it for what ever i like. it can be a midi controller for music applications, sequenzer, modular controller, video mixer, lightning desk etc… the sky is the limit!   still   this is a first test controlling some moogs and plug-ins with open lab's stagelight. thanks to the midibox community for the competent help and documentation.       SPECS: CPU - Midibox NG on STM32F4, 4 x DIN, 4 x DOUT, AINSER64, AOUT_NG, MIDI IO - Intel NUC 3.5 GHz Dual Core i7, 32 GB RAM   SCREEN - 21.5“ capacitive HDMI touchscreen 1920 x 1080 px - 16 x OLED displays 128 x 64 px   HARDWARE - 17 x endless encoder with push - 16 x blue LED buttons - 16 x RGB LED buttons - 6 x bank buttons - 4 x function buttons - resistive XY joystick with push - 2 x 60mm faders   EXTENSIONS - 8 x CV out - 2 x DIN MIDI I/O - 32 x analog IN (for pots, faders, sensors) - 32 x digital I/O (for encoders, switches, leds) - HDMI port for 2nd monitor, beamer (4K) - 2 x USB3 in ports (NUC) - 1 USB out port (switch for internal/external cpu) - modular voltage out +/- 12v, 5v   all the best roberto   ps. how to embed YouTube videos? i dort get it...  P.P.S: moderator fixed this  
  8. 16 x SSD1306 GLCDs on STM32F4

    nice! works...   
  9. 16 x SSD1306 GLCDs on STM32F4

    oh, cool, many thanks latigid on, as always fast and competent answers!  i will try the J10B version, if ist not working then i go with SN74s. thanks for the display driver link, did't saw it ntill now...   other question: i do have the alientek OLED's, the dual color version (blue/yellow). now it's displaying in blue... how to change the color?   best roberto 
  10. Hi i want to extend my project with 16 GLCD's. i found several threads about it but i'm still unsure how to connect the additional CS lines. the first 8 GLCD's work perfect connected to J15A... now i need to know how to connect the other 8 lines. found this wiki where it's stated how to connect additional lines from a J28 named connector. but on a "normal" STM32F4 the J28 isn't available... I read on an other thread that several lines are available on connector J10B. If I look at the schematic J10B is a normal GPIO against the J28 is a audio DAC. Can I use the GPIO's directly as they are to make 8 additional CS lines? if yes, do I need 220 ohm resistors on it? do I need an other boot loader configuration as the one described here in the MBNG manual? if no, how to use a SN74HC595N IC to generate additional lines? Where do i get the clocks (RCK and SCK, Pin 11/12 on 74HC595) and where comes the DISP SER IN (Pin 14 on 74HC595) from?   thanks for some enlightenment, roberto
  11. How to connect Common Anode RGB LEDs

    ...just for the record. im slowly slowly get into the deep sea of MIOS... i managed to map the RGB buttons with the multicolour test mentioned in TK's post above. everything's fine... (although magenta is missing in the map, i added it at the end after red...) back to construction 
  12. How to connect Common Anode RGB LEDs

    switched back to first comuter, and there it is again... button behaviour inversed again, damned...
  13. How to connect Common Anode RGB LEDs

    strange... i booted the whole thing on a second computer and now it's working as expected...  will investigate...
  14. How to connect Common Anode RGB LEDs

    yes, those are nice buttons, rugged, but 10 bucks each...  well, before fiddling with RGB hue, i have to solve following by inverting i turn off the RGBLEDs on startup: # Common Anode RGB LEDs EVENT_LED id=1 inverted=1 type=NoteOn key=36 # Red LED EVENT_LED id=2 inverted=1 type=NoteOn key=37 # Green LED EVENT_LED id=3 inverted=1 type=NoteOn key=38 # Blue Led by sending a NoteOn 36/37/38 and Off from the MIOS Keyboard i can light and turn off the 3 LEDs. Fine.   Now, when i define a button the behaviour is reversed EVENT_BUTTON id=81 fwd_id=LED:1 type=NoteOn key=36 range=0:127 button_mode=Toggle EVENT_BUTTON id=82 fwd_id=LED:2 type=NoteOn key=37 range=0:127 button_mode=Toggle EVENT_BUTTON id=83 fwd_id=LED:3 type=NoteOn key=38 range=0:127 button_mode=Toggle will say, the LEDs are OFF when the button sends a NoteOn and ON by a NoteOff... i tried to inverse also the EVENT_BUTTON and the range (127:0) but nothing helps... is there something else i need to invert? i don't get it.
  15. How to connect Common Anode RGB LEDs

    cool, thanks latigit, works... as i understand following code inverts the output: EVENT_LED id=0 inverted=1 EVENT_LED id=1 inverted=1 EVENT_LED id=2 inverted=1 etc. now i have to figure out how to assign the RGB LEDs to different velocities on the same note... phew, this coding is a big book to get into it...    the RGB button has internal resistors, so i think it's not necessary to match the color brightness...