lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: unexpected \unfoldRepeats behavior


From: Paul Scott
Subject: Re: unexpected \unfoldRepeats behavior
Date: Sun, 07 Jun 2009 01:12:16 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081204 Iceape/1.1.14 (Debian-1.1.14-1)

Jay Anderson wrote:
On Sat, Jun 6, 2009 at 4:53 PM, Paul Scott<address@hidden> 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
structure separate from the individual parts and ran into the same
unfold-not-working problem.

I don't need MIDIs that often. Until it is established that this is a bug or the intended result I can get any MIDIs that I need by defining each section for each part as a separate definition that I can assemble as needed for the two different purposes.
I thought about this a bit and decided it
was best just to have the repeats in each part. If you're going to
make a change to the repeat structure you're almost always going to
have to change each part/voice to match. Since this is the case it
makes sense to have the repeat structure in each part.

*If* this is the case. I am most often working with a structure already determined by the composer who is not me. I often create corrected or easier to read ensemble parts or parts for people who don't do the doubling that the original parts call for.
If for nothing
else it makes it easy to find the beginnings and ends of repeats in
each part.

I put bar numbers or other references when needed.
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 somewhere.

Actually I found that having the repeats in each part made it easier
to notice that bars were off. Lilypond throws errors where it thinks
the repeat timing problem is without having to look too much at the
pdf output.

My first pass at most of what I do is to create the global timing section. I then know by the rehearsal marks, etc. whether I have skipped some bars in the input of the music.

I will now reread the documentation on unfoldRepeats to see if I should go any farther with this.

Thanks,

Paul






reply via email to

[Prev in Thread] Current Thread [Next in Thread]