About *alsa-midi-instrument-map* about cl-patterns HOT 3 CLOSED

This is a good idea! It'd definitely make the instrument map feature more flexible and useful. I'll see about implementing it soon, thanks!

from cl-patterns.

Hmm, actually, thinking further, it seems like there might not even be any need to keep this specific to MIDI backends; it could probably be even more useful if implemented as a generalized event processing mechanism run as the last step of pattern processing, before events are sent to the clock. I'm thinking there could be a global list like *event-processing-functions* or similar, containing functions that are applied to the events yielded by patterns. The list could default to (list 'convert-midi-mapped-instruments-to-midi-parameters) for convenience, so that users don't have to manually implement MIDI instrument mapping themselves.

from cl-patterns.

With commit 49f8dba I added instrument-mapping to map :instruments to arbitrary event parameters, and *post-pattern-output-processors* to process pattern outputs with arbitrary functions.

I'm planning on reworking backends in the future as well so that each enabled backend can have its own list of processor functions that will run on all events the backend receives too.

from cl-patterns.