Re: Required font for simplified Chinese characters?

2017-12-21 Thread Phil Holmes 
- Original Message - 
From: "James Harkins" 
To: "Andrew Bernard" ; "lilypond-user" 


Sent: Wednesday, December 20, 2017 10:46 AM
Subject: Re: Required font for simplified Chinese characters?


 On Sat, 09 Dec 2017 14:23:46 +0800 Andrew Bernard wrote  
With the release of stable version 2.20 coming out in the forseeable 
future, and with 2.19.80 being really stable and excellent, could you 
considering moving up? No crash occurs at 2.19.80, and there are dozens 
of really good new features in this series, well worth having.


Sorry to come back very late to this thread.

I just tried 2.19.80, and this version *can* render simplified Chinese 
characters. Yes!


BUT... in 2.19, the handling of landscape orientation has changed.

In my v2.18.2 document, I used:

#(set-default-paper-size "a4" 'landscape)

... and I got a document that was wider than it is tall, and I could read 
the notation on screen directly. That's what I wanted.


In 2.19.80, without changing the code, I got a document whose paper is in 
portrait orientation, and whose notation was rotated 90 degrees 
counterclockwise. Staff lines read *upward* (???!) on the screen. Which... 
for reading is... shall we say, difficult.


#(set-default-paper-size "a4landscape") gives me the layout I wanted.

I'm not sure if this is intentional. The manual says "If the symbol 
'landscape is added to the paper size function, pages will be rotated by 
90 degrees, and wider line widths will be set accordingly." I am seeing 
that the page *contents* were rotated by 90 degrees and line widths were 
set accordingly, but the page dimensions did not rotate. So it isn't 
accurate to say that the **pages** will be rotated.


Try it yourself:

\version "2.19.80"
#(set-default-paper-size "a4" 'landscape)
\relative c' { c4 d e f g a b c }

Is it a bug, or out-of-date documentation?

I'm fairly sure nobody wants the behavior that is currently documented as 
the first option.


hjh


See http://lilypond.1069038.n5.nabble.com/PDF-landscape-issue-td204230.html


--
Phil Holmes 



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

Re: Required font for simplified Chinese characters?

2017-12-21 Thread Andrew Bernard 
HI Phil,

It's still very confusing for people, I claim. This landscape business
having two modes is unique to lilypond, I think, so people will stumble
over it for a long time to come. Because it is unfamiliar behaviour, people
will not be reading manuals looking for unusual behaviour.

Andrew


On 21 December 2017 at 19:36, Phil Holmes  wrote:

> - Original Message - From: "James Harkins" 
> To: "Andrew Bernard" ; "lilypond-user" <
> lilypond-user@gnu.org>
> Sent: Wednesday, December 20, 2017 10:46 AM
> Subject: Re: Required font for simplified Chinese characters?
>
>
>
>  On Sat, 09 Dec 2017 14:23:46 +0800 Andrew Bernard wrote 
>>
>>> With the release of stable version 2.20 coming out in the forseeable
>>> future, and with 2.19.80 being really stable and excellent, could you
>>> considering moving up? No crash occurs at 2.19.80, and there are dozens of
>>> really good new features in this series, well worth having.
>>>
>>
>> Sorry to come back very late to this thread.
>>
>> I just tried 2.19.80, and this version *can* render simplified Chinese
>> characters. Yes!
>>
>> BUT... in 2.19, the handling of landscape orientation has changed.
>>
>> In my v2.18.2 document, I used:
>>
>> #(set-default-paper-size "a4" 'landscape)
>>
>> ... and I got a document that was wider than it is tall, and I could read
>> the notation on screen directly. That's what I wanted.
>>
>> In 2.19.80, without changing the code, I got a document whose paper is in
>> portrait orientation, and whose notation was rotated 90 degrees
>> counterclockwise. Staff lines read *upward* (???!) on the screen. Which...
>> for reading is... shall we say, difficult.
>>
>> #(set-default-paper-size "a4landscape") gives me the layout I wanted.
>>
>> I'm not sure if this is intentional. The manual says "If the symbol
>> 'landscape is added to the paper size function, pages will be rotated by 90
>> degrees, and wider line widths will be set accordingly." I am seeing that
>> the page *contents* were rotated by 90 degrees and line widths were set
>> accordingly, but the page dimensions did not rotate. So it isn't accurate
>> to say that the **pages** will be rotated.
>>
>> Try it yourself:
>>
>> \version "2.19.80"
>> #(set-default-paper-size "a4" 'landscape)
>> \relative c' { c4 d e f g a b c }
>>
>> Is it a bug, or out-of-date documentation?
>>
>> I'm fairly sure nobody wants the behavior that is currently documented as
>> the first option.
>>
>> hjh
>>
>
> See http://lilypond.1069038.n5.nabble.com/PDF-landscape-issue-
> td204230.html
>
>
> --
> Phil Holmes
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Required font for simplified Chinese characters?

2017-12-21 Thread David Kastrup 
Andrew Bernard  writes:

> HI Phil,
>
> It's still very confusing for people, I claim. This landscape business
> having two modes is unique to lilypond, I think, so people will stumble
> over it for a long time to come. Because it is unfamiliar behaviour, people
> will not be reading manuals looking for unusual behaviour.

You need to reed the manual in the first place to learn how to set the
paper size.  Paper size and paper orientation are two different things,
and if you actually want to print landscape, you'd certainly want your
page getting rotated.

I think we found out that different viewers react differently to
landscape mode.

-- 
David Kastrup

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

Ligatures question

2017-12-21 Thread Menu Jacques 
Hello folks,

MusicXMl has the notion of brackets (LilyPond’s ligatures) line-ends:

Re: retrying in and out polyphony

2017-12-21 Thread Mike Dean 
Carl: Thanks!
I finished the engraving of the piano score of "Jesus Paid It All",
although I still haven't solved starting and ending hairpins in
simultaneous voices as of yet (I think that it may not start outside of of
such a section and end inside it)

Mike Dean

On Wed, Dec 20, 2017 at 12:33 AM, Mike Dean  wrote:

> In this multi-voice context, I'm not sure where to put the hairpin
> decrescendo to not generate a warning
>
> Mike Dean
>
> On Tue, Dec 19, 2017 at 11:36 PM, Mike Dean  wrote:
>
>> So far , it has helped!
>> In this construct, though, do I need to put the meter change in each part
>> of this system (4/4 in measure 6, 3/4 in measure 7)
>> (English accidentals used)
>> <<
>> \relative c' {
>>  \once \stemDown c2. | c4. bf8 af bf |
>>  \once \stemDown c2. | c4. bf8 af bf |
>>  \once \stemDown c2. |
>> }
>> \\
>> \relative c {
>>   2.\pp (| 2.)-> \mp \> |
>>   2.\pp (| 2.)-> \mp \> |
>>   2.\pp
>> }
>>   >>
>> Next two measures
>> \time 4/4
>> c4 c8 bf af gf
>> ---
>> 1
>>
>> \time 3/4
>> < e g! c >2 \> < d! f b! >4 | < e g c >4. < f a >8 /mp  
>>
>> Mike Dean
>>
>> On Tue, Dec 19, 2017 at 7:03 PM, Carl Sorensen 
>> wrote:
>>
>>>
>>>
>>> From: Mike Dean 
>>>
>>> Measures 1,3,5 are chords, while measures 2,4,6 has the temporary
>>> polyphony and trying to fit what I want to do into the example is a
>>> struggle...
>>>
>>> I use \stemDown to put the stem down and merge it with the chord:
>>>
>>> {
>>>   \clef bass
>>>   \time 3/4
>>>   <<
>>> \relative c' {
>>>   \once \stemDown c2. |
>>>   c4. bes8 aes bes
>>> } \\
>>> \relative c {
>>>   2.(  |
>>>   2.)
>>> }
>>>   >>
>>> }
>>>
>>>
>>> HTH,
>>>
>>> Carl
>>>
>>>
>>>
>>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Beam question

2017-12-21 Thread Mike Dean 
In a piece with a double backslash to denote voices

  \clef treble
  \key c \major
  \time 3/4
<< { d, g d g fs a | d, g d g }
   \\
   {  q  | q }>>

The construct  ends after beat 2, leaving the four eighth notes unbeamed.
is there something in the manual beaming syntax that I can use to beam the
four notes?





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

Re: Beam question

2017-12-21 Thread Ben 

On 12/21/2017 1:05 PM, Mike Dean wrote:

In a piece with a double backslash to denote voices

  \clef treble
  \key c \major
  \time 3/4
<< { d, g d g fs a | d, g d g }
       \\
       {  q  | q }>>

The construct  ends after beat 2, leaving the four eighth notes 
unbeamed. is there something in the manual beaming syntax that I can 
use to beam the four notes?






Hi Mike,
I'm afraid your code does not compile due to failed bar checks. I don't 
see any eighth notes.

Can you re-check the code? :) They are all quarter notes in 3/4 time.

\version "2.19.80"
\language "english"
  \clef treble
  \key c \major
*\time 3/4*
<< { d, g d g fs a | d, g d g }
   \\
   {  q  | q }>>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Beam question

2017-12-21 Thread Mike Dean 
Ben: That serves me right for ripping a text out of context and forgetting
to put an "8" after the first note in the snippet...
\version "2.19.80"
\language "english"
  \clef treble
  \key c \major
  *\time 3/4*
<< { d,8 g d g fs a | d, g d g }
   \\
   {  q  | q }>>

Mike Dean

On Thu, Dec 21, 2017 at 1:13 PM, Ben  wrote:

> On 12/21/2017 1:05 PM, Mike Dean wrote:
>
> In a piece with a double backslash to denote voices
>
>   \clef treble
>   \key c \major
>   \time 3/4
> << { d, g d g fs a | d, g d g }
>\\
>{  q  | q }>>
>
> The construct  ends after beat 2, leaving the four eighth notes unbeamed.
> is there something in the manual beaming syntax that I can use to beam the
> four notes?
>
>
>
>
> Hi Mike,
> I'm afraid your code does not compile due to failed bar checks. I don't
> see any eighth notes.
> Can you re-check the code? :) They are all quarter notes in 3/4 time.
>
> \version "2.19.80"
> \language "english"
>   \clef treble
>   \key c \major
>   *\time 3/4*
> << { d, g d g fs a | d, g d g }
>\\
>{  q  | q }>>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reduce PianoStaves for rest

2017-12-21 Thread Helge Kruse 
I have a score for an orchestra instrument (harp). The harp starts after 
tens of measures. There are several meter changes. Therfore a simple 
multi-measure-rest is inappropriate. Instead I would like to write all 
measures and meter changes, so that the harpist can follow the music and 
get the right moment to start.


For that purpose it's not necessary to write this multi lines of rest 
measures in two staves. I would like to reduce the lines that have only 
rests to a single staff line. I.e. somthing similar like 
\RemoveEmptyStaves, but it should leave one staff line. I tried to adapt 
http://lsr.di.unimi.it/LSR/Item?id=307 and changed ChoirStaff to 
PianoStaff. But this doesn't work if I make this change.


Any idea?

Best regards
Helge



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

Re: Beam question

2017-12-21 Thread Ben 

On 12/21/2017 1:16 PM, Mike Dean wrote:
Ben: That serves me right for ripping a text out of context and 
forgetting to put an "8" after the first note in the snippet...

\version "2.19.80"
\language "english"
  \clef treble
  \key c \major
*\time 3/4*
<< { d,8 g d g fs a | d, g d g }
   \\
   {  q  | q }>>

Mike Dean

On Thu, Dec 21, 2017 at 1:13 PM, Ben > wrote:


On 12/21/2017 1:05 PM, Mike Dean wrote:

In a piece with a double backslash to denote voices

  \clef treble
  \key c \major
  \time 3/4
<< { d, g d g fs a | d, g d g }
       \\
       {  q  | q }>>

The construct  ends after beat 2, leaving the four eighth notes
unbeamed. is there something in the manual beaming syntax that I
can use to beam the four notes?





Hi Mike,
I'm afraid your code does not compile due to failed bar checks. I
don't see any eighth notes.
Can you re-check the code? :) They are all quarter notes in 3/4 time.

\version "2.19.80"
\language "english"
  \clef treble
  \key c \major
*\time 3/4*
<< { d, g d g fs a | d, g d g }
   \\
   {  q  | q }>>

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





Mike,

Aside from the bar check fails that still occur after you add the 8, I 
just removed them to work from a more clean slate...not a problem...


But, what exactly do you want for beams? I can't follow you. As of now, 
there are 2 sets of 4-note-beamed eighth notes. Looks good.


Where do you want the split exactly? What's the subdivision or 
screenshot of the outcome?


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

Re: lilypond-user Digest, Vol 181, Issue 111

2017-12-21 Thread Mason Hock 

Thanks for your response.

For dynamics within the staff that isn't necessary, as \magnifyStaff 
works fine.


\version "2.19.63"
\score {
<<
  \new Staff \with { \magnifyStaff #(magstep -2) }
  \relative c' { c\p\< c c c\f }
  >>
}

The issue is changing the size of a separate dynamics staff. Changing 
the font size was my solution in 2.18,


\version "2.18.2"
<<
  \new Staff \with {
fontSize = -3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
  }
  \relative c'' { c4 c c c}
  \new Dynamics \with {
fontSize = -3
\override Hairpin.height = #(magstep -3)
\override Hairpin.thickness = #(magstep -3)
  }
  { s4\p\< s s s\f }
>>

but I was hoping to use 2.19's \magnifyStaff to simplify this.

Mason


Date: Wed, 20 Dec 2017 21:27:38 -0500
From: Ben 
To: lilypond-user@gnu.org
Subject: Re: \magnifyStaff for dynamics?
Message-ID: <6c63c15d-9bd7-8893-d58a-24da56f09...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"


You could use something like this to change the font of the dynamics
too?

<<
\new Staff {
  \relative c'' {
\dynamicDown
c8\ff c c c c c c c
  }
}
\new Staff \with {
  *fontSize = #-3 \override StaffSymbol.staff-space = #(magstep -3)*
} {
  \clef bass
  c8 c c c c\f c c c
}
http://lsr.di.unimi.it/LSR/Item?id=399






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

Re: Beam question

2017-12-21 Thread Mike Dean 
[image: Inline image 1]
Well, here's hoping that this will clarify...
The simultaneous voice ends on beat 2 in the left hand, and it's those four
eighth notes I desire to beam
(Thought: would putting square braces around the last three do it? Yes, now
it is clearin reading the section I didn't get the correct mental
picture...Thanks!)

Mike Dean

On Thu, Dec 21, 2017 at 1:22 PM, Ben  wrote:

> On 12/21/2017 1:16 PM, Mike Dean wrote:
>
> Ben: That serves me right for ripping a text out of context and forgetting
> to put an "8" after the first note in the snippet...
> \version "2.19.80"
> \language "english"
>   \clef treble
>   \key c \major
>   *\time 3/4*
> << { d,8 g d g fs a | d, g d g }
>\\
>{  q  | q }>>
>
> Mike Dean
>
> On Thu, Dec 21, 2017 at 1:13 PM, Ben  wrote:
>
>> On 12/21/2017 1:05 PM, Mike Dean wrote:
>>
>> In a piece with a double backslash to denote voices
>>
>>   \clef treble
>>   \key c \major
>>   \time 3/4
>> << { d, g d g fs a | d, g d g }
>>\\
>>{  q  | q }>>
>>
>> The construct  ends after beat 2, leaving the four eighth notes unbeamed.
>> is there something in the manual beaming syntax that I can use to beam the
>> four notes?
>>
>>
>>
>>
>> Hi Mike,
>> I'm afraid your code does not compile due to failed bar checks. I don't
>> see any eighth notes.
>> Can you re-check the code? :) They are all quarter notes in 3/4 time.
>>
>> \version "2.19.80"
>> \language "english"
>>   \clef treble
>>   \key c \major
>>   *\time 3/4*
>> << { d, g d g fs a | d, g d g }
>>\\
>>{  q  | q }>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>
> Mike,
>
> Aside from the bar check fails that still occur after you add the 8, I
> just removed them to work from a more clean slate...not a problem...
>
> But, what exactly do you want for beams? I can't follow you. As of now,
> there are 2 sets of 4-note-beamed eighth notes. Looks good.
>
> Where do you want the split exactly? What's the subdivision or screenshot
> of the outcome?
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re:\magnifyStaff for dynamics?

2017-12-21 Thread Mason Hock 

Resending this with the correct subject line.

Thanks for your response.

For dynamics within the staff that isn't necessary, as \magnifyStaff 
works fine.


\version "2.19.63"
\score {
<<
  \new Staff \with { \magnifyStaff #(magstep -2) }
  \relative c' { c\p\< c c c\f }
  >>
}

The issue is changing the size of a separate dynamics staff. Changing 
the font size was my solution in 2.18,


\version "2.18.2"
<<
  \new Staff \with {
fontSize = -3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
  }
  \relative c'' { c4 c c c}
  \new Dynamics \with {
fontSize = -3
\override Hairpin.height = #(magstep -3)
\override Hairpin.thickness = #(magstep -3)
  }
  { s4\p\< s s s\f }
>>

but I was hoping to use 2.19's \magnifyStaff to simplify this.

Mason


Date: Wed, 20 Dec 2017 21:27:38 -0500
From: Ben 
To: lilypond-user@gnu.org
Subject: Re: \magnifyStaff for dynamics?
Message-ID: <6c63c15d-9bd7-8893-d58a-24da56f09...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"


You could use something like this to change the font of the dynamics
too?

<<
\new Staff {
  \relative c'' {
\dynamicDown
c8\ff c c c c c c c
  }
}
\new Staff \with {
  *fontSize = #-3 \override StaffSymbol.staff-space = #(magstep -3)*
} {
  \clef bass
  c8 c c c c\f c c c
}
http://lsr.di.unimi.it/LSR/Item?id=399








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

Re: Beam question

2017-12-21 Thread Ben 


On 12/21/2017 1:38 PM, Mike Dean wrote:

Inline image 1
Well, here's hoping that this will clarify...
The simultaneous voice ends on beat 2 in the left hand, and it's those 
four eighth notes I desire to beam
(Thought: would putting square braces around the last three do it? 
Yes, now it is clearin reading the section I didn't get the 
correct mental picture...Thanks!)


Mike Dean



Hi Mike,

I just threw this code together to show you that default beaming 
/should/ be pretty much what you want :) Glad you figured it out! Have a 
great day!


Yes you can always manually beam with the [ ]

(see attached)

\version "2.19.80"
\language "english"
  \clef treble
  \key c \major
  \time 3/4

<<
  \relative c''
  { d,8 g d g fs a  d, g d g }
   \\
   \relative c'
   { 4 q   q }>>



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

Re: Beam question

2017-12-21 Thread Ben 


On 12/21/2017 1:38 PM, Mike Dean wrote:

Inline image 1
Well, here's hoping that this will clarify...
The simultaneous voice ends on beat 2 in the left hand, and it's those 
four eighth notes I desire to beam
(Thought: would putting square braces around the last three do it? 
Yes, now it is clearin reading the section I didn't get the 
correct mental picture...Thanks!)





\version "2.19.80"
\language "english"

 <<
  \clef treble
  \key c \major
  \time 3/4
  \relative c''

  { d,8[ g d g fs a]  d, g d g }
   \\
   \relative c'
   { 4 q   q }>>

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

Re: Beam question

2017-12-21 Thread Simon Albrecht 

On 21.12.2017 19:38, Mike Dean wrote:

(Thought: would putting square braces around the last three do it?


That isn’t the right way to think of it. The [] aren’t placed _around_ 
the notes they apply to, but rather attached to the first and last notes 
as _post events_ (just like slurs, ties, fingering, articulations and 
many other things). That’s why one writes

d[ g d g]
and not
d [g d g]

Best, Simon

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

Re: Beam question

2017-12-21 Thread Mike Dean 
Thanks, Simon!
Not much of an improvement from my original thought of putting square
brackets around the group of notes, but it got me closer to the truth

Mike Dean

On Thu, Dec 21, 2017 at 3:35 PM, Simon Albrecht 
wrote:

> On 21.12.2017 19:38, Mike Dean wrote:
>
>> (Thought: would putting square braces around the last three do it?
>>
>
> That isn’t the right way to think of it. The [] aren’t placed _around_ the
> notes they apply to, but rather attached to the first and last notes as
> _post events_ (just like slurs, ties, fingering, articulations and many
> other things). That’s why one writes
> d[ g d g]
> and not
> d [g d g]
>
> Best, Simon
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Beam question

2017-12-21 Thread Mike Dean 
Original thought: [d g d g] (wound up trying to attach a beam to a quarter
rest...)
Improved: d [g d g]
Correct: d[ g d g]



Mike Dean

On Thu, Dec 21, 2017 at 3:39 PM, Mike Dean  wrote:

> Thanks, Simon!
> Not much of an improvement from my original thought of putting square
> brackets around the group of notes, but it got me closer to the truth
>
> Mike Dean
>
> On Thu, Dec 21, 2017 at 3:35 PM, Simon Albrecht 
> wrote:
>
>> On 21.12.2017 19:38, Mike Dean wrote:
>>
>>> (Thought: would putting square braces around the last three do it?
>>>
>>
>> That isn’t the right way to think of it. The [] aren’t placed _around_
>> the notes they apply to, but rather attached to the first and last notes as
>> _post events_ (just like slurs, ties, fingering, articulations and many
>> other things). That’s why one writes
>> d[ g d g]
>> and not
>> d [g d g]
>>
>> Best, Simon
>>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Reduce PianoStaves for rest

2017-12-21 Thread Robert Schmaus 
Not sure if I understand you correctly, but is this what you're looking for?

http://lilypond.org/doc/v2.18/Documentation/notation/writing-rests#full-measure-rests



> On 21 Dec 2017, at 19:20, Helge Kruse  wrote:
> 
> I have a score for an orchestra instrument (harp). The harp starts after tens 
> of measures. There are several meter changes. Therfore a simple 
> multi-measure-rest is inappropriate. Instead I would like to write all 
> measures and meter changes, so that the harpist can follow the music and get 
> the right moment to start.
> 
> For that purpose it's not necessary to write this multi lines of rest 
> measures in two staves. I would like to reduce the lines that have only rests 
> to a single staff line. I.e. somthing similar like \RemoveEmptyStaves, but it 
> should leave one staff line. I tried to adapt 
> http://lsr.di.unimi.it/LSR/Item?id=307 and changed ChoirStaff to PianoStaff. 
> But this doesn't work if I make this change.
> 
> Any idea?
> 
> Best regards
> Helge
> 
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Reduce PianoStaves for rest

2017-12-21 Thread Simon Albrecht 

On 21.12.2017 22:45, Robert Schmaus wrote:
Not sure if I understand you correctly, but is this what you're 
looking for?


http://lilypond.org/doc/v2.18/Documentation/notation/writing-rests#full-measure-rests


No, that’s not what the question was about. Helge is working on a harp 
part, and he wants systems that contain only MMRs reduced to one staff.


On 21 Dec 2017, at 19:20, Helge Kruse > wrote:


I have a score for an orchestra instrument (harp). The harp starts 
after tens of measures. There are several meter changes. Therfore a 
simple multi-measure-rest is inappropriate. Instead I would like to 
write all measures and meter changes, so that the harpist can follow 
the music and get the right moment to start.


For that purpose it's not necessary to write this multi lines of rest 
measures in two staves. I would like to reduce the lines that have 
only rests to a single staff line. I.e. somthing similar like 
\RemoveEmptyStaves, but it should leave one staff line. I tried to 
adapt http://lsr.di.unimi.it/LSR/Item?id=307 and changed ChoirStaff 
to PianoStaff. But this doesn't work if I make this change.


There’s one key difference between PianoStaff and ChoirStaff/StaffGroup: 
the Keep_alive_together_engraver. It has RemoveEmptyStaves work only on 
all or none of the staves in the PianoStaff. So you should do something 
like:


\new PianoStaff \with { \remove Keep_alive_together_engraver } <<
  \new Staff {}
  \new Staff \with { \RemoveAllEmptyStaves } {}
>>

That way only one of the staves gets removed.
(If you don’t use development versions or want it not to take effect on 
the first staff, get rid of the All.)

This is jotted down from memory, so please excuse eventual errors.

HTH, Simon

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

Re: Reduce PianoStaves for rest

2017-12-21 Thread David Kastrup 
Simon Albrecht  writes:

> \new PianoStaff \with { \remove Keep_alive_together_engraver } <<
>   \new Staff {}
>   \new Staff \with { \RemoveAllEmptyStaves } {}
>>>

Easier to just use

\new GrandStaff << ... >>

The only difference is the Keep_alive_together_engraver if I remember
correctly.

-- 
David Kastrup

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