latigid on

No worries! You can use the old one for practice!

Damn, any gory photos? Upside-down or rotated around the wrong way? I might be able to ship you a replacement wCore board (no USB).

MIDI is actually a current loop, not really anything to do with voltages.

Aren't the GPIOs used as LED outputs already at 3v3? So where are the current values derived from? E.g. the Res/SD board specifies 1k for each in the BOM tool. ? don't really like giving resistor values for LED brightness, as it's always so subjective. Starting values, sure, but you can always season to taste.

Again, I'm not sure where? Twelve ports maybe? Anyway, no bother . The SEQ v4(+) natively has four USB busses, each with the normal 16 channels. IIRC the USB-MIDI communication protocol is even enhanced over DIN-MIDI. So if your interest is interfacing with softsynths and hardware, that comes right out of the box! Of course for the synth dungeons, something like Bruno's moar16 would come in handy, but the "basic" SEQ can already do quite a lot.

Thanks for the kind feedback! I'm not sure where you got 16 MIDI outs from? The max here would be 8 (MIDI8 + I2C). There is a possibility to use a second I2C with a firmware hack to gain 4 more, but for space and latency versions this wasn't included in the standard build. @Antichambre is developing a 16x16 MIDI expander but again it doesn't fit in here. Another thing I can think of is hosting a GM5x5x5 or the newer chip, but it's also not in the plan nor complete at the moment. Of course you have 8 outputs with 16 channels each, so plenty to work with using the 16 sequencer tracks. What was your plan with 16 MIDI outs? CV/gate would go through the DB-25 line driver. On the other end AOUT/DOUT modules are required (under development, some solutions already available).

I haven't tested the 5E, indeed it might be too short. The LED mounting is also different and has no "groove" to fit inside. But hey, feel free to try if you like the aesthetics better.

Sure, might even be better. I left the panel spacing up to Adrian and have never seen the case in person yet :) Not sure if 5G fits? But there's 16mm: https://www.mouser.com/ProductDetail/MEC-Switches/1S11-160?qs=XkGcM6gst%2F8pgAO1bVm7xw%3D%3D

Would need to talk to Adrian about different colours. It might be that the cases are ordered in low (e.g. <10) quantity, which could leave some room for customisation. Very likely we'll keep a stock of "standard" colours though. It's too much to keep too many options, especially considering we start with two possible variants (LH/RH). I'll leave you to check the datasheets if you're interested. The switches have 1mm travel. 19.0mm caps are suggested. https://www.apem.com/int/multimec-3f-287.html http://www.produktinfo.conrad.com/datenblaetter/700000-724999/705191-da-01-en-MULTIMEC_KAPPE.pdf

Lefty version from Adrian. The Apem caps on the JA board are too tall, they should all be the same height. The blue will be lighter in real life.

It's one of those things where you just try and see how it goes. There are other tricks too, such as RC termination or buffering. All need extra circuitry, so give it a go first.

It's not a priority at the moment, sorry.

For some reason I thought you only had an LED matrix. So you actually need: +5V 0V (ground) SO (serial out) SI (serial in) SC (serial clock) RC1 (latch for DOUT) RC2 (latch for DIN) You could probably get away with sharing RC1 and RC2, but still that's more pins than a DIN5 has. Or did you power it somehow differently?

Did you consider using the DIN8? Or do you plan to build a 16x16+X BLM?

The three pins were intended to connect a MIDI port if the BLM wasn't used, hence using the standard MIDI pins and leaving the others floating. This was before the days of MIDIO/MIDI8. So it should work to connect, but yull deffo need some bodge wirez maaate! Keep in mind that the SRIO signal can get dicey if the cables are long. This would be the idea of the Line Drivers.

With regards to naming, I don't want to take the v4+ moniker away from Wilba ones. Although it's true that the version I've designed (with input from Adrian/TK./Peter/Bruno) does represent UI improvements and thus fits with the "plus" suffix as put forward by TK., any F4 Core version will run the V4+ firmware. TK. created the hardware config "antilog," which is the name I use for PCB projects. You could also call it the latigid version, the andy version, whatever :).

To differentiate from Peter's TPD (or your PCBs), the one built into the SEQ is called the "activity" matrix. This means we have a JA board (jog wheel + activity). When he has time, Peter intends to add some extra features to display. Not sure if they'll necessarily be compatible with the TPD. Well spotted! The colour choices on the smaller ones are quite limited, although it goes with the "clean" look of the UI. I'll probably put the matrix schem up at some point. For now, I'm happy to supply it to those who have purchased the PCBs (just Peter, Adrian H, TK. and lazy beta testers :P ) or to those who need troubleshooting advice.

Ah, you want clock input. Not currently supported in the SEQ I think, but I believe it was done in the CV app? You can ask in the general firmware updates thread.

Correct. Clocks and start/stop (i.e. "DIN sync") are sent over the DOUT shift registers. JCI is not used. Check in the CV config:

I don't understand the question sorry. Gates and clocks go through the DOUT (SRIO) chain.

If you use a non-standard protocol, consider using a different connector e.g. a DIN5 240/270 degree pin pattern.

I would say it's about 50:50 SMT/THT. I also don't like squinting too much, and that's why the resistor/cap packages are 1206, the transistors and diodes SOT-23 and the chips SOIC or larger. This can be easily done without a microscope. I recommend to use a decent light source and check the joints after. People who've never done SMT before are often surprised by how much quicker it can be than through hole. No lead forming, no flipping the board (if you bottom solder), no parts sliding away and no lead clipping. Tack one pad, align the part, finish the other pads. Use a low angle with the iron and heat the pad rather than the pin. Even use a solder sucker to remove excess solder.

At the moment that's the idea, yes. What customisation did you have in mind?

Recommended at least for building/debugging. No worries, just solder onto a piece of perfboard etc.

Hello, welcome to the forum. I'll try to answer your questions. Check out the "Step A" build. This is the minimum control surface http://www.ucapps.de/midibox_sid_cs.html You can even use a DB plug for a bankstick: http://www.ucapps.de/mbhp_bankstick.html Cross-reference the list of compatible devices with the PICs you intend to use. Note that only the initial bootloader flash is done with a programmer, thereafter over MIDI/MIOS Studio. For two SIDs only? Probably okay. Step A CS should work.