Re: separating music and guitar instructions
On Wed 22 Sep 2010, 00:38 Vicente Solsona wrote:
this doesn't work
c4\3
It does! This avoids a string number indication in standard
notation and leads to a correct fret number in tablature. See
Default tablatures in the Notation Reference.
and this does:
c\34
This basically has the same effect but a string number indication
is added in standard notation.
Hi!
Sorry for delay. I am still brave enough to add this to the tracker but not
sure that this issue is clear enough, sorry.
a-ha, ok!
I don't use tablatures, so I didn't realize that, sorry for my confusion.
Then it makes sense to me.
But the original issue remains though:
should the following example (and the larger one in my first post)
to be expected to work? if yes (and I'm not doing something wrong),
then there's a bug.
%
music = { c4 c }
fingers = {s4\2 s4-\rightHandFinger #2}
(Missed space after #2 causes Expecting number or string, found
#unspecified error)
\score {
\new Staff \context Voice = A \music
\context Voice = A \fingers
}
%
I am affraid, if this is _a question_ (should or should not), it's still not
a valid issue report?
(I believe i will not forget about this issue, it's marked with ugly red text
on black background in my mailer,-)
Ok, let me try:
%-8
Summary: fingering indications are not displayed if entered with no angle
braces.
Type: Defect
Priority: Medium
music = { c4 c }
fingers = { s4\2 s4-\rightHandFinger #2 }
\score {
\new Staff \context Voice = A \music
\context Voice = A \fingers
}
%-8
How do you think -- is this correct enough? May be this should be enhancement
request (with different summary)?
Is it a valid report at all?
Excuse me, my knowlegde is weak in this area. And i feel like i have no time
to digg.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autobeaming in cadenza
On Mon 27 Sep 2010, 17:49 Keith E OHara wrote:
% Automatic beaming does not work through the length of a cadenza
%
% This issue occurs, differently in the details, in 2.12.3 and 2.13.34
%
\relative c'' {
\time 4/4 % note: \time x/2 gives the desired result on 2.12.3
\cadenzaOn
\repeat unfold 8 {
c8 c c c % \bar
}
\cadenzaOff
}
Sorry, why do you expect it to work? I wouldn't expect, because of the nature
(my understanding of) of cadenza...
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1279 in lilypond: autobeaming swung triplets in x/8 time
Status: Accepted
Owner:
Labels: Type-Defect Priority-Low
New issue 1279 by brownian.box: autobeaming swung triplets in x/8 time
http://code.google.com/p/lilypond/issues/detail?id=1279
Sorry, my beaming counting arithmetic is weak, so, since there is no any
discussion in the list, posting this AS IS. With original images.
Reported by Keith E OHara,
http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00403.html :
% Automatic beaming does connect the c8 c16 triplet
% in time signatures that have a 1/8-note beat
%
% Time signatures 3/8 and 5/8 show this issue after
% \set Timing.beamExceptions = #'()
%
% 2.12, by contrast, misses these beams when written
% in the corresponding 3/16 time signature
%
\version 2.13.34
\relative c'' {
\time 6/16
c16 c c c8 c16
\time 2/8
\times 2/3 {c16 c c} \times 2/3 {c8 c16}
\scaleDurations #'(2 . 3) {c16 c c c8 c16}
}
Attachments:
test-2.12.3.png 4.5 KB
test-2.13.34.png 4.0 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autobeaming swung triplets in x/8 time
On Mon 27 Sep 2010, 17:49 Keith E OHara wrote:
% Automatic beaming does connect the c8 c16 triplet
% in time signatures that have a 1/8-note beat
%
% Time signatures 3/8 and 5/8 show this issue after
% \set Timing.beamExceptions = #'()
%
% 2.12, by contrast, misses these beams when written
% in the corresponding 3/16 time signature
%
\version 2.13.34
\relative c'' {
\time 6/16
c16 c c c8 c16
\time 2/8
\times 2/3 {c16 c c} \times 2/3 {c8 c16}
\scaleDurations #'(2 . 3) {c16 c c c8 c16}
}
Thanks, added this as 1279:
http://code.google.com/p/lilypond/issues/detail?id=1279
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1280 in lilypond: \displayMusic does not properly quote cons lilypond properties
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1280 by brownian.box: \displayMusic does not properly quote cons
lilypond properties
http://code.google.com/p/lilypond/issues/detail?id=1280
Reported by Jeff Epstein,
http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00317.html :
%-8
I'm trying to get the \displayMusic for the following:
c1^\markup {
\caps \center-align
\override #'(box-padding . 0.5)
\box V. S.}
It results, partially, in this:
(markup
#:line
(#:caps
(#:center-align
(#:override (box-padding . 0.5) (#:box V. S.
Note that
(box-padding . 0.5)
should be
'(box-padding . 0.5)
I believe this is a bug.
Thank you. Let me know if there's anything else I can do.
PS. Thanks to Carl Sorensen for helping me discover this.
%-8
Just for the record.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \displayMusic does not properly quote cons lilypond properties
On Sun 26 Sep 2010, 01:33 Neil Puttock wrote: On 22 September 2010 11:18, Jeff Epstein aliteralmind-lilyp...@yahoo.com wrote: Note that (box-padding . 0.5) should be '(box-padding . 0.5) I believe this is a bug. Thanks for the report. This will be fixed in 2.13.35. Thaks to both of you! Just for the record: http://code.google.com/p/lilypond/issues/detail?id=1280 -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book safe mode
On Wed 22 Sep 2010, 07:52 Julien Rioux wrote:
Dear list,
This is a feature request for a safe mode for lilypond-book.
Thanks, added as 1281:
http://code.google.com/p/lilypond/issues/detail?id=1281
One can run lilypond with the -dsafe switch to avoid a security risk
when compiling .ly files including evil scheme code. There is no
equivalent switch for lilypond-book, and using --process leads to
errors.
I'll post below a simple example.
Thanks,
Julien
---
$ cat docu.lytex
\documentclass{article}
\begin{document}
\begin{lilypond}
{c' d' e'}
\end{lilypond}
\end{document}
$ lilypond-book --process=lilypond -dsafe -dbackend=eps docu.lytex
lilypond-book (GNU LilyPond) 2.12.3
Reading docu.lytex...
Running latex...This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live
2009/Debian)
restricted \write18 enabled.
entering extended mode
(/tmp/tmpgwVO1K.tex
LaTeX2e 2009/09/24
Babel v3.8l and hyphenation patterns for english, usenglishmax,
dumylang, noh
yphenation, french, basque, ngerman, german, german-x-2009-06-19,
ngerman-x-200
9-06-19, ukenglish, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo))
No file tmpgwVO1K.aux.
textwidth=345.0pt
columnsep=10.0pt
(./tmpgwVO1K.aux) )
No pages of output.
Transcript written on tmpgwVO1K.log.
Dissecting...
Writing snippets...
Processing...
Running lilypond...GNU LilyPond 2.12.3
Processing `/scratch/examples/Test/snippet-map--1168004333.ly'
Parsing...
/scratch/examples/Test/snippet-map--1168004333.ly:4:1: error: GUILE
signaled an error for the expression beginning here
#
(ly:add-file-name-alist '((d6/lily-79fd5fcc.ly . docu.lytex)
Unbound variable: ly:add-file-name-alist
/scratch/examples/Test/snippet-map--1168004333.ly:0: warning: no
\version statement found, please add
\version 2.12.3
for future compatibility
Processing `/scratch/examples/Test/d6/lily-79fd5fcc.ly'
Parsing...
/scratch/examples/Test/d6/lily-79fd5fcc.ly:3:9: error: include files
are not allowed in safe mode
\include
lilypond-book-preamble.ly
/scratch/examples/Test/d6/lily-79fd5fcc.ly:13:3: error: GUILE
signaled an error for the expression beginning here
#
(define dump-extents #t)
Wrong type argument in position 1: #srcprops ((breakpoint . #f)
(line . 40) (column . 7) (filename .
/usr/share/lilypond/2.12.3/ly/music-functions-init.ly))
/scratch/examples/Test/d6/lily-79fd5fcc.ly:17:22: error: GUILE
signaled an error for the expression beginning here
force-assignment = #
Wrong type argument in position 1: #srcprops ((breakpoint . #f)
(line . 40) (column . 7) (filename .
/usr/share/lilypond/2.12.3/ly/music-functions-init.ly))
/scratch/examples/Test/d6/lily-79fd5fcc.ly:18:16: error: GUILE
signaled an error for the expression beginning here
line-width = #
(- line-width (* mm 3.00))
Wrong type argument in position 1: #srcprops ((breakpoint . #f)
(line . 40) (column . 7) (filename .
/usr/share/lilypond/2.12.3/ly/music-functions-init.ly))
/scratch/examples/Test/d6/lily-79fd5fcc.ly:0: warning: no \version
statement found, please add
\version 2.12.3
for future compatibility
Interpreting music...
Preprocessing graphical
objects.../usr/share/lilypond/2.12.3/scm/titling.scm:9:34: In
procedure ly:paper-get-number in expression (ly:paper-get-number
layout (quote line-width)):
/usr/share/lilypond/2.12.3/scm/titling.scm:9:34: Wrong type
(expecting real number): #unspecified
command failed: lilypond -dsafe -dbackend=eps -I
/scratch/examples/Test --formats=eps -deps-box-padding=3.00
-dread-file-list -dno-strip-output-dir
/scratch/examples/Test/snippet-names--1168004333.ly
Child returned 1
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1281 in lilypond: enhancement: lilypond-book safe mode
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 1281 by brownian.box: enhancement: lilypond-book safe mode
http://code.google.com/p/lilypond/issues/detail?id=1281
Reported by Julien Rioux,
http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00318.html :
%-8
Dear list,
This is a feature request for a safe mode for lilypond-book.
One can run lilypond with the -dsafe switch to avoid a security risk when
compiling .ly files including evil scheme code. There is no equivalent
switch for lilypond-book, and using --process leads to errors.
I'll post below a simple example.
Thanks,
Julien
---
$ cat docu.lytex
\documentclass{article}
\begin{document}
\begin{lilypond}
{c' d' e'}
\end{lilypond}
\end{document}
$ lilypond-book --process=lilypond -dsafe -dbackend=eps docu.lytex
lilypond-book (GNU LilyPond) 2.12.3
Reading docu.lytex...
Running latex...This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live
2009/Debian)
restricted \write18 enabled.
entering extended mode
(/tmp/tmpgwVO1K.tex
LaTeX2e 2009/09/24
Babel v3.8l and hyphenation patterns for english, usenglishmax, dumylang,
noh
yphenation, french, basque, ngerman, german, german-x-2009-06-19,
ngerman-x-200
9-06-19, ukenglish, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo))
No file tmpgwVO1K.aux.
textwidth=345.0pt
columnsep=10.0pt
(./tmpgwVO1K.aux) )
No pages of output.
Transcript written on tmpgwVO1K.log.
Dissecting...
Writing snippets...
Processing...
Running lilypond...GNU LilyPond 2.12.3
Processing `/scratch/examples/Test/snippet-map--1168004333.ly'
Parsing...
/scratch/examples/Test/snippet-map--1168004333.ly:4:1: error: GUILE
signaled an error for the expression beginning here
#
(ly:add-file-name-alist '((d6/lily-79fd5fcc.ly . docu.lytex)
Unbound variable: ly:add-file-name-alist
/scratch/examples/Test/snippet-map--1168004333.ly:0: warning: no \version
statement found, please add
\version 2.12.3
for future compatibility
Processing `/scratch/examples/Test/d6/lily-79fd5fcc.ly'
Parsing...
/scratch/examples/Test/d6/lily-79fd5fcc.ly:3:9: error: include files are
not allowed in safe mode
\include
lilypond-book-preamble.ly
/scratch/examples/Test/d6/lily-79fd5fcc.ly:13:3: error: GUILE signaled an
error for the expression beginning here
#
(define dump-extents #t)
Wrong type argument in position 1: #srcprops ((breakpoint . #f) (line .
40) (column . 7)
(filename . /usr/share/lilypond/2.12.3/ly/music-functions-init.ly))
/scratch/examples/Test/d6/lily-79fd5fcc.ly:17:22: error: GUILE signaled an
error for the expression beginning here
force-assignment = #
Wrong type argument in position 1: #srcprops ((breakpoint . #f) (line .
40) (column . 7)
(filename . /usr/share/lilypond/2.12.3/ly/music-functions-init.ly))
/scratch/examples/Test/d6/lily-79fd5fcc.ly:18:16: error: GUILE signaled an
error for the expression beginning here
line-width = #
(- line-width (* mm 3.00))
Wrong type argument in position 1: #srcprops ((breakpoint . #f) (line .
40) (column . 7)
(filename . /usr/share/lilypond/2.12.3/ly/music-functions-init.ly))
/scratch/examples/Test/d6/lily-79fd5fcc.ly:0: warning: no \version
statement found, please add
\version 2.12.3
for future compatibility
Interpreting music...
Preprocessing graphical
objects.../usr/share/lilypond/2.12.3/scm/titling.scm:9:34: In procedure
ly:paper-get-number in expression (ly:paper-get-number layout (quote
line-width)):
/usr/share/lilypond/2.12.3/scm/titling.scm:9:34: Wrong type (expecting real
number): #unspecified
command failed: lilypond -dsafe -dbackend=eps -I /scratch/examples/Test
--formats=eps -deps-box-padding=3.00 -dread-file-list
-dno-strip-output-dir /scratch/examples/Test/snippet-names--1168004333.ly
Child returned 1
%-8
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1282 in lilypond: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate
Status: Accepted Owner: Labels: Type-Documentation Priority-Medium New issue 1282 by brownian.box: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate http://code.google.com/p/lilypond/issues/detail?id=1282 Reported by Vicente Solsona, http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00295.html : -8 hello, the example in the third entry of NR 4.6.2 Changing spacing is inaccurate afaik: -8- e4 c g\f c \override DynamicText #'extra-offset = #'( -2.2 . 2.0) e4 c g\f c -8- #'extra-offset does *not* affect vertical nor horizontal spacing, so it does not save vertical space... [...] -8 ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tiny correction to NR
On Mon 20 Sep 2010, 19:12 Vicente Solsona wrote: hello, the example in the third entry of NR 4.6.2 Changing spacing is inaccurate afaik: Since it's still inaccurate, added as 1282: http://code.google.com/p/lilypond/issues/detail?id=1282 Thank you! -8- e4 c g\f c \override DynamicText #'extra-offset = #'( -2.2 . 2.0) e4 c g\f c -8- #'extra-offset does *not* affect vertical nor horizontal spacing, so it does not save vertical space. we have to disable the collision first so the dynamics don't take vertical space and then move it for aesthetical purposes, so the valid example should be (after a native english revision): -8- e4 c g\f c \override DynamicLineSpanner #'outside-staff-priority = ##f % make dynamics not to take vertical space \override DynamicText #'extra-offset = #'(-2.2 . 2.2) % place the dynamics manually to improve appearance e4 c g\f c -8- greetings, Vicente side note: why \once doesn't work in the previous example (in 2.12.3)? -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1274 in lilypond: convert-ly does not warn about #'dash-period = #-1 for LyricHyphen
Comment #5 on issue 1274 by brownian.box: convert-ly does not warn about #'dash-period = #-1 for LyricHyphen http://code.google.com/p/lilypond/issues/detail?id=1274 Ok then .) Two questions: 1. After Neil's last comment (#4) -- shouldn't summary be changed? How?-) 2. What about manuals? There are other places with misleading information (for instance: 3.1.57 LyricHyphen says that minimum-distance is for Minimum distance between rest and notes or beam.), So, is it possible to correct those sentences for dash-period and minimum-distance? If yes, this, i guess, should be reported as issue? And, since there are more then one place, i guess, should separate issue be added for each? Thanks. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
(no subject)
http://pawojuy.t35.com/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1026 in lilypond: Documentation: adapting Lyrics when using \repeatTie
Updates:
Status: Fixed
Labels: 2.13.35
Comment #7 on issue 1026 by tdanielsmusic: Documentation: adapting Lyrics
when using \repeatTie
http://code.google.com/p/lilypond/issues/detail?id=1026
Documentation for using \alternative in repeats with lyrics has been added
to NR 2.1 Vocal music/Techniques specific to lyrics/Lyrics and repeats in
git, and it covers this point.
For the record, the issue is not straightforward, as the example in comment
5 illustrates. In order to get the volta brackets in music and lyrics to
line up correctly it is necessary to disable the automatic detection of a
melisma over a tied note and insert manual skips in both sections (AFAICS):
\relative c' {
\repeat volta 2 {
\set melismaBusyProperties = #'()
c d e f~ |
}
\alternative {
{ f a b c }
{ f, \repeatTie g a c }
\unset melismaBusyProperties
}
}
\addlyrics {
\repeat volta 2 {
c d e f
}
\alternative {
{ _ a b c }
{ _ g a c }
}
}
This may be a bug, or indicate a desirable enhancement. If so, a separate
issue should be raised.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autobeaming in cadenza
On Wed 29 Sep 2010, 02:35 Keith E OHara wrote: On Wed, 29 Sep 2010 00:13:44 -0700, Dmytro O. Redchuk brownian@gmail.com wrote: Sorry, why do you expect it to work? I wouldn't expect, because of the nature (my understanding of) of cadenza... Dmytro, Very good point. Reasons to expect auto-beaming to work: Even though a cadenza has a free rhythm and is not divided into bars, it usually has a rhythmic structure, and is written using the usual conventions of music with a beat. Beethoven's 'emperor' concerto (small image attached) opens with a cadenza, but is written using tuplets and beams to show how the notes fit in the underlying pulse. Most cadenzas are simpler (Chopin image attached). The examples for \cadenzaOn in NR 1.2.3 show notes that are autobeamed, which implies that users can expect autobeaming to work. Autobeaming _tries_ to work: if the notes are beam-able, at least some of them are auto-beamed according to the time signature in effect before \cadenzaOn. Reasons we should not expect auto-beaming to work: No, i can agree that autobeaming should (or would be great to) work in cadenzas; but i can not imagine how to describe expected behavior. _How_ this should work? This can be a valid issue report (most probably enhancement/feature request); please, could you modify your initial minimal example -- include some explicit autobeaming rule[1] and describe what you expected to have. (I hardly can imagine which autobeaming defaults should be in cadenzas.) Thanks! ___ 1. Yes, i can see that all notes in your example are beamed together, but i don't know what should be instead, to be precise .( -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1280 in lilypond: \displayMusic does not properly quote cons lilypond properties
Updates: Status: Fixed Owner: n.puttock Labels: fixed_2_13_35 Comment #1 on issue 1280 by Carl.D.Sorensen: \displayMusic does not properly quote cons lilypond properties http://code.google.com/p/lilypond/issues/detail?id=1280 Fixed with commit 1af002a26299daf2881c28b3d8366a354cffa5da ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: separating music and guitar instructions
On Wed, 29 Sep 2010 09:11:45 +0200, Dmytro O. Redchuk
brownian@gmail.com wrote:
Sorry for delay. I am still brave enough to add this to the tracker
but not
sure that this issue is clear enough, sorry.
Dmytro,
many thanks for taking the time to keep this alive :)
I am affraid, if this is _a question_ (should or should not), it's
still not
a valid issue report?
I definitely think it is, but we are mixing two things:
1) fingering indications are not displayed in *standard notation* if
entered with no angle braces, but they are displayed in *tablature*.
this is a Lilypond *feature*. Some users seem to be fine with it
(myself included) while some other may have some objections: Xavier
Scheuer finds it annoying, and David Kastrup observed:
Would seem like a case for a context variable rather than hardwired
We can discuss whether this is a real issue or it is fine as it is
now.
For me, it's not so important to raise a real issue. I can live with
this feature as it is now (but as Patrick Schmidt pointed, then the
Notation Manual must should be adjusted, but let's forget this for
now,
I can make a proper issue request later).
2) what I'm actually reporting seems really a *bug* to me. Please let me
reformulate it with a more complete example:
%-8
Summary: some fingering indications and fingering related commands are not
displayed
when entered in a separate expression
Type: Defect
Priority: Medium
\version 2.12.3
music = \relative c'' {c4 c c c c \stemUp c}
fingerings = {
s4-1% it's displayed
s4\2% it's not displayed
s4-\rightHandFinger #2 % it's not displayed
\set fingeringOrientations = #'(down) % doesn't work
s4-2
\override Fingering #'staff-padding = #'() % *does* work
s4-3
\override Fingering #'add-stem-support = ##f % doesn't work
s4-1
}
\score {
\new Staff \context Voice = A \music
\context Voice = A \fingerings
}
%-8
This is the real issue report I'd want to make.
I'm not a native english, and sometimes I express myself awfully. My
apologies for this. Please let me know if I can make the report clearer.
Many thanks again.
Greetings,
Vicente
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1282 in lilypond: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate
Comment #1 on issue 1282 by pkx1...@hotmail.com: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate http://code.google.com/p/lilypond/issues/detail?id=1282 Patch submitted to Graham. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: separating music and guitar instructions
On Wed 29 Sep 2010, 13:58 Vicente Solsona wrote: I definitely think it is, but we are mixing two things: 1) fingering indications are not displayed in *standard notation* if entered with no angle braces, but they are displayed in *tablature*. this is a Lilypond *feature*. Some users seem to be fine with it (myself included) while some other may have some objections: Xavier Scheuer finds it annoying, and David Kastrup observed: Would seem like a case for a context variable rather than hardwired We can discuss whether this is a real issue or it is fine as it is now. For me, it's not so important to raise a real issue. I can live with this feature as it is now (but as Patrick Schmidt pointed, then the Notation Manual must should be adjusted, but let's forget this for now, I can make a proper issue request later). 2) what I'm actually reporting seems really a *bug* to me. Please let me reformulate it with a more complete example: The latter added as is as 1283: http://code.google.com/p/lilypond/issues/detail?id=1283 Regarding the former -- let's discuss it later?-) Please *start a new thread* and post an issue request :-) Thank you! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1282 in lilypond: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate
Comment #2 on issue 1282 by vsolsona: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate http://code.google.com/p/lilypond/issues/detail?id=1282 Please note that after my exchange with James Lowe and Graham my suggestion for the definitive example is (*): -8 e4 c g\f c e4 c g-\tweak #'X-offset #-2.7 -\tweak #'Y-offset #2.5 \f c -8 (*) http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00309.html many thanks!! ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tiny correction to NR
On Wed, 29 Sep 2010 09:33:12 +0200, Dmytro O. Redchuk brownian@gmail.com wrote: added as 1282: http://code.google.com/p/lilypond/issues/detail?id=1282 thanks! I've added a comment in the issue with an update as per: http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00309.html I hope I have proceeded correctly. greetings, Vicente ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1026 in lilypond: Documentation: adapting Lyrics when using \repeatTie
Updates: Labels: -2.13.35 fixed_2_13_35 Comment #8 on issue 1026 by PhilEHolmes: Documentation: adapting Lyrics when using \repeatTie http://code.google.com/p/lilypond/issues/detail?id=1026 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 506, or something similar, can still occur
On Tue, Sep 21, 2010 at 8:51 PM, Keith E OHara k-ohara5...@oco.net wrote:
% Something like issue 506 can still be observed.
%
% Relative to the original report for issue 506,
% remove the slur, and add an accent with a
% forced direction. The beam is badly placed.
%
% I did *not* find this during normal use, but
% while testing a workaround for a different bug.
% Small changes avoid the bug. In this example, either
% move the accent, or put the slur back in.
% Maybe just file this under 506, so we know there
% are limits to that fix?
\version 2.12.3
% version 2.13.33 gives visibly the same output
\paper { ragged-right = ##t }
\new PianoStaff
\new Staff = rh { s1 }
\new Staff = lh \relative c {
\clef bass
%
% LilyPond reports 'programming error: Grob direction
% requested while calculation in progress.'
% Inserting
% \stemDown
% removes this error report, but still produces
% a badly-placed beam, very similar to original 506.
%
e16-\markup{a}_ b'
\change Staff = rh
g' b
}
%{%}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Bug List moderator : 506 is closed. Should this be set up as a new issue,
or can the number 506 be reinstated?
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
(no subject)
http://mercuryinformatica.it/94416.html ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 506, or something similar, can still occur
On Wed, Sep 29, 2010 at 12:48:26PM -0400, Ralph Palmer wrote: On Tue, Sep 21, 2010 at 8:51 PM, Keith E OHara k-ohara5...@oco.net wrote: Bug List moderator : 506 is closed. Should this be set up as a new issue, or can the number 506 be reinstated? No. Please add a new issue, but mention 506 in the description. Once an issue has been Verified, the **only** thing that should be done is un-verify it if you still see the same bug, with exactly the same input, with exactly the version number that it was claimed to be fixed in. I don't think it's worth download version 2.11.45 to re-test 506, so just add a new issue. :) Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autobeaming in cadenza
Carl Sorensen wrote: I think that autobeaming in cadenzas should beam according to baseMoment, i.e. all beats should be grouped together in baseMoment units. The very concept of beats within a cadenza goes against the whole idea of a cadenza in the first place. I think a better system would be to break beams only when the note duration changes, and *not* after a dotted note. But there's simply no algorithm that will work in most cases. The user will almost always need to do some manual beams. One possibility to ease some of the burden for the user would be to set up beaming styles, not unlike the accidental styles that we currently have. So we could have \groupBeats and \groupDurations, for example. - Mark ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autobeaming in cadenza
On 9/29/10 11:35 AM, Mark Polesky markpole...@yahoo.com wrote: Carl Sorensen wrote: I think that autobeaming in cadenzas should beam according to baseMoment, i.e. all beats should be grouped together in baseMoment units. The very concept of beats within a cadenza goes against the whole idea of a cadenza in the first place. I think a better system would be to break beams only when the note duration changes, and *not* after a dotted note. But there's simply no algorithm that will work in most cases. The user will almost always need to do some manual beams. One possibility to ease some of the burden for the user would be to set up beaming styles, not unlike the accidental styles that we currently have. So we could have \groupBeats and \groupDurations, for example. \groupBeats would require a dramatically different autobeaming algorithm. Perhaps the best answer is to have \candezaOn turn off autbeaming. Since the cadenza is in free time, perhaps the composer should be responsible for giving whatever metric hints are desired with the beam by indicating the beaming manually. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autobeaming in cadenza
On 9/29/10 4:18 AM, Dmytro O. Redchuk brownian@gmail.com wrote:
On Wed 29 Sep 2010, 02:35 Keith E OHara wrote:
On Wed, 29 Sep 2010 00:13:44 -0700, Dmytro O. Redchuk
brownian@gmail.com wrote:
Sorry, why do you expect it to work?
[ ... ]
The examples for \cadenzaOn in NR 1.2.3 show notes that are autobeamed, which
implies that users can expect autobeaming to work.
Autobeaming _tries_ to work: if the notes are beam-able, at least some of
them are auto-beamed according to the time signature in effect before
\cadenzaOn.
Reasons we should not expect auto-beaming to work:
No, i can agree that autobeaming should (or would be great to) work in
cadenzas; but i can not imagine how to describe expected behavior.
_How_ this should work?
This can be a valid issue report (most probably enhancement/feature request);
On Wed, 29 Sep 2010 08:46:46 -0700, Carl Sorensen c_soren...@byu.edu wrote:
I think that autobeaming in cadenzas should beam according to baseMoment,
i.e. all beats should be grouped together in baseMoment units.
Yes, this could be a simple feature request, but I do not request this feature.
Looking at how \cadenzaOn is used in practice (by google \cadenzaOn
site:www.mutopiaproject.org) it seems that manual beams (or using \bar
instead of \cadenzaOn) are clean solutions.
Also, \cadenzaOn is a simple LilyPond definition in property-init.ly, so users
like me can reasonably adapt that definition (probably implementing the rule
that Carl suggested) and submit a feature _suggestion_ if our own definition
works well.
The reason I raised this issue is that while creating scores I _thought_
autobeaming worked in cadenzas (along the lines Carl suggests) and version
2.12.3 did so for the length of a couple cadenzas. LilyPond's irregular
behavior could frustrate users, but that can be solved with:
@knownissues Automatic beaming rules are unlikely to produce the desired beams
in cadenzas longer than one or two beats, so it is best to specify beams
manually with @code{[} and @code{]}.
--
Keith
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1240 in lilypond: Music overflows page: #'((space . N) (stretchability . 0)) and nothing more with spacings
Updates: Labels: -Priority-Medium Priority-Critical Comment #6 on issue 1240 by percival.music.ca: Music overflows page: #'((space . N) (stretchability . 0)) and nothing more with spacings http://code.google.com/p/lilypond/issues/detail?id=1240 Thanks for the example, Keith! I'm bumping this up to Critical. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
\revertTimeSignatureSettings broken?
In NR 1.2.3 Displaying rhythms - Time signature, the \revertTimeSignatureSettings example (the last one before the snippets) doesn't do what I'd expect from the text: http://kainhofer.com/~lilypond/Documentation/notation/displaying-rhythms.html#time-signature http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/notation/rhythms.itely#l1107 - Mark ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1282 in lilypond: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate
Comment #3 on issue 1282 by pkx1...@hotmail.com: the example in the third entry of NR 4.6.2 Changing spacing is inaccurate http://code.google.com/p/lilypond/issues/detail?id=1282 Patch pushed Commit 3685a38706539efeaf642de0f435c5ffc43dad55 James ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: tiny correction to NR
Patch Pushed. Commit: 3685a38706539efeaf642de0f435c5ffc43dad55 Tracker updated. Thanks Vincente. James -Original Message- From: bug-lilypond-bounces+james.lowe=datacore@gnu.org on behalf of Vicente Solsona Sent: Wed 29/09/2010 16:47 To: Dmytro O. Redchuk Cc: bug-lilypond@gnu.org Subject: Re: tiny correction to NR On Wed, 29 Sep 2010 09:33:12 +0200, Dmytro O. Redchuk brownian@gmail.com wrote: added as 1282: http://code.google.com/p/lilypond/issues/detail?id=1282 thanks! I've added a comment in the issue with an update as per: http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00309.html I hope I have proceeded correctly. greetings, Vicente ___ 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
(no subject)
http://agilium.it/24105.html ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Comment #5 on issue 1269 by pkx1...@hotmail.com: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 So is this invalid? I see this is mentioned on the front page of http://lilypond.org/index.html If not exactly what is needed to be documented? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato)
Comment #27 on issue 687 by chicagogrooves: Enhancement: inequal MIDI quantization of equal durations (swing, rubato) http://code.google.com/p/lilypond/issues/detail?id=687 adam.spiers: Great video on a set of 'parameters' of swing which made it into Ableton Live 8. Not saying its the best model for lilypond, but it certainly does more than my current implementation provides for: http://www.youtube.com/watch?v=zcDaWRXlvIE ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
lilypond-book with LaTex: quote / quotation - environment
Hello,
I use Lilypond-Book with LaTex and have following suggestion concerning the
'quote'-%option:
I always get a bad layout using the quote option, because it uses the
'quotation' environment in LaTex, which implies an indention of the first line
in LaTex. This causes in all my documents and in a 'clean' example, the first
line of my lilypond-examples to be indented without adjusting the line-length.
But Lilypond should set the indentation, not LaTex. So I think using
\begin{quotation} ... \end{quotation} is a bad choice. In my opinion the quote
environment should use \begin{quote} ... \end{quote}.
So I decided for my personal setup to change the lines 754-756 of the
lilypond-book-script, version 2.12.3 in Ubuntu Lucid Lynx, (which is now
lilypond-2.13.35/python/book_latex.py line 124-126 in the dev version 2.13.35)
from:
QUOTE: r'''\begin{quotation}
%(str)s
\end{quotation}''',
into:
QUOTE: r'''\begin{quote}
%(str)s
\end{quote}''',
This works for me and I hope this can be useful for you, too.
Example:
\documentclass[a4paper]{article}
\begin{document}
\begin[quote]{lilypond}
{
c'4 d' e' f'
g' a' b' c''
d'' e'' f'' g''
a'' b'' c'''2
c'''4 b'' a'' g''
f'' e'' d'' c''
b' a' g' f'
e' d' c'2
}
\end{lilypond}
\end{document}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
