Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>>
>> I have started working on a rewriting of the way performance works,
>> using the way Paper_score works as a guide. In the same way as
>> Paper_score::process returns a set of systems, I want to make
>> Performance o
[EMAIL PROTECTED] writes:
>
> I have started working on a rewriting of the way performance works,
> using the way Paper_score works as a guide. In the same way as
> Paper_score::process returns a set of systems, I want to make
> Performance output a set of SCM "threads" (or "tracks", or "channe
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>> I am looking at restructuring some of the MIDI code, in the hopes of
>> letting the user have a little more control over the output. I have
>> looked carefully at the way things are currently done, and have a few
>> idea
[EMAIL PROTECTED] writes:
> I am looking at restructuring some of the MIDI code, in the hopes of
> letting the user have a little more control over the output. I have
> looked carefully at the way things are currently done, and have a few
> ideas how to go about doing this. But I have several que
I am looking at restructuring some of the MIDI code, in the hopes of
letting the user have a little more control over the output. I have
looked carefully at the way things are currently done, and have a few
ideas how to go about doing this. But I have several questions first:
1) How tied is the
