|
|
|
|
|
by darraghenright
1310 days ago
|
|
Interesting article with some very useful information. This reminds me of a perennial, and mostly untouched back-burner project of mine :) I've owned a Roland MC-202 Microcomposer for many years. It's an early '80s analogue monosynth with a two track sequencer that's a LOT of fun, but is infamously awkward to program. It allows you to dump sequences in an audio-based format to tape and load them back. Rather than endure the slog of programming sequences directly on the machine, I've often dreamed of a workflow where you could program sequences in a UI, and then encode that information to generate an audio file that you could then load into the MC-202. For example, it'd be relatively straightforward to create a web-based UI using HTML5 audio to create a simple sequence builder that you could then dump to some text/cell format. The challenging part would be using this information to encode the final audio file. I've done a little research, and I read the MC-202 uses an encoding format that's similar to, but not the same as, the Kansas City Standard. One day I'll dive into this (hopefully it won't be too complex for me!) |
|