Phatline

the first time i planed and built a Eurorack Case on my own... autocad was my friend... now that i have the power, and the mounting-space - i can build a test environment for my CV1.... so hopefully next time some sound-demos...

yes but you need some encoder... thats why i thougt of the DIO-Matrix (it has DIN+Resistors, + DOUT without resistors>which makes it smaller...) .... so yes 2xDOUTx4 is ok... + a DIN X1 (the one missing extra button can be taken directly from the core... 3 Pushencoder - makes 9 DIN Pins... 8 taken from the DIN register, one diretly from the core)

about RGB-Leds... midibox could do that too... http://www.midibox.org/mios32/manual/group___w_s2812.html , but i dont have much expierence whith them (in sense of codeing...but i have project here were i have to find about them anyway) you change the Faders to motorfaders? (or are they motorfaders anyway?) there are 32Bit Functions for Motorfaders here... but in the past they used 8bit cores: http://ucapps.de/mbhp_mf_ng.html cant help here, havent done that before. about space: the dinx4 modules doutx4 modules and CoreSTM take a lot of space... when you for example integrate the 595ers on your Display-motherboard you could save some space... still there is the big core... you could overcome that with dipcore + Dipboard (http://wiki.midibox.org/doku.php?id=dipboardf4) dipcore has only 2 LCD CS-Lines onboard... so you would a second DIO-Module anyway. ... but if space is no problem... but the overall height wouldnt change on booth variants... so Z=equal, but xy would differ

double post...

i made a list for needet hardware: 1x this can handle the Encoders and Buttons + 16 Displays : http://ucapps.de/mbhp_dio_matrix.html 1x this can handle 32 Displays: http://ucapps.de/mbhp_dout.html 1x this should handle 8 Displays(+the Discovery board and all the parts of course...) http://ucapps.de/mbhp_core_stm32f4.html hmm makes 56 Displays. so if you want 64 you add a 595 by yourself with protoboard, or take a nother DIO-Matrix... 1x SD-Card (+Fullsize adapter) of different Fabricates --- very often that one is not working i have 2 of this -and booth are working: https://www.mouser.at/ProductDetail/SparkFun/COM-15107?qs=0lSvoLzn4L%2B%2BrzcqjOiTEA%3D%3D 64x Pinheaders that are sitting strong (or take hotglue) in order to better repear or swap or debug the LCD from your cables A lot of cables... i dont know how big the desk is, and whats about the cable length is (really dont know where the limit is?!) And very hard to find - this tiny Screws and Nuts for the LCDs to mount(they are not M3!), if you go ali express then you wait a month or 3... and like you said a 3.3V Voltageregulator that supply with ease 1.5 to 2A, and psu that deliever that too...

if height is a problem this could spare 2mm: https://www.mouser.at/ProductDetail/Hirose-Connector/MDF7-7S-254DSA55?qs=%2Fha2pyFaduiZ71eBiARkwzzUReMZP2WhzZTuqPhRayn1qNB0%2FX2TxKoytKf%2BS9gq (not realy needett when shorten the pinheaders of the displays by hand, and removing the header-plastic) but maybe its whise to use standart pinheader - because of price and aviable... ..just a thought.

a dinx4 would also help (for the encoder) - could be solved with the pins onboard too but easer to implementate with a Digital-In-Shiftregister & if you decide to make that project then you could start a "name"list...Labels.ods i can later copy paste this into the code... (my labels in there are not really usefull for you project, but the structure is already for copy paste...) i hide some tabs in there: { ' 3 ' , ' 0 ' , ' 3 ' , ' ' , ' ' , ' ' , ' ' , ' ' }, so dont overwrite this ’, and }{

no not sure.

i think you will need a the cap and resistor on reset for every display (they told me...dont know if necessery)

now a eurorack -frontplate....

ya i made a custom ui where the microntrollerboard is plugged into... but for your job, you only need a core32stmF4, 2x doutx4, and 1x midio IO...and a relative simple app (where i can help...)

i now implemented this custom-Label change... see the first view minutes of this video:

the UI is almost finished. next is to modulate some noise... (but for this on a other video):

@6 Pins: i also have 8 of them sadly... and i would love to see them working ---maybe someone have expirience with that (change the driver? or pinout? i dont know - maybe someone other can help?) @ picturen, i made a short video for you... its uploading right now... will be aviable here in 45 minutes: its not really a Typing -its "set cursor" "change Letter" "press save", as far as i know you cant connect a normal Keyboard to the Midibox - and i didnt see a driver (usb-host is possible on midibox.... but i dont think there is a driver?)

"normally" we use here 7 Pin SPI SSD1306 (GND,VCC,D0,D1,RES,DC,CS) connected like this: purple Lines = CS-Lines: the first (8or?) 16 CS/purple lines you get direct from the Core STM32F4, > http://www.ucapps.de/mbhp_core_stm32f4.html the 48 Rest CS-Lines from 595-Dout-Shiftregistors-Pins (6xICs with each 8 Pins) > we call that http://www.ucapps.de/mbhp_dout.html The Update Rate will be a bit slow - but for Label a static Mixer Desk, it will be ok? custom Bitmaps: http://wiki.midibox.org/doku.php?id=how_to_create_custom_glcd_fonts_icons_bars_for_midibox_ng @ Labelitself, I myself have a simular thing, but for a Midi>CV Device, i have to label Encoders... i managed it to save a huge array of "chars" - like this...: char Label[512][8] = { {'3','0','3',' ',' ',' ',' ',' '}, {'6','0','6',' ',' ',' ',' ',' '}, {'7','0','7',' ',' ',' ',' ',' '}, {'8','0','8',' ',' ',' ',' ',' '}, {'9','0','9',' ',' ',' ',' ',' '}, {'-',' ',' ',' ',' ',' ',' ',' '}, {'*',' ',' ',' ',' ',' ',' ',' '}, {'/',' ',' ',' ',' ',' ',' ',' '}, {'+',' ',' ',' ',' ',' ',' ',' '}, {'A','M','P',' ',' ',' ',' ',' '}, {'A','M','P',' ','E','N','V',' '}, {'A','M','P',' ','L','F','O',' '}, {'A','M','P',' ','M','S','Q',' '}, {'A','D','S','R',' ',' ',' ',' '}, ... with all possible Names - that i could use for Control-Voltage Projects.... i save this on SD-Card, on a .sys file (no PC involved the microcontroller do that) - in a Patch aka Song i then Recall it like this: MIOS32_LCD_DeviceSet( 3 ); // select Display 3 MIOS32_LCD_CursorSet(0, 1); // Select Vertical the second Line, Leftmost Horizontal MIOS32_LCD_PrintFormattedString("%c%c%c%c%c%c%c%c", // 8 Chars is max if you use BIG-FONTS Label[ aout[ENC].sel_label] [0], Label[ aout[ENC].sel_label] [1], Label[ aout[ENC].sel_label] [2], Label[ aout[ENC].sel_label] [3], Label[ aout[ENC].sel_label] [4], Label[ aout[ENC].sel_label] [5], Label[ aout[ENC].sel_label] [6], Label[ aout[ENC].sel_label] [7]); where ENC is the Encoder Number where the LCD is situated. aout[].sel_label: i save that Var on SD-Card-with the Patch / and load the Patch via Midiprogramchange. // with a given Number you adress a Name... you can also custom Labels, with ease with 2 additonal Rotary Encoders (while one is the cursor) (and the other one change the Letter), you might need for a UI-for Midibox at least 3 Encoders(with inbuilt pushbuttons) and 1 SSD1306 in order to SAVE and LOAD or ADD Custom Names...

thx realized that i can print LCD-Messages in the APP_init itself... -- now i entertain the user a bit with some progress. i have put the heavy copy file thing into the App_init itself (512x84Kb files), this is working now, since i realized that i has only 2,2V on the SD-Card... which was a faulty core PSU.... now its working like a glance. while a SSD1306 is working with no probs on 2,2V a SD-Card is not - good now i know that.

i have trouble by initize my SD, Card, in sense of i copy big Files multiple times... and that fails when making a freertos Function for it.... or by adding it into one of the standart Functions like "Background" or by making a new Function in the Program loop... Because of the SD-Card reacts to slow, the files to big, to much of the files.... i already avoidet all "for loops", and copy one file after a nother once a Program-loop-cycle.... when i put the copy function into the "app_init" it is functional, but of course the display is Black -feeled forever- until the program starts the first time... so the user may think the device has failed... what makes me think, of an second App_init Like Function, which is only performed once, and which attribut is: it can run forever, and when its done, MIOS runs without it. but maybe i have not understand some basics again...

Labels.ods this is what i get : gives a array of:

on my Midibox CV Project, i make char-arry with alpabetical sorted Words --- which are Labels under Encoders to show you the Parameter names because its a modular project, i will make it easy via Drop-Down-menue to change the Labels on the fly for this i started a Excel (in order to sort alphabetical) looking like this: later i copy this block, into a text editor, replace automaticly the spaces, and copy paste it into the c program. may char array in C-Code will end up like this: char Label[512][8] = { {'a','b','c','d','e','f','g','h'}, {'i','j','k','l','m','n','o','p'}, {'q','r','e','s','t','u','v','w'}, {'1','2','3','4','5','6','7','8'}, .... }; my Font-Size only allow 8 Chars on a SSD1306 (128x64pix) i will report my list here, and if anyone has some idea which should be add (because its missing), then write it here. thx.

bright enough! I made a mistake by creating the Transistor-Array-Footprint, so i bridged it out for the Protoboard, but for me its bright enough anyway.

programming programming programming...

the wires that are going out of the din or dout modules are not so importent (except that they itself transmit radio...) so they can be long (except you make a scan-matrix... i think) @ pots... they 5V and GND lines: make them thick.... the signal line - you may take a shielded wire...

depends on the modules - and what you do with it.... i cant tell you that - sorry bro. as example SD-Card-Module: as short as possible < 10cm... but i want you to keep in mind: * keep the Flatbands between the modules short * and dont give a shit on wirelength off the single wires which are going out of this modules - when it comes to the question - module interconnection vs single wires( aka shiftregister outputs/inputs) - except it is analog stuff. * when you interconnect the cores via MIDI > Midi length dont care! but the interconnection Midi-Module>Core CARE! (since a midicable can be a shieldet cable, the flatbandcable is not at all!) - so could built some Places of cores and Modules on different places of your controller... * i talk about big consoles --- if you have a 19" Inch controller i would not care so much about Cable lengths. (but keep them in mind when you design it) because of? because of RADIO Waves? or electromagnetical Interferencys? or may it be "Runtime-delays" thats a way of latency....

cascade matrices... & multiple modules >>> keep Flat-band-Wires from module to module as short as possible (if you build a big console: position the modules near the cores...)

if ableton: showing vpot does ableton from stock - when you you goe in midi cc edit mode - then click a vpot, then move a midibox rotary - done - the rest is a thing of midibox (showing the value) fot VU valjes inside the channelstrip (between the vsts) you can use max4live to detect peak or average signal values and send it via midi or ethernet (to get midi outsidd a audio max patch was in the past a problem -there are workarounds-dont know what ableton11 fixex)to your midibox - you might not get vu values from inside of a plugin! but befor and afterwards. on first scenario you have to script midibox ng (or code your own app in c based on mios...) in second you have to code max msp - thats object programming (connect boxes with wires)