Hi all,
I think the question is rather self-explanatory.
If it is possible, how?
I tried overriding the #'text property of BarNumber but nothing happens.
What I actually want to achieve is print two bar numbers in a column for one
bar.
Thanks for helping.
Regards,
Tao
--
View this message in
Need the MI in the Aiken heads to be slightly narrower and taller so it lines
up nicely with the DO. Can produce appropriate glyph but how do I compile just
the final Emmentaler fonts?
Tim Sheasby
t...@sheafpublishing.co.za
<>
___
lilypond-user mail
- Original Message -
From: "TaoCG"
To:
Sent: Saturday, February 26, 2011 10:02 AM
Subject: How to use Markup for Barnumbers?
Hi all,
I think the question is rather self-explanatory.
If it is possible, how?
I tried overriding the #'text property of BarNumber but nothing happens.
Can a notehead be scaled by different factors in the x and y directions?
Tim Sheasby
t...@sheafpublishing.co.za
<>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Phil Holmes-2 wrote:
>
> I'm sorry - I personally can't visualise the effect you're trying to
> achieve. Could you provide an image or scan so we can understand better?
>
> --
> Phil Holmes
>
Here is a sample image what it should more or less look like.
http://old.nabble.com/file/p31019278/
Hello
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Tim
Sheasby [t...@sheafpublishing.co.za]
Sent: 26 February 2011 10:07
To: lilypond-user@gnu.org
Subject: MF fonts
Need t
Tao wrote:
I tried overriding the #'text property of BarNumber but nothing happens.
Maybe this is because the bar counter sets up the #'text property at
a late stage and so overwrites what you had put there;
ChordName does that too.
You can bypass the #'text property with
repl
Robin Bannister wrote:
>
> You can bypass the #'text property with
>
>> replaceBN = #(define-music-function (parser location new) (markup?)
>> #{\once \override Score.BarNumber #'stencil =
>> #(lambda (grob) (grob-interpret-markup grob $new)) #})
>
> and then say
>
>>
Hi,
I need to remove the staff in one part of a single instrument score but
\RemoveEmptyStaves seems to keep at least one Staff alive, it just removes
the staff and bar lines and the key and time signature but the bar number
stays there and occupies the vertical space of a whole staff.
Actually
- Original Message -
From: "TaoCG"
To:
Sent: Saturday, February 26, 2011 12:59 PM
Subject: How to remove all empty staves?
Hi,
I need to remove the staff in one part of a single instrument score but
\RemoveEmptyStaves seems to keep at least one Staff alive, it just removes
the staf
\grace, \afterGrace, \appoggiatura and \acciaccatura yield problems when used
in << {...} \\ {...} >> setups. Among other ways of doing it, I have tried
the following five setups with bad results (errors, colliding columns,
etc.):
4( 8-.)
<< { \grace fs'8 es8( ds es-.) }
\\ { gs,4
- Original Message -
From: "MusFelix"
To:
Sent: Saturday, February 26, 2011 2:32 PM
Subject: Grace notes in multiple voices << {} \\ {} >>
\grace, \afterGrace, \appoggiatura and \acciaccatura yield problems when
used
in << {...} \\ {...} >> setups. Among other ways of doing it, I
Phil Holmes-2 wrote:
>
> If the music only has full measure rests for that section, then putting
> this
> layout block in the definition will allow the staff to disappear:
>
> \layout {
> \context {
> \RemoveEmptyStaffContext
> }
>
>
> --
> Phil Holmes
>
Actually I have:
\context {
Hello,
I am typesetting a piano score, in which I have chords which I want to span
both staves. I've determined that this is still not possible, and found that
the only suggested workaround was to align notes on both staves and to
extend the stem of one of the notes to join with the other. Unfortu
On Feb 25, 2011, at 2:35 PM, Jérémie Lumbroso wrote:
> Hello,
>
> I am typesetting a piano score, in which I have chords which I want to span
> both staves. I've determined that this is still not possible, and found that
> the only suggested workaround was to align notes on both staves and to e
On 26 February 2011 15:32, MusFelix wrote:
>
> \grace, \afterGrace, \appoggiatura and \acciaccatura yield problems when used
> in << {...} \\ {...} >> setups. Among other ways of doing it, I have tried
> the following five setups with bad results (errors, colliding columns,
> etc.):
>
> [...]
>
On 26 February 2011 15:41, TaoCG wrote:
>
> Actually I have:
>
> \context {
> \Staff \RemoveEmptyStaves
> }
>
> Does this make any difference?
>
> I tried changing it to your example but the result seems to be the same.
> Again I tried to remove the rehearsal mark to see if it is keeping the sta
On Fri, Feb 25, 2011 at 10:45 PM, MusFelix wrote:
>
> Whenever there is an articulation on the first or last note of a slur the
> other end is offset by the same amount, whether it has an articulation or
> not. Is this intentional in the algorithm or a problem? And is there a way
> to fix it gen
- Original Message -
From: "TaoCG"
To:
Sent: Saturday, February 26, 2011 2:41 PM
Subject: Re: How to remove all empty staves?
Phil Holmes-2 wrote:
If the music only has full measure rests for that section, then putting
this
layout block in the definition will allow the staff to d
Have you read the section called "Cross-staff stems" in the Notation Reference?
--
Phil Holmes
- Original Message -
From: Jérémie Lumbroso
To: lilypond-user@gnu.org
Sent: Friday, February 25, 2011 7:35 PM
Subject: Extending stem length without affecting spacing
Hello,
Tao wrote:
maybe this is a bug?
It is an issue:
http://lists.gnu.org/archive/html/bug-lilypond/2009-03/msg00019.html
Try turning skipTypesetting on and off:
\set Score.skipTypesetting = ##t
[ ... empty section ... ]
\set Score.skipTypesetting = ##f
Cheers,
Robin
__
On 25 February 2011 20:35, Jérémie Lumbroso wrote:
>
> Hello,
> I am typesetting a piano score, in which I have chords which I want to span
> both staves. I've determined that this is still not possible, and found that
> the only suggested workaround was to align notes on both staves and to
> exte
Thanks. I'll try a hidden grace in the other voice to see what that
produces.
Phil, good thing you asked me for a separate working example. When I wrote
one up, I didn't get any errors (see my snippet below), just some
collisions. As it turns out, I had this line in the original:
\override Sc
Thanks. But that only works when the articulation is on the notehead side,
not when it is on the bar side. See this:
\version "2.13.51"
\include "english.ly"
\relative c'
{
\override Slur #'details #'steeper-slope-factor = #0
\override Slur #'details #'non-horizontal-penalty = #
- Original Message -
From: "MusFelix"
To:
Sent: Saturday, February 26, 2011 3:09 PM
Subject: Re: Grace notes in multiple voices << {} \\ {} >>
Thanks. I'll try a hidden grace in the other voice to see what that
produces.
Phil, good thing you asked me for a separate working example
On 2/26/11 4:18 AM, "James Lowe" wrote:
> Hello
>
> From: lilypond-user-bounces+james.lowe=datacore@gnu.org
> [lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Tim
> Sheasby [t...@sheafpublishing.co.za]
> Sent: 26 February 2011 10:07
Phil Holmes-2 wrote:
>
> I still get an error with your example:
>
> error: syntax error, unexpected DIGIT
>
> 4( 8-.)
>
The left and right angled brackets and everything between them are not
showing up due to the HTML. What code do I need to use to get around that?
--
View this mess
2011/2/26 Tim Sheasby :
> Can a notehead be scaled by different factors in the x and y directions?
>
A while ago I was trying to have more rounded noteheads, and to
position the stem from its middle point, to get a more precise
representation of time.
I would like to know that too, maybe it's rel
On Sat, Feb 26, 2011 at 08:25:59AM -0800, MusFelix wrote:
> I still get an error with your example: error: syntax error, unexpected
> DIGIT 4( 8-.)
>
>The left and right angled brackets and everything between them are not
>showing up due to the HTML. What code do I need to use to
Don't post as HTML - use plain text.
--
Phil Holmes
- Original Message -
From: MusFelix
To: lilypond-user@gnu.org
Sent: Saturday, February 26, 2011 4:25 PM
Subject: Re: Grace notes in multiple voices << {} \\ {} >>
Phil Holmes-2 wrote:
I still get an error with you
Robin Bannister wrote:
>
> Tao wrote:
>> maybe this is a bug?
>
> It is an issue:
> http://lists.gnu.org/archive/html/bug-lilypond/2009-03/msg00019.html
>
>
> Try turning skipTypesetting on and off:
>
>> \set Score.skipTypesetting = ##t
>> [ ... empty section ... ]
>> \set
On 26 February 2011 17:11, Carl Sorensen wrote:
>
> Finally, regarding your question about scaling note heads. It is possible
> to scale a note head differently in x and y if you are using it in a markup,
> but as far as I know, there is no way to scale it differently in x and y as
> a note head
I posted all 17 .png pages to my facebook wall :)
On Sat, Feb 19, 2011 at 3:24 PM, Graham Percival
wrote:
> Wow. Brilliant work here:
> http://99-bottles-of-beer.net/language-lilypond-1351.html
>
> (I was doing a google search for "lilypond music function",
> because I couldn't remember the exa
On 2/26/11 9:45 AM, "Xavier Scheuer" wrote:
> On 26 February 2011 17:11, Carl Sorensen wrote:
>>
>> Finally, regarding your question about scaling note heads. It is possible
>> to scale a note head differently in x and y if you are using it in a markup,
>> but as far as I know, there is no way
I was going through Nabble, with the HTML explicitly turned off. Is there a
setting somewhere I'm missing???
--
From: "Phil Holmes"
Sent: Saturday, February 26, 2011 11:43 AM
To: "MusFelix" ;
Subject: Re: Grace notes in multiple voices << {} \\
Tao wrote:
Unfortunately this seems to neutralize all \break commands.
This is probably due to the new vertical spacing.
Something relevant must have changed between 2.13.40 and 2.13.46.
Cheers,
Robin
___
lilypond-user mailing list
lil
On 26/02/11 22:03, Tim Sheasby wrote:
Can a notehead be scaled by different factors in the x and y directions?
There's a snippet showing how to generate noteheads with PostScript. You
could adapt that to get any shape and scaling you like:
http://lsr.dsi.unimi.it/LSR/Item?id=516
Nick
_
Robin Bannister wrote:
Something relevant must have changed between 2.13.40 and 2.13.46.
I've narrowed this down to between 2.13.42 and 2.13.43,
so it's probably the commit to fix issue 1336
http://code.google.com/p/lilypond/issues/detail?id=1336
"Don't make paper columns if skipTypesetti
Robin Bannister wrote:
>
> Robin Bannister wrote:
>> Something relevant must have changed between 2.13.40 and 2.13.46.
>
> I've narrowed this down to between 2.13.42 and 2.13.43,
> so it's probably the commit to fix issue 1336
> http://code.google.com/p/lilypond/issues/detail?id=1336
>
I'm using glissandos with fingering in guitar scores to indicate that a
finger should be kept on the string when moving up/down the fretboard.
If this is between bars and across a line break, the glissando does not
appear at the beginning of the new stave. Is there a way to have it show
at the
On 26 February 2011 22:01, Nick Payne wrote:
> I'm using glissandos with fingering in guitar scores to indicate that a
> finger should be kept on the string when moving up/down the fretboard. If
> this is between bars and across a line break, the glissando does not appear
> at the beginning of the
Tim Sheasby wrote:
Can a notehead be scaled by different factors in the x and y directions?
In the recent development versions (starting with 2.13.38) you can.
The following snippet uses an X-factor of 2:
wideNH = #(lambda (grob) (ly:stencil-scale (ly:note-head::print grob) 2 1))
{
2011/2/26 Robin Bannister :
> b'4 g'4 \override NoteHead #'stencil = #wideNH
Nice! Thanks!
And what is the tweak to position the stem in the center of the
notehead (moving it horizontally to left or right, depending if it is
stemUp or stemDown)?
___
I mean:
{
\override Stem #'extra-offset = #'(0.4 . 0)
b'4
\override Stem #'extra-offset = #'(-0.4 . 0)
g'4
}
But automatically
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailma
On 27/02/11 09:14, Neil Puttock wrote:
On 26 February 2011 22:01, Nick Payne wrote:
I'm using glissandos with fingering in guitar scores to indicate that a
finger should be kept on the string when moving up/down the fretboard. If
this is between bars and across a line break, the glissando does
See below. The output is fine until I add the '\3' string number
indication to the last note on the lower stave, at which point the
output gets garbaged. The problem doesn't happen if the string number
orientation is set to down rather than up, nor does it happen with a
kneed beam on a single s
46 matches
Mail list logo
