David Kastrup wrote Sunday, June 07, 2009 8:22 AM
Jay Anderson writes:
On Sat, Jun 6, 2009 at 4:53 PM, Paul Scott
wrote:
I don't mind having a separate file for the midi output but not
being
able to factor out the common timing and dynamics costs a lot of
input time and makes it a lot h
Jay Anderson wrote:
On Sat, Jun 6, 2009 at 4:53 PM, Paul Scott wrote:
Which is kind of ridiculous if you're writing an ensemble piece with many
(even more than one) voices/parts. How can a midi of a multi-voice work
with any repeats be done?
I was working on a large score and original
Jay Anderson writes:
> On Sat, Jun 6, 2009 at 4:53 PM, Paul Scott wrote:
>
>> I don't mind having a separate file for the midi output but not being
>> able to factor out the common timing and dynamics costs a lot of
>> input time and makes it a lot harder to make sure I haven't dropped a
>> bar s
On Sat, Jun 6, 2009 at 4:53 PM, Paul Scott wrote:
> Which is kind of ridiculous if you're writing an ensemble piece with many
> (even more than one) voices/parts. How can a midi of a multi-voice work
> with any repeats be done?
I was working on a large score and originally kept the repeat
structu
Jay Anderson wrote:
On Sat, Jun 6, 2009 at 3:22 AM, Mark Polesky wrote:
I tried to answer a question on -user but hit a brick wall.
\unfoldRepeats failed to work when the music block was funneled from 2
separate expressions. Can someone explain this to me? Why does the
following code work for
On Sat, Jun 6, 2009 at 3:22 AM, Mark Polesky wrote:
>
> I tried to answer a question on -user but hit a brick wall.
> \unfoldRepeats failed to work when the music block was funneled from 2
> separate expressions. Can someone explain this to me? Why does the
> following code work for voiceA but not
I tried to answer a question on -user but hit a brick wall.
\unfoldRepeats failed to work when the music block was funneled from 2
separate expressions. Can someone explain this to me? Why does the
following code work for voiceA but not for voiceB?
Thanks.
- Mark
