Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Simon Albrecht

Am 15.04.2017 um 16:14 schrieb Son_V:

to have every beat numbered could help when in a
choir the Maestro calls to sing from a given beat.


The vast majority of scores available have bar numbers at the start of 
each system. So if you don’t want the trouble of writing bar numbers in 
each and every score on every single bar by hand, you have to learn 
counting them.
If you are used to have every bar numbered, then you won’t learn 
counting them at a glance. If you just practice getting along with the 
convention used practically everywhere, you’ll be able to get really 
fast at counting bars at a glance, presuming you invest a minimum of 
time and concentration. I always prefer the latter strategy – don’t dumb 
it down, get clever instead!


Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread David Sumbler
On Sat, 2017-04-15 at 07:14 -0700, Son_V wrote:
> I understand (maybe), but to have every beat numbered could help when
> in a
> choir the Maestro calls to sing from a given beat.
> That's the reason why I want them to be visible.
> 
> Sorry to be such an humble learner.

This reminds me of an old joke:

In rehearsal, the conductor stops the orchestra and says "Let's try it
again from bar 5."  At the back of the viola section (I told you it was
a joke) a tentative hand goes up and a voice calls out "Please,
Maestro, these parts haven't got bar numbers."

Seriously, would anyone need to have every beat numbered?  Surely
anybody can find the nth beat in a bar (unless you are using some truly
unorthodox time signature like 29/4).

David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Son_V
I understand (maybe), but to have every beat numbered could help when in a
choir the Maestro calls to sing from a given beat.
That's the reason why I want them to be visible.

Sorry to be such an humble learner.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Last-number-on-a-score-but-this-is-the-first-in-the-next-one-tp202294p202307.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Minimal examples (was: Last number on a score; but this is the first in the next one...)

2017-04-15 Thread Son_V
Thanks for your kind lesson. I hope I will make a good use of this (bu I'm
unsure of).
Thnx again



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Last-number-on-a-score-but-this-is-the-first-in-the-next-one-tp202294p202306.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Malte Meyn


Am 15.04.2017 um 15:47 schrieb Son_V:
>> \override Score.BarNumber.break-visibility = #end-of-line-invisible 
> 
> Thanks! That was successful.
> 
> But I'm still in doubt of what should be the correct way.

There is no single correct way. In classical music traditionally you
have bar numbers only at the beginning of each line; that’s why
#begin-of-line-visible is LilyPond’s default. Film scores often have bar
numbers at every measure. IIRC the don’t set a number on the last bar
line. So this would be #end-of-line-invisible.

Some publishers set bar numbers every now and then (f. e. every 5 or 10
measures in classical music or at significant places every 4 to 20
measures in film scores) but modern editions of classical music don’t do
that any more (at least, I haven’t seen such an edition yet).

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Son_V
> \override Score.BarNumber.break-visibility = #end-of-line-invisible 

Thanks! That was successful.

But I'm still in doubt of what should be the correct way.

Is it right to show the last number in the staff, or is it not?
IMHO I prefer not to leave the last number visible (and I am going to change
all my scores for the little choir where i sing in this way). But, I repeat,
what is the correct way?

Thanks.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Last-number-on-a-score-but-this-is-the-first-in-the-next-one-tp202294p202303.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Malte Meyn


Am 15.04.2017 um 15:40 schrieb Son_V:
>> And a solution
> 
> Sorry but I wasn't able to find it, surely, my fault. I tried some of your
> code without success. I'm using version "2.18.2" on Linux.

Maybe try all code, not some code ;)

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Minimal examples (was: Last number on a score; but this is the first in the next one...)

2017-04-15 Thread Malte Meyn


Am 15.04.2017 um 14:30 schrieb Son_V:
> I'm not able to make a truly "minimum example", that's what I could do:

I’ll show you how this can be simplified.

> \version "2.18.2"
> \header {
>   }
You don’t need an empty \header, \paper, \layout, … block.
> PartPOneVoiceOne =  \relative a' {
>   \override Score.BarNumber #'break-visibility = #'#(#t #t #t)
>   \clef "treble" \key c \major \numericTimeSignature\time 4/4 a1 | % 2
Clef, key, time signature style don’t have anything to do with your
problem. Omit them.
>   a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 | % 3 
Try less notes, and if you want multiple lines of music with little
input, try R1*20 or \repeat unfold 20 a1 or something like that. Apart
from that your comments are neither bar nor line numbers so why are they
there?
>   b1 | % 4
>   c1 \bar "|."
You don’t need that bar line.
> }
> \score {
You don’t need a score block if there is only one score in your lilypond
file.
>   <<
You don’t need these outermost << >> because there is only one Staff.
> \new Staff <<
>   \set Staff.instrumentName = "Piano"
>   \set Staff.shortInstrumentName = "Pno."
Instrument names have nothing to do with your problem.
>   \context Staff <<
> \context Voice = "PartPOneVoiceOne" { \PartPOneVoiceOne }
You are already in a Staff context, why state that explicitely again?
And why name your Voice if you don’t have \change commands or \lyricsto
or something similar?
>   >>
> >>
>   >>
These << >> aren’t necessary if there are no things happening in
parallel (multiple voices, staves, …).
>   \layout {}
You don’t need that unless you have some content in this \layout block
or an additional \midi block.
>   }

This gives the following almost-minimal example:

%%% BEGIN
\version "2.18.2"

PartPOneVoiceOne =  \relative a' {
  \override Score.BarNumber.break-visibility = #'#(#t #t #t)
  R1*20
}

\new Staff \PartPOneVoiceOne
%%% END

Why almost minimal? Because you don’t need the \new Staff (a staff
created anyway) and your example is so small that you don’t need a
variable definition and usage. Oh, and of course without notes you don’t
need \relative. So here comes a truly minimal working example:

%%% BEGIN
\version "2.18.2"

{
  \override Score.BarNumber.break-visibility = #'#(#t #t #t)
  R1*20
}
%%% END

Why not omit the version number making this even smaller? Because nobody
has to ask which version you use then :)

Of course it’s not a problem to have a small example that’s not truly
minimal. But your example had 22 lines, mine has 6 (if you count empty
lines) and in so few lines you don’t first have to find out which lines
are relevant for the problem and which are not.

HTH
Malte

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Son_V
> And a solution

Sorry but I wasn't able to find it, surely, my fault. I tried some of your
code without success. I'm using version "2.18.2" on Linux.





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Last-number-on-a-score-but-this-is-the-first-in-the-next-one-tp202294p202300.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Malte Meyn


Am 15.04.2017 um 13:54 schrieb Son_V:
> Hi all, Lilypond (using \override Score.BarNumber #'break-visibility = #'#(#t
> #t #t) ) writes at the end of a score, the number of the next beam, that is
> written at the beginning of the subsequent score; and it writes at the end
> of the last score the number that should be at the beginning of an
> inexistent next score.
> Now I don't have at hand "Beyond bars", so I can't say if it's a correct
> behaviour or not. But it seems strange to me IMHO.

It’s strange indeed, but it’s also exactly what you asked for by setting
break-visibility to #'#(#t #t #t) or it’s shortcut #all-visible.

Try
  \override Score.BarNumber.break-visibility = #'#(#f #t #t)
or the shortcut
  \override Score.BarNumber.break-visibility = #end-of-line-invisible
instead.

And concerning Kieren’s comment about patches: This is not LilyPond’s
mistake. And if you turn off the very last bar number even if bar
numbers are set to #all-visible that would be very confusing.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Kieren MacMillan
Hi,

> I'm not able to make a truly "minimum example", that's what I could do:

I showed you a much smaller example.
And a solution.

Kieren.



Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Son_V
I'm not able to make a truly "minimum example", that's what I could do:

\version "2.18.2"
\header {
  }
PartPOneVoiceOne =  \relative a' {
  \override Score.BarNumber #'break-visibility = #'#(#t #t #t)
  \clef "treble" \key c \major \numericTimeSignature\time 4/4 a1 | % 2
  a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 a1 | % 3 
  b1 | % 4
  c1 \bar "|."
}
\score {
  <<
\new Staff <<
  \set Staff.instrumentName = "Piano"
  \set Staff.shortInstrumentName = "Pno."
  \context Staff <<
\context Voice = "PartPOneVoiceOne" { \PartPOneVoiceOne }
  >>
>>
  >>
  \layout {}
  }

I would like to know if the "9" at the end of the first bar, and expecially
the "17" at the end of the last bar, are correct or not. I don't have
"Beyond Bars" at hand. But these numbers seems IMHO to me useless.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Last-number-on-a-score-but-this-is-the-first-in-the-next-one-tp202294p202297.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Last number on a score; but this is the first in the next one...

2017-04-15 Thread Kieren MacMillan
Hi,

Please include tiny compilable examples with your questions.

> Lilypond (using \override Score.BarNumber #'break-visibility = #'#(#t
> #t #t) ) writes at the end of a score, the number of the next beam, that is
> written at the beginning of the subsequent score; and it writes at the end
> of the last score the number that should be at the beginning of an
> inexistent next score.

e.g.

\version "2.19.43"

\layout {
  \context {
\Score
\override BarNumber.break-visibility = #'#(#t #t #t)
  }
}

{ c'1 1 \bar "|.” }

> I don't have at hand "Beyond bars", so I can't say if it's a correct
> behaviour or not. But it seems strange to me IMHO.

It does seem a little strange…

> If not, how to correct this behavior?

Well, I’m not sure it’s worth anyone writing a patch, when it’s a fringe case 
(most scores don’t have measure numbers every measure), and easy to turn off:

{ c'1 1 \once \omit Score.BarNumber \bar "|." }

Hope this helps,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Last number on a score; but this is the first in the next one...

2017-04-15 Thread Son_V
Hi all, Lilypond (using \override Score.BarNumber #'break-visibility = #'#(#t
#t #t) ) writes at the end of a score, the number of the next beam, that is
written at the beginning of the subsequent score; and it writes at the end
of the last score the number that should be at the beginning of an
inexistent next score.
Now I don't have at hand "Beyond bars", so I can't say if it's a correct
behaviour or not. But it seems strange to me IMHO.
Am I wrong? If not, how to correct this behavior? 
Thanks.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Last-number-on-a-score-but-this-is-the-first-in-the-next-one-tp202294.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user