Re: Start new score without line break

2017-02-23 Thread Andrew Bernard 
Hi Simon,

I think MuseScore can do it also, for simple cases. Nothing is impossible -
it's just software after all!

Harm has given me a pointer to as way to fake this out which works fine
when adapted a little. But it's lots of code, and the idea of \noBreak
\score would be very helpful to many people I feel sure.

Andrew



On 24 February 2017 at 08:54, Simon Albrecht  wrote:

> Am 22.02.2017 um 14:41 schrieb Andrew Bernard:
>
>> I would still like to be able to start a new score with no break, for
>> example in books of say, harpsichord music with lots of small, short
>> movements, where the systems would be the same proportions but the piece is
>> new.
>>
>
> There are other conceivable use cases, e.g. the attached one, or other
> cases with a very short recitativo inbetween larger scored movements. But
> they are exceedingly rare.
> Also, a proper solution would certainly require the C++ page layout
> algorithms to optionally not make a line break between scores (the input
> syntax could theoretically be as simple as
> \score { c } \noBreak \score { d }
> ). I like that idea, but allow me to say that this is probably never going
> to be possible (in any music notation software)…
>
> Best, Simon
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Start new score without line break

2017-02-23 Thread tisimst 
Hi, Simon!

On Thu, Feb 23, 2017 at 3:01 PM, Simon Albrecht-2 [via Lilypond] <
ml-node+s1069038n200415...@n5.nabble.com> wrote:

> Am 22.02.2017 um 14:41 schrieb Andrew Bernard:
> > I would still like to be able to start a new score with no break, for
> > example in books of say, harpsichord music with lots of small, short
> > movements, where the systems would be the same proportions but the
> > piece is new.
>
> There are other conceivable use cases, e.g. the attached one, or other
> cases with a very short recitativo in between larger scored movements.
> But they are exceedingly rare.
> Also, a proper solution would certainly require the C++ page layout
> algorithms to optionally not make a line break between scores (the input
> syntax could theoretically be as simple as
> \score { c } \noBreak \score { d }
> ). I like that idea, but allow me to say that this is probably never
> going to be possible (in any music notation software)…
>

Actually, it's already quite easy to do in at least two GUI apps: PriMus
and Dorico.

Best,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Start-new-score-without-line-break-tp200371p200417.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: ancient custom time signature

2017-02-23 Thread Simon Albrecht 

Am 21.02.2017 um 13:23 schrieb k...@aspodata.se:

Jean Brefort:
...

You might use something like:
   \override Staff.TimeSignature #'stencil = #ly:text-interface::print
   \override Staff.TimeSignature #'text = \markup {\musicglyph #"timesig.mensural34" 
\lower #0.9 \bold \large "3"}

Thanks, that make the time sigs same size.


Though you might want to additionally use the \number markup command in 
order to get the usual number style.


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

Re: Start new score without line break

2017-02-23 Thread Simon Albrecht 

Am 22.02.2017 um 14:41 schrieb Andrew Bernard:
I would still like to be able to start a new score with no break, for 
example in books of say, harpsichord music with lots of small, short 
movements, where the systems would be the same proportions but the 
piece is new.


There are other conceivable use cases, e.g. the attached one, or other 
cases with a very short recitativo inbetween larger scored movements. 
But they are exceedingly rare.
Also, a proper solution would certainly require the C++ page layout 
algorithms to optionally not make a line break between scores (the input 
syntax could theoretically be as simple as

\score { c } \noBreak \score { d }
). I like that idea, but allow me to say that this is probably never 
going to be possible (in any music notation software)…


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

Re: Quotes in Lyrics

2017-02-23 Thread Simon Albrecht 

Am 23.02.2017 um 01:57 schrieb David Wright:

But why not do the Right Thing and dispose of this problem with
\addlyrics { “I am so lone- ly” said she }
and have yourself a proper set of 66 and 99 quotation marks
without needing to enclose them in quotes.


+1
Simon

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

Re: Quotes in Lyrics

2017-02-23 Thread David Wright 
On Thu 23 Feb 2017 at 11:06:16 (-0500), Tim Slattery wrote:
> Joseph Austin  wrote:
> 
> >I don't fully understand the point or effect of the "extra" quotes in the 
> >example.
> >Why is the f example incorrect?
> 
> Looks like a quotation mark must be within a quoted string (or it
> means something else). But once you start a quoted string, another
> quote will end it. The back slash "escapes" the following character,
> telling LP that it's not a control character, but an actual quote. 

Yes, the source of the confusion is the backslash. It might be clearer
if the documentation quoted by the OP finished thus:

… any 8-bit character with an ASCII code over 127, or a two-character
combination of a backslash followed by one of `, ', ", or ^.
Note that backslash itself is not in this list, so strings beginning
with those combinations must be quoted.

Cheers,
David.

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

Re: Melisma with manual syllable durations

2017-02-23 Thread Trevor Daniels 

David Kastrup wrote Thursday, February 23, 2017 2:29 PM


> Alexander Kobel  writes:
> 
>> It might be surprising that a non-existing voice does not even produce
>> a warning; but there *is* a (very sensible) difference.
>
[snip] 
> If searchForVoice is set (a context property) and this voice has
> a name, then this name is shortened by everything following its last
> hyphen and used as the corresponding voice name to synchronize to.
> 
> Really.  Fortunately, the default has been off for 6 years without
> anybody noticing or complaining:
> 
>commit 4133b4e0ec939a427a70361ad838c65a84a0dfda
>Author: Trevor Daniels 
>Date:   Fri Apr 8 08:26:15 2011 +0100
> 
>Search of context hierarchy for voice for lyrics is optional
> 
> - add new context property, searchForVoice, to indicate
>   whether the extended search for a voice containing lyric
>   rhythms should be conducted
> 
> - fixes 1579
> 
> * lily/lyric-engraver.cc
> 
>   test searchForVoice in get_voice_to_lyrics () to decide
>   whether to conduct an extended search
> 
> * ly/engraver-init.ly
> 
>   set default value of searchForVoice to #f
> 
>   (also in passing remove duplicated instrumentname
>and shortInstrumentName settings)
> 
> * scm/define-context-properties.scm
> 
>   add and document searchForVoice
> 
> Maybe we should remove that -- thing.

Probably sensible.  As I said at the time, I left it available in 
case any score or user was relying on it.  I'd no means of
determining whether or not that was the case then (nor have I now),
but if no one shouts soon that they are setting searchForVoice 
maybe it would be good to tidy this up.

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

Re: Quotes in Lyrics

2017-02-23 Thread Tim Slattery 
Joseph Austin  wrote:

>I don't fully understand the point or effect of the "extra" quotes in the 
>example.
>Why is the f example incorrect?

Looks like a quotation mark must be within a quoted string (or it
means something else). But once you start a quoted string, another
quote will end it. The back slash "escapes" the following character,
telling LP that it's not a control character, but an actual quote. 

A bit clumsy but logical, kind of like using ##T to set some LP option
true. The first # to tell LP that a Scheme expression is following,
then #T means "True".

-- 
Tim Slattery
tim  risingdove  com


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

Re: Quotes in Lyrics

2017-02-23 Thread Joseph Austin 
DUH--don't know how I missed that.

> On Feb 23, 2017, at 9:01 AM, lilypond-user-requ...@gnu.org wrote:
> 
> The preceding paragraph to the one you quote says:
> 
> "Normal quotes may be used in lyrics, but they have to be preceded with a 
> backslash character and the whole syllable has to be enclosed between 
> additional quotes"
> 
> So presumably it's a function of how LilyPond parses quote marks.  Best just 
> to accept that and do as the manual says.

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

Re: Melisma with manual syllable durations

2017-02-23 Thread David Kastrup 
Alexander Kobel  writes:

> On 2017-02-22 17:21, David Sumbler wrote:
>> [...]
>> So I experimented.  I find that, not only does it not matter which
>> voice or stave I name as "associatedVoice", but it does not even matter
>> whether such a voice exists! [...]
>
> Wrong.  Compare the extenders in:

[...]

> It might be surprising that a non-existing voice does not even produce
> a warning; but there *is* a (very sensible) difference.

lily/lyric-engraver.cc:92

[...]
  SCM voice_name = lyrics->get_property ("associatedVoice");
  string nm = lyrics->id_string ();

  if (scm_is_string (voice_name))
nm = ly_scm2string (voice_name);
  else if (nm == "" || !searchForVoice)
return 0;
  else
{
  ssize idx = nm.rfind ('-');
  if (idx != NPOS)
nm = nm.substr (0, idx);
}

  SCM voice_type = lyrics->get_property ("associatedVoiceType");
  if (!scm_is_symbol (voice_type))
return 0;

  Context *voice = find_context_near (lyrics, voice_type, nm);
  if (voice)
return voice;

  return find_context_near (lyrics, voice_type, "");
}

The last lines are the fallback.  Like most of the lyric
alignment/synchronization stuff, this seems like a collection of awful
hacks.  If searchForVoice is set (a context property) and this voice has
a name, then this name is shortened by everything following its last
hyphen and used as the corresponding voice name to synchronize to.

Really.  Fortunately, the default has been off for 6 years without
anybody noticing or complaining:

commit 4133b4e0ec939a427a70361ad838c65a84a0dfda
Author: Trevor Daniels 
Date:   Fri Apr 8 08:26:15 2011 +0100

Search of context hierarchy for voice for lyrics is optional

 - add new context property, searchForVoice, to indicate
   whether the extended search for a voice containing lyric
   rhythms should be conducted

 - fixes 1579

 * lily/lyric-engraver.cc

   test searchForVoice in get_voice_to_lyrics () to decide
   whether to conduct an extended search

 * ly/engraver-init.ly

   set default value of searchForVoice to #f

   (also in passing remove duplicated instrumentname
and shortInstrumentName settings)

 * scm/define-context-properties.scm

   add and document searchForVoice

Maybe we should remove that -- thing.

-- 
David Kastrup

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

Re: Melisma with manual syllable durations

2017-02-23 Thread Alexander Kobel 
On 2017-02-22 17:21, David Sumbler wrote:
> [...]
> So I experimented.  I find that, not only does it not matter which
> voice or stave I name as "associatedVoice", but it does not even matter
> whether such a voice exists! [...]

Wrong.  Compare the extenders in:

\version "2.18.2"

\paper { ragged-right = ##f }

lyr = \lyricmode { Foo2 __ bar4 __ baz4 }

\score {
  <<
\new Voice = "A" { \repeat unfold 16 c''16 }
\new Voice = "B" { \repeat unfold 8 c''8 }
\new Lyrics \with { associatedVoice = "A" } \lyr
  >>
}

\score {
  <<
\new Voice = "A" { \repeat unfold 16 c''16 }
\new Voice = "B" { \repeat unfold 8 c''8 }
\new Lyrics \with { associatedVoice = "B" } \lyr
  >>
}


It might be surprising that a non-existing voice does not even produce a 
warning; but there *is* a (very sensible) difference.


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

Re: Quotes in Lyrics

2017-02-23 Thread Phil Holmes 
- Original Message - 
From: "Joseph Austin" 

To: 
Sent: Wednesday, February 22, 2017 11:52 PM
Subject: Quotes in Lyrics


LilyPons Notation Reference 2.1.2 contains the following example of quotes 
in lyrics:


\relative c' { \time 3/4 e4 e4. e8 d4 e d c2. }
\addlyrics { "\"I" am so lone- "ly\"" said she }

And there follows a statement that seems to say a lyrics word can begin 
with backslash quote:


QUOTE:
A word in Lyrics mode begins with: an alphabetic character, _, ?, !, :, ', 
the control characters ^A through ^F, ^Q through ^W, ^Y, ^^, any 8-bit 
character with ASCII code over 127, or a two-character combination of a 
backslash followed by one of `, ', ", or ^.

ENDQUOTE.

I don't fully understand the point or effect of the "extra" quotes in the 
example.

Why is the f example incorrect?

\relative c' { \time 3/4 e4 e4. e8 d4 e d c2. }
\addlyrics { \"She is so lone- ly\" said he }

(BTW, adding spaces around the \" doesn't help:
\addlyrics { \" She is so lone- ly \" said he }

I get the following errors:

Processing `/Users/josephaustin/lilypond/scripts/TEST/quote2.ly'
Parsing...
/Users/josephaustin/lilypond/scripts/TEST/quote2.ly:8:36: error: EOF found 
inside string

\addlyrics { \"She is so lone- ly\"
   said he }
/Users/josephaustin/lilypond/scripts/TEST/quote2.ly:8:36: error: 
Unfinished main input

\addlyrics { \"She is so lone- ly\"
   said he }
/Users/josephaustin/lilypond/scripts/TEST/quote2.ly:8:36: error: syntax 
error, unexpected end of input

\addlyrics { \"She is so lone- ly\"
   said he }
Interpreting music...
...
fatal error: failed files: 
"/Users/josephaustin/lilypond/scripts/TEST/quote2.ly"


The preceding paragraph to the one you quote says:

"Normal quotes may be used in lyrics, but they have to be preceded with a 
backslash character and the whole syllable has to be enclosed between 
additional quotes"


So presumably it's a function of how LilyPond parses quote marks.  Best just 
to accept that and do as the manual says.


--
Phil Holmes 



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