Whole note rests misplace following notes
I'm not top posting.
% Inserting a whole-note rest misplaces notes after it, regardless of the time
signature used. Examples are given of what happens with groups of quavers
following a whole note rest in 3/4, 4/4 and 5/4 time.
\version 2.10.5
\paper{ ragged-right=##t }
{
\relative c' {
\time 3/4 r1 c8[c c c c c c] \bar ||
\time 4/4 r1 c8[c c c] c[ c c c] \bar ||
\time 5/4 r1 c8[c c c c c c c c c]
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Whole note rests misplace following notes
Sandy wrote: I'm not top posting. % Inserting a whole-note rest misplaces notes after it, regardless of the time signature used. Examples are given of what happens with groups of quavers following a whole note rest in 3/4, 4/4 and 5/4 time. Not a bug; r1 means 4 quarter beats of rest. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Whole note rests misplace following notes
Graham Percival gpermus at gmail.com writes: Not a bug; r1 means 4 quarter beats of rest. I filed this as a bug as, in my experience, entering a whole note in any software (I use Noteworthy Composer) will give the regular four beats, but a whole note /rest/ will fill an entire bar's complement of beats, regardless of time signature. I've scrutinised several relevant sections in the documentation, and I I can't seem to locate any references to inserting a rest that fills up all the beats in a bar. In the piece that I'm writing (in 3/4) I've had to use either three quarter-note rests, or a dotted half-note rest -- both look wrong. Sandy ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Whole note rests misplace following notes
Graham Percival gpermus at gmail.com writes: Not a bug; r1 means 4 quarter beats of rest. I must not have scrutinised /quite/ enough -- I missed the section on multi-measure rests -- it's not really obvious that a whole bar rest is considered multi-measured. -.- Apologies for the erroneousness of my original post. Sandy ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
‹ Prev 7 of 7
segfault,
programming error bad number of pages
X-BeenThere: bug-lilypond@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LilyPond Bug Reports bug-lilypond.gnu.org
List-Unsubscribe: http://lists.gnu.org/mailman/listinfo/bug-lilypond,
mailto:[EMAIL PROTECTED]
List-Archive: http://lists.gnu.org/pipermail/bug-lilypond
List-Post: mailto:bug-lilypond@gnu.org
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://lists.gnu.org/mailman/listinfo/bug-lilypond,
mailto:[EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
I'm not top posting.
segmentation fault, programming error: tried to space systems on a bad number of
pages.
%%% BEGIN %%%
\version 2.11.27
% segfault for REP= 27 to 30, 35 to 50
REP=27
\paper {
ragged-right = ##f
ragged-bottom = ##t
ragged-last-bottom = ##t
}
music = \relative c'' {
\repeat unfold \REP {c4 d e f }
}
\score {
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
\new Staff \music
}
%%% END %%%
lilypond score.ly
GNU LilyPond 2.11.27
Processing `score.ly'
Parsing...
Interpreting music... [8][16][24]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 3 or 4 pages...
programming error: tried to space systems on a bad number of pages
continuing, cross fingers
Segmentation fault
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: ‹ Prev 7 of 7
Joe, can you have a look at this? 2007/7/3, Toine Schreurs [EMAIL PROTECTED]: segfault, programming error bad number of pages -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: volta brackets displayed on all staves
Graham Percival [EMAIL PROTECTED] writes: Thanks, this issue has already been reported, http://code.google.com/p/lilypond/issues/detail?id=366can=2q=volta BTW, is anyone working on this? It's a show-stopper for any score with volta brackets. And it's a regression and should probably be classified as such. It's worked in any version I've used (from 1.4 or something) until (and including) 2.11.23... -- Arvid ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
completion_heads_engraver is missing a note
I'm not top posting.
when rendering the example below the whole note is not rendered correctly:
it appears as a dotted 1/4 in the first measure: that is ok.
it appears as a 1/2 in the second measure: there is missing an 1/8.
ie. the second measure contains a 1/2, an 1/8 and 1/4 ie. an 1/8 is missing.
\version 2.10.25
\new Voice \with {
\remove Note_heads_engraver
\consists Completion_heads_engraver
}
{
c'2 d'8 c'1
d'8 c'4
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*)
Hi, Do we need to worry about this programming error? I was interpreting a gigantic inputfile (65,000 lines) but the output turned out just fine. Here's the complete output of the run (which is quite clean except for the one error), running under OS X: GNU LilyPond 2.11.26 Processing `1083.ly' Parsing... Interpreting music... [8][16][24][32][40][48][56] Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 55 or 56 pages... Drawing systems... Layout output to `1083.ps'... Converting to `1083.pdf'... programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*) continuing, cross fingers I can send over the complete inputfile if anyone cares; but, again, the output is just fine. -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*)
No, we don't worry about programming errors. We produce too many false warning messages to bother fixing them. If it's a first-time bug reporter, I'll faithfully add it to the tracker, but they get the lowest priority. Cheers, - Graham Trevor Bača wrote: Hi, Do we need to worry about this programming error? I was interpreting a gigantic inputfile (65,000 lines) but the output turned out just fine. Here's the complete output of the run (which is quite clean except for the one error), running under OS X: GNU LilyPond 2.11.26 Processing `1083.ly' Parsing... Interpreting music... [8][16][24][32][40][48][56] Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 55 or 56 pages... Drawing systems... Layout output to `1083.ps'... Converting to `1083.pdf'... programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*) continuing, cross fingers I can send over the complete inputfile if anyone cares; but, again, the output is just fine. ___ 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
Issue 366 in lilypond: repeat brackets printed over all staves
Issue 366: repeat brackets printed over all staves http://code.google.com/p/lilypond/issues/detail?id=366 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Labels: -Priority-Medium Priority-Regression -- 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: volta brackets displayed on all staves
[EMAIL PROTECTED] wrote: Graham Percival [EMAIL PROTECTED] writes: Thanks, this issue has already been reported, http://code.google.com/p/lilypond/issues/detail?id=366can=2q=volta BTW, is anyone working on this? It's a show-stopper for any score with volta brackets. According to http://code.google.com/p/lilypond/issues/list we have 118 unresolved bugs. There's actually another 40 or so that were marked duplicate or invalid, and are waiting for me to verify or re-open those bugs. I'm certain that some of those will be re-opened. Patches appreciated. And it's a regression and should probably be classified as such. It's worked in any version I've used (from 1.4 or something) until (and including) 2.11.23.. Ok, fair enough. I've modified the report. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in documentation
Thanks for the report. This actually isn't a typo; the word is correctly typed as \tweak, but somewhere along the processing chain, \t is interpreted as a tab. I'm investigating the issue. http://code.google.com/p/lilypond/issues/detail?id=389 Cheers, - Graham Christian Herzberg wrote: Hi, There's a typo mistake on page: http://lilypond.org/doc/v2.11/input/lsr/other/collated-files The important option is called tweak instead of weak. There's a t missing. The last textline: With the weak command, you can tune every grob directly. Here are some examples of available tweaks. should be: With the tweak command, you can tune every grob directly. Here are some examples of available tweaks. Thanks a lot for Lilypond and the great online documentation Regards Christian ___ 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
Re: Whole note rests misplace following notes
Sandy wrote: Graham Percival gpermus at gmail.com writes: Not a bug; r1 means 4 quarter beats of rest. I must not have scrutinised /quite/ enough -- I missed the section on multi-measure rests -- it's not really obvious that a whole bar rest is considered multi-measured. -.- Can you suggest any improvements so that the documentation is better? http://lilypond.org/web/devel/participating/documentation-adding Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 389 in lilypond: \t -gt; tab in LSR snippets
Issue 389: \t -gt; tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 New issue report by gpermus: input/lsr/other/using* doesn't happen in the manual texinfo, but apparently something's different about the collated-files texinfo. (devel team: I'm handling this bug) Issue attributes: Status: Accepted Owner: gpermus Labels: Type-Defect Priority-Low -- 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 390 in lilypond: Completion_heads_engraver loses an eighth
Issue 390: Completion_heads_engraver loses an eighth
http://code.google.com/p/lilypond/issues/detail?id=390
New issue report by gpermus:
% there should be an extra eighth note in the second bar
% even more confusing, when we add a Staff of 8th notes,
% the missing eighth note appears -- in the wrong place!
% possibly a duplicate of 330
\version quot;2.10.25quot;
\layout { \context{ \Voice
\remove quot;Note_heads_engraverquot;
\consists quot;Completion_heads_engraverquot;
}}
\new Staff {
c'2 d'8 c'1
d'8 c'4
}
lt;lt;
\new Staff {
c'2 d'8 c'1
d'8 c'4
}
\new Staff \relative c' {
c8 c c c c c c c
c8 c c c c c c c
}
gt;gt;
Attachments:
foo.png 13.4 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Medium
--
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: completion_heads_engraver is missing a note
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=390
Cheers,
- Graham
andy wrote:
I'm not top posting.
when rendering the example below the whole note is not rendered correctly:
it appears as a dotted 1/4 in the first measure: that is ok.
it appears as a 1/2 in the second measure: there is missing an 1/8.
ie. the second measure contains a 1/2, an 1/8 and 1/4 ie. an 1/8 is missing.
\version 2.10.25
\new Voice \with {
\remove Note_heads_engraver
\consists Completion_heads_engraver
}
{
c'2 d'8 c'1
d'8 c'4
}
___
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
Re: programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*)
I wouldn't bother; output is fine. On 7/3/07, Graham Percival [EMAIL PROTECTED] wrote: No, we don't worry about programming errors. We produce too many false warning messages to bother fixing them. If it's a first-time bug reporter, I'll faithfully add it to the tracker, but they get the lowest priority. Cheers, - Graham Trevor Bača wrote: Hi, Do we need to worry about this programming error? I was interpreting a gigantic inputfile (65,000 lines) but the output turned out just fine. Here's the complete output of the run (which is quite clean except for the one error), running under OS X: GNU LilyPond 2.11.26 Processing `1083.ly' Parsing... Interpreting music... [8][16][24][32][40][48][56] Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 55 or 56 pages... Drawing systems... Layout output to `1083.ps'... Converting to `1083.pdf'... programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*) continuing, cross fingers I can send over the complete inputfile if anyone cares; but, again, the output is just fine. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
