Re: 2/4 not before repeat line in incipit to `Repeats'
Hans Aberg writes: > On 9 Aug 2009, at 21:07, Bernard Hurley wrote: > >>> The default rule is really that one should have a minimum number of >>> time >>> signatures if the repeat construct is expanded*). >> >> That seems like a reasonable rule. But a quick look through my pile >> of full scores (Mostly Dover reprints of 18th and 19th century >> scores) shows it is not always obeyed. I.e. there are plenty of >> cases where the a time signature change is placed after the repeat >> sign even though there is no time change inside the repeat. > > If one of the alternatives of the repeat end in a meter different from > what it begins, then if the expansion rule should prevail, there must > be a time signature at the beginning of the repeat after the |:. And > it is then unnecessary to have one extra before. > > But not even that was followed in the Bulgarian score. It looks like: > 11/16 |: ... | 8/16 ... | 11/16 ... | 8/16 ... :| > >> As a composer/arranger I always put the time change after the repeat >> sign! Rather than talk about the right or wrong way of doing this it >> should just be a user's option. > > > I figure LilyPond might support what people want to typeset. Yes, if I tell it explicitly. Short of that, Lilypond should pick the way that best reflects the art of typesetting, as recognized by the developers. It is ok if there are manual overrides (and style overrides for a whole document), but the defaults should not require music typesetting taste and choices. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2/4 not before repeat line in incipit to `Repeats'
On 9 Aug 2009, at 21:07, Bernard Hurley wrote: The default rule is really that one should have a minimum number of time signatures if the repeat construct is expanded*). That seems like a reasonable rule. But a quick look through my pile of full scores (Mostly Dover reprints of 18th and 19th century scores) shows it is not always obeyed. I.e. there are plenty of cases where the a time signature change is placed after the repeat sign even though there is no time change inside the repeat. If one of the alternatives of the repeat end in a meter different from what it begins, then if the expansion rule should prevail, there must be a time signature at the beginning of the repeat after the |:. And it is then unnecessary to have one extra before. But not even that was followed in the Bulgarian score. It looks like: 11/16 |: ... | 8/16 ... | 11/16 ... | 8/16 ... :| As a composer/arranger I always put the time change after the repeat sign! Rather than talk about the right or wrong way of doing this it should just be a user's option. I figure LilyPond might support what people want to typeset. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2/4 not before repeat line in incipit to `Repeats'
On Sat, Aug 08, 2009 at 11:41:37PM +0200, Hans Aberg wrote: > On 8 Aug 2009, at 15:41, Valentin Villenave wrote: > >> Er, I got lost in the discussion. Could you sum up your report >> (possibly with a picture)? > > The default rule is really that one should have a minimum number of time > signatures if the repeat construct is expanded*). That seems like a reasonable rule. But a quick look through my pile of full scores (Mostly Dover reprints of 18th and 19th century scores) shows it is not always obeyed. I.e. there are plenty of cases where the a time signature change is placed after the repeat sign even though there is no time change inside the repeat. As a composer/arranger I always put the time change after the repeat sign! Rather than talk about the right or wrong way of doing this it should just be a user's option. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ghostscript fails with special characters in filename
> Could you run lilypond --verbose on your file? That still looks a lot like #811; perhaps I'll Fwd it to the ghostscript team. The relevant section of the output of lilypond --verbose (2.12.2): Converting to `./ő.pdf'... Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="./?\x91.pdf" -c .setpdfwrite -f "?\x91.ps"'...GPL Ghostscript SVN PRE-RELEASE 8.57 (2007-03-15) Copyright (C) 2007 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. WARNING: /Unicode /Decoding resource is not accessible but it is useful for generating ToUnicode CMap. Error: /undefinedfilename in (\305\\x91.ps) Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push Dictionary stack: --dict:1087/1123(ro)(G)-- --dict:0/20(G)-- --dict:69/200(L)-- Current allocation mode is local Last OS error: 2 GPL Ghostscript SVN PRE-RELEASE 8.57: Unrecoverable error, exit code 1 `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="./?\x91.pdf" -c .setpdfwrite -f "?\x91.ps"' failed (256) error: failed files: "?\x91.ly" It seems the invocation is incorrect, since issuing the command gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="./ő.pdf" -c .setpdfwrite -f "ő.ps" succeeds... > Maybe 8.70 final has fixed the problem, as I can't seem to reproduce this problem here... Unfortunately I couldn't build it on OS X, and MacPorts doesn't have the most recent version. I'll try it on Linux soon. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange word `oud' in world.itely
> See: http://en.wikipedia.org/wiki/Oud Ahh, thanks. I've reformulated the sentence, together with a small explanation. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange word `oud' in world.itely
See: http://en.wikipedia.org/wiki/Oud Thomas > > In the end of `world.itely' there is the following sentence: > > Oud methods by the following authors, contain examples of mainly > Turkish and Arabic compositions. > > Obviously, the word `oud' is wrong. However, I can't see the right > one... > > > Werner > > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Strange word `oud' in world.itely
In the end of `world.itely' there is the following sentence: Oud methods by the following authors, contain examples of mainly Turkish and Arabic compositions. Obviously, the word `oud' is wrong. However, I can't see the right one... Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2/4 not before repeat line in incipit to `Repeats'
On 9 Aug 2009, at 11:13, Valentin Villenave wrote: 2009/8/8 David Kastrup : Meter changes should occur before an opening repeat sign. If there is a closing one immediately adjacently, opening and closing one are placed apart, and the meter change in between. Thanks, I've added it as http://code.google.com/p/lilypond/issues/detail?id=828 This is not correct if meter change takes place within the repeats, as I indicated. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2/4 not before repeat line in incipit to `Repeats'
2009/8/8 David Kastrup : > Meter changes should occur before an opening repeat sign. If there is a > closing one immediately adjacently, opening and closing one are placed > apart, and the meter change in between. Thanks, I've added it as http://code.google.com/p/lilypond/issues/detail?id=828 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 786 in lilypond: Extenders in lyrics stop prematurely if a single underscore is found
Updates: Labels: Lyrics Comment #4 on issue 786 by v.villenave: Extenders in lyrics stop prematurely if a single underscore is found http://code.google.com/p/lilypond/issues/detail?id=786 Another report by Werner: " The attached image is taken from notation.pdf, subsection `Multiple notes to one syllable'; the bug IMHO is that the extender line is too short. Similar to `-- _ _' (with respect to the length), `__ _ _ _' should construct an extender line up to the `e'. " Attachments: melisma.png 12.1 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 828 in lilypond: New time signatures should be inserted between repeat barlines
Status: Accepted Owner: v.villenave CC: lemzwerg Labels: Type-Enhancement Priority-Medium New issue 828 by v.villenave: New time signatures should be inserted between repeat barlines http://code.google.com/p/lilypond/issues/detail?id=828 Meter changes should occur before an opening repeat sign. If there is a closing one immediately adjacently, opening and closing one are placed apart, and the meter change in between (see attached example). Please refer to the complete discussion on http://lists.gnu.org/archive/html/bug-lilypond/2009-08/msg00059.html Attachments: brahms.png 17.4 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lyric extender problem
>> The attached image is taken from notation.pdf, subsection `Multiple >> notes to one syllable'; the bug IMHO is that the extender line is >> too short. Similar to `-- _ _' (with respect to the length), `__ _ >> _ _' should construct an extender line up to the `e'. > > Could this be related to #786 or #800? It looks like #786 indeed. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lyric extender problem
2009/8/8 Werner LEMBERG : > The attached image is taken from notation.pdf, subsection `Multiple > notes to one syllable'; the bug IMHO is that the extender line is too > short. Similar to `-- _ _' (with respect to the length), `__ _ _ _' > should construct an extender line up to the `e'. Could this be related to #786 or #800? Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: typo
2009/8/9 Werner LEMBERG : > -denoted by a cicle with a vertical line going from the center upwards > +denoted by a circle with a vertical line going from the center upwards Thanks, corrected. Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
typo
--- snap-pizzicato-bartok-pizzicato.ly 2009-08-06 07:16:24.0 +0200 +++ snap-pizzicato-bartok-pizzicato.ly.new 2009-08-09 09:47:59.0 +0200 @@ -35,7 +35,7 @@ A snap-pizzicato (also known as \"Bartok pizzicato\") is a \"strong pizzicato where the string is plucked vertically by snapping and rebounds off the fingerboard of the instrument\" (Wikipedia). It is -denoted by a cicle with a vertical line going from the center upwards +denoted by a circle with a vertical line going from the center upwards outside the circle. " doctitle = "Snap-pizzicato (\"Bartok pizzicato\")" ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
