Re: 2.18.2: modern-voice-cautionary and no way to force accidental
Isn't it an ugly collision, really?
2016-02-25 10:57 GMT+02:00 Dmytro O. Redchuk :
> Yes! Thank you for this workaround!
>
> ps. Anyway, I think this is an issue.
>
> \version "2.18.2"
>
> \score {
> \context ChoirStaff <<
> \accidentalStyle ChoirStaff.modern-voice-cautionary
> <<
> \relative c'' { cis4 c cis c }
> \\
> \relative a' {
> a4
> \once \accidentalStyle modern
> c! a c,
> }
> >>
> >>
> }
>
> \layout {
> \context {
> \Staff
> \override AccidentalCautionary #'font-size = #-3
> }
> }
>
> 2016-02-24 22:58 GMT+02:00 Noeck :
>> I also think there should be only one accidental in this place. As a
>> workaround, you can set the accidental style to modern for this note:
>>
>>
>>> \version "2.18.2"
>>>
>>> \score {
>>> \context ChoirStaff <<
>>> \accidentalStyle ChoirStaff.modern-voice-cautionary
>>> <<
>>> \relative c'' { cis4 c }
>>> \\
>>> % how to force cancellation, not caution?
>>> \relative a' { a4
>>
>> \once \accidentalStyle modern
>>
>>> c! }
>>> >>
>>> >>
>>> }
>>>
>>> \layout {
>>> \context {
>>> \Staff
>>> \override AccidentalCautionary #'font-size = #-3
>>> }
>>> }
>>
>>
>> ___
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>
>
> --
> Dmytro O. Redchuk
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.18.2: modern-voice-cautionary and no way to force accidental
Yes! Thank you for this workaround!
ps. Anyway, I think this is an issue.
\version "2.18.2"
\score {
\context ChoirStaff <<
\accidentalStyle ChoirStaff.modern-voice-cautionary
<<
\relative c'' { cis4 c cis c }
\\
\relative a' {
a4
\once \accidentalStyle modern
c! a c,
}
>>
>>
}
\layout {
\context {
\Staff
\override AccidentalCautionary #'font-size = #-3
}
}
2016-02-24 22:58 GMT+02:00 Noeck :
> I also think there should be only one accidental in this place. As a
> workaround, you can set the accidental style to modern for this note:
>
>
>> \version "2.18.2"
>>
>> \score {
>> \context ChoirStaff <<
>> \accidentalStyle ChoirStaff.modern-voice-cautionary
>> <<
>> \relative c'' { cis4 c }
>> \\
>> % how to force cancellation, not caution?
>> \relative a' { a4
>
> \once \accidentalStyle modern
>
>> c! }
>> >>
>> >>
>> }
>>
>> \layout {
>> \context {
>> \Staff
>> \override AccidentalCautionary #'font-size = #-3
>> }
>> }
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
2.18.2: modern-voice-cautionary and no way to force accidental
Hello,
in the example below two voices have the same c'', but there is a
cancellation in one voice and cautionary cancellation in another.
Not that I have reduced font size for cautionary accidentals too much,
just for the sake of demonstration (however it should be reduced
accordingly to our local notation rules/traditions).
Result is bad.
I can make both of them cautionary, but I need just cancellation there.
The same result I get with 2.19.32.
% -- 8<
\version "2.18.2"
\score {
\context ChoirStaff <<
\accidentalStyle ChoirStaff.modern-voice-cautionary
<<
\relative c'' { cis4 c }
\\
% how to force cancellation, not caution?
\relative a' { a4 c! }
>>
>>
}
\layout {
\context {
\Staff
\override AccidentalCautionary #'font-size = #-3
}
}
% -- 8< ----
Now I think this is an issue.
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
2015-12-19 8:30 GMT+02:00 Masamichi HOSODA : >> In the case of text font, variable `font' is set to #f. >> In the case of music font, variable `font' is set to non-#f. > > I've created issue 4701. Thank you! -- Dmytro O. Redchuk ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
2015-12-09 15:10 GMT+02:00 tisimst : > Dmytro, > > Sorry for my delayed comment. I don't know what is causing this, but I've > seen this come up before from other users. I'm excited to see you like > Improviso! I hope we can get this figured out. Abraham, yes, I like it very much, THANK you :) When I insert some (display ...)'s into framework-ps.scm I can see that ly:find-file fails to find font-file with --pdf option for some reason. Ok, as you can see, I can be wrong! Don't mind, please :) Now I've simply added "fallback" workaround: --- framework-ps.scm.orig 2015-12-08 10:44:54.293262621 +0200 +++ framework-ps.scm2015-12-08 12:07:52.786888984 +0200 @@ -237,16 +237,18 @@ (let* ((font (car font-name-filename)) (name (cadr font-name-filename)) (file-name (caddr font-name-filename)) - (bare-file-name (ly:find-file file-name))) + (bare-file-name (ly:find-file file-name)) + (font-file-name (ly:find-file (format #f "~a.otf" file-name (cons name (if (mac-font? bare-file-name) (handle-mac-font name bare-file-name) (cond ((internal-font? file-name) - (ps-load-file (ly:find-file - (format #f "~a.otf" file-name + (ps-load-file font-file-name)) ((string? bare-file-name) (ps-load-file file-name)) + ((string? font-file-name) + (ps-load-file font-file-name)) (else (ly:warning (_ "cannot embed ~S=~S") name file-name) "")) -- Dmytro O. Redchuk ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
Sorry, this "patch" has huge problems .(
2015-12-08 11:44 GMT+02:00 Dmytro O. Redchuk :
> With this patch it looks like "it works for me".
>
> I will check more. What would I check besides of a "regular"
> (lilypond's and lilypond-book's) output generation?
>
> Please, anyone knowledgeable, review this diff and give your feedback,
> because, as usually, I don't know what I am doing.
>
> Thank you!
>
> 2015-12-08 9:57 GMT+02:00 Dmytro O. Redchuk :
>> 2015-12-08 9:55 GMT+02:00 Dmytro O. Redchuk :
>>> Hello,
>>>
>>> to avoid any misunderstanding with any "include"'s I've tested this
>>> issue with this source:
>> And the command was (no -I...), of course:
>>
>> $ lilypond-book --out=out [--pdf] test.lytex
>>
>>>
>>> % 8< --
>>> \documentclass{article}
>>> \begin{document}
>>> \begin{lilypond}
>>> { c''4 }
>>> \paper {
>>> #(define fonts
>>> (set-global-fonts
>>> #:music "improviso"
>>> #:factor (/ staff-height pt 20)
>>> ))
>>> }
>>> \end{lilypond}
>>> \end{document}
>>> % 8< --
>>>
>>> And I have the same result, attached.
>>>
>>> 2015-12-07 22:00 GMT+02:00 Dmytro O. Redchuk :
>>>> 2015-12-07 19:55 GMT+02:00 James :
>>>>> Hello Dmytro,
>>>> Hello James :)
>>>>
>>>>>>> I want lilypond to engrave it with "improviso" font,
>>>>>>> https://fonts.openlilylib.org/improviso/ --- I have set it up, it's
>>>>>>> ok.
>>>> ... and the subject of this thread is: "lilypond-book: 'external'
>>>> fonts and --pdf option problem" .)
>>>>
>>>> I have no any problem with lilypond-book and Emmentaler (lilypond's
>>>> default) font. With or without --pdf, really.
>>>>
>>>> I am sorry to be unclear. That \include imports the stylesheet for
>>>> improviso font (https://fonts.openlilylib.org/improviso/, an alternate
>>>> font for lilypond).
>>>>
>>>> So, without --pdf I have nice result, with --pdf I have a score(s)
>>>> with "improviso-related" objects missed.
>>
>> --
>> Dmytro O. Redchuk
>
>
>
> --
> Dmytro O. Redchuk
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
With this patch it looks like "it works for me".
I will check more. What would I check besides of a "regular"
(lilypond's and lilypond-book's) output generation?
Please, anyone knowledgeable, review this diff and give your feedback,
because, as usually, I don't know what I am doing.
Thank you!
2015-12-08 9:57 GMT+02:00 Dmytro O. Redchuk :
> 2015-12-08 9:55 GMT+02:00 Dmytro O. Redchuk :
>> Hello,
>>
>> to avoid any misunderstanding with any "include"'s I've tested this
>> issue with this source:
> And the command was (no -I...), of course:
>
> $ lilypond-book --out=out [--pdf] test.lytex
>
>>
>> % 8< --
>> \documentclass{article}
>> \begin{document}
>> \begin{lilypond}
>> { c''4 }
>> \paper {
>> #(define fonts
>> (set-global-fonts
>> #:music "improviso"
>> #:factor (/ staff-height pt 20)
>> ))
>> }
>> \end{lilypond}
>> \end{document}
>> % 8< --
>>
>> And I have the same result, attached.
>>
>> 2015-12-07 22:00 GMT+02:00 Dmytro O. Redchuk :
>>> 2015-12-07 19:55 GMT+02:00 James :
>>>> Hello Dmytro,
>>> Hello James :)
>>>
>>>>>> I want lilypond to engrave it with "improviso" font,
>>>>>> https://fonts.openlilylib.org/improviso/ --- I have set it up, it's
>>>>>> ok.
>>> ... and the subject of this thread is: "lilypond-book: 'external'
>>> fonts and --pdf option problem" .)
>>>
>>> I have no any problem with lilypond-book and Emmentaler (lilypond's
>>> default) font. With or without --pdf, really.
>>>
>>> I am sorry to be unclear. That \include imports the stylesheet for
>>> improviso font (https://fonts.openlilylib.org/improviso/, an alternate
>>> font for lilypond).
>>>
>>> So, without --pdf I have nice result, with --pdf I have a score(s)
>>> with "improviso-related" objects missed.
>
> --
> Dmytro O. Redchuk
--
Dmytro O. Redchuk
--- framework-ps.scm.orig 2015-12-08 10:44:54.293262621 +0200
+++ framework-ps.scm2015-12-08 11:14:49.600462497 +0200
@@ -237,16 +237,16 @@
(let* ((font (car font-name-filename))
(name (cadr font-name-filename))
(file-name (caddr font-name-filename))
- (bare-file-name (ly:find-file file-name)))
+ (bare-file-name (ly:find-file file-name))
+ (font-file-name (ly:find-file (format #f "~a.otf" file-name
(cons name
(if (mac-font? bare-file-name)
(handle-mac-font name bare-file-name)
(cond
((internal-font? file-name)
- (ps-load-file (ly:find-file
- (format #f "~a.otf" file-name
- ((string? bare-file-name)
- (ps-load-file file-name))
+ (ps-load-file font-file-name))
+ ((string? font-file-name)
+ (ps-load-file font-file-name))
(else
(ly:warning (_ "cannot embed ~S=~S") name file-name)
""))
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
2015-12-08 9:55 GMT+02:00 Dmytro O. Redchuk :
> Hello,
>
> to avoid any misunderstanding with any "include"'s I've tested this
> issue with this source:
And the command was (no -I...), of course:
$ lilypond-book --out=out [--pdf] test.lytex
>
> % 8< --
> \documentclass{article}
> \begin{document}
> \begin{lilypond}
> { c''4 }
> \paper {
> #(define fonts
> (set-global-fonts
> #:music "improviso"
> #:factor (/ staff-height pt 20)
> ))
> }
> \end{lilypond}
> \end{document}
> % ---- 8< ------
>
> And I have the same result, attached.
>
> 2015-12-07 22:00 GMT+02:00 Dmytro O. Redchuk :
>> 2015-12-07 19:55 GMT+02:00 James :
>>> Hello Dmytro,
>> Hello James :)
>>
>>>>> I want lilypond to engrave it with "improviso" font,
>>>>> https://fonts.openlilylib.org/improviso/ --- I have set it up, it's
>>>>> ok.
>> ... and the subject of this thread is: "lilypond-book: 'external'
>> fonts and --pdf option problem" .)
>>
>> I have no any problem with lilypond-book and Emmentaler (lilypond's
>> default) font. With or without --pdf, really.
>>
>> I am sorry to be unclear. That \include imports the stylesheet for
>> improviso font (https://fonts.openlilylib.org/improviso/, an alternate
>> font for lilypond).
>>
>> So, without --pdf I have nice result, with --pdf I have a score(s)
>> with "improviso-related" objects missed.
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
Hello,
to avoid any misunderstanding with any "include"'s I've tested this
issue with this source:
% 8< --
\documentclass{article}
\begin{document}
\begin{lilypond}
{ c''4 }
\paper {
#(define fonts
(set-global-fonts
#:music "improviso"
#:factor (/ staff-height pt 20)
))
}
\end{lilypond}
\end{document}
% 8< --
And I have the same result, attached.
2015-12-07 22:00 GMT+02:00 Dmytro O. Redchuk :
> 2015-12-07 19:55 GMT+02:00 James :
>> Hello Dmytro,
> Hello James :)
>
>>>> I want lilypond to engrave it with "improviso" font,
>>>> https://fonts.openlilylib.org/improviso/ --- I have set it up, it's
>>>> ok.
> ... and the subject of this thread is: "lilypond-book: 'external'
> fonts and --pdf option problem" .)
>
> I have no any problem with lilypond-book and Emmentaler (lilypond's
> default) font. With or without --pdf, really.
>
> I am sorry to be unclear. That \include imports the stylesheet for
> improviso font (https://fonts.openlilylib.org/improviso/, an alternate
> font for lilypond).
>
> So, without --pdf I have nice result, with --pdf I have a score(s)
> with "improviso-related" objects missed.
>
> --
> Dmytro O. Redchuk
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
2015-12-07 19:55 GMT+02:00 James : > Hello Dmytro, Hello James :) >>> I want lilypond to engrave it with "improviso" font, >>> https://fonts.openlilylib.org/improviso/ --- I have set it up, it's >>> ok. ... and the subject of this thread is: "lilypond-book: 'external' fonts and --pdf option problem" .) I have no any problem with lilypond-book and Emmentaler (lilypond's default) font. With or without --pdf, really. I am sorry to be unclear. That \include imports the stylesheet for improviso font (https://fonts.openlilylib.org/improviso/, an alternate font for lilypond). So, without --pdf I have nice result, with --pdf I have a score(s) with "improviso-related" objects missed. -- Dmytro O. Redchuk ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book: "external" fonts and --pdf option problem
2015-12-07 15:12 GMT+02:00 Dmytro O. Redchuk :
> Hello bug squad, hello list,
>
> I've found a problem with this "book":
I am sorry, forgot to mention,
tested with 2.18.2 and 2.19.32, got the same result.
>
> % test.lytex:
> % 8<
> \documentclass{article}
> \begin{document}
> \begin{lilypond}
> \include "improviso.ily"
> { c''4 }
> \end{lilypond}
> \end{document}
> % 8<
>
> I want lilypond to engrave it with "improviso" font,
> https://fonts.openlilylib.org/improviso/ --- I have set it up, it's
> ok.
>
> Now: lilypond-book does well without --pdf option:
>
> $ lilypond-book -I ${HOME}/lilyponds/local-includes --out=out test.lytex
> $ cd out
> $ latex test && dvips -o test.ps test.dvi && ps2pdf test.ps
>
> Now I have the desired result.
>
> But it fails when I want to do it for pdflatex:
> % 8<
> $ lilypond-book -I ${HOME}/lilyponds/local-includes --out=out --pdf test.lytex
>
> Layout output to `b5/lily-09c4cef9.eps'...
> попередження: cannot embed "improviso-20"="improviso-20"
> Converting to `b5/lily-09c4cef9.pdf'...
> Layout output to `b5/lily-09c4cef9-1.eps'...
> попередження: cannot embed "improviso-20"="improviso-20"
> Converting to `b5/lily-09c4cef9-1.pdf'...
> Writing b5/lily-09c4cef9-systems.texi...
> Writing b5/lily-09c4cef9-systems.tex...
> Writing b5/lily-09c4cef9-systems.count...
> Success: compilation successfully completed
> Linking files...
> Compiling /home/dor/tmp/ly-test/out/test.tex...
> Writing `/home/dor/tmp/ly-test/out/test.tex'...
> % 8<
>
> Now I have pdf containing a score with no clef, key signature and notehead.
>
> I've attached png files produced by
> $ convert -density 150 -1.eps -flatten -1.png
> for both ways, with and without --pdf.
>
> Is this an issue? How to work around?
>
> Thank you!
>
> --
> Dmytro O. Redchuk
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
lilypond-book: "external" fonts and --pdf option problem
Hello bug squad, hello list,
I've found a problem with this "book":
% test.lytex:
% 8<
\documentclass{article}
\begin{document}
\begin{lilypond}
\include "improviso.ily"
{ c''4 }
\end{lilypond}
\end{document}
% 8<
I want lilypond to engrave it with "improviso" font,
https://fonts.openlilylib.org/improviso/ --- I have set it up, it's
ok.
Now: lilypond-book does well without --pdf option:
$ lilypond-book -I ${HOME}/lilyponds/local-includes --out=out test.lytex
$ cd out
$ latex test && dvips -o test.ps test.dvi && ps2pdf test.ps
Now I have the desired result.
But it fails when I want to do it for pdflatex:
% 8<
$ lilypond-book -I ${HOME}/lilyponds/local-includes --out=out --pdf test.lytex
Layout output to `b5/lily-09c4cef9.eps'...
попередження: cannot embed "improviso-20"="improviso-20"
Converting to `b5/lily-09c4cef9.pdf'...
Layout output to `b5/lily-09c4cef9-1.eps'...
попередження: cannot embed "improviso-20"="improviso-20"
Converting to `b5/lily-09c4cef9-1.pdf'...
Writing b5/lily-09c4cef9-systems.texi...
Writing b5/lily-09c4cef9-systems.tex...
Writing b5/lily-09c4cef9-systems.count...
Success: compilation successfully completed
Linking files...
Compiling /home/dor/tmp/ly-test/out/test.tex...
Writing `/home/dor/tmp/ly-test/out/test.tex'...
% 8<
Now I have pdf containing a score with no clef, key signature and notehead.
I've attached png files produced by
$ convert -density 150 -1.eps -flatten -1.png
for both ways, with and without --pdf.
Is this an issue? How to work around?
Thank you!
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: Problem with Kerning
On Wed 28 Sep 2011, 23:57 Janek Warchoł wrote: > Hello Frank, > > thanks for the information. While unfortunately i can't help you with > this problem, i think that development team should know about this > issue, so i'm forwarding your mail to our bug-reporting mailing list. Thank you, added as 1946: http://code.google.com/p/lilypond/issues/detail?id=1946 -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Mobile Safari web docs truncated
On Sat 24 Sep 2011, 08:00 Peekay Ex wrote: > Hello, > > On Sat, Sep 24, 2011 at 2:12 AM, Matt Puumala wrote: > > When viewing the tutorial documentation on an Ipod Touch V3 (v4.3.1) using > > Safari, the pages are truncated at the bottom of the first screenful. This > > is > > exactly one screenful, even if that's in the middle of a line of text. > > Attempts > > to scroll down "spring back" like the bottom of the page is there. > > > > This has happened on pages > > http://lilypond.org/doc/v2.14/Documentation/learning/entering-input > > http://lilypond.org/doc/v2.14/Documentation/learning/windows > > Yes this happens on an ipad too. It doesn't occur on Safari 'desktop' > editions. > > I guess that doesn't really help anyone, but I thought it might be > additional knowledge. > > Opera Mini seems to be ok. Added as 1934: http://code.google.com/p/lilypond/issues/detail?id=1934 Thank you! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: possible bad output in mensural-ligatures.ly
On Sun 18 Sep 2011, 23:55 Janek Warchoł wrote: > Hi, Hi! > i've noticed something strange in mensural-ligatures.ly: in the last > system, a flat symbol collides with the notes (attached). Should it > look like this? > I tried to determine when it was introduced, but i cannot open eps > files in Lilydev so all regtest archives from > http://lilypond.org/download/binaries/test-output/ are useless for > me... I've finally added this as 1918: http://code.google.com/p/lilypond/issues/detail?id=1918 Please, anyone, help me adjust labels. -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: possible bad output in mensural-ligatures.ly
On Thu 22 Sep 2011, 14:06 Bertrand Bordage wrote:
> I'm ok with this subject.
>
> A better minimal example would be :
>
> \new MensuralStaff {
> \cadenzaOn
> \[ a'\breve g' as' \]
> }
Thank you, added as 1916:
http://code.google.com/p/lilypond/issues/detail?id=1916
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: possible bad output in mensural-ligatures.ly
On Thu 22 Sep 2011, 13:18 Benkő Pál wrote:
> copy that part from mensural-ligatures.ly?
Please, I am doing just paper work. I know nothing about ligatures. I am not
sure I have lilypond source code repository .)
> untested version:
>
> \context MensuralStaff
> {
> \[ a\breve g as \]
> }
So, the subject "lilypond should issue a warning regarding incorrect ligature"
is ok?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: possible bad output in mensural-ligatures.ly
On Thu 22 Sep 2011, 13:01 Janek Warchoł wrote: > However, according to Benko Pal we shouldn't worry about it: > > 2011/9/19 Benkő Pál : > > this is an impossible ligature, LilyPond should (but never did) > > refuse it (with an explanation). If lilypond should refuse it (with an explanation) -- please, can anyone prepare a tiny example? -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \fill-line, \column bug
У чт., 22-го вер. 2011, о 11:53 a...@bflat.demon.co.uk писали:
> Apologies, I thought that this WAS a tiny example - it's from a very much
> larger set of lines.
> I tried to remove text etc. to reduce the size, burt the problem went away.
Anyway, I believe this should be simplified to be a good snippet,
which demonstrates a particular problem.
I spent some 10 minutes to do it but failed. Sorry.
ps. Please, Cc: to list, thanks!
pps. \hspace #40 is the problem? Why? How to rewrite this with fewer code?
Or \null is the problem? ... etc-etc.
ppps. If nobody helps with this, I can add this with Needs-evidence,
to avoid it to get lost, though.
> kind regards,
> Arthur Lawrence
> PS I can send the complete score if it helps
>
> On 22 Sep 2011, at 8:38 am, Dmytro O. Redchuk wrote:
>
> > On Tue 20 Sep 2011, 11:52 a...@bflat.demon.co.uk wrote:
> >> The following snippet produces the desired effect with LilyPond version
> >> 2.12.3, but the output is shifted off the left of the page in version
> >> 2.14.2 (pdfs attached)
> >>
> >> Arthur Lawrence
> >>
> >>>>>>> begin snippet
> >>
> >> \paper {
> >>#(set-paper-size "a4" )
> >>line-width = 18\cm
> >> }
> >>
> >>\markup \fill-line {
> >>\line {
> >>\column {
> >>\line { \bold \large { Before the Gospel }
> >> \hspace #40 }
> >>\line { \char ##x0022 Hear the Gospel of our
> >> Lord }
> >>\line { \hspace #3 Jesus Christ according to
> >> \italic N. \char ##x0022 }
> >>}
> >>\column {
> >>\line \bold \large { After the Gospel }
> >>\null
> >>\line {
> >>\char ##x0022 This is the Gospel of the
> >> Lord
> >> \char ##x0022 \hspace #40
> >>}
> >>}
> >>}
> >>}
> >>
> >>
> >> <<<<< end snippet
> > Could you please prepare a tiny example?
> >
> > http://lilypond.org/doc/v2.15/Documentation/web/tiny-examples
> >
> > It could help a lot.
> >
> > Thank you!
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: slurs don't avoid other voices
On Sun 28 Aug 2011, 03:52 -Eluze wrote:
> slurs don't avoid other voices:
>
> \context Staff <<
> \new Voice { a'8( b') a'8( b') }
> \new Voice { \voiceTwo e'4 s}
> >>
>
> http://old.nabble.com/file/p32350964/test-small.png
> this looks as if the slur goes from the e of the 2nd voice to the g of the
> 1st.
Added ad 1915:
http://code.google.com/p/lilypond/issues/detail?id=1915
Sorry, I am not sure that this is a valid issue -- I've marked it with
"Needs-evidence".
Thank you!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Manual page break in a user defined variable
On Wed 21 Sep 2011, 18:57 Ed Gordijn wrote:
> Hi,
>
> This is related to http://code.google.com/p/lilypond/issues/detail?id=1903
> The alternative that is suggested in 1903 doesn't work when you use a variable
> for the pageBreak.
Thank you, added as 1914:
http://code.google.com/p/lilypond/issues/detail?id=1914
> See also http://lists.gnu.org/archive/html/lilypond-user/2011-09/msg00263.html
>
> mvtI = { c'4 c' c' c' }
> mvtII = { d'4 d' d' d' }
> myPageBreak = \pageBreak
>
>
> \score {
>\new Staff { \mvtI }
>\header { piece = "Page 1"}
> }
>
> \myPageBreak
>
> \score {
>\new Staff { \mvtII }
>\header { piece = "Should be page 2"}
> }
>
> Greeting, Ed
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Horizontal spacing depends on stem 'direction
On Thu 22 Sep 2011, 09:40 David Kastrup wrote: > In my opinion, this report is invalid. Since Lilypond does optical > justification of noteheads (cf node "Optical Spacing" in the Lilypond > Essay), of _course_ its spacing depends on the stem direction. And of > _course_ this implies that there will be a small borderline where page > break decisions _also_ differ depending on the stem direction. > > A human engraver will make a random decision, and stick with this > decision even when one stem is flipped around for the next iteration, > changing the spacing slightly. > > Lilypond does not remember what it did last time around with that score, > and it does not throw dice. Please, I think it would be great it you added your opinion to tracker. I've marked this issue as "needs-evidence" -- but this "evidence" should not be lost. Thank you! -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly: not converted in the presence of a non-empty
On Sat 17 Sep 2011, 14:52 Patrick Schmidt wrote: > Hi Reinhold et al., > > this is how musicxml2ly works at the moment: > > 1) if XML: bli> --> LilyPond: title = bli > 2) if XML: bla --> LilyPond: title = bla > 3) if XML: (empty) AND > bla --> LilyPond: title = bla > > so far so good, but > > 4) if XML: bli (non-empty!) AND > bla --> LilyPond: title = bli > > So any information in a -element is lost in the conversion > with musicxml2ly when the .xml-file also contains a non-empty > -element. I tried to change the code in order to reach something > like the following (but never managed to meet all 4 demands): > > if XML: bli (non-empty!) AND > bla --> LilyPond: title = bli; subtitle = bla > > How can I say this in python? I've added this as 1913: http://code.google.com/p/lilypond/issues/detail?id=1913 -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \fill-line, \column bug
On Tue 20 Sep 2011, 11:52 a...@bflat.demon.co.uk wrote:
> The following snippet produces the desired effect with LilyPond version
> 2.12.3, but the output is shifted off the left of the page in version 2.14.2
> (pdfs attached)
>
> Arthur Lawrence
>
> >>>>> begin snippet
>
> \paper {
> #(set-paper-size "a4" )
> line-width = 18\cm
> }
>
> \markup \fill-line {
> \line {
> \column {
> \line { \bold \large { Before the Gospel }
> \hspace #40 }
> \line { \char ##x0022 Hear the Gospel of our
> Lord }
> \line { \hspace #3 Jesus Christ according to
> \italic N. \char ##x0022 }
> }
> \column {
> \line \bold \large { After the Gospel }
> \null
> \line {
> \char ##x0022 This is the Gospel of the
> Lord
> \char ##x0022 \hspace #40
> }
> }
> }
> }
>
>
> <<<<< end snippet
Could you please prepare a tiny example?
http://lilypond.org/doc/v2.15/Documentation/web/tiny-examples
It could help a lot.
Thank you!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction
On Thu 22 Sep 2011, 09:30 m...@apollinemike.com wrote: > Is this a regression? 2.12.3 engraves the same output. > If so, do you know what the last version was that made the two lines equal? -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: possible bad output in mensural-ligatures.ly
On Sun 18 Sep 2011, 23:55 Janek Warchoł wrote: > Hi, Hi! > i've noticed something strange in mensural-ligatures.ly: in the last > system, a flat symbol collides with the notes (attached). Should it > look like this? > I tried to determine when it was introduced, but i cannot open eps > files in Lilydev so all regtest archives from > http://lilypond.org/download/binaries/test-output/ are useless for > me... It looks like an issue to be reported, but please, could you be more specific? What is mensural-ligatures.ly, where could I find it? -- etc. Thank you! -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Horizontal spacing depends on stem 'direction
On Thu 08 Sep 2011, 23:57 Trevor Daniels wrote:
> I'd class this as an engraving nitpick, but we don't have that
> classification anymore.
>
> It seems the horizontal spacing is slightly dependent on the stem
> direction. This can cause a score to mysteriously spread over an
> extra system when a single note with stem down is changed to one
> with stem up, if the original system exactly fitted the line width.
>
> The following example demonstrates this by showing the slight
> difference in the two line lengths.
Thank you, I've added this as 1912:
http://code.google.com/p/lilypond/issues/detail?id=1912
> \version "2.15.8"
> \score {
> \relative c'' {
>\repeat unfold 6 { a4 a a a }
> }
> }
>
> \score {
> \relative c'' {
>\repeat unfold 6 { c4 c c c }
> }
> }
>
> Trevor
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: packed-spacing works improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver
On Wed 07 Sep 2011, 17:26 Marek Klein wrote:
> Hello,
> packed-spacing works improperly with Mensural_ligature_engraver and
> Vaticana_ligature_engraver. See below:
>
> http://gregoriana.sk/gg/wp-content/uploads/ligature.jpg
> At the picture is the result of following code:
> \version "2.14.1"
This was added by Phil Holmes as 1879:
http://code.google.com/p/lilypond/issues/detail?id=1879
(I may be missed his email to list)
Thank you!
> \markup "Mensural_ligature_engraver"
> \score {
> \relative c' {
> \set Score.timing = ##f
> \[ c'\breve d e \] b1
> \[ e\breve d c \] e1
> }
> \layout {
> \context {
> \Voice
> \remove Ligature_bracket_engraver
> \consists Mensural_ligature_engraver
> }
> \context{
> \Score
> \override SpacingSpanner #'packed-spacing = ##t
> }
> }
> }
>
> \markup "Ligature_bracket_engraver"
> \score {
> \relative c' {
> \set Score.timing = ##f
> \[ c'\breve d e \] b1
> \[ e\breve d c \] e1
> }
> \layout {
> \context{
> \Score
> \override SpacingSpanner #'packed-spacing = ##t
> }
> }
> }
>
> Here is the same problem in gregorian context:
> http://gregoriana.sk/gg/wp-content/uploads/ligature-gg.jpg
>
> \version "2.14.1"
> \include "gregorian.ly"
>
> \markup "Vaticana_ligature_engraver"
> \score {
> \new VaticanaVoice \relative c'{
> \[ c d e \] c
> \[ e d c \] e
> }
> \layout {
> }
> }
>
> \markup "Without ligature"
> \score {
> \new VaticanaVoice \relative c'{
> c d e c
> e d c e
> }
> \layout {
> }
> }
>
>
> With best Wishes
>
> Marek Klein
> http://gregoriana.sk
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: dynamics on chords with notehead to left and right of stem are wrongly aligned
On Mon 05 Sep 2011, 01:45 Reinhold Kainhofer wrote: > Dynamics on chords with a notehead to the left and to the right of the > stem align differently than when there are only noteheads to the right. > > Simple test case is attached. The two \pp don't line up as they should. Thank you, added as 1911: http://code.google.com/p/lilypond/issues/detail?id=1911 As far as I can see from the discussion, it "Needs-evidence"? -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Empty lyrics lead to inaccurate 'cannot find Voice' warning
On Tue 13 Sep 2011, 16:51 Sietse Brouwer wrote:
> Dear bug auditor,
>
> This bug concerns Lilypond 2.12.3. It may affect later versions, I
> have been unable to test this.
> When I add an empty set of lyrics to a voice with \addlyrics, the
> compiler gives the following warning:
> bug.ly:14:16: warning: cannot find Voice `vSoprano'
> when in fact the problem is that the Lyrics expression is empty
>
> Why I think this could be a problem: I was typesetting a song in
> parts, and I'd made some dummy variables for the verses I had yet to
> enter. This warning cost me half an hour as I tried to figure out what
> was wrong with how I defined the Voice's name.
This has been fixed:
http://code.google.com/p/lilypond/issues/detail?id=750
You can use the latest stable, I believe.
> Desired behaviour: a warning like "Warning: skipping empty lyrics"
> would be more appropriate, I think, especially as that is indeed what
> seems to happen. (See example below. Verse C appears right under verse
> A.)
>
> Kind regards,
>
> Sietse
> Sietse Brouwer
>
>
> %Lilypond problem: inaccurate warning when lyrics are empty
>
> verseOne = \lyricmode { This is verse A }
> verseTwo = \lyricmode { } % empty verse
> verseThree = \lyricmode { This is verse C }
>
> \score {
> \new ChoirStaff <<
> \new Staff = "upper" <<
> \new Voice = "vSoprano" { a b c' d' }
> >>
> \new Lyrics \lyricsto "vSoprano" { \verseOne }
> \new Lyrics \lyricsto "vSoprano" { \verseTwo }
> \new Lyrics \lyricsto "vSoprano" { \verseThree }
> >>
> }
>
>
>
> GNU LilyPond 2.12.3
> Processing `bug.ly'
> Parsing...
> Interpreting music...
> bug.ly:15:16: warning: cannot find Voice `vSoprano'
>
> \new Lyrics
> \lyricsto "vSoprano" { \verseTwo }
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `bug.ps'...
> Converting to `./bug.pdf'...
>
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tests for flower appear to miss instantiations of classes
On Thu 08 Sep 2011, 14:13 David Kastrup wrote: > When configured with > > ./configure CXXFLAGS=-fkeep-inline-functions > > (which does not optimize unused functions away) > > make test fails in the flower subdirectory in the linking stage with > quite inscrutable error messages. > > I don't have the error message handy right now, but since this has been > bugging me on and off for at least a month (basically the only thing > failing with make check for me) and I have not been able to make any > progress on figuring out just what to do (spent about a day on it), I > decided to report this before I forget again. Added as 1875: http://code.google.com/p/lilypond/issues/detail?id=1875 Please, how critical it is? Thanks! -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \tempo indication not printed
On Mon 05 Sep 2011, 10:02 Reinhold Kainhofer wrote:
> Am Monday, 5. September 2011, 09:41:58 schrieb Dmytro O. Redchuk:
> > On Thu 01 Sep 2011, 16:06 Reinhold Kainhofer wrote:
> > > BTW, this is a really minimal example:
> > > \version "2.15.9"
> > >
> > > {
> > >
> > > s1
> > > \tempo "Waldo"
> > > s1
> > >
> > > }
> >
> > Neil mentioned issue 1276. What do you think, should this one be a separate
> > issue?
>
> AFAICS, it's a separate issue. 1276 wrongly aligns on the note, even if it
> should align on other grobs, while this issue does not print the mark at all,
> because there is no column to attach that survives.
Thank you, added as 1865:
http://code.google.com/p/lilypond/issues/detail?id=1865
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \tempo indication not printed
On Thu 01 Sep 2011, 16:06 Reinhold Kainhofer wrote:
> BTW, this is a really minimal example:
> \version "2.15.9"
>
> {
> s1
> \tempo "Waldo"
> s1
> }
>
> The issue is that the moment after the \tempo command does not have any grobs
> where the tempo could be attached to. As soon as you change the s1 to a note
> or rest, or if you have clef/key/timesig change at the same moment as the
> \tempo, the tempo mark can be reparented. But it seems that the engraver
> misses the case that there are no other grobs at the same moment as the
> \tempo
> change. In that case, the tempo mark should be reparented to the barline...
Neil mentioned issue 1276. What do you think, should this one be a separate
issue?
Thank you.
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken
On Fri 02 Sep 2011, 21:42 lilyp...@googlecode.com wrote: > Updates: > Status: Verified > > Comment #8 on issue 1295 by percival.music.ca: Support for Mac OSX > 10.3.9 "Panther" is broken > http://code.google.com/p/lilypond/issues/detail?id=1295 > > Every item in "issues to be verified" should be verified. Yes. However I was not so wrong this time .) For some reason "Invalid" issues need not to be verified, please compare: http://code.google.com/p/lilypond/issues/list?can=1&q=status%3Ainvalid http://code.google.com/p/lilypond/issues/list?can=7 I am not sure this is bad. What do you think? -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
On Wed 31 Aug 2011, 17:07 Reinhold Kainhofer wrote: > Am Mittwoch, 31. August 2011, 16:56:10 schrieb Dmytro O. Redchuk: > > On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote: > > > Updates: > > > Labels: fixed_2_15_9 > > > > I can not change it to "Verified", because of "Issue owner must be a > > project member" -- what's wrong? > > Nothing. Graham or someone with admin rights on the bug tracker needs to add > janek to the project members on code.google.com... Ok, thank you, I will wait .) -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote: > Updates: > Labels: fixed_2_15_9 I can not change it to "Verified", because of "Issue owner must be a project member" -- what's wrong? > Comment #16 on issue 1767 by n.putt...@gmail.com: Feta font - change > breve vertical lines > http://code.google.com/p/lilypond/issues/detail?id=1767 > > (No comment was entered for this change.) -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Part_combine_iterator::last_playing_ not initialized
On Sun 21 Aug 2011, 02:44 Dan Eble wrote:
> % valgrind reports that a member of Part_combine_iterator is used
> % before being initialized. Initializing last_playing_ = SOLO1 in
> % the constructor makes the warning go away.
> \version "2.14.2"
>
> \partcombine { s } { s }
Added this as 1829:
http://code.google.com/p/lilypond/issues/detail?id=1829
Thank you!
On Mon 22 Aug 2011, 00:14 Graham Percival wrote:
> IMO, please push any patch that initializes variables as long as
> they don't break a regtest. In the worst case, you would just
> introduce a reproducible bug, instead of having us "rely" on
> having an uninitialized variable.
>
> (if you notice broken regtests as a result of your patch, then
> let's discuss it before pushing)
Ha-ha, I've decided that type-defect and _security_ are the best for this
issue. I am in doubt. _Performance_? -- not sure. Anything else? What?-)
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: convert-ly myfile.ly > mynewfile.ly
On Wed 17 Aug 2011, 19:43 Patrick Schmidt wrote: > Hi all, > > by accident I noticed that when you try to upgrade a file (to version > 2.14.2) that is already up to date (2.14.0) with > > convert-ly myfile.ly > mynewfile.ly > > a new but empty file is created. There aren't any error messages. When you > fake an older version number everything works out and a new file (with > content) is created. Thank you, added as 1825: http://code.google.com/p/lilypond/issues/detail?id=1825 -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: More \quoteDuring problems, with and without \partcombine
On Wed 17 Aug 2011, 02:48 Keith OHara wrote:
> > > In particular, if you change your file to (notice the added \new Voice):
> > > staffFlute = \new Staff \new Voice {
> > > then everything works just fine.
> >
> > How is this not a bug? Or is that not what you're saying?
> >
>
> It is a bug. I think it is warned about in the manual, but will
> need to check. The natural response to problems is to first help the
> user who is stuck, but eventually some nice person will come along and
> put the bug(s) on a list of things to fix, or at least warn people about.
Thank you all for the discussion.
About the topic -- I found a warning here:
http://lilypond.org/doc/v2.15/Documentation/notation/writing-parts#quoting-other-voices
%--8<--
Only the contents of the first Voice occurring in an \addQuote command will be
considered for quotation, so the music expression must not contain \new and
\context Voice statements which would switch to a different Voice. Quoting
grace notes is unsupported and may cause LilyPond to crash whereas quoting
nested triplets may result in poor notation.
%--8<--
If it is related to the topic -- it should be corrected to mention
\quoteDuring also, shouldn't it?
If not -- another warning should be added.
Please, let me know. Thanks!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: --png does not properly obey landscape setting
On Mon 15 Aug 2011, 14:03 Reinhold Kainhofer wrote: > Am Monday, 15. August 2011, 13:22:33 schrieb Dmytro O. Redchuk: > > On Sun 14 Aug 2011, 22:22 Reinhold Kainhofer wrote: > > > If one uses landscape setting, i.e. > > > #(set-global-page-size "a4" 'landscape) > > > then the output of "lilypond --png landscape.ly" will NOT be landscape > > > (90 degree rotation is missing). > > > The PDF file has the proper rotation. > > > > Should 413 be reopened? Or rather "reincarnated"? > > > > http://code.google.com/p/lilypond/issues/detail?id=413 > > It's a different issue. The image extent seems correct, just the rotation is > missing. Thank you, added as 1819: http://code.google.com/p/lilypond/issues/detail?id=1819 -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: --png does not properly obey landscape setting
On Sun 14 Aug 2011, 22:22 Reinhold Kainhofer wrote: > If one uses landscape setting, i.e. > #(set-global-page-size "a4" 'landscape) > then the output of "lilypond --png landscape.ly" will NOT be landscape (90 > degree rotation is missing). > > Attached is a sample file landscape.ly. Run it with > lilypond --png landscape.ly > and you will get a png like the attached one. While the staves are properly > layed out, the final png is missing the 90 degree rotation (i.e. the staves > do > not got from left to right, but from bottom to top). The PDF file has the > proper rotation. Should 413 be reopened? Or rather "reincarnated"? http://code.google.com/p/lilypond/issues/detail?id=413 Thank you! -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Inconsistent baseline-skip in markups with multi-rows commands
On Sun 14 Aug 2011, 13:38 Bertrand Bordage wrote:
> Hi,
>
> In such examples, baseline-skip doesn't behave as expected:
Added by Bertrand as 1818:
http://code.google.com/p/lilypond/issues/detail?id=1818
(just for the record)
> %%
> #(set-default-paper-size "a9")
> \markuplines {
> \justified-lines { a a a a a a a a a a a a }
> "a" }
> %%
>
> I think this would be avoided if multi-rows commands were really creating a
> new markup for each line instead of making a single markup.
> A fix for this may probably require a lot of downstream changes.
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Misleading autobeaming in 3/4
On Sun 14 Aug 2011, 15:20 Phil Holmes wrote:
> "Phil Holmes" wrote in message
> news:j28lct$52o$1...@dough.gmane.org...
> >"Bertrand Bordage" wrote in message
> >news:cae7-6udnowlhzt+6cc-t9m8lohmsoctq2xmjwj7jvdxbrbo...@mail.gmail.com...
> >>Hi again,
> >>
> >>There's a small defect in autobeaming:
Added by Phil as 1817:
http://code.google.com/p/lilypond/issues/detail?id=1817
(just for the record)
> >>%%%
> >>\markup "This:"
> >>\relative c'' { \time 3/4 a4. b8 c d e d c b4. a8 b c d c b a2. }
> >>\markup "looks like 6/8:"
> >>\relative c'' { \time 6/8 a4. b8 c d e d c b4. a8 b c d c b a2. }
> >>\markup "but should be like this:"
> >>\relative c'' { \time 3/4 a4. b8\noBeam c d e d c\noBeam b4. a8 b c d c b
> >>a2. }
> >>%%%
> >>
> >>Unfortunately, I don't think this can be easily fixed with the current
> >>system.
> >>
> >>Regards,
> >>Bertrand
> >
> >Gardner Read gives the "correct" beaming pattern for 3/4 to be 6
> >beamed quavers, so the implication is that any available quavers
> >are beamed. Gotta say that seems wrong to me, but can we wait
> >until a beaming guru comments before raising this as an issue?
> >
> >--
> >Phil Holmes
> >Bug Squad
>
> Stay that - I've just found the correct bit of Gould (page 153),
> where she's clear it shouldn't look like this (and I've seen Carl's
> comment). I'll raise this as an issue.
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs and PhrasingSlurs with simultaneous start or end
On Thu 28 Jul 2011, 13:49 Nick Payne wrote:
> The automatic positioning of Slurs and PhrasingSlurs that both
> either start or finish on the same note is not very good. See below.
> Commercial scores that I have where this happens position the two
> slurs so that they don't intersect or touch, as in the second bar
> where the PhrasingSlur has been tweaked so that it doesn't intersect
> the slur:
I guess this is 304:
http://code.google.com/p/lilypond/issues/detail?id=304
And may be related to:
http://code.google.com/p/lilypond/issues/detail?id=163
> \version "2.14.0"
>
> offsetPhrasingSlurPos =
> #(define-music-function (parser location offsets) (pair?)
> #{
>\once \override PhrasingSlur #'positions = #(lambda (grob)
> `(,(+ (car $offsets) (cdar
> (ly:phrasingslur::calc-control-points grob))) .
>,(+ (cdr $offsets) (cdr (cadddr
> (ly:phrasingslur::calc-control-points grob))
> #})
>
> \relative c'' {
> \time 3/4
> \slurDashed
> c16\(( d) e f g8\) c,8 d16\(( c) b a\)
> \offsetPhrasingSlurPos #'(0.3 . 0) c16\(( d) e f g8\) c,8
> \offsetPhrasingSlurPos #'(0.3 . 0) d16\(( c) b a\)
> }
>
>
> Nick
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Completion_rest_engraver fails with fractional rests
On Thu 21 Jul 2011, 13:43 m...@apollinemike.com wrote:
> On Jul 21, 2011, at 1:37 PM, Dmytro O. Redchuk wrote:
>
> > On Thu 21 Jul 2011, 13:20 m...@apollinemike.com wrote:
> >> \new Voice
> >> \with { \remove "Rest_engraver" \consists "Completion_rest_engraver" }
> >> { r1*6/4 r2 }
Thank you, added as 1772:
http://code.google.com/p/lilypond/issues/detail?id=1772
> >> This gets me the attached output.
> > Please, what's the expected output?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Completion_rest_engraver fails with fractional rests
On Thu 21 Jul 2011, 13:20 m...@apollinemike.com wrote:
> \new Voice
> \with { \remove "Rest_engraver" \consists "Completion_rest_engraver" }
> { r1*6/4 r2 }
>
> This gets me the attached output.
Please, what's the expected output?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ties colliding in single-staff polyphony
On Mon 18 Jul 2011, 11:00 Bertrand Bordage wrote: > Could not there be more code in common between ties and slurs? Oh, sorry!-) I don't know, really. > A tie isn't so different from a slur, is it ? > By doing so, we could get rid of TieColumn and many bugs. > Do you think that keeping just the slur scoring and an hypothetic > slur_collision_engraver would do the job? -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ties colliding in single-staff polyphony
On Mon 18 Jul 2011, 11:34 I wrote:
> On Mon 18 Jul 2011, 10:14 Bertrand Bordage wrote:
> > Hi all,
Please, take look at Issue 458, it seems to describe exactly your case.
Thanks!
> > A bug I noticed years ago :
> >
> > <<
> > { a'4~ a' a'~ a' ~ } \\
> > { c' c' c' c' } \\
> > { f'~ f' \shiftOff f'~ f' } \\
> > >>
> >
> > Ties should take noteheads from other contexts into account.
> Please send us a tiny example.
>
> (Is three voices really needed? Can this issue be demonstrated with single
> pitches/chords only? Is \shoftOff necessary to demonstrate the problem?
> Please, this guide can help you: http://lilypond.org/tiny-examples.html )
>
> Thanks!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ties colliding in single-staff polyphony
On Mon 18 Jul 2011, 10:14 Bertrand Bordage wrote:
> Hi all,
Hi!
> A bug I noticed years ago :
>
> <<
> { a'4~ a' a'~ a' ~ } \\
> { c' c' c' c' } \\
> { f'~ f' \shiftOff f'~ f' } \\
> >>
>
> Ties should take noteheads from other contexts into account.
Please send us a tiny example.
(Is three voices really needed? Can this issue be demonstrated with single
pitches/chords only? Is \shoftOff necessary to demonstrate the problem?
Please, this guide can help you: http://lilypond.org/tiny-examples.html )
Thanks!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc: Usage 5.5, wrong file name in snippet
On Sun 17 Jul 2011, 23:39 Federico Bruni wrote: > In the second snippet of code: > > %%% top of file "symphony-cello.ly" > \include ../definitions.ily > \include ../Notes/cello.ily > > ../definitions.ily > should be replaced by > ../symphonyDefs.ily > > because definitions.ily is not in the directory tree Thank you, I've added this as 1769: http://code.google.com/p/lilypond/issues/detail?id=1769 -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \displayLilyMusic causes error with \addFingering from LSR 768
On Thu 14 Jul 2011, 07:58 -Eluze wrote:
> this code
>
> \version "2.15.5"
> \displayLilyMusic { \addFingering a #"-5" }
>
> reports in the log:
>
> GNU LilyPond 2.15.5
> Processing `test.ly'
> Parsing...ERROR: No applicable method for #< map (0)> in
> call (map # #f)
>
> without \displayLilyMusic it works.
I've added this as 1764:
http://code.google.com/p/lilypond/issues/detail?id=1764
Thank you!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.14.2
On Thu 14 Jul 2011, 16:30 Urs Liska wrote: > But OTOH one could also argue to leave such issues completely > unverified if you can't verify them completely. I believe there is nothing wrong in either "verifying partially" or leaving untouched until mentioned binary release occurs. We are now doing exactly that (waiting for 2.14.2) :-) (Particularly, today is "my day", and I've already verified all issues which were -- as for me -- "ready" for verifying). Thank you for your effort, anyway!-) ps. We will have some GOP discussion regarding issues, won't we? So, I think, we should save some energy for that discussion ,) -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura)
On Wed 13 Jul 2011, 18:54 lilyp...@googlecode.com wrote: > > Comment #20 on issue 75 by carl.d.s...@gmail.com: Slurs cannot be > nested (including acciaccatura and appoggiatura) > http://code.google.com/p/lilypond/issues/detail?id=75 > > Scratch those commits. In order to make every commit build the > baseline, I've done a rebase that includes both commits. > > New commit is > > ebdea7566554c26f752de6c2bef25df47ec3ee42 Thank you Reinhold and Carl! Still waiting to verify this in 2.14.2 :-) -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issues regarding too-short-tie
Hi! As I can see, these issues are the same very probably: * http://code.google.com/p/lilypond/issues/detail?id=298 * http://code.google.com/p/lilypond/issues/detail?id=840 * http://code.google.com/p/lilypond/issues/detail?id=1219 If yes, I would leave the first, marking others as duplicates. Please, any thoughts? -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative
On Fri 08 Jul 2011, 00:14 Nicolas Sceaux wrote:
> Le 7 juil. 2011 à 12:13, lilyp...@googlecode.com a écrit :
>
> >
> > Comment #3 on issue 1747 by brownian.box: parallelmusic problem: q-notation
> > does not work in \relative
> > http://code.google.com/p/lilypond/issues/detail?id=1747
> >
> > Probably, this is the issue of chord repetition in relative mode:
> >
> > \version "2.15.4"
> >
> > % should be identical:
> > \new Voice {
> > \relative c'' { g, q q }
> > \relative c'' { g, q }
> > }
>
> Could you explain why the two ought to be identical?
> From what `q' is for (*repeating* a chord), reading this snippet I'd conclude
> that they shall produce different results, as the repeated chord is not the
> same
> in both cases (the second does not have the same octave as the first
> one).
>
> `q' is not a textual macro. It is really for repeating the very same chord
> (with
> the same octave).
I deduced that .)
http://lilypond.org/doc/v2.14/Documentation/notation/single-voice.html#chord-repetition
"The chord repetition symbol always remembers the last instance of a chord so
it is possible to repeat the most recent chord even if other non-chorded notes
or rests have been added since."
I am not sure, thought. Please, don't mind. I should test it more in relative
mode, probably.
> [1747 is indeed a duplicate for 1110, but this is orthogonal from the
> above case.]
Thank you!
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Switcing accidental style doesn't always work
On Thu 07 Jul 2011, 17:24 Ole Vedel Villumsen wrote: > Only I feel this information is perhaps lacking from the docs. I would have > expected the full story to be in > http://lilypond.org/doc/v2.14/Documentation/notation/displaying-pitches#automatic-accidentals, > or at least a reference to it. Am I expecting too much, or does the > documentation need more precision? Very probably the documentation does need more precision! Why not, after all?-) Please, feel free to send your suggestions as described here: http://lilypond.org/doc/v2.15/Documentation/contributor/documentation-suggestions Thank you! > I see now that the docs only say to call set-accidental-style right in the > beginning of Staff << ... >>, which I didn't follow. But you, Neil, shows that > it does work elsewhere. -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Possible regression in 2.13 series? "no viable configuration" warning
On Sun 24 Apr 2011, 18:51 Valentin Villenave wrote: > On Wed, Apr 20, 2011 at 4:47 PM, m...@apollinemike.com > wrote: > > That said, the following code still produces the same message: Hi, Valentin! Yes, indeed, sorry for so late reply .) > Greetings everybody, hi Mike, > > Since there's a lot of activity wrt beaming code these days, I'm > wondering whether the possible regression I mentioned earlier is > likely to evolve (for better or for worse), and/or if I'd better open > a tracker page about it. (Or perhaps it could be related to #1613 or > #1619, for all I know.) Now there is 1702, "Unaesthetic beam slope", which reflects this situation, I believe: http://code.google.com/p/lilypond/issues/detail?id=1702 I mean that including into your code this \override \override StaffGrouper #'staff-staff-spacing #'basic-distance = #10.5 causes message to disappear. -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Many single-system scores produces bad output and overflow
On Wed 06 Apr 2011, 16:17 Xavier Scheuer wrote:
> It seems single-line (single-system) scores prevent _totally_ page
> breaks and thus produce overflow and bad output.
Hi, Xavier!
Sorry for so late reply, I've been flagged your message on Wed 06 Apr 2011,
actually .)
Anyway: this is issue 1286:
http://code.google.com/p/lilypond/issues/detail?id=1286
Page breaking works fine when I replace all your "a"s with "a1".
> IMHO beginning of a score at the end of a page should have assigned a
> "bad factor" penalty but should not prevent completely page breaks to
> occur.
>
>
> %% Reported by Bertrand Bordage on the French users mailing list
> %%
> %% Many "single-system" scores on one page produces bad output and
> %% overflow.
> %% Note that 2.12 did not handle it and produced even worse output
> %%
>
> \version "2.13.57"
> \book {
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> }
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: accidentaled notes too far from the barline
On Mon 14 Feb 2011, 08:43 Janek Warchoł wrote:
> hi,
Hi, Janek,)
> The amount of whitespace after the barline is fixed, while it should depend
> on whether the first note in the measure has an accidental or not. This
> results in notes being too far from the barline, especially when there is
> only one note in measure:
>
> { c'4 d' g' f' e'2 a' d'1 }
> { c'4 d' g' f' es'2 a' dis'1 }
>
> I attach another example with engraved reference. It was made with an old
> version of LilyPond, but the behaviour is the same.
> When compiled with 2.13.49, the amount of whitespace after the barline is
> generally smaller, but still isn't corrected for accidental.
Sorry for somewhat late reply (this message have been flagged in my mailbox
since Mon 14 Feb 2011) -- if you consider this issue as still unresolved,
please let me know. Thanks!
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: parallelmusic problem: q-notation does not work in \relative
On Wed 06 Jul 2011, 15:05 Arno Waschk wrote:
> dear list,
>
> the following
>
> \version "2.15.4"
> \parallelMusic #'(abc def) {
> 2 q|
> 2 q|
> % 2 2 |
> % 2 2 |
> }
>
> \new Staff {<<
> \relative c'' \abc
> \relative c' \def
> >>}
>
>
> does not produce the desired result, since the second "chord" is one
> octave lower then the first.
> it does work when processing the commented lines instead.
I've added this as 1747:
http://code.google.com/p/lilypond/issues/detail?id=1747
I've modified your example a bit -- please, take a look and correct me, if I
am wrong .)
Thank you!
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: v2.13.48 docball adds offline-root/ directory...
On Tue 05 Jul 2011, 13:01 Jan Nieuwenhuizen wrote: > > ...and thus breaks documentation links, notably info pages. > This will probably happen in all binary builds, it happens > in GUB. > > 12:54:19 janneke@abc:/var/www/lilypond/download/binaries/documentation > $ tar taf lilypond-2.13.47-1.documentation.tar.bz2 | grep /examples.html > ./share/doc/lilypond/html/examples.html > ./share/doc/lilypond/html/Documentation/web/examples.html > 12:56:23 janneke@abc:/var/www/lilypond/download/binaries/documentation > $ tar taf lilypond-2.13.48-1.documentation.tar.bz2 | grep /examples.html > ./share/doc/lilypond/html/offline-root/examples.html > ./share/doc/lilypond/html/offline-root/Documentation/web/examples.html > 12:58:58 janneke@abc:/var/www/lilypond/download/binaries/documentation > > With this change, quite possibly we need all distribution maintainers to > update/change their build scripts. Is this intentional? Can > this be reverted? Do we need to warn package maintainers (how?). I've added this as 1746: http://code.google.com/p/lilypond/issues/detail?id=1746 Thank you! -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tuplet number on cross-staff kneed-beam
On Thu 07 Jul 2011, 10:33 I wrote: > On Tue 05 Jul 2011, 23:22 David Nalesnik wrote: > > I've also attached a pared-down version of the file which should work > > in either release, as is. It distills the problem a little more -- at > > the expense of centering the number directly on the beam . . . > > > > I hope that in some way this is useful :) > I've added this as 1745: > http://code.google.com/p/lilypond/issues/detail?id=1745 For the record -- tuplet number placement is a subject of issue 696: http://code.google.com/p/lilypond/issues/detail?id=696 -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tuplet number on cross-staff kneed-beam
On Tue 05 Jul 2011, 23:22 David Nalesnik wrote: > Hi, Colin -- > > On 7/5/11, Colin Campbell wrote: > > > > This will probably require an issue, David, but could you send the code > > you used to produce the 2.12.3 version, please? I can't reproduce the > > previous stable example, in order to confirm the regression, because > > your Scheme-ing gives an error: > > LilyPond 2.12.3 [music.ly] starting (preview mode)... > > Processing `music.ly' > > Parsing... > > Interpreting music... > > Preprocessing graphical objects... > > Finding the ideal number of pages... > > Fitting music on 1 page... > > Drawing systems...music.ly:19:12: In procedure + in expression (+ > > (ly:grob-property beam #) (/ # 2)): > > music.ly:19:12: Wrong type argument in position 1: () > > LilyPond [music.ly] exited with return code 1. > > > Oops -- yes, the error happened because 'thickness is now > 'beam-thickness. I've attached the file I used for the 2.12.3 image. > > I've also attached a pared-down version of the file which should work > in either release, as is. It distills the problem a little more -- at > the expense of centering the number directly on the beam . . . > > I hope that in some way this is useful :) I've added this as 1745: http://code.google.com/p/lilypond/issues/detail?id=1745 Thank you! -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 153 in lilypond: \once \set fails to restore previous setting
On Wed 06 Jul 2011, 14:00 -Eluze wrote: > actually i don' feel like discussing time problems with the technical > approach to \set properties. if Lilypond cannot do it then let's live with > it and forget about \once \set in conjunction with fingeringOrientations or > others. > > of course then the documentation should not mention the pointless > possibility of using \once \set - or are there other situations where it > makes sense? > > > also i'd like to come back to one point that nearly vanished during this > discussion: > > it would be very practical if one could define fingeringOrientations per > voice (and not on the Score level). the advantage: if you once change the > fingerin policy - e.g. from left to right - you can \unset this and > automatically the Voice setting would be recovered - this is much easier > than redefining the voice specific fingeringOrientations. > > can this be taken as a feature/enhancement request? I've added 1744: http://code.google.com/p/lilypond/issues/detail?id=1744 Now issue 153 already _is_ an enhancement request. May be, it appears invalid after some (more or less possible) discussion. Let's wait a bit. Thank you! -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Switcing accidental style doesn't always work
On Mon 04 Jul 2011, 18:20 Ole Vedel Villumsen wrote:
> > I'm not top posting.
>
> In a piano composition I chose #(set-accidental-style 'piano-cautionary), but
> a
> few of the reminders (cautionary accidentals) seemed more confusing than
> helpful. I thought I could switch to 'default. I could, it worked; but then I
> couldn't switch back to 'piano-cautionary again.
>
> Example:
>
> \version "2.14.1"
>
> \relative c' {
> \time 4/4
>
> #(set-accidental-style 'piano-cautionary)
> gis'1 g % gives natural in brackets as expected
> #(set-accidental-style 'default)
> dis d% no accidental before d; as expected
> #(set-accidental-style 'piano-cautionary)
> ais' a % expected natural in brackets before a, didn't get
> }
This way it works:
\relative c' {
\time 4/4
#(set-accidental-style 'piano-cautionary 'Staff)
gis'1 g
#(set-accidental-style 'default 'Staff)
dis d
#(set-accidental-style 'piano-cautionary 'Staff)
ais' a
}
And it seems to me, it should work exactly this way?
NR says:
% -8<--
This function is called as follows:
\new Staff <<
#(set-accidental-style 'voice)
{ … }
>>
The accidental style applies to the current Staff by default [...]
% -8<--------------
So, it it called "at Staff level", or so.
I don't know why it works with 'default in your sample, thought.
I can be wrong; let's discuss more before submitting an issue report.
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: quarter-tone tablature bug
On Tue 05 Jul 2011, 23:14 Bernardo Barros wrote:
> > I'm not top posting.
>
> (Sorry, I didn't know I should have sent the bug report to this list instead
> of
> the google code bug tracker)
I have updated your report in the tracker:
http://code.google.com/p/lilypond/issues/detail?id=1741
Thank you for your effort.
> In the Following code, the `string 2' is tuned to `beh'.
> The bug sets bih *and* cih to fret 1 on that same string,
> and all other notes are not correctly set,
> the tablature is always one fret down from the third note on.
>
> Trying more variants I find it does have nothing to do with the pitch beh,
> but
> maybe setting a quarter-tone tune to the second string will always triggers
> the
> bug?
>
> Also tested with git version from 27/jun/2011.
>
>
>
> \makeStringTuning #'custom-tuning
>
> notes = {
> beh\2 bih\2 cih'\2 deh'\2 dih'\2 eeh'\2
> }
>
> \score {
> <<
> \new Staff {
> \clef "treble_8"
> \notes
> }
> \new TabStaff {
> \set TabStaff.stringTunings = #custom-tuning
> \notes
> }
> >>
> }
>
>
>
>
> Changing the second string from beh to aeh is also buggy:
>
>
>
> \makeStringTuning #'custom-tuning
>
> notes = {
> beh\2 bih\2 cih'\2 deh'\2 dih'\2 eeh'\2
> }
>
> \score {
> <<
> \new Staff {
> \clef "treble_8"
> \notes
> }
> \new TabStaff {
> \set TabStaff.stringTunings = #custom-tuning
> \notes
> }
> >>
> }
>
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: after \once \set fingeringOrientations… Lilypond falls back to #up
On Mon 04 Jul 2011, 14:17 -Eluze wrote:
> Dmytro O. Redchuk-2 wrote:
> >
> > pps. Let's continue with "\once \set" issue.
> >
> sure - i'll try to summarize:
>
>
> \set deals with context properties
> \override deals with grob properties
> \override stacks the previous settings and recalls them when \once is used
> \revert falls back to the "original" settings (whatever this means)
> \set does not stack the previous (changed) settings so it does not fall back
> on those when \once is used
> \unset falls back to the original settings as well
I've added this as issue 1740:
http://code.google.com/p/lilypond/issues/detail?id=1740
Thank you!
>
>
>
> now there is a problem when you define your own context properties:
>
> fingeringOrientations are defined at the \Score level; even if you define a
> different list in the \voice level, after a \unset or \once \set the
> fallback will go to the original \Score definitions.
>
> this is not very helpful when you write guitar notes which often need 3 (or
> even more) polyphonic voices:
>
> often you will put the bass, discant and the notes between into three
> different voices and use a different fingering policy for each: the bass
> gets the fingering below, the discant above and the notes between are
> fingered on the left (or right). you can define this in a \with or \layout
> {\context … }command
>
> sometimes you have to change this policy (there are many reasons for such a
> temporary change) - that's life (or music)!
>
> and that's where the lack of stacking the previous settings becomes
> disastrous: you have to redefine what you thought was defined for the rest
> of the voice; what you had defined for the voice is overridden and has gone.
>
> the \once becomes some kind of "shortcut" for "\set it for the next
> espression and then forget all the previous settings" - except for the high
> level definition.
>
>
>
> hope this does not sound to pessimistic but shows what is needed from a
> practical view. i wouldn't qualify the actual situation as buggy but
> certainly worth to be thought over, documented or even changed!
>
> in any case - if i missed something please let me know!
>
> cheers
>
> Eluze
>
>
>
> --
> View this message in context:
> http://old.nabble.com/after-%5Conce-%5Cset-fingeringOrientations%E2%80%A6-Lilypond-falls-back-to--up-tp31987692p31992608.html
> Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Mon 04 Jul 2011, 17:15 I wrote:
> On Mon 04 Jul 2011, 16:17 I wrote:
> > For windows I would try to start with .cmd like this:
> This seems to work (tested under VirtualBox, WinXP):
Sorry for the noise, final ("initial") version is so far:
rem --8<--
@echo off
rem
rem -- trimtagline.bat --
rem
rem -- Get only file name, no extension:
set LY=%~n1
IF filename%LY%==filename (
echo Usage: %0 test[.ly].
) ELSE (
echo \header { tagline = ##f } | lilypond -dinclude-settings=- --png
%LY%
rem -- This is ImageMagick's "convert.exe":
imconvert %LY%.png -trim %LY%-trim.png
)
rem
rem -- Note, you need to copy/rename convert.exe
rem -- to something like imconvert.exe
rem -- because windows already has convert.exe in the path.
rem
rem
rem -- Note, if you can not (or do not want to) install ImageMagick,
rem -- you can use this "kind of trimming":
rem echo \header { tagline = ##f } | lilypond -dinclude-settings=-
-dbackend=eps -dno-aux-files --png %LY%
rem
rem -- This will produce "almost as vertically trimmed as above" png,
rem -- but leave full "linewidth".
rem
rem --8<--
I've added it to my fork and will ask Graham to pull it in some future,
I guess.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Mon 04 Jul 2011, 16:17 I wrote:
> For windows I would try to start with .cmd like this:
This seems to work (tested under VirtualBox, WinXP):
rem 8<--
rem trimtagline.bat
rem
rem get only file name, no extension:
set LY=%~n1
echo \header { tagline = ##f } | lilypond -dinclude-settings=- --png %LY%
imconvert %LY%.png -trim %LY%-trim.png
rem 8<--
Note, you need to copy/rename convert.exe to something like imconvert.exe
because windows already has convert.exe in the path.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Mon 04 Jul 2011, 15:19 Neil Puttock wrote: > On 4 July 2011 15:16, Neil Puttock wrote: > > > Ah, I didn't notice that (though it only applies to single-system > > snippets where you'd usually use -dpreview). > > Silly me. Of course, with ragged-right = ##t the same applies to > multi-system snippets. :) Anyway, I'll add your suggestion to comments in the script (win version) -- it can be useful for those who can not (does not want to) install IM. Thank you! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Mon 04 Jul 2011, 14:48 Neil Puttock wrote:
> On 4 July 2011 14:17, Dmytro O. Redchuk wrote:
>
> > I've not tested! I have no any windows (with lilypond and ImageMagick)
> > about.
>
> You don't need ImageMagick. The eps backend will produce a trimmed
> png (assuming the tagline's been removed):
>
> echo "\\header { tagline = ##f }" | lilypond -dinclude-settings=-
> -dbackend=eps -dno-aux-files --png $ly
Thank you for suggestion!
But this gives "wide" image, with a width of paper, I guess. (And some extra
space at top... and bottom).
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Mon 04 Jul 2011, 07:06 Colin Campbell wrote:
> Sorry for the delay, Dmytro! I was trying to find a bit of time to
> test whether it, or a slightly different version, would work under
> Windows. The convert command comes from ImageMagik which seems to
> have a Windows binary available.
For windows I would try to start with .cmd like this:
rem ---8<-
set LY=%~n1
echo "\\header { tagline = ##f }" | lilypond -dinclude-settings=- --png %LY%
# trim PNG:
convert %LY%.png -trim %LY%-trim.png
rem ---8<-
I've not tested! I have no any windows (with lilypond and ImageMagick) about.
> Anyway, I'll make up a patch at the office today, Dmytro.
Thank you!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: after \once \set fingeringOrientations… Lilypond falls back to #up
On Mon 04 Jul 2011, 05:15 -Eluze wrote:
> \version "2.15.2"
>
> \layout {
> \context {
> \Score
> fingeringOrientations = #'right
> }
> }
> { }
>
> if i have no fingering it does not crash!
>
> cheers
> Eluze
Thank you, added as 1734:
http://code.google.com/p/lilypond/issues/detail?id=1734
ps. I tagged this as Critical. May be this is too high (because of incorrect
syntax?); anyway, I've decided it would be right.
pps. Let's continue with "\once \set" issue.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: after \once \set fingeringOrientations… Lilypond falls back to #up
On Mon 04 Jul 2011, 04:22 -Eluze wrote:
> btw: writing fingeringOrientations = #'right brings Lilypond to crash!
It does not here (ubuntu linux 64bit):
$ cat test.ly
\relative {
\once \set fingeringOrientations = #'right
< e -1>
}
$ LANG=C lilypond test.ly
GNU LilyPond 2.14.1
Processing `./test.ly'
Parsing...
./test.ly:0: warning: no \version statement found, please add
\version "2.14.1"
for future compatibility
Interpreting music...
warning: type check for `fingeringOrientations' failed; value `right' must be
of type `list'
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
success: Compilation successfully completed
ps. Regarding "\once \set"’s behavior -- probably, it can be valid issue (to
change this behavior), but I feel like similar discussions already have been;
I need some time to search, I guess.
Let's wait some time (while I'm searching,) for possible feedback from
developers.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Thu 23 Jun 2011, 14:19 Graham Percival wrote: > Colin: add this to the CG (since Dmytro isn't trained in making > patches). Hi! Please, Colin, would you add this to the CG? I guess, to "8.5 Adding issues to the tracker" :) http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker The script is here now: https://raw.github.com/gperciva/lilypond-extra/master/bug-squad/trimtagline.sh Thanks! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Odd-looking tie on a chord
On Mon 04 Jul 2011, 15:39 James Harkins wrote:
> \version "2.14.1"
>
> \include "english.ly"
>
> \score {
> \new Staff {
> \key d \major
> \numericTimeSignature
> \time 4/4
> r4
> \times 4/5 { 16\< b''>~ }
> 16 8.
>
> %% Here: the tie on the D's looks funny
> %% Too tall? Left-hand endpoint is not aligned with the B tie?
> ~
>
> 8 [ ->\mf ]
> }
> }
>
> It looks even funnier at lower resolution, somewhat better when viewed up
> close.
>
> I'm aware of \override TieColumn #'tie-configuration but would just as soon
> avoid it if possible.
I found this is an instance of known issue, 1126:
http://code.google.com/p/lilypond/issues/detail?id=1126
I have added your example there thougth.
Thank you!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: after \once \set fingeringOrientations… Lilypond falls back to #up
On Mon 04 Jul 2011, 01:43 -Eluze wrote:
> the code
>
> \relative {
> \set fingeringOrientations = #'(left)
> < e -1>1 |
> \once \set fingeringOrientations = #'(right)
> < e -1> |
> < e -1> |
> }
>
> produces
> http://old.nabble.com/file/p31987692/chord%2Bfingering%2Bsmall.jpg
>
>
> imo the fingering in the 3rd "chord" should be at the left of the note.
> the way it works now the use of \once is needless because you must reset the
> fingeringOrientation to whatever you had defined before!
As far as I can see, "\once \set" actually does "\set and then \unset". Very
probably this is exactly what it should to do.
So, this is rather an issue and should be documented?
I would add this to this, at the very bottom:
http://lilypond.org/doc/v2.14/Documentation/notation/the-set-command
Please, anyone? Any other thoughts?
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: occasional segfault when compiling input/regression/midi/key-initial.ly
ppets -I > /home/fede/lilypond-master/input/regression/ -I > /home/fede/lilypond-master/Documentation/included/ -I > /home/fede/lilypond-master/build/mf/out/ -I > /home/fede/lilypond-master/build/mf/out/ -I > /home/fede/lilypond-master/Documentation/pictures -I > /home/fede/lilypond-master/build/Documentation/pictures/./out-test > -dbackend=eps --formats=ps -dseparate-log-files -dinclude-eps-fonts > -dgs-load-lily-fonts --header=texidoc -I > /home/fede/lilypond-master/Documentation/included/ -ddump-profile > -dcheck-internal-types -ddump-signatures -danti-alias-factor=1 -I > "/home/fede/lilypond-master/build/out/lybook-testdb" -I > "/home/fede/lilypond-master/build/input/regression" -I > "/home/fede/lilypond-master/input/regression" -I > "/home/fede/lilypond-master/build/input/ > regression/out-test" -I "/home/fede/lilypond-master/input" -I > "/home/fede/lilypond-master/Documentation" -I > "/home/fede/lilypond-master/Documentation/snippets" -I > "/home/fede/lilypond-master/input/regression" -I > "/home/fede/lilypond-master/Documentation/included" -I > "/home/fede/lilypond-master/build/mf/out" -I > "/home/fede/lilypond-master/build/mf/out" -I > "/home/fede/lilypond-master/Documentation/pictures" -I > "/home/fede/lilypond-master/build/Documentation/pictures/out-test" > --formats=eps -deps-box-padding=3.00 -dread-file-list > -dno-strip-output-dir > "/home/fede/lilypond-master/build/out/lybook-testdb/snippet-names--1315969467.ly" > Child returned 139 > make[2]: *** [out-test/collated-files.texi] Error 1 > make[2]: Leaving directory `/home/fede/lilypond-master/build/input/regression' > make[1]: *** [local-test] Error 2 > make[1]: Leaving directory `/home/fede/lilypond-master/build/input/regression' > make: *** [test] Error 2 > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: DynamicTextSpanner collides with DynamicText
On Wed 29 Jun 2011, 13:21 Xavier Scheuer wrote:
> I'm surprised this issue seems not yet reported (at least I did not find
> it on the tracker).
>
> The example below is "extreme". I used 16th notes in order to show
> clearly the issue. It happens in "real-life" scores with more logical
> rhythm also.
>
> Ideally LilyPond should avoid the collision (I do not know what would
> be the proper way to do that). At least in the case where there is
> a collision, LilyPond should emit a warning!
> This issue might be related to issue #1089 .
>
> %% DynamicTextSpanner collides with DynamicText if the notes are close
> %% to each other.
> %%
Thank you, added as 1725:
http://code.google.com/p/lilypond/issues/detail?id=1725
> \relative c' {
> c4..\p c16\cresc c4..\f c16\cresc
> c1\ff
> }
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: DynamicTextSpanner inside Dynamics context are shifted due to pedal
On Wed 29 Jun 2011, 10:38 Xavier Scheuer wrote:
> %% DynamicTextSpanner inside a Dynamics context are shifted to the left
> %% if there is a Pedal inside another Dynamics context.
> %% That leads to really poor output of the DynamicTextSpanner, which
> %% are shifted left (compared to when they are well aligned without the
> %% pedal) and so colliding with the bar line.
> %%
> %% This is really an issue for every piano score (using the Dynamics
> %% context, i.e. centered dynamics and pedal on a horizontal line).
> %%
Thank you, added as 1724:
http://code.google.com/p/lilypond/issues/detail?id=1724
(I've modified your code a bit)
> \version "2.15.2"
>
> \score {
> <<
> \new PianoStaff <<
> \new Staff = "up" {
> \clef treble
> \repeat unfold 48 c'4
> }
> \new Dynamics = "dynamics" {
> \repeat unfold 2 {
> s1\cresc s1\f s1\dim s1\p
> }
> }
> \new Staff = "down" {
> \clef bass
> \repeat unfold 48 c4
> }
> \new Dynamics= "pedal" {
> \repeat unfold 4 {
> % comment the pedal and the DynamicTextSpanner are well
> % aligned in the Dynamics context above!
> s1\sustainOn s1\sustainOff
> }
> }
> >>
> >>
> }
>
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [translations] Doc: @snippets links are broken when translated
On Wed 29 Jun 2011, 23:46 James Lowe wrote:
> Hello,
>
> From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
> [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Valentin
> Villenave [valen...@villenave.net]
> Sent: 29 June 2011 23:45
> To: Jean-Charles Malahieude
> Cc: Translations list at lilynet; Lilypond Bugreports
> Subject: Re: [translations] Doc: @snippets links are broken when translated
>
> On Wed, Jun 29, 2011 at 7:42 PM, Jean-Charles Malahieude
> wrote:
> > Just because I use
> > @rlsrnamed{Keyboards, Claviers}
> > to have it labeled in French even if the target wont be translated.
>
> Clever. Then we'd probably need to harmonize this policy through the
> docs, since even in French the last link at the bottom of
> http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.fr.html
> doesn't use @rlsrnamed
>
> Is this policy advertised in the CG? I couldn't find it. (I could
> provide a patch but for now it's safer to open a tracker page if it's
> deemed worth one.)
>
>
>
> I struggled to find a coherent documentation policy/instruction for this
> (although I don't deal with translations).
>
> I don't think having a tracker open is a bad thing, and I'm happy to help
> pushing or editing the CG for whomever wants it.
Thank you, all, added as 1721:
http://code.google.com/p/lilypond/issues/detail?id=1721
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [informatique] Re: Full notes and half notes are drawn filled
On Mon 27 Jun 2011, 23:18 "Jérôme M. Berger" wrote: > I would say that it depends on whether the bug is with LilyPond > producing a wrong file (which Ghostscript 8.70 hides somehow) or > with Ghostscript 9.02 interpreting wrongly a correct file. If the > former, then I believe LilyPond should fix it (especially since > sooner or later you are going to want to upgrade the official > Ghostscript). If the latter, then either you or I need to report the > issue to Ghostscript so that they can fix it at their end. I do not > know enough about Postscript to tell which case applies here... Thank you! Added as 1717: http://code.google.com/p/lilypond/issues/detail?id=1717 On Mon 27 Jun 2011, 19:44 Graham Percival wrote: > Please add it as build-medium. We're probably not going to be > switching to ghoscript 9.0 for 2.16, but we'll probably try it in > 2.18, so if there's some incompatibility, it would be good to > start working on that now. -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [informatique] Re: Full notes and half notes are drawn filled
On Mon 27 Jun 2011, 19:40 "Jérôme M. Berger" wrote: > Dmytro O. Redchuk wrote: > > So, it is *not* your pdf viewer. > > > > Wich version do you use? -- I mean binary install or built from sources? > > > Binary install. The package description file is here if you want to > see the compilation options they used: > http://projects.archlinux.org/svntogit/community.git/tree/lilypond/repos/community-x86_64/PKGBUILD > > > As far as i can understand, no one can reproduce this issue so far. > > > > Can you send me that pdf (from above snippet) privately? > > > Follows in a separate email. Well.. Your pdf was produced with GPL Ghostscript 9.02, while mine (locally made) was produced with GPL Ghostscript 8.70 -- and 8.70 is the version of gs shipped with official lilypond 2.14.1 binary install. So, i guess, your pdf was produced, for some reason, with "external" gs, and this may cause the problem. Or, on the other hand, everything is ok, 9.02 was shipped with archlinux' package, but that package may be a kinda broken. What do you think? In any case i doubt this may be a valid issue (because of "foreign package" mentioned and unability to reproduce with official package). As far as I understood. -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [informatique] Re: Full notes and half notes are drawn filled
On Mon 27 Jun 2011, 19:24 "Jérôme M. Berger" wrote:
> Dmytro O. Redchuk wrote:
> > On Sat 25 Jun 2011, 08:31 Jérôme M. Berger wrote:
> >> Hi,
> >>
> >> With lilypond 2.14.1, full notes and half notes are drawn filled. For
> >> example
> >> given the following snippet:
> >>
> >> \score {
> >>\relative c'' { a1 a2 a4 }
> >> }
> >>
> >> The first note will be drawn completely black and the second and third
> >> notes are
> >> identical. The same snippet renders fine with version 2.12.3.
> > Everything is great here (ubuntu 64bit, all lilypond versions so far are
> > ok).
> >
> > May be, this is an issue of your pdf viewer?
> >
> I was using postscript output and gv, but pdf output gives the same
> results with okular and xpdf.
So, it is *not* your pdf viewer.
Wich version do you use? -- I mean binary install or built from sources?
As far as i can understand, no one can reproduce this issue so far.
Can you send me that pdf (from above snippet) privately?
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ligatures and ambits don't mix
On Mon 27 Jun 2011, 10:58 Laura Conrad wrote:
>
> The attached test file bombs with a segmentation fault in lilypond
> 2.14.1.
>
> If you comment out either the ambitus_engraver or the stuff about the
> ligature engravers, it compiles as expected.
Could you please prepare a tiny example?
(Please see http://lilypond.org/tiny-examples.html , "How do I create them?")
I have removed (commented out) a half of the code without any change in behavior
(\context { Staff ... } in \layout seems to be unneeded? what about
NoteHead/BarType/TimeSignature?)
Since i know *nothing* about ancient music, i can not be sure that my exercises
will produce valid tiny example.
Sorry, we should accept tiny examples only.
Thank you for your effort and contribution!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1
On Mon 27 Jun 2011, 05:33 Marc Payne wrote:
> Hi there.
Hi.
Thank you, I've added this as 1714:
http://code.google.com/p/lilypond/issues/detail?id=1714
> I haven't found any references to this problem on the mailing lists or
> elsewhere, so I hope my input is useful.
>
> On my Arch Linux system, fully up-to-date, with the latest texlive in Arch's
> testing repo, I get the following error when trying to build lilypond 2.14.1
> from source:
>
> "Sorry, I can't find the 'mf2pt1' preload file; will try 'plain'.This is
> MetaPost, version 1.504 (kpathsea version 6.0.1)"
>
> I am left with an mpost prompt.
>
> To hack around the problem, I had to make a minor change to
> scripts/build/mf2pt1.pl (line 429) in addition to the patch provided by Arch
> (http://goo.gl/5o1xs):
>
> - execute_command 1, ("mpost", "-mem=mf2pt1", "-progname=mpost",
> + execute_command 1, ("mpost", "-mem=../../mf2pt1", "-progname=mpost",
>
> Obviously this isn't a proper fix, but it allowed lilypond to compile and run.
>
> If you need more info, I'll be glad to provide it.
>
> Thanks! :)
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Full notes and half notes are drawn filled
On Sat 25 Jun 2011, 08:31 Jérôme M. Berger wrote:
> Hi,
>
> With lilypond 2.14.1, full notes and half notes are drawn filled. For example
> given the following snippet:
>
> \score {
>\relative c'' { a1 a2 a4 }
> }
>
> The first note will be drawn completely black and the second and third notes
> are
> identical. The same snippet renders fine with version 2.12.3.
Everything is great here (ubuntu 64bit, all lilypond versions so far are ok).
May be, this is an issue of your pdf viewer?
> ==> lilypond --version
> GNU LilyPond 2.14.1
>
> ==> uname -a
> Linux wraith 2.6.39-ARCH #1 SMP PREEMPT Mon Jun 6 22:37:55 CEST 2011 x86_64
> AMD
> Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
>
> Jerome
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Thu 23 Jun 2011, 06:48 Colin Campbell wrote:
> A problem arises when, as I suspect, the default behaviour is
> tagline = ##t, even when not explicitly stated in the \header block.
> IOW, the absence of "tagline = " doesn't mean absence of a tagline.
> The presence of the tagline means convert must include the entire
> page in the trimmed area, which defeats the purpose of the trim.
No, there is no problem, i guess.
If ly file does not contain tagline, lilypond inserts default tagline --
this one can be overriden by the script. And should be, for the tracker.
If ly file does contain tagline -- it either should not be overriden
("fortunately enough" that script can not override existing tagline)
or should be removed (for a particular test.ly, let's say).
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Wed 22 Jun 2011, 18:52 Colin Campbell wrote: > overridden if the tag exists in the destination file. Where a .ly > file already has the tagline set, it cancels the imported one. To Yes, right, imported tagline overrides default one only .) This is enough for most (all?) of tests however, isn't it? -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Wed 22 Jun 2011, 11:53 Graham Percival wrote:
> ok, how about this? Your script should:
> echo "\header { tagline = ##f } " > /tmp/lilypond-no-header.ly
. o O ( \\header, of course )
> lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --png bug.ly
> convert bug.png -trim bug-upload.png
>
> something like that. Could you test it, then we can have a set
> script for bug squad members (on linux and osx at least) to
> produce great pngs for the tracker?
I would start with this:
#!/bin/bash
#
#
ly=${1:?Usage: $0 test[.ly]}
# strip extension, if any:
lynoext=${ly%%.ly}
# process test file:
echo "\\header { tagline = ##f }" | lilypond -dinclude-settings=- --png $ly
# trim PNG:
convert ${lynoext}.png -trim ${lynoext}-trim.png
# do we want to overwrite "original" PNG?
# mv ${lynoext}-trim.png ${lynoext}.png
Do we need more options? For trimming "in place" or something else?
>
> Cheers,
> - Graham
On Wed 22 Jun 2011, 13:17 David Kastrup wrote:
> lilypond -dinclude-settings=<(echo "\header { tagline = ##f }") --png bug.ly
I does not work here; i don't know why.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> On Tue, Jun 21, 2011 at 12:52:01PM +0300, Dmytro O. Redchuk wrote:
> > In such cases I add
> > \header { tagline = "" }
> > to a source file and then:
> >
> > lilypond --png test.ly
> > convert test.png -trim test-trim.png
>
> Excellent!
>
> Could you write a short shell script to do this? i.e. using
> lilypond -e ...
> to remove the tagline (maybe that's already in LSR),
> and then call convert automatically? I'd really like to add this
> to the CG so that we have a simple way to generate images.
> (at least on non-windows machines)
As far as I can see, Phil asked how to remove the tagline from the comand
line*, but the answer was "it's impossible".
Another option, proposed by Valentin, was to use external file
(-dinclude-settings=...), but i would find this "inconvenient" for the build
system?
And... I'd be happy to appear wrong -- so, please, is this really possible
with scheme? I will search more if "yes" .)
> This would allow us to standardize on 1-page pngs (automatically
> trimmed) and multi-page pdfs, and avoid -dpreview entirely.
___
* http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00080.html
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 11:15 lilyp...@googlecode.com wrote:
>
> Comment #9 on issue 163 by brownian.box: huge (ugly) slur (both
> phrasing and normal)
> http://code.google.com/p/lilypond/issues/detail?id=163
I have removed this comment (see the next one, comment #10);
sorry for the noise.
> Another real-life example (by David Kastrup,
> http://lists.gnu.org/archive/html/bug-lilypond/2011-06/msg00325.html)
> :
>
> <<
> \chords { d2:m a:7 d:m a:7 d:m g:m d:m a:7
> d2:m a:7 d:m a:7 d:m g:m d4:m a:7 d2:m
> c1 f c f c f2 d:m a1:7 d:m
> a:7 d:m c f a:7 d:m a:7 d:m }
[...]
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 10:33 David Kastrup wrote:
>
> Here is another real-life example (I have not been able to boil this
> down to something smaller, like by omitting the chords or trying to
> capture just the bars before and after the break). In this case it
> would appear the insane slur slope after the line break comes from
> trying to avoid the key signature.
I have cut this example as much as could
and added as comment #10.
Thank you.
This case is a variant of issue 379;
however I've added it to "ugly slurs" collection, too.
> <<
> \chords { d2:m a:7 d:m a:7 d:m g:m d:m a:7
> d2:m a:7 d:m a:7 d:m g:m d4:m a:7 d2:m
> c1 f c f c f2 d:m a1:7 d:m
> a:7 d:m c f a:7 d:m a:7 d:m }
> \new Staff {
>\time4/4 \key d\minor
>\relative c' <<
> { a'2( bes a bes
>a2 g f e)
>f( g a bes
>a g f4 e d2)
>e1( f g a) g( f e f)
>e( f g a~ a~ a~ a~ a~)
> } \\
> {
>d,1~( d~ d~ d) d~( d~ d~ d)
>c~( c~ c~ c) c~( c2 d~ d cis d1)
>cis( d e f) e( d cis d)
> } >>
>}
> >>
>
> Here is the result: uh, no it isn't. What is the preferred method for
> generating a two-system preview? -dpreview just makes the first system.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 11:10 David Kastrup wrote:
> Graham Percival writes:
>
> > On Tue, Jun 21, 2011 at 10:33:31AM +0200, David Kastrup wrote:
> >>
> >> Here is the result: uh, no it isn't. What is the preferred method for
> >> generating a two-system preview?
> >
> > Using a full --png, unfortunately:
> > http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker
> > But that's not something that you need to do; the bug squad should
> > take care of this step.
>
> I've been told in private communication to use Windows Paint. That's
> not a useful option for me and takes some time (one could similarly do
> this in the Gimp if one likes interactive workflows). What I did in the
> end was
>
> pngtopnm kelbl.png |pnmcut -bottom -40|pnmcrop |pnmtopng >kelbl2.png
>
> (first cutting off the foot line, then cropping down), resulting in
Wow.
In such cases I add
\header { tagline = "" }
to a source file and then:
lilypond --png test.ly
convert test.png -trim test-trim.png
It is ok to me usually.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: slur moves on its own (in specific situations)
On Wed 08 Jun 2011, 23:30 Mark Polesky wrote:
> Hey guys,
>
> I found another head-scratcher bug... This is the sort of thing
> you can only find by accident. The first measure contains two
> identical halves; the slur in the first half is printed properly,
> but the slur in the second half is printed too high above the
> beam.
I've added this as 1703:
http://code.google.com/p/lilypond/issues/detail?id=1703
Thank you.
> I honestly tried to make this example file as tiny as possible,
> but the combination of elements needed to trigger the bug seems
> curiously specific. For example, if I remove any one of these
> elements, the problem disappears:
>
> #(set-default-paper-size "letter")
> #(set-global-staff-size 17)
> left-margin = 0.75\in --and-- right-margin = 0.75\in
> \key bf \major
> \break
>
> Stranger still, if I change staff-size to 15, 16, 18, 19, or 20,
> the problem goes away, and if I change both margins to 0.5\in or
> 1\in, the problem also goes away.
>
> So, what's going on? This is bizarre...
>
> Thanks.
> - Mark
>
>
> * * * * * * * * * * * * * * * *
>
>
> \version "2.14.0"
>
> #(set-default-paper-size "letter")
> #(set-global-staff-size 17)
>
> \paper {
> left-margin = 0.75\in
> right-margin = 0.75\in
> }
>
> \relative bes' {
> \key bes \major
> <<
> { bes='4 f8 f16( f-.) bes4 f8 f16( f-.) | }
> \\
> { d='8 d4 d16 r d8 d4 d16 r | }
> \\
> { d='8 d16 f s4 d8 d16 f s4 | }
> >>
> \break
> bes4 r2. |
> }
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: fretted-string-harmonics-in-tablature snippet
On Mon 23 May 2011, 20:17 Federico Bruni wrote: > I think it's pretty clear, but I might be missing something. > So we just need a guitar player, or someone who knows something about > physics (this is definitely not me), to confirm it. Please, someone who knows physics! I am a bit lost -- bug? Or not? Federico: Well, i've flagged this thread; let's wait a bit. Thanks! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI ignores dynamics parallel to notes
On Mon 23 May 2011, 10:06 Richard Sabey wrote:
> Lilypond's MIDI output sometimes fails to account for dynamic indications if
> the
> code specifies them in parallel with the music rather than directly attached
> to
> notes.
>
> In the example, the notes sound fairly loud to me.
This stressed me... In fact i can hear only one note (the second one i
believe).
Is this another issue? Or is this normal?
> Related to issue 1646?
> %%
> \version "2.13.61"
>
> \score
> {
> <<
> \new Staff \with { midiInstrument = #"contrabass"}
> <<
> { c2 f }
> { s1\ }
> >>
> >>
> \midi
> {
> \context
> { \Staff
> \remove "Staff_performer"
> }
> \context
> { \Voice
> \consists "Staff_performer"
> }
> }
> } % score
> %%
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two predefined guitar fretboards typos genereate incorrect fret diagrams
On Mon 23 May 2011, 11:33 K. Kellogg-Smith wrote:
> >I'm not top posting
> Predefined-guitar-fretboards.ly (v2.12.0): Missing semi-colon at end of
> finger
> position strings for chords {dis:aug} and {ees:aug} result in incorrect fret
> diagrams.
Please, provide a tiny example, THANKS!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: harmonicOn doesn't work in TabStaff
On Sun 22 May 2011, 21:54 Federico Bruni wrote:
> As you can see in the following example, when using harmonicOn, fret
> numbers in TabStaff are not enclosed by angled brackets (while Staff is
> ok).
>
> It looks like a bug.
>
> \version "2.15.0"
>
> music = \relative c'' {
>% Ok, it works in Staff and TabStaff
> 2
>
> % it works on Staff only: bug or what?
> \harmonicsOn
> b2\2 e
> \harmonicsOff
>
> 1
> }
>
> \new StaffGroup <<
> \new Staff { \clef "G_8" \music }
> \new TabStaff { \clef "moderntab" \music }
> >>
Thank you, added as 1660:
http://code.google.com/p/lilypond/issues/detail?id=1660
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: fretted-string-harmonics-in-tablature snippet
On Sun 22 May 2011, 21:47 Federico Bruni wrote: > I think that there are some wrong pitches in this snippet: > http://lilypond.org/doc/v2.13/Documentation/snippets/fretted-strings#fretted_002dstring-harmonics-in-tablature > Please, anyone, i need help!-) > Can you check it? > > I would write as in the attached file (see diff). What is wrong there? What is the problem? Which issue "Summary" would you propose? Thank you! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
