summaryrefslogtreecommitdiff
path: root/LiberationMono-Bold.ttf
diff options
context:
space:
mode:
authorAndrew Cady <d@jerkface.net>2015-12-07 02:00:55 -0500
committerAndrew Cady <d@jerkface.net>2015-12-07 02:00:55 -0500
commit7ed747a7db1fcfd5f57524b7ffca45a527951d9f (patch)
tree40149d947e0d5ab85415c0f9ece280fa261fa432 /LiberationMono-Bold.ttf
parent990bae4f495b80e38a2ca1c3f2fbe6482c2e6cc8 (diff)
Output replayed recordings to MIDI channel 1
The live output goes to channel 0. This prevents the two from messing with each other (cancelling each others' notes). Simply hard-coding channel 1 is a bad idea long-term, though. We actually could have input from more than one channel (if we pump a midi file into the program with "aplaymidi", for example). I suppose we want to map the entire range of channels based on the input source in order to prevent input sources from affecting one another. Then generated playback could be considered a separate input source. All of this will have to be done in order to deal with simultaneous looping of multiple tracks, anyway.
Diffstat (limited to 'LiberationMono-Bold.ttf')
0 files changed, 0 insertions, 0 deletions