latigid on

You could write an NGR script to address LEDs in sequence: https://github.com/midibox/mios32/tree/master/apps/controllers/midibox_ng_v1/cfg/midiphy It is a very hacky script and could be much nicer with a few for loops. You can use the MIOS terminal command set dout all 1 (or 0 if the cathodes sink into 595 inputs). It really depends on your setup, whether you have transistors, whether you drive LEDs in a matrix etc. You will need a better +5V PSU though as whatever MCU you are using might drop out of regulation with too much draw.

Not sure if it is supported as I think it expects a Standard Control Surface (SCS). To change the "LCD configuration" you first must upload the bootloader app and choose the appropriate LCD type (including OLEDS :) )

Hi! @k2z3k0 does a lot of that though I don't know the exact workflow used http://midibox.org/forums/search/?q=k2z3k0&type=forums_topic&nodes=18 SEQ uses the concept of loopback tracks, so you can control a track with another one. Best, Andy

Well done, Gratulation!

@TK. makes sense! I tried to make the wCore etc. compatible with the DISCO so no surprises!

Some people noticed that the LoopA can get stuck in booloader hold mode. As a potential remedy, install resistors R101 and R102. If you don't have the exact values it doesn't really matter. JPA0 should be left unjumpered except if you want to enforce bootloader hold. With the resistors installed the state of PA0 is properly defined rather than floating. If you don't notice the issue, no need to change it! The BOM is updated to reflect this.

Congrats and thanks for the kind testimonial! Totally right about SMT not being the devil, well as long as it's conceived for hand soldering in the design. :) #36 is your serial number

I'm very glad; that's a great resolution! :)

Awesome job and thanks for the testing and feedback! Let us know how it goes with the light|shield flex :)

I don't think a custom naming is possible and every synth will likely use different names. But how about editing the respective label file? https://github.com/midibox/mios32/blob/master/apps/sequencers/midibox_seq_v4/core/seq_cc_labels.c Then recompile the app with the change implemented.

Nice idea! Are they 0402 parts? Were they soldered by hand or preassembled?

I think we could use a beta tester :) Peter will be in contact!

Very well done and thanks for the beers!?! Hope you can enjoy one yourself -- during the next jam? Best, Andy

http://midibox.org/forums/topic/21457-wts-seq-control-surface-pcb/

Great tip! Not sure exactly what temperature you need for heatshrink (maybe around 100°C is fine), but if you use a low airflow rate and just bring the nozzle as close as needs be you should be good.

What other CAD software experience do you have? If it's all new and you'd rather not learn, Protocase is still okay. With the possible costs of e.g. a Fusion subscription and a few design iterations of the first attempts you do, probably that $340 is pretty good. If you want to develop your skills and do more case work in the future, definitely go down that route. Another option would be to design the panel as a PCB, have it fabbed and find a matching case for it e.g. the PT-10. Yet another option is to design an acrylic case that can be laser-cut in 2D and snaps together.

For what project do you need an enclosure? Protocase is awesome and very reasonably priced for one-offs where they take care of everything for you. A great company to work with. The other way would be to machine your own but this requires tools and skills on your part

Awesome job! Almost forgot your serial number #34

Yep, the case hardware screws won't work perfectly with the Mouser part. I would personally recommend to use the 4-40 MF standoffs that come with the DB-25 socket as case mounts and keep the black screws for another day. Then you can properly mate a DB-25 cable. If you prefer the look of the >>panhead<< screws, feel free to mangle the thread in the DB-25, but you need nuts on the inside to keep it tight.

Building an RH Building an LH But Peter shows you the differences here. So if I understand the assembly video you can change the location of the longer cable to suit your case variant.

Nice that you got the FLUXTEST working! Cables should be almost the same lengths for RH/LH, as they have to travel from the left to the right for both cases' cases. :)

Funky!

These statements contradict each other. Can you get a state where the LoopA is running and sending MIDI? Or do you mean "boot the LoopA and then afterwards connect the MIDI outs"? Curious whether you installed the scratch washer and hence grounded the case -- or not? Sometimes these sorts of peculiar things come back to grounding. We can't of course rule out hardware issues (e.g. we know of one dodgy Waveshare Core) or your build process e.g. stressed or overheated pins, shorts etc. Maybe there is flux residue on the MIDI sockets? Worth another look there.

Hard to say if that's a hardware issue or software. IMO best practice would be to make all connections before applying power and avoid hot-swapping... The LoopA shouldn't care what its outputs are connected to. For your case #4 above, what is connected to your MI1/2? Do you have a MIDI loop? MIDI outs have the 0V connected, so you should consider how the other parts are powered: maybe a so-called "ground loop"?