Le mardi 07 novembre 2023 à 16:48 -0500, David Zelinsky a écrit :
> Though I am curious whether this was just an accident of implementation
> and would be easy to change, or if there is a more structural reason.
It is purely a bug. I've just
found https://gitlab.com/lilypond/lilypond/-/issues/188
Jean Abou Samra writes:
> Le mardi 07 novembre 2023 à 00:55 -0500, David Zelinsky a écrit :
>> Is there a way to change the spacing between staves (single-staff
>> systems) in one score, in a document with multiple scores, without
>> introducing a page break?
>
> Unfortunately, the answer is curr
Assuming your sections are all (or nearly all) less than half a page, you could
halve the paper requirement by typesetting onto landscape A5 (or whatever is
half the size of your output paper) and print from Acrobat (or whatever) two-up
on each page.
Paul
From: David Zelinsky
To:
S
Le mardi 07 novembre 2023 à 00:55 -0500, David Zelinsky a écrit :
> Is there a way to change the spacing between staves (single-staff
> systems) in one score, in a document with multiple scores, without
> introducing a page break?
Unfortunately, the answer is currently no.
Best,
Jean
signature
Ming,
Bar 4 in both are identical. What is “wrong” in the second score?
What is wrong with bar 6? There is only one example.
What adjustment do you want to the beam in bar 5?
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of ming tsa
Yes, that does it. Thanks!
--
Knute Snortum
On Sat, Nov 7, 2020 at 2:38 PM damianlegassick wrote:
>
> urgh
>
> and you'll have to add
>
> \once \override Dots.stencil = ##f
>
> just before the gis8.
>
> Damian
>
> On 7 November 2020 at 22:33, damianlegassick wrote:
>
> fiddly one this
>
> \ve
Hi Knute,
Am 07.11.20 um 20:02 schrieb Knute Snortum:
Here's a better MWE with my try using voices in the left hand:
%%% Start
\version "2.20.0"
\language "english"
staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"
rh = \relative c' {
s8. \crossStaff e16
}
lh = \rela
urgh
and you'll have to add
\once \override Dots.stencil = ##f
just before the gis8.
Damian
On 7 November 2020 at 22:33, damianlegassick wrote:
fiddly one this
\version "2.21.7"
\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}
rhmusic = {
\time 3/4
\key e \major
\
fiddly one this
\version "2.21.7"
\layout {
\context {
\PianoStaff
\consists #Span_stem_engraver
}
}
rhmusic = {
\time 3/4
\key e \major
\change Staff = "lower"
\stemUp
8[ r16
\change Staff = "upper"
e'16]
}
lhmusic = {
\key e \major
\clef "bass"
<<
{
\once \omit Stem
\once \omit Beam
\slurD
Oh, this is so close! The snippet provided doesn't have the slur from
the lower g sharp to the b in it, so I tried adding it. The b is in
the lower hand so I tried slurring to the e and then use \shape to fix
it, but it produces a programming error. Here's the modified
snippet...
%%% Start
\ver
That looks good! Thanks!
--
Knute Snortum
On Sat, Nov 7, 2020 at 11:09 AM damianlegassick wrote:
>
> Try this for starters
>
> \version "2.21.7"
>
> \layout { \context { \PianoStaff \consists #Span_stem_engraver } }
>
> rhmusic = {
> time 3/4 \key e \major
> \change Staff = "lower"
> \stemUp 8
Try this for starters
\version "2.21.7"
\layout { \context { \PianoStaff \consists #Span_stem_engraver } }
rhmusic = {
time 3/4 \key e \major
\change Staff = "lower"
\stemUp 8[ r16
\change Staff = "upper" e'16]
}
lhmusic = {
\key e \major
\clef "bass"
<< { s8. \crossStaff {b16} } \\ { e,4 } >
Here's a better MWE with my try using voices in the left hand:
%%% Start
\version "2.20.0"
\language "english"
staffUp = \change Staff = "upper"
staffDown = \change Staff = "lower"
rh = \relative c' {
s8. \crossStaff e16
}
lh = \relative c' {
\clef bass
<< { 8[ r16 b] } \\ { e,,4 } >>
}
On 2020-09-30 1:09 pm, Philippe Auclair wrote:
Oups... Sorry, here are the pdf files.
In the following example, in the piano left staff music, \clef "bass"
is BEFORE \dynamicUp : the score goes completely wild ! (1st attached
pdf).
If \clef "bass" is AFTER \dynamicUp, the score is correct (2nd p
Oups... Sorry, here are the pdf files.
In the following example, in the piano left staff music, \clef "bass" is
BEFORE \dynamicUp : the score goes completely wild ! (1st attached pdf).
If \clef "bass" is AFTER \dynamicUp, the score is correct (2nd pdf).
Is there an explanation?
Philippe Auclai
On 2/4/19 10:18 AM, Aaron Hill wrote:
I overlooked \cueClefUnset so that's the better option.
For the grob, the Internals reference is your friend: CueEndClef
Thanks! I really need to get more familiar with the internals
reference. One of these days in my copious free time.
David, thanks
On 2019-02-04 6:47 am, Christopher R. Maden wrote:
On 2/4/19 6:03 AM, Aaron Hill wrote:
Note in this case I changed the CueClef font-size to match the reduced
size of a non-cue clef when it appears within a line.
That looks great, thanks! The \cueClefUnset bass clef still looks
tiny, and if I
On 2/4/19 6:03 AM, Aaron Hill wrote:
Note in this case I changed the CueClef font-size to match the reduced
size of a non-cue clef when it appears within a line.
That looks great, thanks! The \cueClefUnset bass clef still looks tiny,
and if I use \cueClef to switch back to bass, it shows up i
"Christopher R. Maden" writes:
> This is probably a FAQ, but I can’t find the right combination of
> search terms to tease it from the ether...
>
> I want a piano staff, with the left hand to start with bass clef, but
> then immediately switch to treble clef after the time signature.
>
> Mnon-WE
On 2019-02-03 8:44 pm, Christopher R. Maden wrote:
On 2/3/19 9:43 PM, Aaron Hill wrote:
Does \cueClef help?
It does... though then when I \clef bass back again it’s ignored. I
can use \cueClefUnset...
Thanks, this is a great workaround. I suspect there is a better (more
properly LilyPondish
HI Chris,
That makes sense. I also like to preserve the composer's own notation where
possible. And as said, it's not actually wrong! Good old Sousa!
Andrew
On Mon, 4 Feb 2019 at 16:43, Christopher R. Maden wrote:
>
> I’m transcribing Sousa’s “A Typical Tune of Zanzibar,”[*] and I’m trying
>
On 2/4/19 12:36 AM, Andrew Bernard wrote:
This comes up reasonably often. May I ask why you don't simply start
the piece with the treble clef? If you immediately change to treble,
what is the point of having the bass clef at this point? It's a
musical decision up to you, but it always strikes me
Hi Christopher,
This comes up reasonably often. May I ask why you don't simply start the
piece with the treble clef? If you immediately change to treble, what is
the point of having the bass clef at this point? It's a musical decision up
to you, but it always strikes me as a bit unnecessary. Any p
On 2/3/19 9:43 PM, Aaron Hill wrote:
Does \cueClef help?
It does... though then when I \clef bass back again it’s ignored. I can
use \cueClefUnset...
Thanks, this is a great workaround. I suspect there is a better (more
properly LilyPondish) answer, but this is more than adequate for now.
On 2019-02-03 6:43 pm, Aaron Hill wrote:
On 2019-02-03 6:33 pm, Christopher R. Maden wrote:
This is probably a FAQ, but I can’t find the right combination of
search terms to tease it from the ether...
I want a piano staff, with the left hand to start with bass clef, but
then immediately switch
On 2019-02-03 6:33 pm, Christopher R. Maden wrote:
This is probably a FAQ, but I can’t find the right combination of
search terms to tease it from the ether...
I want a piano staff, with the left hand to start with bass clef, but
then immediately switch to treble clef after the time signature.
Absolutely agree :) Consider my last code a scheme exercise...
On 28 January 2017 at 09:33, Helge Kruse wrote:
> Am 26.01.2017 um 10:51 schrieb Gianmaria Lari:
> > ... and this is one more way to do the change staff using a scheme
> function
> > that toggle between the two staff.
> >
> ...
> > N
Am 26.01.2017 um 10:51 schrieb Gianmaria Lari:
> ... and this is one more way to do the change staff using a scheme function
> that toggle between the two staff.
>
...
> Not sure it can be more useful than the other ones. Also have no idea if
> this logic should be written differently. But it has
... and this is one more way to do the change staff using a scheme function
that toggle between the two staff.
\version "2.19.54"
#(define staffToggle #f)
cs= #(define-music-function (parser location) ;cs = Change Staff
()
(begin
(set! staffToggle (not staffToggl
Thank you, Malte and Noeck, it works perfectly.
I post here another solution, that is interesting because it doesn't use
scheme and more easy to understand.
\version "2.19.54"
csl = { \change Staff = "left" }
csr = { \change Staff = "right" }
right = \fixed c' {
\clef treble
\time 2/4
g8-4
Am 25.01.2017 um 14:38 schrieb SoundsFromSound:
> Do you know how to fix them?
Hi,
you need staves named "right" and "left" for this to work:
\version "2.19.50"
l =
#(define-music-function (music) (ly:music?)
#{
\change Staff = "left"
#music
\change Staff = "right"
#})
ri
Malte Meyn-3 wrote
> Am 25.01.2017 um 11:55 schrieb Gianmaria Lari:
>> - Is there a simpler way to write this source code avoiding all these
>> change staff?
>
> You could use a simple music function:
>
> l =
> #(define-music-function (music) (ly:music?)
>#{
> \change Staff = "left"
>
Am 25.01.2017 um 11:55 schrieb Gianmaria Lari:
> - Is there a simpler way to write this source code avoiding all these
> change staff?
You could use a simple music function:
l =
#(define-music-function (music) (ly:music?)
#{
\change Staff = "left"
#music
\change Staff = "right
AbrahamThank you. It works on v2.19.15 as well.Immanuel,Ming
On Friday, December 19, 2014 11:01 AM, "lilypond-user-requ...@gnu.org"
wrote:
1. Re:\change staff (tisimst)
Message: 1
Date: Fri, 19 Dec 2014 07:33:36 -0700 (MST)
From: tisimst
To: lilypond-user@gnu.org
S
Try this. I know there are multiple ways for doing this (like changing
beam-knee-length, or whatever), but it's a quick hack that works (sorry
it's for 2.18.2, but I think you can convert it back):
%<-- SNIP -
\version "2.18.2"
\language "english"
right = {
\time
Hi,
Since you are naming your staves as "right" and "left" in the \score block,
then you must use \change Staff = "right" or \change Staff = "left" when
changing staves, instead of \change Staff = up. So on line 23 simply
exchange the word up for "right" (with the commas).
Best,
Gilberto
--
Vi
Ming,
In m66, and m67 you have an unassigned number, i.e. a 4.
Your time signature is ¾, yet there are 4 beats written in the first measure
of the upper voice of the screen shot.
Mark
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=
Hello Ming,
if you have a look into the documentation for \change (when in doubt,
look it up in the command index), you’ll find that it does not require
any braces following or indeed any argument. It looks like you try to
enter the notes in parallel, which is illogical, since they are
sequen
t 3:26 AM, Phil Holmes wrote:
> - Original Message - From: "Xavier Scheuer"
> To: "Jeffrey Trevino"
> Cc: "lilypond-user"
> Sent: Friday, January 25, 2013 10:50 AM
> Subject: Re: change staff for component notes of chord
>
>
>
&g
- Original Message -
From: "Xavier Scheuer"
To: "Jeffrey Trevino"
Cc: "lilypond-user"
Sent: Friday, January 25, 2013 10:50 AM
Subject: Re: change staff for component notes of chord
On 25 January 2013 08:17, Jeffrey Trevino
wrote:
hi there,
I like th
On 25 January 2013 08:17, Jeffrey Trevino wrote:
> hi there,
>
> I like the "change staff" interface for switching staffs and beaming across
> them. Is there a similar interface available for chords, which allows the
> user to specify that certain higher or lower notes should be drawn on a
> diffe
In data martedì 13 settembre 2011 17:24:49, hai scritto:
> On 13 September 2011 17:07, Mario Moles wrote:
> > Any idea? Thank's!
> >
> > [code]
Ok! Great! Thank you!
>
> That's because you use the << \\ >> construct, which implicitly
> creates voices "1" and "2" in *both* staves.
>
> Please u
In data martedì 13 settembre 2011 17:14:37, hai scritto:
> There's too much music here to work out your problem. Could you a) say
> what you believe is wrong, and b) cut the music down to a tiny example
> showing your problem.
>
> --
> Phil Holmes
>
Right! I'm sorry!
In the bar 2, leftOne: 2° g
On 13 September 2011 17:07, Mario Moles wrote:
>
> Any idea? Thank's!
>
> [code]
>
That's because you use the << \\ >> construct, which implicitly
creates voices "1" and "2" in *both* staves.
Please use explicitly instantiated voices instead and it should work
fine. See the modified \score
There's too much music here to work out your problem. Could you a) say what
you believe is wrong, and b) cut the music down to a tiny example showing your
problem.
--
Phil Holmes
- Original Message -
From: Mario Moles
To: lilypond-user@gnu.org
Sent: Tuesday, September 13, 2
Cheers. I didn't know where to put this, but I thought here was best, seeing
as I seem to see many people here seem to work on LilypondTool as well.
Thanks
George
Valentin Villenave wrote:
>
> On Mon, Dec 13, 2010 at 11:26 PM, George_ wrote:
>> I seem to be having a problem with \change Staf
On Mon, Dec 13, 2010 at 11:26 PM, George_ wrote:
> I seem to be having a problem with \change Staff screwing up my barchecks.
Thanks, I've added it to the LilyPondTool bug tracker:
https://sourceforge.net/tracker/?func=detail&aid=3138066&group_id=91119&atid=596024
Cheers,
Valentin.
(P.S. -- Hi
On 12/14/10 10:38 AM, "George_" wrote:
>
>
>
> Phil Holmes-2 wrote:
>>
>> - Original Message -
>> From: "George_"
>> To:
>> Sent: Monday, December 13, 2010 10:26 PM
>> Subject: \change Staff and barchecks in LilyPondTool
>>
>> Could you post a tiny, complete example that shows t
Phil Holmes-2 wrote:
>
> - Original Message -
> From: "George_"
> To:
> Sent: Monday, December 13, 2010 10:26 PM
> Subject: \change Staff and barchecks in LilyPondTool
>
> Could you post a tiny, complete example that shows this, please?
>
> --
> Phil Holmes
>
>
>
> __
- Original Message -
From: "George_"
To:
Sent: Monday, December 13, 2010 10:26 PM
Subject: \change Staff and barchecks in LilyPondTool
I seem to be having a problem with \change Staff screwing up my barchecks.
For example:
e16 d c d e8 f
\change Staff = "LH"
gis, e r a |
for me pr
The name of the Staff you want to change to is either "rh"
or "lh", since that's the names you have specified for the
staves. It seems that you have confused these with the
names of the variables/macros/identifiers that contain the
actual music.
/Mats
David Fedoruk wrote:
Hello:
I've used t
2007/8/26, Neil Puttock <[EMAIL PROTECTED]>:
> I've just added it as "Forcing visibility of systems with multi-bar rests
> when using \RemoveEmptyStaffContext"; I hope it's OK.
http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312
A bit long, but I couldn't find any shorter title. It's approved now;
howeve
Hi Valentin,
On 8/26/07, Valentin Villenave <[EMAIL PROTECTED]> wrote:
>
> 2007/8/25, Kieren MacMillan <[EMAIL PROTECTED]>:
>
> > p.s. This is *definitely* an LSR-worthy tip/trick!
>
> It is indeed; feel free to add it and I'll mark it as approved ASAP :)
>
I've just added it as "Forcing visibili
2007/8/25, Kieren MacMillan <[EMAIL PROTECTED]>:
> p.s. This is *definitely* an LSR-worthy tip/trick!
It is indeed; feel free to add it and I'll mark it as approved ASAP :)
Regards,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http:/
Hi Kieren,
On 8/25/07, Kieren MacMillan <[EMAIL PROTECTED]> wrote:
>
>
> If you read the Hara_kiri_engraver docs, it says
> __
>
> Like Axis_group_engraver, but make a hara-kiri spanner, and add
> interesting items (ie. note heads, lyric syllables and normal rests)
>
> Properti
Hi Neil,
I've tried messing around with keepAliveInterfaces, and this is
quite pleasing:
Nicely done -- I hereby retract my offer of sponsorship... =)
Best regards,
Kieren.
p.s. This is *definitely* an LSR-worthy tip/trick!
___
lilypond-user ma
Hi Neil:
The closest I've got is in creating a new staff context with the
properties of \RemoveEmptyStaffContext,
but it only allows you to choose whether a particular stave can be
hidden or not.
If you read the Hara_kiri_engraver docs, it says
__
Like Axis_group_engrav
Hi Kieren,
On 8/24/07, Kieren MacMillan <[EMAIL PROTECTED]> wrote:
>
>
> Just wondering if anyone has solved the problem of turning the hara-
> kiri-ability of a Staff on the fly?
I haven't had much success, unfortunately.
The closest I've got is in creating a new staff context with the propert
Did I missed the solution? How can one change staff within a chord?
Best Regards,
Mehmet Okonsar, pianist-composer
www.okonsar.com
hi mehmet, and everybody who helped me,
this is something i came up with for changing staffs within a chord:
would be still great to have a more explicit way
[EMAIL PROTECTED] wrote:
> hello list,
> how would i change the staff within a chord (it is important that the
> necks keep connected across the staves? the \change Staff command
> doesn't work within the chord < ... >.
You can remove the stem from the upper staff notes, and extend the stem
from
On Thursday 15 September 2005 06.47, Mehmet Okonsar wrote:
> Did I missed the solution? How can one change staff within a chord?
It's not currently possible. You can fake it by manually creating very long
stems, or you can pay Han-Wen to implement a good way to do it.
--
Erik
See http://lists.gnu.org/archive/html/lilypond-devel/2005-08/msg00318.html
with followups (if I understand your questions correctly).
/Mats
[EMAIL PROTECTED] wrote:
hello list,
how would i change the staff within a chord (it is important that the
necks keep connected across the staves? the
62 matches
Mail list logo