The way to print the first bar number is explained in the first of the
"Selected Snippets" of this section.
http://lilypond.org/doc/v2.19/Documentation/notation/bars#bar-numbers
On 12/12/2019 17:32, Peter Toye wrote:
Re: Bar lines within bars inhibit bar numbering Hi Timothy,
J
4/4 + 3/4 time with a dotted barline. I ended up just manually
renumbering the bars numbers with:
\set Score.currentBarNumber
Probably not the solution you're looking for.
From: lilypond-user on
behalf of Peter Toye
Sent: Thursday, December 12, 2019 10:04 AM
To: lilypond-user@gnu.org
t bar number is explained in the first of the
"Selected Snippets" of this section.
http://lilypond.org/doc/v2.19/Documentation/notation/bars#bar-numbers
On 12/12/2019 17:32, Peter Toye wrote:
Re: Bar lines within bars inhibit bar numbering
Am Do., 12. Dez. 2019 um 17:05 Uhr schrieb Peter Toye :
>
> The example below shows the issue. The mid-bar line with a \break does not
> show the bar number at the beginning of the next line - I would expect '2'. A
> \break at the end of a bar gives the expected result.
>
> Also, the commented ou
*From:* lilypond-user
on behalf of
Peter Toye
*Sent:* Thursday, December 12, 2019 10:04 AM
*To:* lilypond-user@gnu.org
*Subject:* Bar lines within bars inhibit bar numbering
The example below shows the issue. The mid-bar line with a \break does
on
behalf of Peter Toye
Sent: Thursday, December 12, 2019 10:04 AM
To: lilypond-user@gnu.org
Subject: Bar lines within bars inhibit bar numbering
The example below shows the issue. The mid-bar line with a \break does not show
the bar number at the beginning of the next line - I would expect
.currentBarNumber
Probably not the solution you're looking for.
From: lilypond-user on
behalf of Peter Toye
Sent: Thursday, December 12, 2019 10:04 AM
To: lilypond-user@gnu.org
Subject: Bar lines within bars inhibit bar numbering
The example below shows the issue. The mid-bar line with a
tBarNumber
Probably not the solution you're looking for.
From: lilypond-user on
behalf of Peter Toye
Sent: Thursday, December 12, 2019 10:04 AM
To: lilypond-user@gnu.org
Subject: Bar lines within bars inhibit bar numbering
The example below shows the issue. T
The example below shows the issue. The mid-bar line with a \break does not show
the bar number at the beginning of the next line - I would expect '2'. A \break
at the end of a bar gives the expected result.
Also, the commented out line doesn't compile, and I can't see why, so can't see
if it wo
Hi James,
See:
http://lilypond.1069038.n5.nabble.com/measure-numbers-with-letters-td204595.html
HTH, Cheers,
Pierre
Le dim. 20 oct. 2019 à 10:23, james via lilypond-user
a écrit :
> I haven't seen this documented, or if I have, I've forgotten where, but is
> it possible to manually set an altern
I haven't seen this documented, or if I have, I've forgotten where, but is it
possible to manually set an alternate bar number, i.e., with a letter?
\set Score.alternativeNumberingStyle = #'numbers-with-letters
\set Score.currentBarNumber = #10a
doesn't work, and I didn't see anything that explai
gt;
>
> However, this option turns off bar numbering in the score. Adding it
> explicitly like this doesn't work:
>
> \context {
>\Score
>\remove "Timing_translator"
>\remove "Default_bar_line_engraver"
>\consists "Bar_numbe
I have created a polymetric score with independent bar lines in different
parts, using the instructions here:
http://lilypondblog.org/2014/05/independent-meters/
<http://lilypondblog.org/2014/05/independent-meters/>
However, this option turns off bar numbering in the score. Add
Dear Kyle,
please reply to the list directly.
> why does it print the bar numbers as such?
It will print the bar numbers at each beginning of a line by default
BarNumber.break-visibility is set to begin-of-line-visible
That means all other bar lines in the middle and at the end of a staff
line
Simon Albrecht writes:
> Hi David,
>
> please read more carefully: the explanations in the manual are for
> that which Kyle said he can already do independently. Combining the
> two is the issue, which requires an approach like the one Noeck
> proposed.
>
> Best, Simon
>
>
> On 06.07.2018 23:32,
Hi David,
please read more carefully: the explanations in the manual are for that
which Kyle said he can already do independently. Combining the two is
the issue, which requires an approach like the one Noeck proposed.
Best, Simon
On 06.07.2018 23:32, David Kastrup wrote:
Kyle Baldwin wri
Kyle Baldwin writes:
> I'm trying to get Lilypond to replicate the way that I number scores
> personally.
>
> When I number my own scores, the bars that get numbers are
>
> 1) The first bar of every staff/system
> 2) Every 10 bars Regardless of location
>
> I can do these two things independently
Dear Kyle,
> When I number my own scores, the bars that get numbers are
>
> 1) The first bar of every staff/system
That's the default.
> 2) Every 10 bars Regardless of location
How about adding this voice in parallel to your music (assuming a 4/4
timing):
{
s1*9
\repeat unfold 5 {
\on
I'm trying to get Lilypond to replicate the way that I number scores
personally.
When I number my own scores, the bars that get numbers are
1) The first bar of every staff/system
2) Every 10 bars Regardless of location
I can do these two things independently, but am having problems getting
them
On Thu, Aug 25, 2016 at 1:33 PM, Pastor Neubauer wrote:
> I have a problem that seems to be part of the way lilypond works. I’m
> using the code below. What I am wondering is how to change the lines
> following the \break command. These lines seem to ignore all page formatt
> ing. The first line
On Thu, Aug 25, 2016 at 2:53 PM, Pastor Neubauer wrote:
> I’ve gotten two pieces of information that have clarified the problem. By
> using \relative so often I am essentially doing first lines each time
> with their indent being set at 10, but when Lilypond does the automatic
> line breaking it
Oh, and because you mentioned time savers: You don’t have to write the
duration of every note. If you don’t write the duration the last
duration is repeated.
So
c4 d4 e4 r4 f8 e8 f4
is the same as
c4 d e r f8 e f4
Am 25.08.2016 um 23:00 schrieb Malte Meyn:
Pleae always reply to the list (
Pleae always reply to the list (at least as CC) so others can see when
your problem is solved or new questions arise ;)
Am 25.08.2016 um 22:39 schrieb Pastor Neubauer:
Is there any way to not have the first line indent?
Yes: replace line 10 (“indent = #10”) by “indent = #0”. You can also
omi
"Pastor Neubauer" writes:
> I have a problem that seems to be part of the way lilypond works. I'm using
> the code below. What I am wondering is how to change the lines following the
> \break command. These lines seem to ignore all page formatting. The first
> line is indented and the remaining l
Am 25.08.2016 um 21:12 schrieb Pastor Neubauer:
I am not using score blocks. I never really trained in on Lilypond, just sort
of started finding what worked so I am going line by line using addlyrics. I
know I have had some difficulties that could be worked out if I used more
“formal” metho
.
From: Abraham Lee [mailto:tisimst.lilyp...@gmail.com]
Sent: Thursday, August 25, 2016 1:41 PM
To: Pastor Neubauer
Cc: Kevin Barry; LilyPond Users
Subject: Re: Alternative bar numbering [0.18571]
On Thu, Aug 25, 2016 at 12:33 PM, Pastor Neubauer wrote:
Thanks for getting back to me
On Thu, Aug 25, 2016 at 12:33 PM, Pastor Neubauer
wrote:
> Thanks for getting back to me. I've attached the pdf of what I've done so
> far so you can see the formatting issue.
>
That is indeed strange. Mind sharing the source file? I'm pretty sure the
solution will be obvious then. Are you using
Hi Pastor,
I see nothing unusual in the output; can you be more specific about
what you want to see? Indentation only affects the first system of a
score. What page formatting have you set that is being ignored?
Kevin
___
lilypond-user mailing list
lil
On Thu, Aug 25, 2016 at 11:33 AM, Pastor Neubauer
wrote:
> I have a problem that seems to be part of the way lilypond works. I’m
> using the code below. What I am wondering is how to change the lines
> following the \break command.
>
Which \break you are talking about (since there are 5 of them)?
I have a problem that seems to be part of the way lilypond works. I'm using
the code below. What I am wondering is how to change the lines following the
\break command. These lines seem to ignore all page formatting. The first
line is indented and the remaining lines are not.
\relative c'{
\set
Hi all,
What about a radical alternative?
What if each non-reference part has an additional “tick” barline (numbered
according to the reference context) whereever the barlines don’t line up?
Just a thought…
Kieren.
Kieren MacMillan, composer
‣ website: www.kier
On Thu, 2015-11-12 at 10:38 -0600, David Wright wrote:
> On Tue 10 Nov 2015 at 13:52:33 (+), Graham King wrote:
> > On Mon, 2015-11-09 at 21:53 -0600, David Wright wrote:
> > On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote:
> > > On Mon, 2015-11-09 at 14:55 -0600, Christopher
On Tue 10 Nov 2015 at 13:52:33 (+), Graham King wrote:
> On Mon, 2015-11-09 at 21:53 -0600, David Wright wrote:
> On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote:
> > On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote:
> > On 11/09/2015 02:47 PM, Kieren MacM
> > > > > > messing things up. Must dash now.
> > > > > >>
> > > > > >> Urs
> > > > > >
> >
> > OK, I think I have a reasonable test case (attached). Toggling the
> > block comment a
Am 11.11.2015 um 11:14 schrieb Graham King:
>
annotate "installs" itself in the Score context, and in polymetric
scores the timing-translator has to be removed from that context.
So to approach the issue one would have to remove \annotationProcessor
from the Score contex
e to create a manual solution, if
> > > >> that's a viable approach given your material (that is: how many of
> > > >> these annotations do you expect, will the numbering be stable or will
> > > >> you have to expect any changes after the fact?)
ution that
>> >> really works automatically and is at the same time sufficiently
>> >> general. But you'd be in any case to create a manual solution, if
>> >> that's a viable approach given your material (that is: how many of
>> >> these anno
27;d be in any case to create a manual solution, if
> >> that's a viable approach given your material (that is: how many of
> >> these annotations do you expect, will the numbering be stable or will
> >> you have to expect any changes after the fact?)
>
> &
e possible to implement a solution that
>> really works automatically and is at the same time sufficiently
>> general. But you'd be in any case to create a manual solution, if
>> that's a viable approach given your material (that is: how many of
>> these annotations d
t the same time sufficiently
> general. But you'd be in any case to create a manual solution, if
> that's a viable approach given your material (that is: how many of
> these annotations do you expect, will the numbering be stable or will
> you have to expect any changes after the
On Mon, 2015-11-09 at 21:53 -0600, David Wright wrote:
> On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote:
> > On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote:
> >
> > On 11/09/2015 02:47 PM, Kieren MacMillan wrote:
> > > The very first thing they said to me was, “A
Am 10.11.2015 um 14:28 schrieb Kieren MacMillan:
> Hi Urs,
>
>> I have no idea if it is also appropriate for ancient music.
>
> Well, the absence of [any] barlines makes barline numbering more complex… ;)
Of course it depends on the way an edition deals with that.
>
>> Aren't there any usefu
Hi Urs,
> I have no idea if it is also appropriate for ancient music.
Well, the absence of [any] barlines makes barline numbering more complex… ;)
> Aren't there any useful references, how have others dealt with that challenge?
I can’t find any!
Cheers,
Kieren.
___
is to break lines only where
> barlines co-incide and to number bars at the start of each line
> (Staff.BarNumber.break-visibility = ##(#f #f #t)), it would work with that.
>
> On the negative side:
> -1We have to introduce non-integers. I don't think the current
> bar
Am 09.11.2015 um 17:34 schrieb Graham King:
> (This note describes an issue arising from the separate thread,
> "Scholarly footnotes" [1])
>
> I would like to use Urs' annotate.ily[2] to add some footnotes to an
> edition of sixteenth-century polyphony. But, before investing too
> much time, I n
Am 10.11.2015 um 00:56 schrieb Kieren MacMillan:
> Hi Graham,
>
>> I've just realised that, under my system as I described it, a part could
>> have the same bar number twice.
> My proposed solution would be an “analytic continuation” (to borrow a
> mathematical term) of the non-polymetric measu
On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote:
> On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote:
>
> On 11/09/2015 02:47 PM, Kieren MacMillan wrote:
> > The very first thing they said to me was, “Add measure numbers.”
> >
> > That’s sufficient reason for
Hi Graham,
> I've just realised that, under my system as I described it, a part could have
> the same bar number twice.
My proposed solution would be an “analytic continuation” (to borrow a
mathematical term) of the non-polymetric measure numbering scheme:
1. A “reference context” would be est
On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote:
> On 11/09/2015 02:47 PM, Kieren MacMillan wrote:
> > The very first thing they said to me was, “Add measure numbers.”
> >
> > That’s sufficient reason for me. =)
>
> Good answer.
>
> In that case, I would pick one part, and force t
On 11/09/2015 02:47 PM, Kieren MacMillan wrote:
The very first thing they said to me was, “Add measure numbers.”
That’s sufficient reason for me. =)
Good answer.
In that case, I would pick one part, and force those measure numbers in
as numeric rehearsal marks in the other parts.
Otherwis
Hi Chris,
> What do you need the bar numbers for? I suspect rehearsal marks would fit
> the bill, no? If not, why not?
The score runs 105 measures in the piano part. I have 9 rehearsal marks (A-I),
for an average of ~12 measures per rehearsal mark.
In anticipation of officially [self-]publis
On 11/09/2015 01:47 PM, Kieren MacMillan wrote:
Is there a standard/convention/best practice on measure numbering in
polymetric scores? I’m running into an issue of that myself (in my
song “The Country Wife”), and can’t find anything definitive.
Note: Gould (p. 484) writes, “Bar numbers should n
Hi all,
Is there a standard/convention/best practice on measure numbering in polymetric
scores? I’m running into an issue of that myself (in my song “The Country
Wife”), and can’t find anything definitive.
Note: Gould (p. 484) writes, “Bar numbers should not be used in music in which
individua
for it to cope with
polymetric music[3].
In case it is relevant, there are two extra features of these scores:
they use \RemoveEmptyStaff, and they (manually) adjust bar numbering to
be continuous along the printed top staff of the system, whichever staff
that happens to be. This is ill
est to
>>> the tracker? Thanks!
>>>
>>> This is by far the most popular enhancement request from the French
>>> users mailing list: Bar numbering of repeat volta _alternatives_.
>>>
>>> Currently LilyPond counts the measures of each "alter
mailing list: Bar numbering of repeat volta _alternatives_.
Currently LilyPond counts the measures of each "alternative" as
normal, unrepeated, measures hence incrementing the currentBarNumber
in both alternative "1." and "2.". Several references supports what is
act
list: Bar numbering of repeat volta _alternatives_.
Currently LilyPond counts the measures of each "alternative" as
normal, unrepeated, measures hence incrementing the currentBarNumber
in both alternative "1." and "2.". Several references supports what
is
actually aske
On 28/11/11 11:04, Xavier Scheuer wrote:
Dear LilyPond developers,
Dear Bug Squad members, could you add this enhancement request to
the tracker? Thanks!
This is by far the most popular enhancement request from the French
users mailing list: Bar numbering of repeat volta _alternatives_
On Mon, Nov 28, 2011 at 01:04:06AM +0100, Xavier Scheuer wrote:
> Dear LilyPond developers,
>
> Dear Bug Squad members, could you add this enhancement request to
> the tracker? Thanks!
>
> This is by far the most popular enhancement request from the French
> users mailin
Dear LilyPond developers,
Dear Bug Squad members, could you add this enhancement request to
the tracker? Thanks!
This is by far the most popular enhancement request from the French
users mailing list: Bar numbering of repeat volta _alternatives_.
Currently LilyPond counts the measures of each
So for the truly picky, insert:
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar ""
just before you change and let the bar numbers fall where they may!
Much thanks Brett...
--hsm
On Tue, Dec 1, 2009 at 9:17 PM, Brett Duncan wrote:
> Hugh Myers wrote:
>>
>> Clearly th
Hugh Myers wrote:
Clearly this doesn't work:
\version "2.13.7"
upper = {
b c d
}
lower = {
< gis, d e, >2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barAlways = ##t
\set Score.defaultBarType = "|"
\new Voice = "1" { \voiceOne \upper }
\new
Clearly this doesn't work:
\version "2.13.7"
upper = {
b c d
}
lower = {
< gis, d e, >2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barAlways = ##t
\set Score.defaultBarType = "|"
\new Voice = "1" { \voiceOne \upper }
\new Voice = "2" { \voice
Just to say this worked - thanks for the tip.
Cheers,
Vivian.
- Original Message
From: Mats Bengtsson <[EMAIL PROTECTED]>
To: Vivian Barty-Taylor <[EMAIL PROTECTED]>
Cc: lilypond-user@gnu.org
Sent: Monday, 8 January, 2007 1:40:57 PM
Subject: Re: Bar numbering with Timing_t
I assume that you refer to the second example in that section.
If I was LilyPond and was asked to print bar numbers that were valid for
the
full score even though each stave has the bar lines at different places,
I would
certainly also get very confused.
Try to move the Bar_number_engraver from
Could somebody please explain how this works? I've moved the Timing_translator
as described in section 8.4.1 of the manual (Polymetric notation). Now bar
numbers appear only irregularly throughout my score (on 2 pages out of 7 ) and
are also incorrect!
Confusingly, the bar numbers don't print e
See the section on "Modifying context plug-ins",
especially about the \new ... \with {...} {...} construct.
/Mats
Till Rettig wrote:
Hello,
I started putting a ChoirStaff together with multimetre mesures.
Because the score context calculates the bar numbering, it cannot
gath
Hello,
I started putting a ChoirStaff together with multimetre mesures. Because
the score context calculates the bar numbering, it cannot gather anymore
information on all staves, since they appear to have different measure
numbers. One possibility is to add the bar_number_engraver to the
http://www.geocities.com/noi_ga/imatges/lilypond_bracket_bar_number_bug.png
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
I agree. And same with instrument names combined with staffgroup. It doesn't
really make any sense not to take the staffgroup-/pianostaff-symbol into
account into account.
--
View this message in context:
http://www.nabble.com/Default-bar-numbering-collision-t1367702.html#a3692531
Sent fro
On 30-Mar-06, at 3:13 AM, Mats Bengtsson wrote:
The answer can, more or less, be found in the manual, at the bottom of
the
page in the section on Bar Numbers. If you are unfamiliar, to the
details
of to set such a property, look at the chapter on Changing Defaults,
especially
Common Tweaks.
I'm using the latest version (2.8.0). I tried the search on Nabble but i'll
try the keywords you suggested, thanks.
--
View this message in context:
http://www.nabble.com/Default-bar-numbering-collision-t1367702.html#a3668210
Sent from the Gnu - Lilypond - User forum at
(See
attached image.) Default bar numbering collision
View this message in context: Default bar numbering collision
<http://www.nabble.com/Default-bar-numbering-collision-t1367702.html#a3667721>
Sent from the Gn
s message in context: Default bar numbering collision
Sent from the Gnu - Lilypond - User forum at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Erik Sandberg <[EMAIL PROTECTED]> writes:
> On Friday 21 May 2004 04.19, Ferenc Wagner wrote:
>
>> [skipped skeleton]
>>
>> resulted in a segmentation fault only...
>> v2.2.1 on Debian Woody.
>
> Cannot reproduce. Can you please send a full example which
> makes lilypond segfault? (all segfaults a
On Friday 21 May 2004 04.19, Ferenc Wagner wrote:
> Hi,
>
> is it possible to remove the bar numbers from the top of the
> topmost staff and add them to a different staff?
>
> \score {
> \new Score \with {
> \remove Bar_number_engraver
> }
> <<
> \new Staff { ... }
>
Hi,
is it possible to remove the bar numbers from the top of the
topmost staff and add them to a different staff?
\score {
\new Score \with {
\remove Bar_number_engraver
}
<<
\new Staff { ... }
\new Staff \with {
\consists Bar_number_engraver
On Wednesday 05 November 2003 01:49 pm, Johan Eidenvall wrote:
> Hi.
>
> I hav found an error/bug regarding partial measuers (I think).
> If you study the input and output of the attatched ly-code (at the
> end othis message)... (1): the accidentals are not reset at the start
> of an partial measur
On Fri, 13 Dec 2002 20:55:13 Paul Scott wrote:
> David Raleigh Arnold wrote:
>
> >On Fri, 13 Dec 2002 01:18:57 Paul Scott wrote:
> >
> >
> >>Heikki Johannes Junes wrote:
>
> I don't even consider that an exception to my comment.
Better and better. I wasn't disagreeing either, really.
DaveA :-
David Raleigh Arnold wrote:
On Fri, 13 Dec 2002 01:18:57 Paul Scott wrote:
Heikki Johannes Junes wrote:
Instead, what one typically wants is bar numbering at 1, 5, 9, 13, ...
Even more accurately, at 5, 9, 13, 17, ...
*If* it matches the phrases. I absolutely
On Fri, 13 Dec 2002 01:18:57 Paul Scott wrote:
> Heikki Johannes Junes wrote:
>
> >>Instead, what one typically wants is bar numbering at 1, 5, 9, 13, ...
> >>
> >>
> >>
> >Even more accurately, at 5, 9, 13, 17, ...
> >
> >
>
Heikki Johannes Junes wrote:
Instead, what one typically wants is bar numbering at 1, 5, 9, 13, ...
Even more accurately, at 5, 9, 13, 17, ...
*If* it matches the phrases. I absolutely *hate* reading music numbered
every 5 bars which is typical of some band music especially when
82 matches
Mail list logo
