latigid on

Hi George, I'm not 100% on how it all works and could be wrong, but to my knowledge you shouldn't see any MIDI data on the computer from the slaved device plugged into USBA. So my first guess is that you should unplug the computer; you can't (or shouldn't be able to) have the SEQ as both host and slave at the same time. You could then check the SEQ MIDI monitor and route it out a different DIN port. Second thought is that the controller (which ones, so we can consider making a whitelist?) does not initialise properly. Best, Andy

Green and gold! We're keeping track here: http://midibox.org/forums/topic/20885-midiphy-seq-v4/?page=23

Your connections are unclear; do you use the buttons in a matrix or directly connected to DIN pins? For direct connections, one common wire must be connected to 0V (ground), not to a digital input! Switches then trigger when the inputs connect to 0V. Matrix wiring is more complicated and you have to arrange the buttons and LEDs (electrically, not necessarily layout-wise) in grids.

I suppose you mean an AOUT with MAX525? What app are you testing with? The SEQ has a calibration part too. But first, have you adjusted the trim pots to give a good scaling factor? The DAC with external reference outputs a voltage between 0-2.048V with graduations of 1/4096. The gain equation is also on the page.

Nice, and good to know!

Hmm, breaks the MIDI standard a bit :) Sorry about your switches! It must be possible because the BLM can start and stop the SEQ, but that is in a compressed/non-standard format. I don't think it's anything simple and would need some firmware hacking but I guess it's possible.

All that MIOS cares about is the position of the respective register in the chain. You can also run parallel chains of DIN/DOUT (no mixing in this case) by attaching three IDC plugs on the ribbon that attaches to the Core.

You should be able to set the SEQ to slave from a MIDI start stop message? Or maybe I don't understand your question. But no, I don't think it's possible to assign a CC as a start/stop, at least not without recoding/hacking something.

@mfk your skills will be just fine! All of the parts are huge by SMT standards and several builders have completed even with no prior DIY experience. And, as Peter says, there's actually a fair amount of THT there too :)

Wow, was very nicely written and explains everything well. Thanks for the heads-up!

:-)

Well done #28!

No waiting list! There might be a teaser soon but it's hard to guess timelines at the moment. Hopefully there'll be something to tease shortly. Best, Andy

Awesome work, thanks for the update! Your serial number is waiting :)

Did you change the device ID to 1 when flashing the .hex? You should be able to communicate with the Core that way. Or how did you upload the .hex file?

What is the device ID printed on the PIC? Maybe the two both have the same ID and hence communication only works with one of them? You can try to disconnect the known-working one and see if you get input. If you need to change the IDs there's an app (.hex) for that that you upload with MIOS terminal. Thereafter reload your program.

Nice!

Could be a buffer size thing but you should start a new topic, try to e.g. record the output with MIOS Studio (set up the router) or through a utility like MIDIOX or so. Try also to delay the transmission rate?

Here you go! Please don't short the (typically unpopulated) J3-6 headers for (+5V supply buss). The next run of PCBs will have the polyfuse added, thanks Adam for the research and suggestion!

Hi Manu, Great that you're nearly done! Thanks a lot for looking through the other troubleshooting ideas first. For this one: Does it mean that you removed the cables from the OLED end, and the known-good J15 port and cable also showed the same behaviour with the "right-hand" OLED? Normally I would expect that the cable had a missing connector or shorted cable. It might be worth building a brand-new cable if you have the connectors and ribbon handy. You can also check the Core module IC2 and resolder the pins. Do you notice any different behaviour if you just connect one OLED at a time? Also, how are you powering up? You might try a phone charger USB or hub with more power available. Maybe a cable got loose? There was one IDC8 connector that didn't fit well. Otherwise, I'm not sure what to suggest if everything else is running. Did you check with the correct _L/_R NGC and the correct SEQ HWCFG? Best, Andy

Not 100% sure how the drum track architecture works, but as a hack could you configure your drum instruments (notes) one octave higher then transpose the whole track back down one octave? My guess is that the MIDIbox relies on that empty note data for something e.g. a placeholder.

The midiphy A1 expander sets an offset for this reason. You can also transpose your SEQ track...

You could add feature requests to http://midibox.org/forums/topic/13137-midibox-seq-v4-release-feedback/?page=61 I'm not sure if MIDI channel makes sense because it's part of the track events/setup. But you can ask! I think mute/solo was on the list for a while. For button assignments, you can freely choose any function you see in the HWCFG file. I don't know if you can reassign the encoder presses, or if that's generally a good idea vs. leaving them reserved as accelerators.

Maybe the AOUT isn't calibrated or the Moog uses something different than 1 V/oct? I remember something like that for the Voyager or similar. What AOUT setup are you using?

Congrats #27! Looks like a groovy colour-scheme and thanks for the kind feedback! EDIT and beer (?) !