Leaderboard

Hey everyone, just wanted to share my latest build since I'm sure there are some 3D printing enthusiasts here like myself. I bought the parts for an MB6582 about 5 years ago, if you remember Meeblip was selling those 8580 SID chips and I picked up 8 of them, and then put everything into a box in a closet . 3D printing has come a very long way since the original MB6582 was created by Wilba. I read that the JB Weld solution may or may not be holding up great after all this time. Also, I wanted to use a Newhaven OLED which is much thinner than the original LCD. I thought there must be a solution to lower the gap distance so why not create some type of spacer for between the front panel and the PCB? I designed all parts in Fusion360. The PCB screws directly into the spacer using M2.5 nuts/screws and plastic screws. The top of it has a flange that rests in the panel groove for the PT-10. Total spacer height is 5.7mm which is the height of the base of the encoders. The front panel is another 1.25mm. Everything is printed out of ASA, which is very strong and heat resistant. I designed the panel graphics in Inkscape and printed on translucent vinyl. I used Davies knobs with small printed skirts to cover up the threads of the encoders since they were exposed. I do not have a vinyl autocutter but I do have an exacto and lots of patience Overall tried going with a 80s beige computer look. A build plate for my printer created the carbon fiber effect on the panel. I'm happy to share the 3D files if anyone could use them.

Hey man. It's actually an FR4-Standard PCB. Non aluminium. But seems pretty robust anyway.

DM sent

Prompted by a message from freddy, I've attached the project files below. They contain the source and the binaries for the bootloader and the main code. 1.05 is the latest version - there was a fix in the bootloader and the main code. I included some memory in the final hardware design but never got around to doing anything useful with it. I had plans to save one or more demo tunes as MIDI files and perhaps save some settings as profiles for different scenarios - my interests had moved on before that happened. You can find more project info at https://web.archive.org/web/20210206041027/http://www.grapevyne.com/pic.projects/ - the documentation links are all active so you can download the magazine articles and also my original source for the articles (a few errors crept into the magazine article during editing). mistralXG project files.zip mistralBoot.zip

Hi all I am having a very hard time making any progress with a problem with my left LeMec board. When I first assembled the JA and LeMec boards and tested them, everything was working on JA board and the two LeMec boards except: - encoder 3 on left Lemec board was not registering depress events - encoder 8 on left LeMec board was generating garbage counter values when rotating. Since then I have gone backwards and been stuck for over several weeks with no progress. I first tried to solve the issues above with reflowing the ICs on left LeMec board but that didn't help. I then reflowed the ICs on the core, and after that, I am in this worse state with left LeMec board - encoder 8 does not register turns - none of the encoders are registering push events - 4 leftmost buttons on are not registering push events - 12 of the 16 LEDs light up immediately upon powering up as seen in attached pic I haven't bothered testing the Matias switch events as this is enough wrong already I have reflowed the ICs, diodes and transistors on that board multiple times, and on the core board too, and nothing is changing. The only advice I get from Midiphy is to reflow/check for dry joints/shorts which I have done over and over. It would help to have proper circuit diagrams to try to chase down likely culprits instead of messing with everything all the time. If I just connect the JA board to core and run the seq_l test, that is still testing fine for everything. The right LeMec board is out of the picture for now; I think it was all working well at least. Any help will be most welcome as I am close to assuming I just have to abandon this and write it off as a very expensive exercise in frustration and futility. Thanks Graham

To use Studio on newer Ubuntu Desktops you need to install the old libwebkit2gtk-4.0.so.37. To do so create a sources.list file for apt containing the following line: deb http://gb.archive.ubuntu.com/ubuntu jammy main And install the lib. sudo apt update sudo apt install libwebkit2gtk-4.0-dev After this delete the sources.list file. More infos on https://www.weigu.lu/music/midibox_hp_2x2/index.html

II replaces the remaining ICs and its working! Woohoo!

Reflowed the ttasnsistors on the top side and now I am back to 12 LEDs on. I'm assuming the LEDs shouldn't be on, but otherwise that feels like an improvement as it means I get mattias switch events for 12 of 16. I'm also getting events for depresses on the right 4 encoders although they seem a bit random in the actual event details. I've also replaced IC2, IC3 and T3 based on advice from ChatGPT but that made no difference.

Thanks, perhaps I'll shoot over to the UK ;-) I've rebuilt the core board now and I'm back where roughly where I started. At least I feel confident I have eliminated the core as a possible cause; the problem must be with my LeMec board. Done some more reflowing on that board and now: - just 4 LEDs light up on power up now - all encoders generate counts when rotated but not depresses - botton left 4 buttons generate no events; bottom right four are working - mattias switches generate events for the four that have illuminated LEDs but not the rest

This looks amazing! With some of the older chips like vintage vca, filter or delay chips you really have to be careful regarding heat and also (or even more so) static discharge. Nowadays with most ics these issues have long been solved by modern manufacturing processes and built in safety measures. I had to lear the hard way that this is not the case with chips from the 80s... So the heatsink is probably a good idea, as would be any way to allow for some airflow. On the other hand, i have removed the fans from some of my gear with no issues at all, as commercial units have to consider every worst case scenario (crowded rack in hot environment). So if you know how you use your gear you can get away with things that could not be allowed for every scenario.

With velocity bars there is more info displayed and the spacing is more uniform. The hyphen/minus as a spacer for natural notes helps to connect them; with spaces it is more confusing. Do you really use those low octaves so often @anonyme-x22? If it bothers you, a workaround is to transpose either on the SEQ or your synth.

Arrived and kicking. Thank u for your service ❤️

Confirmed over here, no humanizer being applied to CC’s. I tried with an empty track sending layer A as CC on buss 1, and another track listing to buss 1. The listening track was responding to the cc’s, but humanizer did not effect the CC’s. Then moved the cc to layer B (usually the velocity layer) and still no changing of CC’s sent. steve

New top as requested PM me please, or I can send the details as well.

Thanks for the tpd-test app it really helped me along with this build!.

i made a passive design, since the fan which came from mouser, was dead from the beginning... since it is a 6582, it was not going very hot anyway... but i drilled Holes into the pcb under the SID-Sockets, and cut aways some plastic from the socket too. i too drilled some holes in the plastic body under the Main-PCB too, the backside off the SID should be enough to get rid off the hot air...

a nother passive SID alive...

Thank's for the tip! What I'm looking for is either the fpd file which fits the Heidenreich case or maybe a ready made panel. The fpd file I found in the Wiki seems to be not specifically made for the Heidenreich case. I prever a fpd file which is proven to fit into the Heidenreich case before trying to adapt Wilbas files to the case.

If you made your own PCBs using the available schematics, then I think you may be free to sell them to others here, since they're your own derived work. However, you cannot sell the finished and fully assembled sammichSID or MB-6582 synths as commercial product without express permission. Someone else here may want to jump in and correct me if I got that wrong...

Hi ssp, I don't remember if labels can be called from a map, but i don't think so. However, i think it is possible to change the display using a .ngr script. Bests Thomas

Just a small necro-bump :-) …by now we are roughly 150 people over there with some occasional chatting going on. Feel free to drop by!

maybe its the Ripple off the PSU about your PSU - reichelt specs is saying : "Ondulation résiduelle : 80 mVcàc" i guess this is not a 50Hz ripple but HF ripple... --- i guess some small cap (100nf, 10pF) and a big Cap (depends on the load, use for example a 100uF and a 2200uF) on the output off the PSU would reduce that "ripple"... * maybe that caps are not enough and you need some more filtering (coil, resistor, lpf...) but i would start with some caps... the connections in your 2nd picture are not necessery - i guess (dont seeing the whole picture, but i think so...) --- so picture 1 is correct. by the way - its only the last LED that flickers? maybe you have to terminate the DO line on the very last LED off the Chain with a 10K resistor to 5V or Ground. else it could be a software problem, when the software loops thru the LEDs, and when it comes to the last one it jumps to the beginning off the chain... try to programm in the ng code one more LED (which in reality not exists) - so you can be sure that this is not a software bug... - but dont ask me about ng-programming --- no glue about that. - mike.

Hello, first of all thank you for your previous answers. I haven't fixed the problem with the pads yet. I'm focusing on another problem for now: with the LED rings. with 16 led ring of 16 led no problem. when I add more, the LEDs flicker. https://youtu.be/HyLkVeFtALw?si=gT09lbCxEwLRmHt8 I read here: http://midibox.org/forums/topic/21095-lre-4x1-breakable-rgb-led-ringrotary-encoder-pcb-bulk-order/?do=findComment&comment=184155 FantomXR had flickering problems, solved with a 10uf capacitor. Should I add a 10uf capacitor at the input of my LED ring cards? (as in the image below) (C129) To understand my configuration see the pdfs: LEDRING: https://drive.google.com/file/d/1XpDQBUE42IqXpXicO--B2gfIoNQDh5ga/view?usp=drive_link “power card”: https://drive.google.com/file/d/1NJ-H-QXD-tl9rU6nbYdEh2Q4jFqjWt6b/view?usp=drive_link I made a PCB that I call a “power card” that I supply with 5v 10 amps. The J2 connector of the "power card" is connected to J4b of core 32. Connector J44 of the first OLED card is connected to J3 of the “power card” Connector J45 of the first OLED card is connected to J4 of the “power card” Connector J44 of the second OLED card is connected to J5 of the “power card” Connector J45 of the second OLED card is connected to J6 of the “power card” etc.. Thank you

Hi all , Was wondering about opening a KiCAD Section in the wiki? For tutorials , midibox libs etc... where should i put it? regards, JK Edit : A Frontpanel designer section could be useful too ?That's a soft that i think most of us use? Maybe create a "Softwares" Section?

the next generation off Triggermatrix, with insights to shematic, the board-files i will not set free... the Pictures from the Boards are for debugging reasons only. where possible, i made pick and place ready boards - to reduce soldering time... at this point the big BLM16x16 board is not pick and place ready. WIKI: Triggermatrix 5 Display-Driver-SMD BLM16x16-V2 Core 4 Discovery Core 4 Disc - Midi Expansion TM5-codeblock TM5 Din Dout Gates TM5 Gate - Breakoutboards TM5 Gate - In TM5-Housing

Hello, I have a rebound problem with the sparkfun pads, do you have an idea how to fix this? Hardware? Software ? Thanks The rest works fine

j2/j17 should do the trick yes.

the ssd1306 oleds i received where 5V tolerant... the ws2812b is also in a range from 3.3-5.3V, dout modules also needs 5V... so your reichelt psu should do the job, and you could power them directly from the psu... but i guess you power them with the ribbon cables from your core... i dont know what Core you will use? if you use the WCORE from midiphy, then you may ran into some problems when using a external 5V PSU, see this topic: https://forum.midiphy.com/d/151-wcore-non-usb-powerd-but-still-use-as-usb-device/5 also if you are unlucky you will get walking lines on your SSD1306 screens... then it best it would to buffer each D0 D1 Clock... Pins, which are done for example in this module: http://wiki.midibox.org/doku.php?id=displaydriver-smd a plus is then you can then use more then 8 screens!

Hi Long time I don't play with NG config, but It should be possible with enc_mode=Inc41_Dec3F , combined with fwd to 2 sender and conditional filtering, something like if_equal=0x41 send note A, and if_equal=0x3F send note B ?

@ pusbutton: the LEDs in the shematic are REVERSED for example look into: http://ucapps.de/mbhp/mbhp_doutx4_32leds.pdf but in the board itself the Silkscreen for the Diode is painted correct - so if somebody just solder the PCB without looking into the Shematic - all is good, when someone look into the shematic he may be confused a bit. what type off Switch are using here > type it on the silkscreen - like you did on the Potentiometerboard. because: i see in the footprint its a le mec > then there are different types, with different Switch contacts - like you see here: 5GTH9 + 5ETH9 will work, while 5GTH9 with inbuilt LED will not work off course... i for me find the correct switch matching to your PCBs Footprint-Pinout - a bit hard... so label the type.... the rest off the PCB looks ok.

@ potentiometer: looking good, but labeling the Holes is not necessery (i think) :

maybe by removing the pull-Hi resistor off the HC165 Circuit, and using a Inverter on its inputs for example: https://www.mouser.at/ProductDetail/Nexperia/74HCT1G14GW-Q100H?qs=SKY61BOKKY4Uv%2FaFLc8SsQ%3D%3D https://www.mouser.at/datasheet/2/916/74HC_HCT1G14_Q100-2937184.pdf (just a example maybe there are better parts for this porpuse, and i dont know how hard to solder this one is) that would reverse Lo and Hi, and you could use this bloddy 3 LEDs ( where i think thats not a good idea, the Encoder is expensive - and not really a standard part...) but for that quick idea i would prototype that first (order a inverter, order a Encoder, make wires without pcb) ... specially iff any pull hi or pull low resistors are needet elsewhere, i guess you need a 10K pull-low resistor (to ground) on pin 3 off your Encoder then: HC165 > Inverter > Pull-Low + Pin3 since i have not much time these times, and you have plenty off modules what module i should check next? i just had a look on your 4x2 Enc RGB SW Led ring Rgb render here... and i am not 100% sure that the inbuilt RGB LEDs that enlighten the Encodersshaft dont shine on the LED-Ring and make them hard too read (maybe need some lightshielding)... by the way hard too read, those Alps Knobs are a bit big for that small Ledring - can you still see the LEDs when looking from a angle that is not 100% from top?

hei i stripped down the BLM-Project (so it cant be cloned with out weeks off routing U B ;) ) BLM-how-to.zip and i wrote some explaination... basicly i made a Grid with a center-cross - so a single button-LED-Fottprint can be placed correct to the Rubber-Button-Grid... you may have to set a a new "zero position off the Kicad Grid" to this crosses when you place the Button-LED-Fottprint on them... this Grid also have the Holes for the PCB which are needet to hold the rubber in Position.. maybe you find a "Flip-Chip" Variant for your RGB-LED... it would be better... you should not place it on the TOP side off the PCB... because it will illuminate the Neightbar-Button-Rubbers... The Hole in the PCB where the LEDs shine thru, act as a Light-Shield... I too have to draw a RGB-LED board (for a other Task, to illuminate a Frontpanel...), since i dont have expierence with that RGB-LEDs... this will take a while... if you found a solution i would copy it from you.... At Kicad 7... didnt know there is a stable out... good to know... will update too (else i cant check your projects)

at RGB-Leds > i dont know, how many you will use? which coremodule you will use? is it eurorackbased > and eurorack powerd? Which RGB-LED you will use - and what is the Voltage it needs? and so on.... i looked into your files.... some notices: @BP: dont connect the mountingholes to ground, or any other potential, best would be to make a keep out-area (sperrfläche) arround it, like i did for example here: http://wiki.midibox.org/lib/exe/fetch.php?w=600&tok=f96292&media=phatline:daw-btn-3d-b.jpg since you can plastic and/or metall standoffs to mount that pcb to the panel, you would need at least 6mm or more keepout-area.... background: you want to avoid groundloops over the frontpanel, and the risk of a electrical shock is less.... The LEDs in the diagram are connected false, the tip off the arrow should always be connected to the ground. (you should turn them 180°) which buttons do you want to use? please check the pinout off them... for me it happend that i did not connect the correct pins, so double check this.... why you made those cuts on the 4 corners? its better to make them rectangular - background: if you panelize the pcb, you have to draw a V-Grove line, the machine can only Grove in 90°, the idea, is to put 2 off this boards on one 100x100 PCB so you can save money on FAB.... way more oversight you have if you use a Groundsymbol... instead off paint Lines to a ground inside your shematic... look into "control" to see what i mean...also it makes it easyier to work with groundplanes, since this needs a NET... @Control: please open this file:Control.zip the same like above, and, you dont need that vias next to PIN 2 off the switches > Pin 2 is a via itself.... - same for Pin 1 off P2, the Problem it did not fill without your Vias: because you dont used a Ground-Net.... Pin1 - which is labeld as VDD (+) was connect to all your buttons and the pot (which is a Encoder)... normaly we connect them to ground..... VSS is ground.... so i exchanged the whole thing.... i dont know iff this is then still correct in your big picture- wiring diagram.... how ever thats the way i would make it - at least iff the Pin-Labels off the IDC Connectors are right... you should put the 4 mounting holes in the shematic, so you dont loose them when updating the PCB Also dont label your Encoder with Pot or RV >>> this is not a Potentiometer... that confused me until i realized this is a Encoder.... also the google-Drive files are a bit corrupt - the footprints where not assigned to the Shematic symbols...... when you save the project and upload it somewhere - zip it inside Kicad with "Projektdaten archivieren" - dont know the french word for it. -please overwork also your BP like/or simular like i did.... @Fader 1/2.... please open this file: Fad_2.zip shematic: also better use GND and VDD Nets.... more oversight! if you dont use a Pin off your IDC-Header (P5), then "x" them out with the blue "x" on the right side off your editor.... For what are those outer Mounting holes? they are too near to the Faders...make the pcb bigger so there is space for a Spacer/standoff, or use only the 4 inner mounting holes... which i think is enough.... again better 90° corners.... fill out your Shematics "Circuit-Field" right down - dont know the englisch or french word for "Plankopf" ... by the way you can design your own "Plankopf", so you dont see there thing like "KiCAD E.D.,A kicad 6.0.10......" keep out for mounting holes again... (see PB) dont make outher planes on VDD(+) ... mostly there can happen problems when mounting the thing to a panels, better use Ground-Planes... When looking on your FAders Footprint, and on the DAtasheet for the RA6020F then i am not sure iff the pinout is correct (the datasheet is bullshit...) but i guess you imported the Symbol and Footprint from mouser or something....then i guess its oky.... also use the design-rule check function (in a shematic and PCB-Editor) i did not looked in the other kicad-projects... but i guess its the same - a bit overwork needet..

Yes, absolutely. Please PM me for details, ideally including your location so I can give you a shipping quote if interested.

Yes you usually need a metallized knob to make the touch detection usable !!!

Looks very nice and neat .I didnt know you are so busy with things . (Thank you for your support). I was working a lot with max/msp and m4l too. Its a lot of fun , but it takes a lot of time as well :) . Enjoy and keep up this amazing work.

So good and inspiring to see what you are creating! Good luck with your further progress, I‘m watching you :-)!

could be... you can try to filter out some psu-spikes by soldering a 100nf (maybe add also a 1uF or higher for too more stabilize the psu as addition) cap between + and - on the potis legs (most off the time these are the outer 2 legs off the trio)

@poti; if the shaft's center is in the end on the same position - so same frontpanel holes can be used.... and: when soldering the thing: first mount the pcbs with loose potis on the frontpanel then solder it (and document this in the "how too build"... @ - : use thermal destress traces (cant remember the kicad word) when using groundplanes, so you can desolder the the poti much easier.

PM sent!

this will take a while - look into the forum in 5 weeks or so. i need the PCB to make a new version off Triggermatrix (http://wiki.midibox.org/doku.php?id=triggermatrix4) the Frontpanel is not a generic MatrixController thing - it has 17 Displays, 8 Faders, some rotarys and buttons, the Software for this is not a normal Midicontroller-code (aka Midibox NG) - its my own creation a sequencer based on MIOS. - but if i not make a shematic mistake, the pcb should be usable like the orginal BLM16*16+X in other Midibox Projects.

Oh, wow, I totally missed that! Thank you!!! I wasted an entire day rummaging around and didn't manage to see that :) Just in case others run across this: You want 4SPI configuration, not IIC like I have in the pic. The number of screens you have must match the configuration you set in the bootloader, otherwise you get noise, and won't be able to write to all the lines/columns Also easy to miss, but for the 1306 RES connection, you need to wire it up like this (again, connections on your 1306 PCB): GND -> 10uf cap -> 1k resistor -> VCC. Once done, RES will be tied to where the cap and resistor meet (like this) It wasn't clear to me how to actually use the bootloader for the STMF4 board, but it's essentially: Plugin your board as you normally do Open MIOS Studio Click Browse and choose the mios32_bootloader app (download here) Click Start. If it won't complete, try unpluging/pluging the board and trying again Unplug/plugin the board In the MIDI IN and MIDI OUT sections whatever app you had prior to all of this might be listed, but it doesn't actually exist (and it shouldn't). That's why you now see the error "No response...". The new app, MIOS32, took its place and you need to refresh to see it. Click Application -> Rescan MIDI Devices Click Understood in the pop-up (this will make your old app disappear, and the MIOS32 app show up) Change MIDI IN and MIDI OUT to MIOS32 Enter these one by one into the input box: (send a command to MIOS32 application). Keep in mind lcd_num_x must match the number you have chained: set lcd_type GLCD_SSD1306 set lcd_num_x 1 set lcd_num_y 1 set lcd_width 128 set lcd_height 64 store Yah. Bootloader is done. Time to restore your app in MIOS Studio: Click Browse and choose whatever app you want, like midibox_ng Click Start. Like the bootloader, if it won't complete, try unpluging/pluging the board and trying again Unplug/plugin the board Now for some test display data. Lets set some values for your SSD1306 OLED's in MIOS Studio: Click on Tools -> MIOS32 File Browser Click Create File Create some name like LCD.NGC Click Update Click on the file you just created Click Edit Text and add the following test example: RESET_HW LCD "%C" LCD "@(1:1:1)A23456789012345678901234567890" LCD "@(1:1:2)B23456789012345678901234567890" LCD "@(1:1:3)C23456789012345678901234567890" LCD "@(1:1:4)D23456789012345678901234567890" LCD "@(1:1:5)E23456789012345678901234567890" LCD "@(1:1:6)F23456789012345678901234567890" LCD "@(1:1:7)G23456789012345678901234567890" LCD "@(1:1:8)H23456789012345678901234567890" Click Save You should now have 8 rows and 21 columns of text. If you need to flip it 180 degrees, you can redo the steps above and add set lcd_type GLCD_SSD1306_ROTATED before you store.

@Hawkeye Thank you for the thoughtful replies. It is easy to think of future wishes and add ons but at the same time forget about how it would effect everything else. I love the Seq4+, very little I would change! And the fact that I can get into the code and try things myself is pretty amazing. That alone is a "feature" that very few seq's can boast. @flyweightIf I was looking for more humanized recordings I'd use the longer tracks with higher divisions OR the humanizer feature! Also, you can specify your own shuffle parameters, you may find something that gives you YOUR feel.. if you could analyze how your beats groove, you may just be able to create that groove as a template and there ya go. May be worth digging into. At the same time, your experience and learning from building the Seq is not lost if you sell it. You lost time, yes. I'm sure if you put it on the market it will sell pretty quickly. ~Steve

Hi, Check or add the correct path in environment: Page 14 in the pdf Best Bruno

Hi guys, I don't know the best for your project but I can explain what I did for the OLRE16. First is the MASK, it's black PMMA. Both sides are milled. I let some space between the leds on the pcb to keep some matters between the leds housing. Led size is 1.5x2mm On the other side(front side) there's some stripes which will fit inside the translucent PMMA, they will block the light between the leds, between the rings and between the rings and the oleds. . Note: the olre16 top pcb(ring) has no component on the top except the leds and the oleds. In blue are the back leds housing. In Red there are the holes. In Yellow, some stripes to block the light on the front, those stripes will fit inside the back of the translucent PMMA. The second part is the 'WINDOW', in translucent white PMMA, it's a LED special one, the same I used for the beat led window of the Seqv4+. The back part will fit inside the MASK, in other word the base of the WINDOW will receive the MASK's stripes, of course the WINDOW's pipes are in front of the MASK's holes. Then the Aluminum front panel comes to finish blocking the light and the pipes of the WINDOW will fit inside the panel, flush the surface. When they are coupled When coupled , assembled the thickness without the pipes height(front panel thickness) doesn't exceed 2.5mm Voilà! I don't know if it will help you and It's surely an "over-engineered" thing but this is the only solution I found, and it works. Best regards Bruno

Hey people, thanks to @TK.! It's working great. Anyway I had still some flickering on the LEDs. As I stated above I left away the caps ... and this was the reason. I know have added a 10uF on the input and on the output-connector of the LED-rings and the flickering is completely eliminated! Great!! So, one core can handle a total of 10 LED (10*36=360) rings....

Hey people, in this thread I'll post time after time updates about my latest keyboard build. Also I'll use this thread to publish eagle-PCB-layout-files and schematics. But please be patient. Uploading and documenting all that stuff is highly time consuming and it's right before christmas. So far everything works great, but the work under the hood was really time consuming because I used a lot of modules... some available from Tim, some I did on my own. I think modules are great if you need high flexibility... and all the modules are working perfectly. But if it comes down to save space and wiring, modules are a mess. Anyway... here we go: So I was tired using a laptop, a soundcard, tons of cables and all that stuff on stage. So I thought: What if I put the computer into the keyboard? It was quite successful. I used an Mini-ITX mainboard from Gigabyte, an i5-3570k (I'd go with a better i7 if I hadn't had that i5 before) with a low profile cooler. The mainboard is equipped with 16GB of RAM. Also I integrated two Samsung SSDs with 500GB each. The whole thing is powered through a Seasonic SS250U power supply. As soundcard I use a PCIe card from RME HDSPe AiO. Because this only has two audio in/outs, I also bought two expansion-board that gives me another four in and outs. The first two analog-outs are going through a self-made DI-box with high quality LEHLE-transformer... absolutely great stuff. This DI-box features also a 20dB PAD and a GND-lift. Let's hand over to the MIDIbox-side: I use two cores. One of them only takes care of the keyboard scanning. It was very important to me to not make a compromise on this. This core is connected via MIDI-out to the MIDI-In of the other core. Both cores are STM32F4 based. I used my own PCBs for that. @TK. Is it a problem if I publish those schematics and layouts for the core? I know that the official core is not published yet to cover the costs for PCB production and development. The PCB I developed only contains the connectors I need: it has J8/9, J19, J10A, J11 and J30 (as far as I remember... don't have it right in front of me at the moment). I tried to get a smaller footprint of the whole PCB. It also features a MicroSD-card slot instead of the SD-card-slot in the official PCB. My keyboard has nine analog faders build in... they are not motorized. I don't need that for now as they are much more expensive and also take more space. Also they are more difficult to wire up and connect. At first I did some tests with the AINSER8. But after a while I gave AINSER64 a try with the result, that it has less jitter than the AINSER8. The faders are a lot more quiet than with AINSER8. As I needed more than 16 analog inputs this was needed anyway. I power the AINSER64 through the core and the core receives it's power directly from the seasonic-power supply and NOT via USB. I needed some LEDs to visualize the status of my faders. A long long time ago I wanted to start another LED-fader-project but never finished it. So I had a lot of those LED-bars laying around... I took them and putted them into the board... works and feels great! On the next revision I'd try to use one big PCB for all 9 LED-bars to safe wiring and time for mounting. Now I used two 10pin IDC connectors (with only 8 pins of each are connected to the LED-bars = 16 LEDs). I did some mistakes when assembling the LED-PCBs... now sometimes some LEDs don't work... anyway... I can live with that for now. @TK. How about the WS2812 or APA102-LEDs? Do you think it's worth using them as LED-rings? I'm not sure what the status is and if they are supported in that way by MIDIbox. Would be a great alternative but they take a lot more space than 0603 SMD LEDs of course. The LED-bars are connected to small modules I did based on @novski designs. Those small modules are equipped with one or two DIN / DOUT modules. They work great and the advantage is, that I can stack them directly on the pinheader of the PCB... no cables needed! A bit hotglue and you are ready to go. I also have 8 encoders on each side of the keyboard. The right side is not connected yet... not sure if I do need so many encoders ;-) Of course they are also equipped with LED-rings. While the LED-bars where assembled by factory (I think I used SEEED) the encoder-rings came blank... so it took me a looooooong time adding 128 0805 SMD LEDs to all PCBs... at this time I had not have my reflow-oven... with this one that might be an easy task :-) The encoders (and the switches of the encoders) are connected to a 4xDIN board from novski. I'm not sure if this board really works well. Sometimes if I set debug on, MIOS lists tons of EVENT_BUTTONS. I'll need to investigate that. Maybe it has something to do with RC1 / RC2 lines. Underneath the faders I have a set of 2x8 buttons. I'm not really happy with them. I did the caps by myself and this was a really shitty work... next time I will use tact-switches that already come with caps f.e. TC011 like I did in the 1x8 button-row right in front of the player / underneath the display. For the buttons I designed a DIO-breakout-board. This breakout-board splits the matrix configuration of the 2x8 pinheader of the DIO-module to a more usable 2x5pin header-configuration with the row on pin 1 and the switch-lines on 3-10. With this way it's very easy to connect tons of buttons to a MIDIbox. . Same for the LEDs of the buttons. I used a DOUT-module with ULN2803 as LED driver (btw. I drive all LEDs with ULN2803 and do NOT use a resistor before or after the LEDs. As those LED-lines are scanned, a limiting resistor doesn't seem to be necessary). That's mainly it... the keyboard has two MIDI I/Os on the back as well as four pedal connectors for two switches and two expression pedals. The touchscreen in the middle is a 10" capacitive screen... that works awesome!! That's the story for now... like I said I'll try to keep this thread alive and add the PCB layouts and schematics later on. Thanks for reading!! Best, Chris

Hi everyone ! I experienced the same problem, and The Ancient One's solution works perfectly for me. I changed the 220R resistors to 68R for R21 and R22. Now the 9090 detects the signal without any issue. Thank you a lot Michael ! Théo