(1) Several thoughts on this most worthwhile thread. Think of the command stations/P2500 in terms of separate but interrelated systems, especially (as concerns the original question): --(a) the sequencer --(b) the synth engine --(c) the controllers I could be wrong, but the synth engine system [which include "patchcords"] cannot output midi data. The sequencer and controllers can. Even though each preset has settings for arps and riffs, those are really sequencing functions. When you use the knobs (for example) to send CC data to external gear, you are using the knobs as controllers. The synth engine and the sequencer can also do stuff with the knobs, but that doesn't mean that the patchcords can be used to take synth engine functionality and generate a stream of midi data. I agree with the original post--it is wishful thinking to be able to use an lfo [synth engine function] to generate midi data, such as CCs. The thought is so compelling, I would love to find a work around to trick the CS/P2500 into doing that. (2) Don't forget, you can embed sysex commands (with external software) into patterns. As I wrote previously, you can--for example--embed sysex commands that change the CC assignments for all 16 knobs. One application is that if you create a song by chaining together patterns and manipulate the knobs on the fly in a performance, each section [pattern] can have the knobs do different things.
Message
Re: patchcord destinations
2005-09-09 by steve_the_composer
Attachments
- No local attachments were found for this message.