Re: Four Part Piano Staff
On Mon 01 Feb 2016 at 20:31:27 (-0800), Mark Stephen Mrotek wrote:
> In the past I have used the "variable" format.
Naturally.
> This leads to some repeated adjustments in the placement of the second voice.
I don't understand what you mean by "repeated adjustments".
> I prefer not to use variable, yet rather code within the Piano Staff group.
But that throws away one of the great strengths of LP: the separation
of form and content. Obviously one can replace any use of a variable
by its definition, as in
foo = { a b c d }
\new Voice { \foo }
replaced by
\new Voice { a b c d }
but look at what you lose...
Here's a carol with four independent lines, completely defined in
nine variables (drastically compressed for this email):
[... some house-style includes, version, language ...]
global = { \tempo "Leggiero e scherzando" 4=120 \key bf \major \time 4/4
s1 * 13 \bar "||" \key g \major \time 3/4 s2. * 8 \time 4/4 s1 * 4 ... }
soprano = \relative { R1 R1 R1 r2 r4 bf'8 ^\mf c ... }
alto = \relative { R1 R1 r2 r4 r8 ef' ^\mf ... }
tenor = \relative { R1 r2 r4 r8 bf ^\mf c8 d ef c d4~ d8 r ... }
bass = \relative { r2 r4 f8 ^\mf f f4 bf8 bf bf4 bf8 r R1 ... }
sopranotext = \lyricmode { and a pro -- per Christ -- mas tree.” ... }
altotext = \lyricmode { “I’ve bought a nice fresh tur -- key ... }
tenortext = \lyricmode { my true love said to me, __ ... }
basstext = \lyricmode { On the first day of Christ -- mas }
First we generate five cyberbass-style midi files with a
potted ily that overrides the dynamics, for tutti and all
four parts. I have files for saatb, sattb, etc but won't
bother with their implementation here.
\include "Midi-satb.ily"
Now the vocal score with beams broken at the crochet beat:
#(set-global-staff-size 16)
\book { \bookOutputSuffix "vocal" \score {
\new GrandStaff << \set GrandStaff.beamExceptions = ...
\new Staff << \clef treble \global
\new Voice { \soprano } \addlyrics { \sopranotext } >>
\new Staff << \clef treble \global
\new Voice { \alto } \addlyrics { \altotext } >>
\new Staff << \clef "treble_8" \global
\new Voice { \tenor } \addlyrics { \tenortext } >>
\new Staff << \clef bass \global
\new Voice { \bass } \addlyrics { \basstext } >>
>> \layout { }
}
}
Now a piano version for people who don't play from four staves,
with longer beams, and dynamics removed for clarity.
#(set-global-staff-size 17)
\book { \bookOutputSuffix "piano" \score {
\new PianoStaff <<
\new Staff << \clef treble \global
\new Voice { \voiceOne \soprano } \new Voice { \voiceTwo \alto } >>
\new Staff << \clef bass \global
\new Voice { \voiceOne \tenor } \new Voice { \voiceTwo \bass } >>
>> \layout { \context { \Voice \remove "Dynamic_engraver" } }
}
}
I routinely do transposed parts for altos (who don't appreciate
singing early music from tenor clefs in low keys), and so on.
So much is impractical without putting the music into variables.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
On 02.02.2016 03:25, Mark Stephen Mrotek wrote:
Hello,
I want to make a template for a piano staff with two explicitly
instantiated voices (not <<{ } \\{ } >>) in each staff – this for four
part fugues.
Any assistance in accomplishing this would be greatly appreciated.
To come back to your original question: how about the following?
\new Staff = "foo" <<
\time 7/32
\key fes \minor
\new Voice = "soprano" { \voiceOne bisis'32.. }
\new Voice = "alto" { \voiceTwo a'\breve }
>>
If that’s not basically what you want, please be more specific.
Yours, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Four Part Piano Staff
Simon,
Thank you for your reply and the suggested code. What you provide works well
with a single staff - as presented in the documentation. When inserted into
a piano staff two additional staves are included between the two piano
staves.
Mark
-Original Message-
From: Simon Albrecht [mailto:simon.albre...@mail.de]
Sent: Tuesday, February 02, 2016 2:09 PM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; 'lilypond-user'
<lilypond-user@gnu.org>
Subject: Re: Four Part Piano Staff
On 02.02.2016 03:25, Mark Stephen Mrotek wrote:
>
> Hello,
>
> I want to make a template for a piano staff with two explicitly
> instantiated voices (not <<{ } \\{ } >>) in each staff - this for four
> part fugues.
>
> Any assistance in accomplishing this would be greatly appreciated.
>
To come back to your original question: how about the following?
\new Staff = "foo" <<
\time 7/32
\key fes \minor
\new Voice = "soprano" { \voiceOne bisis'32.. }
\new Voice = "alto" { \voiceTwo a'\breve } >>
If that's not basically what you want, please be more specific.
Yours, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
On 03.02.2016 00:09, Mark Stephen Mrotek wrote:
Thank you for your reply and the suggested code. What you provide works well
with a single staff - as presented in the documentation. When inserted into
a piano staff two additional staves are included between the two piano
staves.
You’d need to back that up with the code you used, or better, a minimal
example. I’m having no problem with
%%
\version "2.19.35"
\new PianoStaff <<
\new Staff = "foo" <<
\time 7/32
\key fes \minor
\new Voice = "soprano" { \voiceOne bisis'32.. }
\new Voice = "alto" { \voiceTwo a'\breve*49/64 }
>>
\new Staff = "bar" <<
\time 7/32
\key fes \minor
\clef bass
\new Voice = "tenor" { \voiceOne bisis32.. }
\new Voice = "bass" { \voiceTwo a\breve*49/64 }
>>
>>
%
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
Hi Mark, > Thank you for your reply and the suggested code. What you provide works > well with a single staff - as presented in the documentation. When > inserted into a piano staff two additional staves are included between > the two piano staves. you should start posting the code you use together with your questions. From your descriptions it is impossible to guess what you actually do or what you try to achieve. I strongly suggest to follow the guidelines given at http://lilypond.org/doc/v2.18/Documentation/usage/troubleshooting and http://lilypond.org/doc/v2.18/Documentation/web/tiny-examples HTH, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver signature.asc Description: This is a digitally signed message part. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
Am 03.02.2016 um 00:17 schrieb Simon Albrecht:
> On 03.02.2016 00:09, Mark Stephen Mrotek wrote:
>> Thank you for your reply and the suggested code. What you provide
>> works well
>> with a single staff - as presented in the documentation. When
>> inserted into
>> a piano staff two additional staves are included between the two piano
>> staves.
>
> You’d need to back that up with the code you used, or better, a
> minimal example. I’m having no problem with
>
> %%
> \version "2.19.35"
> \new PianoStaff <<
> \new Staff = "foo" <<
> \time 7/32
> \key fes \minor
> \new Voice = "soprano" { \voiceOne bisis'32.. }
> \new Voice = "alto" { \voiceTwo a'\breve*49/64 }
> >>
> \new Staff = "bar" <<
> \time 7/32
> \key fes \minor
> \clef bass
> \new Voice = "tenor" { \voiceOne bisis32.. }
> \new Voice = "bass" { \voiceTwo a\breve*49/64 }
> >>
> >>
> %
>
> Best, Simon
Well, this is what I wanted to post as well.
But still, you should consider taking the advice of so many from us and
get friends with music variables. They really are the killer advantage
in this context ...
Urs
>
> ___
> 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: Four Part Piano Staff
Michael, Thank you for your response and suggestion. Whenever I make an inquiry I attach a .ly file. Mark -Original Message- From: Michael Gerdau [mailto:m...@qata.de] Sent: Tuesday, February 02, 2016 3:17 PM To: lilypond-user@gnu.org Cc: Mark Stephen Mrotek <carsonm...@ca.rr.com> Subject: Re: Four Part Piano Staff Hi Mark, > Thank you for your reply and the suggested code. What you provide > works well with a single staff - as presented in the documentation. > When inserted into a piano staff two additional staves are included > between the two piano staves. you should start posting the code you use together with your questions. >From your descriptions it is impossible to guess what you actually do or what you try to achieve. I strongly suggest to follow the guidelines given at http://lilypond.org/doc/v2.18/Documentation/usage/troubleshooting and http://lilypond.org/doc/v2.18/Documentation/web/tiny-examples HTH, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Four Part Piano Staff
Simon,
Thank you for your reply and the suggested code. It is exactly what I
wanted!
Mark
-Original Message-
From: Simon Albrecht [mailto:simon.albre...@mail.de]
Sent: Tuesday, February 02, 2016 3:17 PM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; 'lilypond-user'
<lilypond-user@gnu.org>
Subject: Re: Four Part Piano Staff
On 03.02.2016 00:09, Mark Stephen Mrotek wrote:
> Thank you for your reply and the suggested code. What you provide
> works well with a single staff - as presented in the documentation.
> When inserted into a piano staff two additional staves are included
> between the two piano staves.
You'd need to back that up with the code you used, or better, a minimal
example. I'm having no problem with
%%
\version "2.19.35"
\new PianoStaff <<
\new Staff = "foo" <<
\time 7/32
\key fes \minor
\new Voice = "soprano" { \voiceOne bisis'32.. }
\new Voice = "alto" { \voiceTwo a'\breve*49/64 }
>>
\new Staff = "bar" <<
\time 7/32
\key fes \minor
\clef bass
\new Voice = "tenor" { \voiceOne bisis32.. }
\new Voice = "bass" { \voiceTwo a\breve*49/64 }
>>
>>
%
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
On Tue 02 Feb 2016 at 15:37:29 (-0800), Mark Stephen Mrotek wrote:
> Michael,
>
> Thank you for your response and suggestion. Whenever I make an inquiry I
> attach a .ly file.
Your reply, quoted below, implies a question: "Why do I get two
unwanted additional staves?".
I can only hazard a guess: that you pasted Simon's:
\new Staff = "foo" <<
\time 7/32
\key fes \minor
\new Voice = "soprano" { \voiceOne bisis'32.. }
\new Voice = "alto" { \voiceTwo a'\breve }
>>
into your code at the point where you had:
% code for explicitly instantiating two voices
but posting the code _modified by the suggestions_ is what
we need.
> > Thank you for your reply and the suggested code. What you provide
> > works well with a single staff - as presented in the documentation.
> > When inserted into a piano staff two additional staves are included
> > between the two piano staves.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
On Mon 01 Feb 2016 at 18:25:36 (-0800), Mark Stephen Mrotek wrote:
> I want to make a template for a piano staff with two explicitly instantiated
> voices (not <<{ } \\{ } >>) in each staff – this for four part fugues.
Apart from "fugues", sounds like a hymn (set in UK-style). So I
stripped the words from this one and changed the ChoirStaff to
PianoStaff. Is this the sort of thing you want?
Cheers,
David.
\version "2.18.2"
\language "english"
\header { tagline = ##f }
global = {
\key g \major
\time 4/4
s1 * 4 \break
s1 * 4 \break
s1 * 4 \break
s1 * 4
\bar "|."
}
soprano = \relative {
g'2. d4 e fs g a b c a4. g8 g1
a2. g4 fs d g fs e d e4. d8 d1
e2. e4 a gs a b c b a g a1
d2. d4 e d8( c) b4 a b c a4. g8 g1
}
alto = \relative {
b2( c4) d c c d e d d d d d1
d4( cs d) e d d e d cs d b cs d1
c2. d4 c e e e e e e e fs1
g4( d g) f e fs g g g g g fs g1
}
tenor = \relative {
d2. g4 g a g g g a fs c' b( d c b)
a4( g fs) a a a a a a8( g) fs4 g g fs( a g fs)
g2. gs4 a d c d c8( a) gs4 a8( e') d[( cs]) d4( a d c)
b2. g4 g8( c) b[( a]) g4 e' d e d4. c8 b1
}
bass = \relative {
g,2( a4) b c c b c d d d d g( b a g)
fs4( e d) cs d fs cs d a b g a d( fs e d)
c4( d c) b a b a gs a b c e d1
g2. b,4 c d e c d d d d g1
}
\score {
\transpose f f
\new PianoStaff <<
\new Staff <<
\clef treble \global
\new Voice { \voiceOne \soprano }
\new Voice { \voiceTwo \alto }
>>
\new Staff <<
\clef bass \global
\new Voice { \voiceOne \tenor }
\new Voice { \voiceTwo \bass }
>>
>>
\layout { indent = 0 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Four Part Piano Staff
Hello Mark,
What do you mean by « variable format » ?
Using variables is very handy for source code readability and if you need
separate parts and MIDI output, for example.
JM
> Le 2 févr. 2016 à 05:31, Mark Stephen Mrotek <carsonm...@ca.rr.com> a écrit :
>
> David,
>
> Thank you for your response and the code.
> In the past I have used the "variable" format. This leads to some repeated
> adjustments in the placement of the second voice.
> I prefer not to use variable, yet rather code within the Piano Staff group.
>
> Mark
>
> -Original Message-
> From: David Wright [mailto:lily...@lionunicorn.co.uk]
> Sent: Monday, February 01, 2016 7:27 PM
> To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
> Cc: 'lilypond-user' <lilypond-user@gnu.org>
> Subject: Re: Four Part Piano Staff
>
> On Mon 01 Feb 2016 at 18:25:36 (-0800), Mark Stephen Mrotek wrote:
>
>> I want to make a template for a piano staff with two explicitly
>> instantiated voices (not <<{ } \\{ } >>) in each staff – this for four part
>> fugues.
>
> Apart from "fugues", sounds like a hymn (set in UK-style). So I stripped the
> words from this one and changed the ChoirStaff to PianoStaff. Is this the
> sort of thing you want?
>
> Cheers,
> David.
>
>
> ___
> 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: Four Part Piano Staff
Jacques,
As indicated in:
http://www.lilypond.org/doc/v2.18/Documentation/learning/solo-piano
where the voices are indicated by variable, e.g, "upper" and "lower," and coded
outside of the staff context.
Mark
-Original Message-
From: Jacques Menu [mailto:imj-muz...@bluewin.ch]
Sent: Monday, February 01, 2016 9:28 PM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
Cc: Jacques Menu <imj-muz...@bluewin.ch>; lilypond-user@gnu.org
Subject: Re: Four Part Piano Staff
Hello Mark,
What do you mean by « variable format » ?
Using variables is very handy for source code readability and if you need
separate parts and MIDI output, for example.
JM
> Le 2 févr. 2016 à 05:31, Mark Stephen Mrotek <carsonm...@ca.rr.com> a écrit :
>
> David,
>
> Thank you for your response and the code.
> In the past I have used the "variable" format. This leads to some repeated
> adjustments in the placement of the second voice.
> I prefer not to use variable, yet rather code within the Piano Staff group.
>
> Mark
>
> -Original Message-
> From: David Wright [mailto:lily...@lionunicorn.co.uk]
> Sent: Monday, February 01, 2016 7:27 PM
> To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
> Cc: 'lilypond-user' <lilypond-user@gnu.org>
> Subject: Re: Four Part Piano Staff
>
> On Mon 01 Feb 2016 at 18:25:36 (-0800), Mark Stephen Mrotek wrote:
>
>> I want to make a template for a piano staff with two explicitly
>> instantiated voices (not <<{ } \\{ } >>) in each staff – this for four part
>> fugues.
>
> Apart from "fugues", sounds like a hymn (set in UK-style). So I stripped the
> words from this one and changed the ChoirStaff to PianoStaff. Is this the
> sort of thing you want?
>
> Cheers,
> David.
>
>
> ___
> 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: Four Part Piano Staff
David,
Thank you for your response and the code.
In the past I have used the "variable" format. This leads to some repeated
adjustments in the placement of the second voice.
I prefer not to use variable, yet rather code within the Piano Staff group.
Mark
-Original Message-
From: David Wright [mailto:lily...@lionunicorn.co.uk]
Sent: Monday, February 01, 2016 7:27 PM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
Cc: 'lilypond-user' <lilypond-user@gnu.org>
Subject: Re: Four Part Piano Staff
On Mon 01 Feb 2016 at 18:25:36 (-0800), Mark Stephen Mrotek wrote:
> I want to make a template for a piano staff with two explicitly
> instantiated voices (not <<{ } \\{ } >>) in each staff – this for four part
> fugues.
Apart from "fugues", sounds like a hymn (set in UK-style). So I stripped the
words from this one and changed the ChoirStaff to PianoStaff. Is this the sort
of thing you want?
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
