My two modules have been assembled, and are ready for testing. No time to test tonight, but i'm eager to hit it tomorrow.
Top: My current MIDI2CV module, inspired by Jan Ostman's article, and really implemented with Kevin's code. There's no DAC, so there are limitations to accuracy. However, in practice, it is VERY usable.
Bottom right: The 1:5 MIDI Thru. I used 6N138 for the optocoupler and vamped the circuit that Kevin used. Ideally, i should see the same midi data on all 5 of the pin headers at the top. I just bodged a crappy DIN5 connector on there for now, i'll snip that off when it's panel time. I'll use the old MIDI2CV module to test this new 1:5 MIDI Thru.
Bottom Left: My prototype of a Mutable Instruments CVPal with Serial MIDI In. This is not something that is supported by the current CVPal firmware, and i'm not 100% confident that what i want to do is possible. My schematic has removed all of the USB connectivity. Serial MIDI input appears on Pin12 of the ATTiny84. My theory is that the firmware can be modified to use a SoftwareSerial input instead of the USB MIDI library. The most desirable parts of the existing firmware are related to the DAC implementation. Much more hacking ahead.
If the CVPal hax work as planned, i'll build 2 more of that board and tie it all together on a single panel with the MIDI Thru. That should give 6 cv/gate, and render the old MIDI2CV module obsolete ... which just means i can flash a new custom firmware to it and use it as a MIDI drum interface - i think i should be able to get 4 outputs...
If the CVPal can't parse Serial MIDI, i'll have to work on using Kevin's code to interface with the MCP4822.
No comments:
Post a Comment