Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Updates: Labels: -Patch-needs_work Patch-new Comment #4 on issue 2349 by mts...@gmail.com: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349 Removes transparents in TabVoice and replaces with false stencil http://codereview.appspot.com/5694066 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2319 in lilypond: Patch: WebCG: remove projects from HelpUs
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_31 Comment #9 on issue 2319 by janek.li...@gmail.com: Patch: WebCG: remove projects from HelpUs http://code.google.com/p/lilypond/issues/detail?id=2319 pushed as ee5f21d7ed3b985913194699aa1d412e4bced562 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [Klaus Foehl] Re: Lilypond, Mac and 10.4
David Kastrup d...@gnu.org wrote in message news:87aa461m89@fencepost.gnu.org... -- David Kastrup So it appears that something happened to the x86 build for Mac OSX 10.4 between 15.28 and 15.30. Does this seem accurate. Colin - I think you now have a computer running this OS? Can you check this report and confirm you get the same problems? -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [Klaus Foehl] Re: Lilypond, Mac and 10.4
David Kastrup d...@gnu.org wrote in message news:87aa461m89@fencepost.gnu.org... -- David Kastrup Actually, I believe this is http://code.google.com/p/lilypond/issues/detail?id=2338 -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2354 in lilypond: Breath mark collides with natural sign
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2354 by philehol...@gmail.com: Breath mark collides with natural
sign
http://code.google.com/p/lilypond/issues/detail?id=2354
\version 2.15.28
\new Staff
\relative c'' {
\key des \major
c4 bes bes' bes
}
\new Staff
\relative c' {
\clef bass \key des \major
es4 des2 \breathe d4
}
Attachments:
BreathColl.png 3.5 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Breathe mark collides with natural
Frederik Van der Veken frederikvanderve...@gmail.com wrote in message
news:e96c8732-bdbd-4351-b6af-656136fb4...@gmail.com...
% Breathe mark collides with natural
% when using ledger lines
% and more than one stave
\version 2.15.28
\new Staff
\relative c'' {
\key des \major
c4 bes bes' bes
}
\new Staff
\relative c' {
\clef bass \key des \major
es4 des2 \breathe d4
}
Thank you. Reported as
http://code.google.com/p/lilypond/issues/detail?id=2354
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2355 in lilypond: convert-ly uses out-of-tree convertrules.py
Status: Accepted Owner: New issue 2355 by d...@gnu.org: convert-ly uses out-of-tree convertrules.py http://code.google.com/p/lilypond/issues/detail?id=2355 I did make clean make -j3 and got the error chmod 755 out/lilysong /usr/local/tmp/lilypond/scripts/build/out/help2man out/convert-ly out/convert-ly.1 chmod 755 out/lilymidi /usr/local/tmp/lilypond/scripts/build/out/help2man out/lilypond-book out/lilypond-book.1 chmod 755 out/musicxml2ly /usr/local/tmp/lilypond/scripts/build/out/help2man out/abc2ly out/abc2ly.1 Traceback (most recent call last): File out/convert-ly, line 56, in module import convertrules File /usr/local/share/lilypond/2.15.31/python/convertrules.py, line 3323 @rule((2, 15, 31), r\settingsFrom - \context-like ^ SyntaxError: EOL while scanning string literal help2man: can't get `--help' info from out/convert-ly make[1]: *** [out/convert-ly.1] Error 1 make[1]: *** Waiting for unfinished jobs langdefs.py: warning: lilypond-doc gettext domain not found. langdefs.py: warning: lilypond-doc gettext domain not found. make[1]: Leaving directory `/usr/local/tmp/lilypond/scripts' make: *** [all] Error 2 Obviously, this is due to me having installed a bad version of convert-ly previously, but if I do make clean make, no out-of-tree parts of LilyPond should be referenced. Clearly, /usr/local/share/lilypond/2.15.31/python/convertrules.py should never have been read here. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2355 in lilypond: convert-ly uses out-of-tree convertrules.py
Updates: Labels: Type-Build Comment #1 on issue 2355 by d...@gnu.org: convert-ly uses out-of-tree convertrules.py http://code.google.com/p/lilypond/issues/detail?id=2355 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2355 in lilypond: convert-ly uses out-of-tree convertrules.py
Comment #2 on issue 2355 by gra...@percival-music.ca: convert-ly uses out-of-tree convertrules.py http://code.google.com/p/lilypond/issues/detail?id=2355 Indeed. To avoid misunderstandings, the convert-ly script itself can handle being called as part of the build dir; that's in the instructions for the LSR import. This is a question of python calling that module from its PYTHONPATH. I'm guessing that llypond python build dir needs to be prepended to PYTHONPATH, not appended. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: beam slope
2012/2/25 Helge Kruse helge.kruse-nos...@gmx.net:
that looks great. I can control the exact position of the beam.
But default beam slopes are still getting confused by staff changes .
See examples.
The upper beam slope is the reverse of what one expects, when compared
to the lower one.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
attachment: beamsolpe-changestaff-Schumann.pngattachment: beamslope-changestaff-paderewsky.png\version 2.15.25
% Schumann, Op.4, I, 11 last measures
rone = \relative c' {
\time 3/4
r4
\voiceOne
\change Staff = LH
a e8
\change Staff = RH
a b c a d a
}
lone = \relative c {
\voiceTwo
r4 c c,8 d d, e e, f f,
}
\new PianoStaff
\new Staff = RH { \rone }
\new Staff = LH { \clef bass \lone }
% Minueto de I. Paderewski
% Menuet à l' Antique
% From Humoresques de Concert Op.14.
% G. Schirmer, 1899
\version 2.15.25
superior = \relative f {
\time 3/4
R2.
\voiceOne
\change Staff = LH
r16 g,[ b d g b d
\change Staff = RH
g b d g b]
}
inferior = \relative f {
\clef bass
R2.
\voiceTwo
g,,16[ b d g b d g b
\change Staff = RH
d g b d]
}
\score {
\new PianoStaff
\new Staff = RH { \superior }
\new Staff = LH { \inferior }
}
%{
convert-ly (GNU LilyPond) 2.15.31 convert-ly: Procesando «»...
Aplicando la conversión: 2.15.25
%}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2306 in lilypond: add info about Articulations on EventChords to CG
Updates: Labels: Patch-new Comment #1 on issue 2306 by janek.li...@gmail.com: add info about Articulations on EventChords to CG http://code.google.com/p/lilypond/issues/detail?id=2306#c1 CG: a note about articulations on EventChord Explains a bit about iterators. http://codereview.appspot.com/5696080 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2356 in lilypond: Lilypond segfaults
Status: Accepted
Owner:
Labels: Type-Crash Regression
New issue 2356 by philehol...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
There have been 2 reports of lilypond segfaulting on complex scores. Jay
Anderson's report is here:
http://lists.gnu.org/archive/html/bug-lilypond/2011-12/msg01167.html and Hu
Haipeng's is here:
http://old.nabble.com/problem-still-exists-in-the-latest-2.15-version-td33382315.html
Haipeng's complex score crashes LilyPond on my Vista 64-bit machine after
18 seconds compilation time, using about 350Megs memory, which is nowhere
near the machine limit.
Neil suggested adding
\context {
\GrandStaff
\remove Span_bar_stub_engraver
}
to the score's layout block, but that does not fix the crash.
Haipeng says this does not crash on a previous version of Lilypond, but I
can't check this because of new syntax in the version provided.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
NR 4.5.1 v2.15.30 states SeparationItem
In NR 4.5.1 of version 2.15.30 near the end of that paragraph under known issues the non-existent SeparationItem is mentioned. This and the sentence direct above should be deleted. Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 4.5.1 v2.15.30 states SeparationItem
Thomas Morley thomasmorle...@googlemail.com wrote in message news:CABsfGyVbQVd90ESB6_wx2-fvM5Crc0nJQeKH8R3RwQy=vuw...@mail.gmail.com... In NR 4.5.1 of version 2.15.30 near the end of that paragraph under known issues the non-existent SeparationItem is mentioned. This and the sentence direct above should be deleted. Cheers, Harm I've searched for it and can't find it in my downloaded PDF version. You sure it's the NR? -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Windows scheme sandbox
Hi! While translating the Scheme tutorial, I tried in a Windows (XP sp3) virtual machine where I've installed 2.15.30 to access the sandbox. Here is the output: ===8=== C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly Parsing... C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:2:1: Error: Guile signaled an error for the expression beginning here # use-modules ice-9 readline readline is not provided in this Guile installation C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:3:1: Error: Guile signaled an error for the expression beginning here # activate-readline Unbound variable: activate readline guile ===8=== FWIW, GUILE_LOAD_PATH and path are as requested. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2320 in lilypond: Patch: CG: add information about Regtest Checking Project
Updates: Labels: Patch-new Comment #11 on issue 2320 by janek.li...@gmail.com: Patch: CG: add information about Regtest Checking Project http://code.google.com/p/lilypond/issues/detail?id=2320#c11 CG: add information about Regtest Checking Project Phil Holmes wrote a nice web app that allows people to review regtests, one at a time. We can ask users for help and thus painlessly do a full regtest check. This commit contains brief instructions how to use the app. http://codereview.appspot.com/5669047 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 4.5.1 v2.15.30 states SeparationItem
2012/2/26 Phil Holmes m...@philholmes.net: I've searched for it and can't find it in my downloaded PDF version. You sure it's the NR? Yes, I found it here: http://lilypond.org/doc/v2.15/Documentation/notation/horizontal-spacing-overview and in the pdf. (Both in the german translation.) Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2357 in lilypond: Patch: web: rephrase bugreports section
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2357 by janek.li...@gmail.com: Patch: web: rephrase bugreports section http://code.google.com/p/lilypond/issues/detail?id=2357 web: rephrase bugreports section According to Graham's favorite rule (quot;perfection is attained when there's nothing more to deletequot;) i'm rephrasing bugreports section hoping to make it even more brief and straightforward for all users. http://codereview.appspot.com/5698070 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
bug with tupletFullLength
The following code gives a log warning:
\version 2.15.30
\new Staff {
\set tupletFullLength = ##t
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c' c' }
\mark 123456789
}
log:
warning: Found infinity or nan in output. Substituting 0.0
If the mark contains less than 8 characters the warning disappears.
Same, when commenting in \override TupletBracket #'full-length-to-extent = ##f
Compiles without warning using 2.12.3
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2358 in lilypond: Patch: Allow music with layout instructions in output definitions.
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2358 by d...@gnu.org: Patch: Allow music with layout instructions
in output definitions.
http://code.google.com/p/lilypond/issues/detail?id=2358
Allow music with layout instructions in output definitions.
This allows things like
\layout { \accidentalStyle modern }
or
\midi { \tempo 4 = 80 }
to work as intended.
http://codereview.appspot.com/5701049
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 4.5.1 v2.15.30 states SeparationItem
Thomas Morley thomasmorle...@googlemail.com wrote in message news:CABsfGyUNP8p=l95a3tfimvyvkwygvwua_fa_6dg9fgz+of8...@mail.gmail.com... 2012/2/26 Phil Holmes m...@philholmes.net: I've searched for it and can't find it in my downloaded PDF version. You sure it's the NR? Yes, I found it here: http://lilypond.org/doc/v2.15/Documentation/notation/horizontal-spacing-overview and in the pdf. (Both in the german translation.) Cheers, Harm === Only in the German translation - which is why I didn't find it. Added as http://code.google.com/p/lilypond/issues/detail?id=2359 -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2359 in lilypond: German translation uses SeparationItem instead of NonMusicalPaperColumn
Status: Accepted Owner: Labels: Type-Documentation New issue 2359 by philehol...@gmail.com: German translation uses SeparationItem instead of NonMusicalPaperColumn http://code.google.com/p/lilypond/issues/detail?id=2359 In the German NR we have: \once \override Score.SeparationItem #'padding = #10 I believe it should be: \override Score.NonMusicalPaperColumn #'padding = #10 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Comment #18 on issue 2336 by d...@gnu.org: Patch: Add layout changing command \layout-from for getting context defs from music http://code.google.com/p/lilypond/issues/detail?id=2336 Hi Janek. Check out issue 2358. That would obsolete \layout-from. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2343 in lilypond: Faulty file-naming when outputting multiple \books
Comment #10 on issue 2343 by d...@gnu.org: Faulty file-naming when
outputting multiple \books
http://code.google.com/p/lilypond/issues/detail?id=2343
Ian, the patch does not change the use of output-suffix. As long as you
don't declare a book specific suffix with \bookOutputSuffix (or an
assignment to book-outputsuffix or book-filename in a \paper block), the
old usage will work as before.
Would it make sense to use the paper variables output-suffix and, uh,
output-filename instead? Looks redundant to have book- in the variable
name, and, after all, there seems little wrong with just declaring
\book { \paper { outputsuffix = xxx } }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2359 in lilypond: German translation uses SeparationItem instead of NonMusicalPaperColumn
Comment #1 on issue 2359 by paconet@gmail.com: German translation uses SeparationItem instead of NonMusicalPaperColumn http://code.google.com/p/lilypond/issues/detail?id=2359 All snippets should be identical in translations and English, unless they are marked with @c KEEP LY . In this case we can introduce variations such as translated markups, but lilypond code should still be the same. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2358 in lilypond: Patch: Allow music with layout instructions in output definitions.
Updates: Labels: Patch-review Comment #2 on issue 2358 by d...@gnu.org: Patch: Allow music with layout instructions in output definitions. http://code.google.com/p/lilypond/issues/detail?id=2358#c2 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2357 in lilypond: Patch: web: rephrase bugreports section
Updates: Labels: Patch-review Comment #1 on issue 2357 by d...@gnu.org: Patch: web: rephrase bugreports section http://code.google.com/p/lilypond/issues/detail?id=2357#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2350 in lilypond: Patch: Simplify font building.
Updates: Labels: Patch-needs_work Comment #7 on issue 2350 by d...@gnu.org: Patch: Simplify font building. http://code.google.com/p/lilypond/issues/detail?id=2350#c7 Patchy the autobot says: Relevant lines during failed configure: checking for fontforge python bindings... not found ERROR: Please install required programs: fontforge-python ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Updates: Labels: Patch-review Comment #5 on issue 2349 by d...@gnu.org: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349#c5 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2320 in lilypond: Patch: CG: add information about Regtest Checking Project
Updates: Labels: Patch-review Comment #12 on issue 2320 by d...@gnu.org: Patch: CG: add information about Regtest Checking Project http://code.google.com/p/lilypond/issues/detail?id=2320#c12 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2306 in lilypond: add info about Articulations on EventChords to CG
Updates: Labels: Patch-review Comment #2 on issue 2306 by d...@gnu.org: add info about Articulations on EventChords to CG http://code.google.com/p/lilypond/issues/detail?id=2306#c2 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Comment #6 on issue 2349 by d...@gnu.org: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349 Is it expected that there are no visual regtest changes? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [Klaus Foehl] Re: Lilypond, Mac and 10.4
On Sun, Feb 26, 2012 at 10:12:47AM -, Phil Holmes wrote: So it appears that something happened to the x86 build for Mac OSX 10.4 between 15.28 and 15.30. Does this seem accurate. Colin - I think you now have a computer running this OS? Can you check this report and confirm you get the same problems? I have yet to collect it and set it up. Also, the donated machine is a PPC Mac but it is running 10.4. So, yes, I should be able to start work on it later this week. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [Klaus Foehl] Re: Lilypond, Mac and 10.4
On Sun, Feb 26, 2012 at 10:15:37AM -, Phil Holmes wrote: Actually, I believe this is http://code.google.com/p/lilypond/issues/detail?id=2338 I hear from Christian that the tarball he links to from that tracker is intended to resolve the issue but he was unable to verify it. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: complex-beam
On 2/26/12 2:10 AM, David Bobroff bobr...@centrum.is wrote: I'm looking for a way to achieve this beaming pattern: http://notendur.centrum.is/~bobroff/lily/complex-beam.png Can LilyPond do this? I suspect I'll have to use a combination of subdivideBeams and stemRightBeamCount/stemLeftBeamCount. Is there a known solution? Thanks, David Lilypond does not currently do second-level beam subdivisions. Please add this as a feature request. I have been looking for a good example of what it means to have multiple subdivision. I believe this can be achieved; I will try to get to it in the next couple of weeks. I believe this beaming could be expressed as something like: (subdivide . ((1 . 8) . (1 1 1)) ((1 . 16) . (1 1 1 1 1 1))) although I am not proposing this as the syntax. It might be better to change subdivideBeams from a boolean to a list, where each element of the list would be a beat length at which to subdivide. If that were the case we would achieve the beaming in the sample by \set subdivideBeams = #'((1 . 8) (1 . 16)) Or perhaps \set subdivideBeams = #'((ly:make-moment 1 8) (ly:make-moment 1 16)) Or perhaps even (with David K's new syntax, where we can have duration elements) \set subdivideBeams = #'( 8 16 ) I'll put this in the hopper and think about it. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2358 in lilypond: Patch: Allow music with layout instructions in output definitions.
Updates:
Labels: Patch-new
Comment #3 on issue 2358 by d...@gnu.org: Patch: Allow music with layout
instructions in output definitions.
http://code.google.com/p/lilypond/issues/detail?id=2358#c3
Allow music with layout instructions in output definitions.
This allows things like
\layout { \accidentalStyle modern }
or
\midi { \tempo 4 = 80 }
to work as intended.
http://codereview.appspot.com/5701049
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2343 in lilypond: Faulty file-naming when outputting multiple \books
On 26/02/12 18:51, lilyp...@googlecode.com wrote:
Comment #10 on issue 2343 by d...@gnu.org: Faulty file-naming when
outputting multiple \books
http://code.google.com/p/lilypond/issues/detail?id=2343
Ian, the patch does not change the use of output-suffix. As long
as you don't declare a book specific suffix with \bookOutputSuffix
(or an assignment to book-outputsuffix or book-filename in a \paper
block), the old usage will work as before.
\bookOutputSuffix was intended to replace output-suffix, which was
secret-squirrel Scheme stuff and undocumented. I reckon this could be
deprecated.
Would it make sense to use the paper variables output-suffix and,
uh, output-filename instead? Looks redundant to have book- in
the variable name, and, after all, there seems little wrong with
just declaring \book { \paper { outputsuffix = xxx } }
It's OK you hiding the variables in a paper block for use by
\bookOutputFilename and \bookOutputSuffix so they DTRT as far as the
OP's complaint goes.
However, if we are going to make manipulating the output filename
exposed to the LilyPond UI in a \block declaration like \paper,
\layout or \header then I object violently to using the \paper block.
\bookOutputFilename and \bookOutputSuffix affect all types of file
produced by a LilyPond backend. They have a \book prefix because a
\book block (either explicit or implicit) is the entity which determines
a single back-end output unit from a LilyPond compilation.
If you intend to allow users to declare a block which affects all output
files then we need to bite the design bullet and put this stuff in its
own block, how about
\book {\output { file-suffix=foo } ... }
or
\book {\output { file-name=bar } ... }
?
If we do this, we are far closer to implementing what users requested
in the original Enhancement Request for configurable output file names.
I got side-tracked during the original implementation by thinking of
these (wrongly) as properties. This raises questions of \set vs
\override, and also caused other developers to ask the question of
what these properties had to do with translating source-code to
notation, and of course the answer is absolutely zilch.
My instinct is to deprecate the use of the output-suffix global Scheme
variable, keep the \bookOutputName and \bookOutputSuffix functions,
and implement the new \output block with the new variable names.
Also document that the new \output block variables affect the output
for the current \book block, but if they are absent then the defaults
are applied, i.e. a decimal version number counter is generated for
output-suffix, and the output-name is the basefilename part of current
input file. Document, too that you can't play with these variables
reliably using \set or \override.
WDYT?
BTW, a lot of my test files for this contain use of extended Latin
characters like č þ æ ß ř ů etc. in output file-names and suffixes.
These used to cause problems for some of the back-ends, like GS.
Cheers,
Ian
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Status: Accepted Owner: Labels: Type-Scripts New issue 2360 by colingh...@gmail.com: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 Reported by Jean-Charles Malahieude: http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01077.html http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/33973 I reproduced this with Lilypond 2.15.30 on both Windows XP SP3 and Ubuntu Linux 10.04 LTS i686. Text of original bug report follows: Hi! While translating the Scheme tutorial, I tried in a Windows (XP sp3) virtual machine where I've installed 2.15.30 to access the sandbox. Here is the output: ===8=== C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly Parsing... C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:2:1: Error: Guile signaled an error for the expression beginning here # use-modules ice-9 readline readline is not provided in this Guile installation C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:3:1: Error: Guile signaled an error for the expression beginning here # activate-readline Unbound variable: activate readline guile ===8=== FWIW, GUILE_LOAD_PATH and path are as requested. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2343 in lilypond: Faulty file-naming when outputting multiple \books
Ian Hulin i...@hulin.org.uk writes:
However, if we are going to make manipulating the output filename
exposed to the LilyPond UI in a \block declaration like \paper,
\layout or \header then I object violently to using the \paper block.
\bookOutputFilename and \bookOutputSuffix affect all types of file
produced by a LilyPond backend. They have a \book prefix because a
\book block (either explicit or implicit) is the entity which determines
a single back-end output unit from a LilyPond compilation.
If you intend to allow users to declare a block which affects all output
files then we need to bite the design bullet and put this stuff in its
own block, how about
\book {\output { file-suffix=foo } ... }
or
\book {\output { file-name=bar } ... }
?
I think it would be a rather bad idea to have an output definition
called \output. People would not understand that \layout, \midi, and
\header are output definitions as well.
Books don't _have_ midi or layout blocks. All midi parameters are set
globally. The midi filename still is taken identical with the paper
output filename. Not terribly consistent, but convenient.
The paper block basically is what records book-specific parameters.
My instinct is to deprecate the use of the output-suffix global Scheme
variable, keep the \bookOutputName and \bookOutputSuffix functions,
and implement the new \output block with the new variable names.
Also document that the new \output block variables affect the output
for the current \book block, but if they are absent then the defaults
are applied, i.e. a decimal version number counter is generated for
output-suffix, and the output-name is the basefilename part of current
input file. Document, too that you can't play with these variables
reliably using \set or \override.
I don't get at all why you are talking \set or \override here. Those
are used for manipulating context properties, and the output filenames
never had anything at all to do with contexts as far as I can tell.
you can't play with these variables reliably using \set or \override
is about as meaningful as saying you can't play with these variables
reliably using \clef and \markup.
WDYT?
I am not saying that I consider using \paper variables particularly
beautiful. But since that considers the naming of the PDF files, I
don't consider it unfitting either. It would be a possibility to make
the filenames an integral part of a Book, in which case you would need
separate setter and getter functions. I don't really see the point with
that. The paper block is what we have in the line of book-specific
data. That's reasonably straightforward.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2361 in lilypond: Beams with multiple subdivisions
Status: Accepted Owner: Labels: Type-Enhancement New issue 2361 by colingh...@gmail.com: Beams with multiple subdivisions http://code.google.com/p/lilypond/issues/detail?id=2361 Carl Sorensen posted to request this enhancement to Lilypond: http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01097.html http://article.gmane.org/gmane.comp.gnu.lilypond.general/70226 Original enhancement request follows, including David Bobroff's post to lilypond-user: On 2/26/12 2:10 AM, David Bobroff address@hidden wrote: I'm looking for a way to achieve this beaming pattern: http://notendur.centrum.is/~bobroff/lily/complex-beam.png Can LilyPond do this? I suspect I'll have to use a combination of subdivideBeams and stemRightBeamCount/stemLeftBeamCount. Is there a known solution? Thanks, David Lilypond does not currently do second-level beam subdivisions. Please add this as a feature request. I have been looking for a good example of what it means to have multiple subdivision. I believe this can be achieved; I will try to get to it in the next couple of weeks. I believe this beaming could be expressed as something like: (subdivide . ((1 . 8) . (1 1 1)) ((1 . 16) . (1 1 1 1 1 1))) although I am not proposing this as the syntax. It might be better to change subdivideBeams from a boolean to a list, where each element of the list would be a beat length at which to subdivide. If that were the case we would achieve the beaming in the sample by \set subdivideBeams = #'((1 . 8) (1 . 16)) Or perhaps \set subdivideBeams = #'((ly:make-moment 1 8) (ly:make-moment 1 16)) Or perhaps even (with David K's new syntax, where we can have duration elements) \set subdivideBeams = #'( 8 16 ) I'll put this in the hopper and think about it. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2361 in lilypond: Beams with multiple subdivisions
Comment #1 on issue 2361 by colingh...@gmail.com: Beams with multiple subdivisions http://code.google.com/p/lilypond/issues/detail?id=2361 A typical example provided by David Bobroff Attachments: complex-beam.png 3.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug with tupletFullLength
On Sun, Feb 26, 2012 at 06:36:05PM +0100, Thomas Morley wrote:
The following code gives a log warning:
\version 2.15.30
\new Staff {
\set tupletFullLength = ##t
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c' c' }
\mark 123456789
}
log:
warning: Found infinity or nan in output. Substituting 0.0
If the mark contains less than 8 characters the warning disappears.
Same, when commenting in \override TupletBracket #'full-length-to-extent = ##f
Compiles without warning using 2.12.3
Thanks for the bug report, Thomas, but I'm not sure that I should create an
issue tracker for this.
As far as I can tell you are reporting that 2.15.30 gives a warning and 2.12.3
does not.
Do 2.15.30 and 2.12.3 both give good typeset output?
In that case, I think the difference in behaviour is not a bug, but just a
change in the way the software handles a particular case.
Anyone from bug squad or dev care to comment?
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: complex-beam
On Mon, Feb 27, 2012 at 12:02:14AM +, Carl Sorensen wrote: On 2/26/12 2:10 AM, David Bobroff bobr...@centrum.is wrote: I'm looking for a way to achieve this beaming pattern: http://notendur.centrum.is/~bobroff/lily/complex-beam.png Can LilyPond do this? I suspect I'll have to use a combination of subdivideBeams and stemRightBeamCount/stemLeftBeamCount. Is there a known solution? Thanks, David Lilypond does not currently do second-level beam subdivisions. Please add this as a feature request. I have been looking for a good example of what it means to have multiple subdivision. Created issue tracker 2361 for this enhancement request. http://code.google.com/p/lilypond/issues/detail?id=2361 Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Windows scheme sandbox
On Sun, Feb 26, 2012 at 05:27:28PM +0100, Jean-Charles Malahieude wrote: Hi! While translating the Scheme tutorial, I tried in a Windows (XP sp3) virtual machine where I've installed 2.15.30 to access the sandbox. Here is the output: C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:2:1: Error: Guile signaled an error for the expression beginning here # use-modules ice-9 readline readline is not provided in this Guile installation Thanks for the bug report, Jean-Charles. I have created issue tracker 2360. http://code.google.com/p/lilypond/issues/detail?id=2360 Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug with tupletFullLength
On Mon, Feb 27, 2012 at 01:03:31AM +, Colin Hall wrote: Anyone from bug squad or dev care to comment? It's a bug. Please enter his info verbatim; it's good. As a general rule, false or misleading warning messages _do_ qualify as bugs. - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug with tupletFullLength
Colin Hall colingh...@gmail.com writes:
On Sun, Feb 26, 2012 at 06:36:05PM +0100, Thomas Morley wrote:
The following code gives a log warning:
\version 2.15.30
\new Staff {
\set tupletFullLength = ##t
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c' c' }
\mark 123456789
}
log:
warning: Found infinity or nan in output. Substituting 0.0
If the mark contains less than 8 characters the warning disappears.
Same, when commenting in \override TupletBracket #'full-length-to-extent =
##f
Compiles without warning using 2.12.3
Thanks for the bug report, Thomas, but I'm not sure that I should
create an issue tracker for this.
As far as I can tell you are reporting that 2.15.30 gives a warning
and 2.12.3 does not.
Do 2.15.30 and 2.12.3 both give good typeset output?
In that case, I think the difference in behaviour is not a bug, but
just a change in the way the software handles a particular case.
Anyone from bug squad or dev care to comment?
The warning describes a problem with data generated internally, not a
problem with the user input. This is definitely a bug. It is not
necessarily a regression since it is conceivable that 2.12.3 just did
not diagnose the problematic situation. So it will require some
analysis by a developer to decide whether this is also a regression.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug with tupletFullLength
Graham Percival gra...@percival-music.ca writes: On Mon, Feb 27, 2012 at 01:03:31AM +, Colin Hall wrote: Anyone from bug squad or dev care to comment? It's a bug. Please enter his info verbatim; it's good. As a general rule, false or misleading warning messages _do_ qualify as bugs. The warning is likely neither false or misleading. Except that it probably should not be a warning, but a programming error message. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2358 in lilypond: Patch: Allow music with layout instructions in output definitions.
Updates: Labels: Patch-review Comment #4 on issue 2358 by d...@gnu.org: Patch: Allow music with layout instructions in output definitions. http://code.google.com/p/lilypond/issues/detail?id=2358#c4 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug with tupletFullLength
On Mon, Feb 27, 2012 at 02:12:06AM +0100, David Kastrup wrote:
Colin Hall colingh...@gmail.com writes:
On Sun, Feb 26, 2012 at 06:36:05PM +0100, Thomas Morley wrote:
The following code gives a log warning:
\version 2.15.30
\new Staff {
\set tupletFullLength = ##t
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c' c' }
\mark 123456789
}
log:
warning: Found infinity or nan in output. Substituting 0.0
If the mark contains less than 8 characters the warning disappears.
Same, when commenting in \override TupletBracket #'full-length-to-extent =
##f
Compiles without warning using 2.12.3
Thanks for the bug report, Thomas, but I'm not sure that I should
create an issue tracker for this.
As far as I can tell you are reporting that 2.15.30 gives a warning
and 2.12.3 does not.
Do 2.15.30 and 2.12.3 both give good typeset output?
In that case, I think the difference in behaviour is not a bug, but
just a change in the way the software handles a particular case.
Anyone from bug squad or dev care to comment?
The warning describes a problem with data generated internally, not a
problem with the user input. This is definitely a bug. It is not
necessarily a regression since it is conceivable that 2.12.3 just did
not diagnose the problematic situation. So it will require some
analysis by a developer to decide whether this is also a regression.
Thanks for the prompt feedback, David and Graham. I'll enter it as a bug.
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2362 in lilypond: bug with tupletLengthFull
Status: Accepted
Owner:
Labels: Type-Defect
New issue 2362 by colingh...@gmail.com: bug with tupletLengthFull
http://code.google.com/p/lilypond/issues/detail?id=2362
Reported by Thomas Morley:
http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01081.html
http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/33977
Original post from Thomas follows:
The following code gives a log warning:
\version 2.15.30
\new Staff {
\set tupletFullLength = ##t
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c' c' }
\mark 123456789
}
log:
warning: Found infinity or nan in output. Substituting 0.0
If the mark contains less than 8 characters the warning disappears.
Same, when commenting in \override TupletBracket #'full-length-to-extent =
##f
Compiles without warning using 2.12.3
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug with tupletFullLength
On Mon, Feb 27, 2012 at 02:12:06AM +0100, David Kastrup wrote:
Colin Hall colingh...@gmail.com writes:
On Sun, Feb 26, 2012 at 06:36:05PM +0100, Thomas Morley wrote:
The following code gives a log warning:
\version 2.15.30
\new Staff {
\set tupletFullLength = ##t
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c' c' }
\mark 123456789
}
log:
warning: Found infinity or nan in output. Substituting 0.0
If the mark contains less than 8 characters the warning disappears.
Same, when commenting in \override TupletBracket #'full-length-to-extent =
##f
Compiles without warning using 2.12.3
Thanks for the bug report, Thomas, but I'm not sure that I should
create an issue tracker for this.
As far as I can tell you are reporting that 2.15.30 gives a warning
and 2.12.3 does not.
Do 2.15.30 and 2.12.3 both give good typeset output?
In that case, I think the difference in behaviour is not a bug, but
just a change in the way the software handles a particular case.
Anyone from bug squad or dev care to comment?
The warning describes a problem with data generated internally, not a
problem with the user input. This is definitely a bug. It is not
necessarily a regression since it is conceivable that 2.12.3 just did
not diagnose the problematic situation. So it will require some
analysis by a developer to decide whether this is also a regression.
I've created a new issue tracker 2362 for this bug, Thomas. Thanks again for
the bug report.
http://code.google.com/p/lilypond/issues/detail?id=2362
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2337 in lilypond: Endless Loop
Updates: Labels: -Patch-countdown Patch-push Comment #10 on issue 2337 by colinpkc...@gmail.com: Endless Loop http://code.google.com/p/lilypond/issues/detail?id=2337 Counted down to 20120226, please push ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2343 in lilypond: Faulty file-naming when outputting multiple \books
Updates: Labels: -Patch-countdown Patch-push Comment #11 on issue 2343 by colinpkc...@gmail.com: Faulty file-naming when outputting multiple \books http://code.google.com/p/lilypond/issues/detail?id=2343 Counted down to 20120226, please push. If David wants to rename the variables, then I would guess that a test with Patchy would be sufficient. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2318 in lilypond: kievan notation contexts should not contain time_signature_engraver
Updates: Labels: -Patch-countdown Patch-push Comment #10 on issue 2318 by colinpkc...@gmail.com: kievan notation contexts should not contain time_signature_engraver http://code.google.com/p/lilypond/issues/detail?id=2318 Counted down to 20120226, please push ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2246 in lilypond: beaming in 3/4 - a setting to not beam 3 eights against the beat.
Updates: Labels: -Patch-countdown Patch-push Comment #16 on issue 2246 by colinpkc...@gmail.com: beaming in 3/4 - a setting to not beam 3 eights against the beat. http://code.google.com/p/lilypond/issues/detail?id=2246 Counted down to 20120226, please push ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
convert musicxml from regression testing gives errors
This was created with version 2.15.30 $ musicxml2ly lily-1f180798.xml musicxml2ly: Reading MusicXML from lily-1f180798.xml ... Traceback (most recent call last): File /usr/bin/musicxml2ly, line 2984, in module main() File /usr/bin/musicxml2ly, line 2979, in main voices = convert (filename, options) File /usr/bin/musicxml2ly, line 2880, in convert tree = read_musicxml (filename, options.compressed, options.use_lxml) File /usr/bin/musicxml2ly, line 2871, in read_musicxml return read_xml (io_object, use_lxml) File /usr/bin/musicxml2ly, line 2823, in read_xml doc = minidom.parse(io_object) File /usr/lib64/python2.7/xml/dom/minidom.py, line 1914, in parse return expatbuilder.parse(file) File /usr/lib64/python2.7/xml/dom/expatbuilder.py, line 924, in parse result = builder.parseFile(fp) File /usr/lib64/python2.7/xml/dom/expatbuilder.py, line 207, in parseFile parser.Parse(buffer, 0) xml.parsers.expat.ExpatError: syntax error: line 1, column 49 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2337 in lilypond: Endless Loop
Comment #11 on issue 2337 by benko@gmail.com: Endless Loop http://code.google.com/p/lilypond/issues/detail?id=2337 would someone please push for me? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2337 in lilypond: Endless Loop
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_31 Comment #12 on issue 2337 by d...@gnu.org: Endless Loop http://code.google.com/p/lilypond/issues/detail?id=2337 Pushed as 9ef93a7de18000749c30b541f618379bc292aae0 to staging ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Comment #7 on issue 2349 by mts...@gmail.com: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349 The only test that may change is tablature-full-notation, which would in theory have tighter spacing if there were transparent grobs above the staff that are now stencil-less. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2343 in lilypond: Faulty file-naming when outputting multiple \books
Updates: Status: Fixed_2_15_31 Labels: -Patch-push Fixed_2_15_31 Comment #12 on issue 2343 by d...@gnu.org: Faulty file-naming when outputting multiple \books http://code.google.com/p/lilypond/issues/detail?id=2343 Pushed as c37c6f39d18274ccac28ed42559681ea271cc496 to staging. It fixes an existing bug while keeping the documented interfaces, and I don't see that we have a good redesign of the structure of output definitions and books just lurking around the corner where this would be a nicer fit. As long as \midi is not tied into books at all, the proposed redesigns so far don't really address the underlying design discrepancies. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2318 in lilypond: kievan notation contexts should not contain time_signature_engraver
Comment #11 on issue 2318 by janek.li...@gmail.com: kievan notation contexts should not contain time_signature_engraver http://code.google.com/p/lilypond/issues/detail?id=2318 Aleksandr, please send me final patch created with git format-patch for pushing. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: complex-beam
On Mon, Feb 27, 2012 at 1:02 AM, Carl Sorensen c_soren...@byu.edu wrote:
On 2/26/12 2:10 AM, David Bobroff bobr...@centrum.is wrote:
I'm looking for a way to achieve this beaming pattern:
http://notendur.centrum.is/~bobroff/lily/complex-beam.png
Can LilyPond do this? I suspect I'll have to use a combination of
subdivideBeams and stemRightBeamCount/stemLeftBeamCount. Is there a
known solution?
Lilypond does not currently do second-level beam subdivisions.
Please add this as a feature request. I have been looking for a good
example of what it means to have multiple subdivision.
Meanwhile you can take inspiration from this snippet - maybe it'll help you:
\relative c'' {
c32[ c
%% WARNING: #'beaming is written, so this
%% property can not be shared between objects. Always use
%% \once.
%%
\once \override Stem
#'beaming = #(cons (list 1 2) (list 0 2 4))
c
\once \override Stem
#'beaming = #(cons (list 0 2 4) (list 0 1 4))
c c c]
}
HTH,
Janek
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #1 on issue 2360 by d...@gnu.org: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 On Ubuntu, I have it provided with guile-1.8-libs: /usr/lib/libguilereadline-v-17.so I will try commenting it out in the sandbox and suggest putting it into the ~/.guile config file (where it hopefully will get picked up also by LilyPond). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
