Jump to content

roberto

Members
 View Profile  See their activity

  • Posts

    33

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by roberto

  3. MANIPULATÖR 002 - THE OPEN MINDED MIDIBOX NG

    in MIDIbox NG

    Posted

    thanx!

    1 hour ago, Antichambre said:

    How do you select the part which is controlled by the NG? Did you find a way for the NG to follow the stagelight track selection?

    at the moment i select the parts by hand with the bank switches... 

    stagelight isn't fully grown yet, there are several things that aren't working. no proper midi assignements, it's not possible to record and playback controller data and so on...

    so for the moment is cool to jam with it... im working on a max4live interface where things maybe get more easy to do. for example sending controller data to change the banks...

    also it would be cool to have the parameter names feedback on the GLCD's. OSC or midi exclusive? i havent figured out the best way to do yet...

     

    1 hour ago, Antichambre said:

    But I'm afraid for you that people will ask you more information to build their own ;)

    no problem. this is what this forum is for!

  6. MANIPULATÖR 002 - THE OPEN MINDED MIDIBOX NG

    in MIDIbox NG

    Posted

    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

  8. MANIPULATÖR 002 - THE OPEN MINDED MIDIBOX NG

    in MIDIbox NG

    Posted

     

    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... :cry:
    P.P.S: moderator fixed this

     

    • Like 1

  10. 16 x SSD1306 GLCDs on STM32F4

    in Testing/Troubleshooting

    Posted

    oh, cool, many thanks latigid on, as always fast and competent answers! :happy:

    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 :grin:

  11. 16 x SSD1306 GLCDs on STM32F4

    in Testing/Troubleshooting

    Posted

    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

  15. How to connect Common Anode RGB LEDs

    in Testing/Troubleshooting

    Posted

    yes, those are nice buttons, rugged, but 10 bucks each... :decayed:

    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.

  16. How to connect Common Anode RGB LEDs

    in Testing/Troubleshooting

    Posted

    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... :cry:

     

    the RGB button has internal resistors, so i think it's not necessary to match the color brightness...

     

  17. How to connect Common Anode RGB LEDs

    in Testing/Troubleshooting

    Posted

    Hi

     

    After testing the functionality of the CORE, DINs and DOUTs it’s time to layout the Controller.

     

    I want to use (among others) 16 RGB Buttons and im unsure how to connect it to the DOUT’s.

    I read some threads about it but didn’t found the answer that satisfied me.

     

    http://midibox.org/forums/topic/18058-connecting-rgb-leds/?page=1

     

    http://midibox.org/forums/topic/19752-rgb-hue-sweep/#comment-171871

     

     

    The RGB Buttons are COMMON ANODE. One possibility is to attach it to a 6 *8 LED Matrix with the drawback to loose brightness.

    I don’t want that, I have enough DOUTs to connect the LEDs directly, so I would like to go the direct way.

     

    Is it possible to do that without using additional ULN Arrays?

    As I understand it is possible to drive one RGB LED with one Midi Note and make the color with different velocities right?

     

    And since I am at the very beginning of everything I don’t understand how the code should look for that...

     

     

     

  23. BEGINNER - Problems with INPUTS on MBHP CORE STM32F4

    in Testing/Troubleshooting

    Posted · Edited by roberto

    damned, i measure and measure, check and check, over and over, i can't find it. so thank you latigid for the advice...

    RC1 and 2 are NOT conected together. there's continuity from SI to pin PB14, no shorts anywhere to SC, RC, +5V, 0V, pins 9 and 10 are like expected and also 10k pullups are there...

    but yes, the crank has to be there somwhere. i measure 4.9V on the DIN, i think this is ok? im sure it is something really dumb.

    maybe something with the configuration? because i get some invalid infos like: ((don't know what tokens and .NGR and .NGC are for))

    [8346.901] show ngr_tokens
    [8346.903] Token processing is: enabled
    [8346.903] Token memory allocation: 0 of 16384 bytes
    [8346.903] .NGR file is: invalid
    [8346.903] Tokens are: invalid

    attached is the whole config file and at the end the midi routings and the reset info. there is no source port set ON. is this intended like that? or do i have to change that?

    Snapshot #0 not stored in /DEFAULT.NGS yet.. how to store ???

    config.rtf

  24. BEGINNER - Problems with INPUTS on MBHP CORE STM32F4

    in Testing/Troubleshooting

    Posted

    ok, card reader finally arrived... it's recognized it seems:

    [3381.877] sdcard

    [3381.879] SD Card Informations

    [3381.879] ====================

    [3381.879] --------------------

    [3381.879] CID:

    [3381.879] - ManufacturerID:

    [3381.879] - OEM AppliID:

    [3381.879] - ProdName:    

    [3381.879] - ProdRev: 133

    [3381.879] - ProdSN: 0x00000707

    [3381.879] - Reserved1: 193

    [3381.880] - ManufactDate: 135

    [3381.880] - msd_CRC: 0x29

    [3381.880] - Reserved2: 1

    [3381.880] --------------------

    [3381.880] --------------------

    [3381.880] - CSDStruct: 0

    [3381.880] - SysSpecVersion: 0

    [3381.880] - Reserved1: 0

    [3381.880] - TAAC: 62

    [3381.880] - NSAC: 0

    [3381.880] - MaxBusClkFrec: 50

    [3381.880] - CardComdClasses: 1461

    [3381.880] - RdBlockLen: 10

    [3381.880] - PartBlockRead: 1

    [3381.880] - WrBlockMisalign: 0

    [3381.880] - RdBlockMisalign: 0

    [3381.880] - DSRImpl: 0

    [3381.880] - Reserved2: 0

    [3381.880] - DeviceSize: 3779

    [3381.880] - MaxRdCurrentVDDMin: 4

    [3381.881] - MaxRdCurrentVDDMax: 5

    [3381.881] - MaxWrCurrentVDDMin: 4

    [3381.881] - MaxWrCurrentVDDMax: 5

    [3381.881] - DeviceSizeMul: 7

    [3381.881] - EraseGrSize: 31

    [3381.881] - EraseGrMul: 31

    [3381.881] - WrProtectGrSize: 31

    [3381.881] - WrProtectGrEnable: 0

    [3381.881] - ManDeflECC: 0

    [3381.881] - WrSpeedFact: 4

    [3381.881] - MaxWrBlockLen: 10

    [3381.881] - WriteBlockPaPartial: 0

    [3381.881] - Reserved3: 0

    [3381.881] - ContentProtectAppli: 0

    [3381.881] - FileFormatGrouop: 0

    [3381.881] - CopyFlag: 0

    [3381.881] - PermWrProtect: 0

    [3381.881] - TempWrProtect: 0

    [3381.881] - FileFormat: 0

    [3381.881] - ECC: 0

    [3381.881] - msd_CRC: 0x7c

    [3381.882] - Reserved4: 1

    [3381.882] --------------------

    [3381.882] 

    [3381.882] Reading Root Directory

    [3382.057] ======================

    [3382.057] Retrieving SD Card informations - please wait!

    [3382.058] SD Card: '': 990 of 990 MB free

    [3382.058] [......a] 00/00/-20  00:00:00 AM     43432 DEFAULT.NGC

    [3382.058] [......a] 00/00/-20  00:00:00 AM     584 DEFAULT.NGL

    [3382.058] [......a] 00/00/-20  00:00:00 AM     251 DEFAULT.BIN

    [3382.058] [......a] 00/00/-20  00:00:00 AM     520 DEFAULT.NGS

    [3382.058] [......a] 00/00/-20  00:00:00 AM     3124 DEFAULT.NGK

    [3382.058] [......a] 00/00/-20  00:00:00 AM     43432 TEST.NGC

    [3382.059] [......a] 00/00/-20  00:00:00 AM     3124 TEST.NGK

    [3382.059] done.

    i can save and load from card.

    i resoldered all boards again (DIN's, CORE), checked for shorts again and changed the IC's on the CORE (74HCT541 + 74HC595)

    still no luck...

    the DOUT's are working perfectly, the DIN's don't.

    all i get is the attached debug infos when i short VS and D7 on the first Header J3 on the DIN. it sends 64 note-on's on close and 64 note-off's at open.

    i get this on all DIN boards but ONLY on the first header (J3). all other headers (J4-J6) and pins (D0-D7) don't react... 

     

    debug.rtf

×
×
  • Create New...