Re: RemoveEmptyStaves doesnt remove percussion staff

[neuro黃學仁]

> \layout {
>   \context {
> \Staff
> \RemoveEmptyStaves
>   }
> %% You need to add this:
>\context {
> \DrumStaff
> \RemoveEmptyStaves
>   }
> }

Yes~ That works~
Thank you very much~

Valentin Villenave  於 2020年4月19日 週日 下午11:17寫道：
>
> On 4/16/20, neuro黃學仁  wrote:
> > How can one remove the empty percussion staff in Grandscore?
> > The \RemoveEmptyStaves seems not working on percussion staff.
>
> Greetings,
> here is a solution:
>
> 
>
> \layout {
>   indent = 2.6\cm
>   short-indent = 1.6\cm
>   \context {
> \Staff
> \RemoveEmptyStaves
>   }
> %% You need to add this:
>   \context {
> \DrumStaff
> \RemoveEmptyStaves
>   }
> }
>
> 
>
> Cheers,
> V.

Re: RemoveEmptyStaves doesnt remove percussion staff

[Valentin Villenave]

On 4/16/20, neuro黃學仁  wrote:
> How can one remove the empty percussion staff in Grandscore?
> The \RemoveEmptyStaves seems not working on percussion staff.

Greetings,
here is a solution:



\layout {
  indent = 2.6\cm
  short-indent = 1.6\cm
  \context {
\Staff
\RemoveEmptyStaves
  }
%% You need to add this:
  \context {
\DrumStaff
\RemoveEmptyStaves
  }
}



Cheers,
V.

RemoveEmptyStaves doesnt remove percussion staff

[neuro黃學仁]

How can one remove the empty percussion staff in Grandscore?
The \RemoveEmptyStaves seems not working on percussion staff.

Sample files can be reached at http://orchestra.tw/lilypond_Q
including:
00.ly
bdrum.ly
timp.ly
v1.ly
v2.ly

To run lilypond 00.ly (http://orchestra.tw/lilypond_Q/00.ly),
and it results in 00.pdf (http://orchestra.tw/lilypond_Q/00.pdf)

Thanks very much for any advise~

neuro
neu...@gmail.com

Re: remove a staff

[MING TSANG]

 Hi Simon,
For the past few days I try to code something to explain my problem.
A friend of my ask me to code jianpu. I did it by jianpu10a.ly from Paul 
Morris. the out put is good until he said he just want jianpu.  
I try not to code regular staff and I noticed the lyric is out of wack.
Then I thought if I can hide the regular Staff, this will satisfy my friend. 
That was the background of my asking help from the lilypond user community.  I 
appreciated the help from Michael Gerdan, Mark Stephen Mrotek, Karlin High, 
Graham King, Ben (soundsfromsound) and you. The result pdf is fine for the time 
being (my friend said he can live with result). Thank you everyone. 
I was debating if I should sumbit request to fixed jianpu10a.ly which Paul 
Morris provided in 2015.  Anyway I try this time. Attached is rely-test.ly file 
which is not tiny.  I complied the .ly file and generate five pdfs. The 
pdf-file-name depicts the outcome result. I hope it is not too much for such a 
request. Do I need to open up another thread?
Thank you,Ming 
On Saturday, October 12, 2019, 04:28:17 p.m. EDT, Simon Albrecht 
 wrote:  
 
 Hello Ming,

no less than six volunteers have stepped up to help you with this 
problem, and now you don’t see any need to let anyone know if you 
bypassed the problem, solved it, or simply gave up. I find that not 
exactly courteous, to say the least…

Best, Simon

On 09.10.19 03:22, MING TSANG wrote:
> Hi, lilyponders,
>
> Is it possible to remove a staff ( everything)?
>
> Thanks for the help,
> Ming
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilynd-user
  \version "2.19.83"
\language "english"



global = {
  \key d \major
  \partial 4
  \time 4/4
}



eVar =
#(define-music-function (xx start stop) (list? index? index?)
   #{ #@(map (lambda (i) #{ $xx . #i #}) (iota (- stop start -1) start)) #})
bk = \break

mel.00 = { d8 e |}
mel.01 = { fs4 a4 4. fs8 |}
mel.02 = { b4 a2 fs8 e |}
mel.03 = { d4. e8 d4 b, |}
mel.04 = { a,2 r4 fs8 e |}
mel.05 = { d4. 8 4 e |\bk}
mel.06 = { fs4 b a fs |}
mel.07 = { e4. 8 fs4 d |}
mel.08 = { e2 r4 d8 e |}
mel.09 = { fs4 a4 4. fs8 |}
mel.10 = { b4 a2 fs8 e |\bk}
mel.11 = { d4. e8 4 a4 |}
mel.12 = { fs2 r4 8 e |}
mel.13 = { d4. 8 8( c) e4 |}
mel.14 = { fs4 a e fs |}
mel.15 = { d1( |}
mel.16 = { d2) r4 fs8 a |\bk}
mel.17 = { d'4. 8 4 fs |}
mel.18 = { a4. b8 a4 fs8 a |}
mel.19 = { b4. d'8 4 b8 d' |}
mel.20 = { a2 r4 fs8 a |}
mel.21 = { d'4. 8 4 fs |\bk}
mel.22 = { a4. b8 a4 fs8 a |}
mel.23 = { d'4. e'8 d'4 b |}
mel.24 = { \time 2/4 a4. fs8 |}
mel.25 = { \time 4/4 e2 r4 d8 e |}
mel.26 = { fs4 a4 4. fs8 |\bk}
mel.27 = { b4 a2 fs8 e |}
mel.28 = { d4. e8 4 a |}
mel.29 = { fs2 r4 fs8 e |}
mel.30 = { d4. 8 4 e |}
mel.31 = { fs4 a e fs |}
mel.32 = { d2. \bar"|."}

melody = \fixed c' {
  \global
  \eVar \mel 00 32
}



verseI = \lyricmode { 
  回 頭 望 我 歲 月 匆 匆， "" 經 過 困 境 與 浪 濤·  \skip1 \skip1 倚 靠 耶 和 華 重
  造 新 生 命， 重 擔 必 卸 開·  "" "" 這 一 刻 我 縱 是 失 意， "" 失 去 
  平 靜 與 安 穩， "" "" 倚 靠 耶 和 華 令 擔 子 變 輕 省。 "" ""是 祢 
  的 犠 性 令 我 改 變， 是 祢 的 恩 典 導 我 行， "" "" 是 祢 的 恩 手 伴
  我 走 過， 是 祢 的 深 愛 不 捨 不 棄， "" "" 來 日 讓 我 仰 賴
  應 許， "" 充 滿 能 力 與 希 望， "" "" 倚 靠 耶 和 華 伴 我 一 世 走 過。
}
verse = \lyricmode { 
  回 頭 望 我 歲 月 匆 匆， 經 過 困 境 與 浪 濤·  倚 靠 耶 和 華 重
  造 新 生 命， 重 擔 必 卸 開·  這 一 刻 我 縱 是 失 意， 失 去 
  平 靜 與 安 穩， 倚 靠 耶 和 華 令 擔 子 變 輕 省。 是 祢 
  的 犠 性 令 我 改 變， 是 祢 的 恩 典 導 我 行， 是 祢 的 恩 手 伴
  我 走 過， 是 祢 的 深 愛 不 捨 不 棄， 來 日 讓 我 仰 賴
  應 許， 充 滿 能 力 與 希 望， 倚 靠 耶 和 華 伴 我 一 世 走 過。
}
hideS = { \hide Staff.BarLine
  \override Staff.StaffSymbol.line-count = #0
  \hideNotes %\hide Staff.NoteHead
  \hide Staff.TimeSignature
  \omit Score.Slur
  
  \omit Score.KeySignature   
  \hide Staff.Clef }

%%  \include "jianpu10a.ly"  %
% also works with 2.19.x and later   jianpu10a.ly

#(define (get-keysig-alt-count alt-alist)
   "Return number of sharps/flats in key sig, (+) for sharps, (-) for flats."
   (if (null? alt-alist)
   0
   (* (length alt-alist) 2 (cdr (car alt-alist)

#(define (get-major-tonic alt-count)
   "Return number of the tonic note

Re: remove a staff

[Simon Albrecht]

Hello Ming,

no less than six volunteers have stepped up to help you with this 
problem, and now you don’t see any need to let anyone know if you 
bypassed the problem, solved it, or simply gave up. I find that not 
exactly courteous, to say the least…


Best, Simon

On 09.10.19 03:22, MING TSANG wrote:

Hi, lilyponders,

Is it possible to remove a staff ( everything)?

Thanks for the help,
Ming

___
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: remove a staff

[Karlin High]

On Wed, Oct 9, 2019, 5:24 PM Simon Albrecht  wrote:

> If you don’t want a staff to be printed, why do you even have a staff in
> the first place?
>

Looks to me like this is a Chinese Jianpu notation project?

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

Re: remove a staff

[Simon Albrecht]

On 09.10.19 13:14, MING TSANG wrote:


Thank you for the answer. I am able to hide every thing except the key 
signature and bar number.  I can live of bar number but want the key 
signature hided.



Again: a qualified answer would require you giving an actual _code_ 
example, else it’s impossible to tell what you are doing that leads to 
the image. I already sent a link to the instructions on tiny examples, 
which are _very_ important.


But two hints already:

If you don’t want a staff to be printed, why do you even have a staff in 
the first place? Both Lyrics and FiguredBass work perfectly well without 
a staff.


If you want to hide (or omit) something but don’t know the grob name or 
which context it lives in, the Internal Reference (IR) is your friend. 
The Learning Manual already explains how to use it in such a case: You 
want to look at the index of grobs in section 3.1 of this manual 
. Find 
the grob you want to override (both \hide and \omit are internally 
overrides). Now you have the grob name.
If the grob happens to live in Voice (or other bottom contexts), you 
don’t need to specify the context. Otherwise you need to find out in 
which context it does live. Follow the link to its page, at the top of 
that page follow the link to the Engraver that creates the grob, e.g. 
. 
Now at the _bottom_ of that page you can read: “Bar_number_engraver is 
part of the following context(s): Score.” So you need


\omit Score.BarLine

HTH, Simon


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

Re: remove a staff

[Simon Albrecht]

On 09.10.19 15:34, Graham King wrote:

BTW, Simon, did you reply and omit to copy the list?


No, I’ve been busy since noon.

Best, Simon


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

Re: remove a staff

[MING TSANG]

Michael,
Thank you. Please refer answer to Simon & Graham.
Thanks,
Ming.

Sent from my iPhone

> On Oct 8, 2019, at 10:39 PM, Michael Gerdau  wrote:
> 
> Yes, that’s possible.
> 
> Care to provide a MWE so that I or others could easily show you how?
> 
> Kind regards,
> Michael
> 
> Mobil gesendet
> 
>> Am 08.10.2019 um 22:23 schrieb MING TSANG :
>> 
>> 
>> Hi, lilyponders,
>> 
>> Is it possible to remove a staff ( everything)?
>> 
>> Thanks for the help,
>> Ming
>> ___
>> 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: remove a staff

[Graham King]

How about this?  It gets you a bit closer to what you want, but \omit 
Score.Barline seems to take effect too early.  I'll leave it to the real 
experts to comment on that.

BTW, Simon, did you reply and omit to copy the list?

\version "2.19.82"

hideS = {
  \stopStaff
  \hideNotes
  \hide Staff.TimeSignature
  \hide Staff.Clef
  \omit Score.Slur
  \omit Score.KeySignature
  \omit Score.Tie
  \omit Score.BarNumber
  \omit Score.BarLine
}

unhideS = {
  \startStaff
  \unHideNotes
  \undo \hide Staff.TimeSignature
  \undo \hide Staff.Clef
  \undo \omit Score.Slur
  \undo \omit Score.KeySignature
  \undo \omit Score.Tie
  \undo \omit Score.BarNumber
  \undo \omit Score.BarLine
}

lineofnotes = { \repeat unfold 6 { cis''2 ~ cis''4( d''4 ) } \break }

notes = {
  \key d \major
  \lineofnotes
  \hideS
  \lineofnotes
  \unhideS
  \lineofnotes
}

words = \lyricmode { \repeat unfold 18 la  }

\score{
  <<
\new Voice = "one" {
  \notes
}
\new Lyrics \lyricsto "one" \words
  >>
  \layout { }
}


> On 9 Oct 2019, at 12:37, MING TSANG  wrote:
> 
> Hi, Graham:
> 
> Thank you verymuch for the answer.
> I manage to use the following code to  hide every on the staff except the bar 
> number and key signature. I can live with bar number, but would like to hide 
> the key signature as well.
>  
> hideS = { \hide Staff.BarLine
>   \override Staff.StaffSymbol.line-count = #0
>   \hideNotes %\hide Staff.NoteHead
>   \hide Staff.TimeSignature
>   \hide Staff.Clef }
> 
> The result:
> <1570620986187blob.jpg>
> Thanks,
> Ming.
> On Wednesday, October 9, 2019, 05:49:17 a.m. EDT, Graham King 
>  wrote:
> 
> 
> 
>> On 9 Oct 2019, at 02:22, MING TSANG > <mailto:tsan...@rogers.com>> wrote:
>> 
>> Hi, lilyponders,
>> 
>> Is it possible to remove a staff ( everything)?
>> 
>> Thanks for the help,
>> Ming
> 
> Hi Ming,
> you need to give us some context, or you'll just get the answer "yes" !
> 
> For example, if you're trying to remove a staff from a system when that staff 
> contains just empty bars, the answer might be \RemoveEmptyStaves.  But if 
> you're trying to remove an entire part from a score, the answer will be 
> different and will include advice about how to structure the lilypond code.
> 
> Over to you.
> 
> -- Graham
> 
> <1570620986187blob.jpg>

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

Re: remove a staff

[MING TSANG]

 Hi, Graham:
Thank you verymuch for the answer.I manage to use the following code to  hide 
every on the staff except the bar number and key signature. I can live with bar 
number, but would like to hide the key signature as well. hideS = { \hide 
Staff.BarLine          \override Staff.StaffSymbol.line-count = #0          
\hideNotes %\hide Staff.NoteHead          \hide Staff.TimeSignature          
\hide Staff.Clef }
The result:
Thanks,Ming.On Wednesday, October 9, 2019, 05:49:17 a.m. EDT, Graham King 
 wrote:  
 
 

On 9 Oct 2019, at 02:22, MING TSANG  wrote:
Hi, lilyponders,
Is it possible to remove a staff ( everything)?
Thanks for the help,Ming

Hi Ming,you need to give us some context, or you'll just get the answer "yes" !
For example, if you're trying to remove a staff from a system when that staff 
contains just empty bars, the answer might be \RemoveEmptyStaves.  But if 
you're trying to remove an entire part from a score, the answer will be 
different and will include advice about how to structure the lilypond code.
Over to you.
-- Graham
  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: remove a staff

[MING TSANG]

 Hi, Simon,
Thank you for the answer. I am able to hide every thing except the key 
signature and bar number.  I can live of bar number but want the key signature 
hided.
Please refer to :


On Wednesday, October 9, 2019, 06:40:46 a.m. EDT, Simon Albrecht 
 wrote:  
 
 Kidding aside: of course it’s possible, but it’s not clear what your 
problem is. Why can’t you remove a staff? Do you want to hide it in 
certain systems only? We need more context and at best an example to 
answer the question.

http://lilypond.org/tiny-examples.html

Best, Simon

On 09.10.19 03:22, MING TSANG wrote:
> Hi, lilyponders,
>
> Is it possible to remove a staff ( everything)?
>
> Thanks for the help,
> Ming
>
> ___
> 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: remove a staff

[Graham King]

> On 9 Oct 2019, at 02:22, MING TSANG  wrote:
> 
> Hi, lilyponders,
> 
> Is it possible to remove a staff ( everything)?
> 
> Thanks for the help,
> Ming

Hi Ming,
you need to give us some context, or you'll just get the answer "yes" !

For example, if you're trying to remove a staff from a system when that staff 
contains just empty bars, the answer might be \RemoveEmptyStaves.  But if 
you're trying to remove an entire part from a score, the answer will be 
different and will include advice about how to structure the lilypond code.

Over to you.

-- Graham

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

Re: remove a staff

[MING TSANG]

 Hi, Graham & Simon:Additional info, I also find the tie (slur) not hide. How 
to hide at least the key signature abd the tie/slur. I can live with bar 
number.  Refer to image :
 Thanks,Ming 
On Wednesday, October 9, 2019, 07:37:30 a.m. EDT, MING TSANG 
 wrote:  
 
  Hi, Graham:
Thank you verymuch for the answer.I manage to use the following code to  hide 
every on the staff except the bar number and key signature. I can live with bar 
number, but would like to hide the key signature as well. hideS = { \hide 
Staff.BarLine          \override Staff.StaffSymbol.line-count = #0          
\hideNotes %\hide Staff.NoteHead          \hide Staff.TimeSignature          
\hide Staff.Clef }
The result:
Thanks,Ming.On Wednesday, October 9, 2019, 05:49:17 a.m. EDT, Graham King 
 wrote:  
 
 

On 9 Oct 2019, at 02:22, MING TSANG  wrote:
Hi, lilyponders,
Is it possible to remove a staff ( everything)?
Thanks for the help,Ming

Hi Ming,you need to give us some context, or you'll just get the answer "yes" !
For example, if you're trying to remove a staff from a system when that staff 
contains just empty bars, the answer might be \RemoveEmptyStaves.  But if 
you're trying to remove an entire part from a score, the answer will be 
different and will include advice about how to structure the lilypond code.
Over to you.
-- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: remove a staff

[Simon Albrecht]

On 09.10.19 03:22, MING TSANG wrote:

Hi, lilyponders,

Is it possible to remove a staff ( everything)?

Yes.

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

Re: remove a staff

[Simon Albrecht]

Kidding aside: of course it’s possible, but it’s not clear what your 
problem is. Why can’t you remove a staff? Do you want to hide it in 
certain systems only? We need more context and at best an example to 
answer the question.


http://lilypond.org/tiny-examples.html

Best, Simon

On 09.10.19 03:22, MING TSANG wrote:

Hi, lilyponders,

Is it possible to remove a staff ( everything)?

Thanks for the help,
Ming

___
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: remove a staff

[Mark Stephen Mrotek]

Ming,

 

Perhaps

http://lilypond.org/doc/v2.19/Documentation/notation/context-modification-identifiers

 

Mark

 

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of MING TSANG
Sent: Tuesday, October 08, 2019 6:23 PM
To: Lilypond-usermailinglist 
Subject: remove a staff

 

Hi, lilyponders,

 

Is it possible to remove a staff ( everything)?

 

Thanks for the help,

Ming

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

Re: remove a staff

[Ben]

On 10/8/2019 9:22 PM, MING TSANG wrote:

Hi, lilyponders,

Is it possible to remove a staff ( everything)?

Thanks for the help,
Ming



Ming,

An empty staff?

Or do you mean staves with music on them?

If the latter, maybe try this approach:


hideMusic = { \set Staff.keepAliveInterfaces = #'() }
showMusic =   \unset Staff.keepAliveInterfaces

or

showStaff = \set Staff.keepAliveInterfaces = #'(bar-line-interface)
hideStaff = \set Staff.keepAliveInterfaces = #'()
resetStaff = \unset Staff.keepAliveInterfaces



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

Re: remove a staff

[Michael Gerdau]

Yes, that’s possible.

Care to provide a MWE so that I or others could easily show you how?

Kind regards,
Michael

Mobil gesendet

> Am 08.10.2019 um 22:23 schrieb MING TSANG :
> 
> 
> Hi, lilyponders,
> 
> Is it possible to remove a staff ( everything)?
> 
> Thanks for the help,
> Ming
> ___
> 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

remove a staff

[MING TSANG]

Hi, lilyponders,
Is it possible to remove a staff ( everything)?
Thanks for the help,Ming___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Remove 3rd Staff in PianoStaff if empty

[Malte Meyn]

Am 15.08.2015 um 15:49 schrieb Orm Finnendahl:

I tried all sorts of combinations of removing and consisting the
keep-alive-together engraver, tried to create an explicit staffgroup
for the main piano staves within the PianoStaff (this results in
loosing the centered instrument name and the curly braces), but it
didn't work.


If PianoStaff accepts StaffGroup the alignment works, so here is a solution:

\version 2.19.25

\new PianoStaff \with {
  instrumentName = Piano
} 
  \new Staff {
R1 % music
  }
  \new StaffGroup 
\new Staff {
  R1 % music
}
\new Staff {
  R1 % music
}
  


\layout {
  \context {
\Staff
\RemoveEmptyStaves
  }
  \context {
\StaffGroup
\consists Keep_alive_together_engraver
\remove System_start_delimiter_engraver
  }
  \context {
\PianoStaff
\accepts StaffGroup
\remove Keep_alive_together_engraver
  }
}

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

Remove 3rd Staff in PianoStaff if empty

[Orm Finnendahl]

Hi,

 in a piano score I'm writing sometimes a third staff on top of the
other two standard staffs (with a G^15 clef) is used.

I would like to remove this staff if empty, but *always* have the
other two staffs active. If I remove the
Keep_alive_together_engraver from the PianoStaff, every staff can
get removed, which is not optimal as this requires manual tweaking.

I tried all sorts of combinations of removing and consisting the
keep-alive-together engraver, tried to create an explicit staffgroup
for the main piano staves within the PianoStaff (this results in
loosing the centered instrument name and the curly braces), but it
didn't work.

Does anybody know of a solution?

--
Orm

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

Re: Remove 3rd Staff in PianoStaff if empty

[Orm Finnendahl]

Am Samstag, den 15. August 2015 um 16:04:02 Uhr (+0200) schrieb Malte Meyn:
 
 If PianoStaff accepts StaffGroup the alignment works, so here is a solution:

great, thanks!

--
Orm

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

Cannot remove empty staff when dynamic staff is added between piano staff

[MING TSANG]

Hi, lilyponders:

I compile the dropbox share .ly file  with dynamic staff between piano right  
left. the RemoveEmptyStaff is not working anymore.   I hope reader of this 
email can read the following dropbox share 

https://www.dropbox.com/s/emu5vxueljsem7q/test-with-dynamic-staff.ly

https://www.dropbox.com/s/8uvz5y2kzoterkz/test-with-dynamic-staff_remove-empty-staff-works.pdf

https://www.dropbox.com/s/l08l5zkczvttzxu/test-with-dynamic-staff_remove-empty-statt-not-working.pdf


When I comment out %\dynamicPianoPart (line # 236) the RemoveEmptyStaff works.
questions:
1. How to resolve it?  it seems that by adding dynamic staff, the piano right 
and left (rests) no longer an empty staff.
2. What is missing?
3. Is it proper the way I code RemoveEmptyStaff in \layout { .. }?

Sorry about the length of the .ly file.  This is how I can show the problem. 

Your help is appreciated.
Emmanuel,
Ming___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Cannot remove empty staff when dynamic staff is added between pianostaff

[Phil Holmes]

- Original Message - 
From: MING TSANG

To: lilypond-user mailinglist
Sent: Friday, February 07, 2014 11:59 AM
Subject: Cannot remove empty staff when dynamic staff is added between 
pianostaff


[snip html text]

Sorry about the length of the .ly file.  This is how I can show the 
problem.


It pains me to give you the answer somewhat, because I really should point 
you to


http://lilypond.org/tiny-examples.html

It really would have been the work of a few minutes to cut this example down 
to a few lines.  Please try to do this in future.


However:

\context {
 \Dynamics \RemoveEmptyStaves
}

is what you want.  The dynamics context is not a staff context, is it?

--
Phil Holmes 



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

Re: Cannot remove empty staff when dynamic staff is added between pianostaff

[MING TSANG]

Thanks.  It works after added the suggested code.

I will try to code a tiny sample in the future.   Thanks for the solution.

Emmanuel,
Ming



On Friday, February 7, 2014 7:24:00 AM, Phil Holmes m...@philholmes.net wrote:
 
- Original Message - 

From: MING TSANG
To: lilypond-user mailinglist
Sent: Friday, February 07, 2014 11:59 AM
Subject: Cannot remove empty staff when dynamic staff is added between 
pianostaff

[snip html text]

 Sorry about the length of the .ly file.  This is how I can show the 
 problem.

It pains me to give you the answer somewhat, because I really should point 
you to

http://lilypond.org/tiny-examples.html

It really would have been the work of a few minutes to cut this example down 
to a few lines.  Please try to do this in future.

However:

\context {
  \Dynamics \RemoveEmptyStaves
}

is what you want.  The dynamics context is not a staff context, is it?

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[David Kastrup]

Thomas Ruedas rue...@dtm.ciw.edu writes:

 Hi Kieren,
 On 27/4/12 3:00 AM, Kieren MacMillan wrote:
 I doubt that this new default behavior reflects common practice, though
 As a pianist, I can tell you it absolutely does reflect common engraving
 practice for piano staves: It is a very rare piano score (perhaps 1/10 of 1%)
 that contains only a single staff. That is precisely the reason
 Keep_alive_together_engraver was [fairly recently] added to Lilypond.
 to avoid misunderstandings, my full statement was this:
 I doubt that this new default behavior reflects common practice, though;
 to me, it doesn't make much sense, and I'd like to suggest to the developers
 (in case they read this) to reconsider this and keep empty staves only if
 the total number of staffs would otherwise be one (or maybe not even then).
 i.e., my main concern here is the situation where you may have more
 than two staves, which is a much more common situation.

Why would you be using a PianoStaff for those?

-- 
David Kastrup


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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Thomas Ruedas]

Hi Kieren,
On 27/4/12 3:41 AM, Kieren MacMillan wrote:

It should be easy to define a custom context (e.g. MultiStaffPiano) to behave
this way — perhaps when you've got it worked out as you think it should behave,
you can add it to the codebase?
I would like to, but I guess I would have to know GUILE/Scheme and/or 
C++ in order to do that, and I don't even have the most basic knowledge 
of those languages. I'm only an end-user, and a rather inexperienced 
one. Maybe I'll try sometime and take a look, but don't hold your breath 
for it.

Cheers,
Thomas
--
---
Thomas Ruedas
http://www.dtm.ciw.edu/users/ruedas/

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Thomas Ruedas]

Hi David,
On 27/4/12 10:34 AM, David Kastrup wrote:

Thomas Ruedasrue...@dtm.ciw.edu  writes:

i.e., my main concern here is the situation where you may have more
than two staves, which is a much more common situation.

Why would you be using a PianoStaff for those?

I'm not sure I understand what you are wondering about.
I chose a PianoStaff, because, well, it's a piece for piano :-). Being a 
rather unsophisticated user, I chose it because it would give me the 
correct layout (in particular a staff with a brace instead of a 
bracket), and as I said, it behaved exactly the way I expected in an 
earlier version.
In some piano music, you may have three different levels, as it were, 
e.g. a melodic line in the treble, played by the right hand, a deep bass 
consisting of long notes in the left hand, and in between chords filling 
in the time between the bass notes, also played by the left hand. In 
such a situation, which would likely involve large jumps of the left 
hand that may even reach into the realm of the treble clef, the score is 
easier to read if you distribute the notes played by the left hand on 
two staves and have the line of the right hand in the third (uppermost) 
staff.

Thomas
--
---
Thomas Ruedas
http://www.dtm.ciw.edu/users/ruedas/

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[David Nalesnik]

Hi,

In some piano music, you may have three different levels, as it were, e.g.
 a melodic line in the treble, played by the right hand, a deep bass
 consisting of long notes in the left hand, and in between chords filling in
 the time between the bass notes, also played by the left hand. In such a
 situation, which would likely involve large jumps of the left hand that may
 even reach into the realm of the treble clef, the score is easier to read
 if you distribute the notes played by the left hand on two staves and have
 the line of the right hand in the third (uppermost) staff.


And sometimes four can be used, as in Rachmaninoff's Prelude in C# minor
where the number of staves to a system fluctuates between two and four:


http://javanese.imslp.info/files/imglnks/usimg/0/02/IMSLP00333-Rachmaninoff_-_Fantasy_Pieces_2.pdf

Can't think of an example off-hand that uses more.

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Kieren MacMillan]

Hi Thomas,

 I would like to, but I guess I would have to know GUILE/Scheme and/or C++ in 
 order to do that

Not really… Just Lilypond.
What are the features/behaviours you want? I'm sure we can quickly build it 
together.

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

\RemoveEmptyStaffContext doesn't remove empty staff

[Thomas Ruedas]

Hi again,
I have a piano score in which there are sometimes two, sometimes three 
staves, and I want the empty third staff to disappear during long 
stretches in which it is empty. This used to work in an earlier version 
(2.10) but after having converted to 2.14.2, it doesn't anymore. Below 
follows a short example that reproduces the problem; it follows the 
approach given in the example snippet from 
http://lilypond.org/doc/v2.15/input/regression/collated-files.html, 
which is similar to my original.

Any ideas, anybody?
Thanks,
Thomas

\version 2.14.2
\paper {
  #(set-paper-size a4)
}

scoreAGlobal = {
  \key bes \major
  \numericTimeSignature
  \time 6/8
  \partial 8
}

scoreARight = {
  \scoreAGlobal
  \relative { \partial 16*2 g'16\p a
  \repeat unfold 24 { bes4 f'8 }
  }
}

scoreAMiddle = {
  \scoreAGlobal
  \relative { \partial 16*2 g,16 a
  \repeat unfold 24 { bes4 f'8 }
  }
}

scoreALeft = {
  \scoreAGlobal
  s8 s2.*10  % --- doesn't work with r8 r8.*10 either
  %
  r4. r4 \relative { a, a,8~
 %
 a a,4 a a,8~ a a,4 r8
  }
}

\score {
  \new PianoStaff \with {
instrumentName = Klavier
  } 
\new Staff = right \with {
  midiInstrument = acoustic grand
} \scoreARight
\new Staff = middle \with {
  midiInstrument = acoustic grand
} { \clef bass \scoreAMiddle }
\new Staff = left \with {
  midiInstrument = acoustic grand
} { \clef bass \scoreALeft }
  
  \layout {
\context {
  \RemoveEmptyStaffContext
}
\context {
  \Score
  \override VerticalAxisGroup #'remove-first = ##t
}
  }
}
--

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Choan Gálvez]

On 4/27/12 01:51 , Thomas Ruedas wrote:

Hi again,
I have a piano score in which there are sometimes two, sometimes three
staves, and I want the empty third staff to disappear during long
stretches in which it is empty. This used to work in an earlier version
(2.10) but after having converted to 2.14.2, it doesn't anymore. Below
follows a short example that reproduces the problem; it follows the
approach given in the example snippet from
http://lilypond.org/doc/v2.15/input/regression/collated-files.html,
which is similar to my original.
Any ideas, anybody?
Thanks,
Thomas

\version 2.14.2
\paper {
#(set-paper-size a4)
}

scoreAGlobal = {
\key bes \major
\numericTimeSignature
\time 6/8
\partial 8
}

scoreARight = {
\scoreAGlobal
\relative { \partial 16*2 g'16\p a
\repeat unfold 24 { bes4 f'8 }
}
}

scoreAMiddle = {
\scoreAGlobal
\relative { \partial 16*2 g,16 a
\repeat unfold 24 { bes4 f'8 }
}
}

scoreALeft = {
\scoreAGlobal
s8 s2.*10 % --- doesn't work with r8 r8.*10 either
%
r4. r4 \relative { a, a,8~
%
a a,4 a a,8~ a a,4 r8
}
}

\score {
\new PianoStaff \with {
instrumentName = Klavier
} 
\new Staff = right \with {
midiInstrument = acoustic grand
} \scoreARight
\new Staff = middle \with {
midiInstrument = acoustic grand
} { \clef bass \scoreAMiddle }
\new Staff = left \with {
midiInstrument = acoustic grand
} { \clef bass \scoreALeft }
 
\layout {
\context {
\RemoveEmptyStaffContext
}
\context {
\Score
\override VerticalAxisGroup #'remove-first = ##t
}
}
}


Hi Thomas.

Check this thread: 
http://lists.gnu.org/archive/html/lilypond-user/2010-11/msg00427.html.


According to 
http://lists.gnu.org/archive/html/lilypond-user/2010-11/msg00429.html, 
there was a new engraver added to keep alive every staff from a 
PianoStaff while there's one of them alive.


You can remove that engraver by adding

  \context {
\PianoStaff
\remove Keep_alive_together_engraver
  }

to your \layout definitions.

Best.
--
Choan Gálvez

Ukecosas. Los ukeleles que nos gustan, también para ti
Visítanos: http://ukecosas.es/



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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Thomas Morley]

Am 27. April 2012 01:51 schrieb Thomas Ruedas rue...@dtm.ciw.edu:
 Hi again,
 I have a piano score in which there are sometimes two, sometimes three
 staves, and I want the empty third staff to disappear during long stretches
 in which it is empty. This used to work in an earlier version (2.10) but
 after having converted to 2.14.2, it doesn't anymore.

Hi Thomas,

this is a new feature with 2.14.
The Keep_alive_together_engraver: Per default a PianoStaff is
removed only when all staves are empty. A single staff isn't deleted
any more.
If you want this behaviour, remove the Keep_alive_together_engraver.

Your layout should look:

 \layout {
   \context {
 \RemoveEmptyStaffContext
   }
  \context {
 \PianoStaff
 \remove Keep_alive_together_engraver
  }
   \context {
 \Score
 \override VerticalAxisGroup #'remove-first = ##t
   }
 }

 Below follows a short
 example that reproduces the problem; it follows the approach given in the
 example snippet from
 http://lilypond.org/doc/v2.15/input/regression/collated-files.html, which is
 similar to my original.

Would be nice If you name the sippet, the regression-test is very large.

Cheers,
  Harm

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Thomas Ruedas]

Hi Choan and Harm,
thanks for the prompt reply.
On 27/4/12 2:28 AM, Thomas Morley wrote:

this is a new feature with 2.14.
The Keep_alive_together_engraver: Per default a PianoStaff is
removed only when all staves are empty. A single staff isn't deleted
any more.
If you want this behaviour, remove the Keep_alive_together_engraver.

Ah, that explains everything! Yes, now it works as it should.
I doubt that this new default behavior reflects common practice, though; 
to me, it doesn't make much sense, and I'd like to suggest to the 
developers (in case they read this) to reconsider this and keep empty 
staves only if the total number of staffs would otherwise be one (or 
maybe not even then).

Below follows a short
example that reproduces the problem; it follows the approach given in the
example snippet from
http://lilypond.org/doc/v2.15/input/regression/collated-files.html, which is
similar to my original.

Would be nice If you name the sippet, the regression-test is very large.

For the record, the snippet is in
http://lilypond.org/doc/v2.15/input/regression/b5/lily-f6f979e0.ly
the link to which can be found by searching for 
\RemoveEmptyStaffContext on that webpage. The example in it is not a 
PianoStaff, however, but some general sort of staff; I hadn't expected 
this to be the crucial difference.

Best,
Thomas
--

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Kieren MacMillan]

Hi Thomas,

 I doubt that this new default behavior reflects common practice, though

As a pianist, I can tell you it absolutely does reflect common engraving 
practice for piano staves: It is a very rare piano score (perhaps 1/10 of 1%) 
that contains only a single staff. That is precisely the reason 
Keep_alive_together_engraver was [fairly recently] added to Lilypond.

Of course, engraving practice is different for other multi-staff instruments 
(e.g., harp often uses a single staff) — but in that case, you can simply 
define a custom context (e.g., HarpStaff) in which the 
Keep_alive_together_engraver is removed by default.

Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Thomas Ruedas]

Hi Kieren,
On 27/4/12 3:00 AM, Kieren MacMillan wrote:

I doubt that this new default behavior reflects common practice, though

As a pianist, I can tell you it absolutely does reflect common engraving
practice for piano staves: It is a very rare piano score (perhaps 1/10 of 1%)
that contains only a single staff. That is precisely the reason
Keep_alive_together_engraver was [fairly recently] added to Lilypond.

to avoid misunderstandings, my full statement was this:

I doubt that this new default behavior reflects common practice, though;
to me, it doesn't make much sense, and I'd like to suggest to the developers
(in case they read this) to reconsider this and keep empty staves only if
the total number of staffs would otherwise be one (or maybe not even then).
i.e., my main concern here is the situation where you may have more than 
two staves, which is a much more common situation. The case I wanted to 
make in the first place is to drop empty staves beyond the second staff, 
and in the piano scores I have (e.g. Debussy or Messiaen), it is done 
that way. As for the case of a single piano staff, you are right that it 
is very rare; I can only recall one instance in one of Messiaen's Vingt 
Regards sur l'Enfant Jésus (where it was actually printed as a single 
staff score for several lines).

Cheers,
Thomas
--

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

Re: \RemoveEmptyStaffContext doesn't remove empty staff

[Kieren MacMillan]

Hi Thomas,

 i.e., my main concern here is the situation where you may have more than two 
 staves, which is a much more common situation. The case I wanted to make in 
 the first place is to drop empty staves beyond the second staff, and in the 
 piano scores I have (e.g. Debussy or Messiaen), it is done that way.

It should be easy to define a custom context (e.g. MultiStaffPiano) to behave 
this way — perhaps when you've got it worked out as you think it should behave, 
you can add it to the codebase?

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

Remove prefatory staff lines

[Mark Knoop]

Hi all,

I'm trying to remove the empty staff lines that occur when a new staff
is created coinciding with a clef change in another staff - see example.
I've tried various settings of explicitClefVisibility which haven't
worked so far. Any ideas?

As a last resort I'll just whack a white postscript box over it, but I
was hoping there might be a more elegant solution.

\version 2.11.44
\paper{ ragged-right=##t }
{
c'1
 {
\clef bass c'1
} \new Staff \with { \remove Clef_engraver } {
c''1
} 
}

-- 
Mark Knoop


test1.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user