\finger \markup \tied-lyric option for tie to appear above numbers
> I'm not top posting.
Hi folks, I'm working on a back score that requires the following:
{ d''2\finger \markup \tied-lyric #"1~4" }
but I can't seem to find a way to make the tie placement above the
numbers. Is there a way to override? Should an easier method be added.
I have tried the following with no luck:
\override Tie.direction = #UP
\tieUp
\tied-lyric #"1^~4"
etc
Eugene
--
Eugene Cormier
---
Full-time Instructor
Acadia University
www.eugenecormier.com
eugenecorm...@gmail.com
Office: Denton Hall Rm.235
Office Hours: Monday & Wednesday 10:30-11:30 (or by appointment)
Phone: (902) 585-1329
---
Statement of Confidentiality
This message (including attachments) may contain confidential or
privileged information intended for a specific individual or
organization. If you have received this communication in error, please
notify the sender immediately. If you are not the intended recipient,
you are not authorized to use, disclose, distribute, copy, print or rely
on this email, and should promptly delete this email from your entire
computer system.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \finger \markup \tied-lyric option for tie to appear above numbers
Eugene,
I had to do this recently, so here's a simple function catered for this
exact purpose. It uses two string numbers as input and looks very similar
to the normal downward tie (and could be further developed to act more
robustly like the \tied-lyric function, but my needs didn't stretch that
far):
#(define-markup-command (tied-finger-up layout props f1 f2)
(string? string?)
(interpret-markup layout props
#{
\markup {
\override #'(baseline-skip . 1.2)
\center-column {
\scale #'(1 . -1) \musicglyph #"ties.lyric.default"
\concat { #f1 \hspace #0.6 #f2 }
}
}
#}
))
{ d''2\finger \markup { \tied-finger-up #"1" #"4" } }
Like I said, it could be further developed so that it follows the same
input syntax of #"1~4", but there's still some Scheme-fu for me to come to
grips with. I agree, though, that it would be nice to just write "1^~4"
into the \tied-lyric function and have it do it automagically :-)
Maybe I'll have a look at that myself. The only issue I can't quickly
understand is how to use the various markup functions in Scheme-mode.
Perhaps someone with more experience can help out here.
- Abraham
On Tue, Apr 28, 2015 at 10:15 AM, Eugene Cormier [via Lilypond] <
ml-node+s1069038n175595...@n5.nabble.com> wrote:
> > I'm not top posting.
>
> Hi folks, I'm working on a back score that requires the following:
> { d''2\finger \markup \tied-lyric #"1~4" }
>
> but I can't seem to find a way to make the tie placement above the
> numbers. Is there a way to override? Should an easier method be added.
>
> I have tried the following with no luck:
> \override Tie.direction = #UP
> \tieUp
> \tied-lyric #"1^~4"
> etc
>
> Eugene
>
> --
> Eugene Cormier
> ---
> Full-time Instructor
> Acadia University
> www.eugenecormier.com
> [hidden email]
> Office: Denton Hall Rm.235
> Office Hours: Monday & Wednesday 10:30-11:30 (or by appointment)
> Phone: (902) 585-1329
>
>
> ---
> Statement of Confidentiality
> This message (including attachments) may contain confidential or
> privileged information intended for a specific individual or
> organization. If you have received this communication in error, please
> notify the sender immediately. If you are not the intended recipient,
> you are not authorized to use, disclose, distribute, copy, print or rely
> on this email, and should promptly delete this email from your entire
> computer system.
>
>
> ___
> bug-lilypond mailing list
> [hidden email]
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lilypond.1069038.n5.nabble.com/finger-markup-tied-lyric-option-for-tie-to-appear-above-numbers-tp175595.html
> To start a new topic under Bugs, email
> ml-node+s1069038n58488...@n5.nabble.com
> To unsubscribe from Lilypond, click here
>
> .
> NAML
>
>
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/finger-markup-tied-lyric-option-for-tie-to-appear-above-numbers-tp175595p175599.html
Sent from the Bugs mailing list archive at Nabble.com.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
compile failure - "parsed object should be dead" in 2.19.20
>I'm not top posting.
With a MWE:
\version "2.19.20"
\relative c' {
a4 b c d
}
I get the following error in the console output under frescobaldi:
Starting lilypond 2.19.20 [Untitled]...
Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `document.ps'...
Converting to `./document.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -
dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -
r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -
fdocument.ps)' failed (256)
programming error: Parsed object should be dead: #
continuing, cross fingers
programming error: Parsed object should be dead: #) (staff-refpoint-
extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-
break-penalty) (page-turn-permission . allow) (page-break-permission .
allow) (vertical-skylines . #) (stencil . #))() >
continuing, cross fingers
fatal error: failed files: "/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly"
Exited with return code 1.
-
Error output is the same on larger files.
Cheers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - "parsed object should be dead" in 2.19.20
2015-04-28 21:15 GMT+02:00 N. Andrew Walsh :
>>I'm not top posting.
>
> With a MWE:
>
> \version "2.19.20"
>
> \relative c' {
> a4 b c d
> }
>
> I get the following error in the console output under frescobaldi:
>
> Starting lilypond 2.19.20 [Untitled]...
> Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `document.ps'...
> Converting to `./document.pdf'...
> warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -
> dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -
> r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -
> fdocument.ps)' failed (256)
>
> programming error: Parsed object should be dead: #
> continuing, cross fingers
> programming error: Parsed object should be dead: # Prob((Y-offset . 1.0) (system-grob . #) (staff-refpoint-
> extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-
> break-penalty) (page-turn-permission . allow) (page-break-permission .
> allow) (vertical-skylines . #) (stencil . #))() >
>
> continuing, cross fingers
> fatal error: failed files: "/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly"
> Exited with return code 1.
> -
> Error output is the same on larger files.
>
> Cheers
Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04)
All works as expected.
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - "parsed object should be dead" in 2.19.20
according to Urs Liska, this resembles an error he encountered with
ghostscript, as the output on my machine when using --verbose confirms. If
you're also on the user list, the longer output is there. If not, I can
post here (but I imagine you'd prefer avoiding double-posting if it isn't
necessary).
I'm using gs 9.15.
Cheers,
A
On Tue, Apr 28, 2015 at 9:52 PM, Thomas Morley
wrote:
> 2015-04-28 21:15 GMT+02:00 N. Andrew Walsh :
> >>I'm not top posting.
> >
> > With a MWE:
> >
> > \version "2.19.20"
> >
> > \relative c' {
> > a4 b c d
> > }
> >
> > I get the following error in the console output under frescobaldi:
> >
> > Starting lilypond 2.19.20 [Untitled]...
> > Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'
> > Parsing...
> > Interpreting music...
> > Preprocessing graphical objects...
> > Finding the ideal number of pages...
> > Fitting music on 1 page...
> > Drawing systems...
> > Layout output to `document.ps'...
> > Converting to `./document.pdf'...
> > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -
> > dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -
> > r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -
> > fdocument.ps)' failed (256)
> >
> > programming error: Parsed object should be dead: #
> > continuing, cross fingers
> > programming error: Parsed object should be dead: # C++:
> > Prob((Y-offset . 1.0) (system-grob . #) (staff-refpoint-
> > extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-
> > break-penalty) (page-turn-permission . allow) (page-break-permission .
> > allow) (vertical-skylines . #) (stencil . #))() >
> >
> > continuing, cross fingers
> > fatal error: failed files: "/tmp/frescobaldi-NJlynW/tmpIzKobr/
> document.ly"
> > Exited with return code 1.
> > -
> > Error output is the same on larger files.
> >
> > Cheers
>
>
>
> Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04)
> All works as expected.
>
> Cheers,
> Harm
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - "parsed object should be dead" in 2.19.20
Am 28.04.2015 um 21:52 schrieb Thomas Morley: Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04) All works as expected. Cheers, Harm That's consistent with my experience from 2.19.18 on. It works with self-compiled versions (on Debian stable) but not with binary releases. It is related to calling a system vs. a packaged Ghostscript. At least it doesn't seem to be an issue with my personal configuration ... Urs -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \finger \markup \tied-lyric option for tie to appear above numbers
2015-04-28 18:15 GMT+02:00 Eugene Cormier :
>> I'm not top posting.
>
> Hi folks, I'm working on a back score that requires the following:
> { d''2\finger \markup \tied-lyric #"1~4" }
>
> but I can't seem to find a way to make the tie placement above the
> numbers. Is there a way to override? Should an easier method be added.
>
> I have tried the following with no luck:
> \override Tie.direction = #UP
> \tieUp
> \tied-lyric #"1^~4"
> etc
>
> Eugene
Hi,
have a look in my coding here:
http://lilypond.1069038.n5.nabble.com/Changing-fingering-numerals-td147415.html#a147437
http://code.google.com/p/lilypond/issues/detail?id=3088
still needs to be implementd, though.
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \partcombine interacts badly with \tag
H. S. Teoh quickfur.ath.cx> writes: > % Arguably, using \tag with \partcombine is a bad idea, since it can > % easily result in constructs that are probably not representable in a > % way that would make a subsequent \removeWithTag work correctly, but > % Lilypond should at least give a warning and/or reject such input > % instead of generating wrong output. It looks like this is already tracked. https://code.google.com/p/lilypond/issues/detail?id=896 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
figured bass on grace note
> I'm not top posting.
I believe there is a bug when writing figured bass on grace note. The figure
before the grace note is repeated on the grace note. Here is a tiny example:
\version "2.19.15"
<<
\new Voice { \clef bass f4 \grace f8 f2 }
\new FiguredBass { \figuremode { <6>4 \grace <5>8 <4>2 } }
>>
The second figure should be <5> but turns out <6 5>.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
