>> Under 2.22 I do not get extra space.
>
> That’s still more curious. On 2.22.2 I get a warning
> that the break is overwritten by another event, so we
> don’t get the line break that I had specified and wanted.
It's expected. 2.22 doesn't accept mid-measure breaks without
a bar line. You need
On 28/01/2023 06:52, Ole V. Villumsen wrote:
> Thanks, everyone, for your contributions.
>
> First of all Jean. Your code gives me exactly what I wanted. I haven’t
> learned to use the internals, but see here that it’s useful.
>
>> Not sure, but my guess is that LilyPond might be trying to make
On 28/01/2023 16:51, David Kastrup wrote:
> Jean Abou Samra writes:
>
>>> Le 28 janv. 2023 à 08:01, Darren Ng a écrit :
>>>
>>> [subject] How to define a macro that expands to a percussion "pitch"?
>>
>>
>> It may be worth noting that LilyPond does not have macros, only
>> variables and regular
email.
>
> --- Original Message ---
> On Saturday, January 28th, 2023 at 00:09, Jean Abou Samra j...@abou-samra.fr
> wrote:
>
>
>
> > On 27/01/2023 22:35, Ole V. Villumsen wrote:
> >
> > > Hi, I am typesetting a movement with a repeat an
Sent with Proton Mail secure email.
--- Original Message ---
On Saturday, January 28th, 2023 at 00:09, Jean Abou Samra
wrote:
> On 27/01/2023 22:35, Ole V. Villumsen wrote:
>
> > Hi, I am typesetting a movement with a repeat and a clef change right after
> > the repeat. I
: Clef change after end-repeat before break -- how?
Hi, I am typesetting a movement with a repeat and a clef change right after the
repeat. I have a suitable line break where the repeat ends and the clef change
happens. Default Lilypond sets the new clef within the repeat, before the
end-repeat
Subject: Clef change after end-repeat before break -- how?
Hi, I am typesetting a movement with a repeat and a clef change right after the
repeat. I have a suitable line break where the repeat ends and the clef change
happens. Default Lilypond sets the new clef within the repeat, before the
end-repeat
On 27/01/2023 22:35, Ole V. Villumsen wrote:
> Hi, I am typesetting a movement with a repeat and a clef change right after
> the repeat. I have a suitable line break where the repeat ends and the clef
> change happens. Default Lilypond sets the new clef within the repeat, before
On Fri, Jan 27, 2023 at 1:36 PM Ole V. Villumsen <
ole.villum...@protonmail.ch> wrote:
> Hi, I am typesetting a movement with a repeat and a clef change right
> after the repeat. I have a suitable line break where the repeat ends and
> the clef change happens. Default Lilypond se
Hi, I am typesetting a movement with a repeat and a clef change right after the
repeat. I have a suitable line break where the repeat ends and the clef change
happens. Default Lilypond sets the new clef within the repeat, before the
end-repeat sign, which I don’t want and find meaningless in my
Kieren MacMillan writes:
> Hi David,
>
>> Try
>>
>> \new Lyrics \lyricmode {
>> \tweak color #red love
>> \propertyTweak color #blue wonderful
>> }
>>
>> And you'll get the error message
>> /tmp/ba.ly:4:1: error: bad grob property path (wonderful color)
>>
>> In general, tweaks that have som
Hi David,
> Try
>
> \new Lyrics \lyricmode {
> \tweak color #red love
> \propertyTweak color #blue wonderful
> }
>
> And you'll get the error message
> /tmp/ba.ly:4:1: error: bad grob property path (wonderful color)
>
> In general, tweaks that have some chance to be applied to lyrics may
> be
Kieren MacMillan writes:
> Hi Jean,
>
>> I'm not sure if the NR is the best place for explaining
>> \propertyTweak.
>
> I didn’t know of this until David K helped me build my \ignore functions, e.g.
>
> ignoreH =
>\propertyTweak horizontal-skylines ##f
>\propertyTweak extra-spacing-width
Hi Jean,
> I'm not sure if the NR is the best place for explaining
> \propertyTweak.
I didn’t know of this until David K helped me build my \ignore functions, e.g.
ignoreH =
\propertyTweak horizontal-skylines ##f
\propertyTweak extra-spacing-width #empty-interval
\etc
> Its usefulness
>> This code might serve as an example for `\propertyTweak`, which the
>> NR is currently missing.
>>
>> Would you care to submit an MR, expanding the documentation
>> accordingly?
>
> I'm not sure if the NR is the best place for explaining
> \propertyTweak. Its usefulness is basically to be a h
> I'm not sure why this takes into account the right endpoint of the
> extent on the left but not the left endpoint of the extent on the
> right. I think it might just be assuming that all break-aligned
> grobs have an extent starting at 0.
Or maybe it's simply a thinko...
Werner
Le 01/06/2022 à 20:07, Werner LEMBERG a écrit :
This code might serve as an example for `\propertyTweak`, which the NR
is currently missing.
Would you care to submit an MR, expanding the documentation
accordingly?
I'm not sure if the NR is the best place for explaining
\propertyTweak. Its us
Le 01/06/2022 à 21:50, David Kastrup a écrit :
Frankly, I have no idea what I am actually doing there with the
ly:stencil-aligned-to . I was just fudging around until something fell
out that looked like what you wanted to be doing. So "\squashed" is
actually a misnomer from the first attempt wher
Werner LEMBERG writes:
> David,
>
>
> thanks for your code – I consider it quite an elegant solution.
>
>> squashed =
>> \once \propertyTweak stencil
>> #(grob-transformer 'stencil
>> (lambda (grob old)
>> (ly:stencil-aligned-to old X RIGHT)))
>> \etc
>>
>> { 1 \breat
David,
thanks for your code – I consider it quite an elegant solution.
> squashed =
> \once \propertyTweak stencil
> #(grob-transformer 'stencil
> (lambda (grob old)
> (ly:stencil-aligned-to old X RIGHT)))
> \etc
>
> { 1 \breathe | }
>
> { 1 \breathe \squashed Sta
Werner LEMBERG writes:
>> [git f326290b65351]
>>
>> Please have a look at the attached image. What must I do to make
>> the breathe sign 'ignore' the change clef so that the breathe sign
>> is positioned as if the change clef wasn't there?
>
> Well, having some code certainly helps :-)
>
> ```
>>> Please have a look at the attached image. What must I do to make
>>> the breathe sign 'ignore' the change clef so that the breathe sign
>>> is positioned as if the change clef wasn't there? [...]
>
> There's always this sort of trick: [...]
Excellent, thank you!
> Is this canonical present
Le 26/05/2022 à 17:05, Werner LEMBERG a écrit :
[git f326290b65351]
Please have a look at the attached image. What must I do to make
the breathe sign 'ignore' the change clef so that the breathe sign
is positioned as if the change clef wasn't there?
Well, having some code certainly helps :-
> [git f326290b65351]
>
> Please have a look at the attached image. What must I do to make
> the breathe sign 'ignore' the change clef so that the breathe sign
> is positioned as if the change clef wasn't there?
Well, having some code certainly helps :-)
```
{ 1 \breathe | }
{ 1 \breathe \cl
[git f326290b65351]
Please have a look at the attached image. What must I do to make the
breathe sign 'ignore' the change clef so that the breathe sign is
positioned as if the change clef wasn't there?
Werner
Le 05/01/2022 à 07:51, Calvin Ransom a écrit :
Hi everyone,
I want to avoid excessive ledger lines in my score and have LilyPond
change the clef automatically.
I am creating a computer generated piece with LilyPond that covers the
entire pitch gamut.
\autochange does not work for this applicati
Hi everyone,
I want to avoid excessive ledger lines in my score and have LilyPond change the
clef automatically.
I am creating a computer generated piece with LilyPond that covers the entire
pitch gamut.
\autochange does not work for this application because it can only use two
clefs and it uses
schrieb Stefan Thomas:
> Dear David,
> thanks for Your reply.
> Can it also be done with \once \override?
>
> Am Do., 2. Dez. 2021 um 17:07 Uhr schrieb David Kastrup :
> > Stefan Thomas writes:
> > > Dear community,
> > > is it possible to make a clef c
Stefan Thomas writes:
>> Am Do., 2. Dez. 2021 um 17:07 Uhr schrieb:
>>
>>> Stefan Thomas writes:
>>>
>>> > Dear community,
>>> > is it possible to make a clef change invisible, at the end of the line?
>>> > I don't want to
Dear David,
thanks for Your reply.
Can it also be done with \once \override?
Am Do., 2. Dez. 2021 um 17:07 Uhr schrieb David Kastrup :
> Stefan Thomas writes:
>
> > Dear community,
> > is it possible to make a clef change invisible, at the end of the line?
> > I don
Stefan Thomas writes:
> Dear community,
> is it possible to make a clef change invisible, at the end of the line?
> I don't want to see the bass clef at the end of the first line here:
> \version "2.22.1"
> Musik = \relative c'' {
> \clef "tre
Dear community,
is it possible to make a clef change invisible, at the end of the line?
I don't want to see the bass clef at the end of the first line here:
\version "2.22.1"
Musik = \relative c'' {
\clef "treble" g f e d
\break
\clef "bass" c4 b a2 }
\new Staff \Musik
Thanks,
Stefan
I thought so. I had tried that before but i think i tried /grace s8 s and
now i see i didn't use curly brackets which is why it didn't work...doh!
So that was an unnecessary email!
Thank you for your help!
-Molly
On Sat, Oct 30, 2021, 09:49 Lukas-Fabian Moser wrote:
>
> Am 30.10.21 um 15:44 s
Am 30.10.21 um 15:44 schrieb Molly Preston:
When changing clefs in the left hand the treble clef is placed on the
right side of the bar line. It seems to be related to the grace notes
happening in the right hand. Does anyone have a fix for this?
That's LilyPond's most famous bug, a bit annoy
When changing clefs in the left hand the treble clef is placed on the right
side of the bar line. It seems to be related to the grace notes happening
in the right hand. Does anyone have a fix for this?
<<
\new Staff {
\time 7/8
\clef bass
ees8 ( d des d fis)-. d ( fis -. ) |
\t
Ooops! Wrong thread. Sorry.
On Wed, 2021-10-27 at 22:28 +0100, J Martin Rushton wrote:
> Kevin,
> Just a tiny typo: in the last verse of "Go where the glory waits
> thee"
> you have "Draw_w_ one tear from thee;"
>
> Regards,
> Martin
>
>
Kevin,
Just a tiny typo: in the last verse of "Go where the glory waits thee"
you have "Draw_w_ one tear from thee;"
Regards,
Martin
ng to play a g' here, because there's this
tenor clef directly in front of the the note, separated only by the bar
line (which is what you're used to in any clef change).
Unfortunately, as a trombone player (for whom orchestral parts sometimes
mix tenor and bass clef), parts
Le 27/10/2021 à 09:23, Lukas-Fabian Moser a écrit :
but I admit that your solution gives better spacing. (The
extra-spacing-width of both Staff.Clef and Staff.BarLine doesn't seem
to be able to increase the space between clef and barline.)
Even though this behavior may not be clearly
document
alternative. Half of your cellists (or whatever instrument uses tenor
> and bass clef here) is going to play a g' here, because there's this
> tenor clef directly in front of the the note, separated only by the
> bar line (which is what you're used to in any clef ch
Hi Valentin,
Am 27.10.21 um 09:09 schrieb Valentin Petzel:
Hello Lukas, hello Jean, hello David,
Maybe something like this could do the trick.
Yes, maybe (even though I still read f' after the bar line for a second
and had to look in the source to find out what the intended pitch was). :-)
> }
>
> While this is technically perfect, I'd strongly advise against doing it
> this way: It's a recipe for disaster regarding the start of the 2nd
> alternative. Half of your cellists (or whatever instrument uses tenor
> and bass clef here) is going to play a g' here, be
oing to play a g' here, because there's this
> tenor clef directly in front of the the note, separated only by the
> bar line (which is what you're used to in any clef change).
>
> ... usually it's much better to just change notation such that there
> is no clef chang
arated only by the bar
line (which is what you're used to in any clef change).
One could do something like
\version "2.22.1"
{
\clef tenor
\repeat volta 2 {
c'1
\clef bass
c'1
}
\alternative {
{
c'1
\set Staff.clefGlyph = &
Le 26/10/2021 à 01:21, David Zelinsky a écrit :
I have a repeated section that starts in tenor clef, then changes to
bass clef (before the repeat). I want to show a tenor clef at the end
of the 1st ending, just before the repeat sign, as a reminder that the
repeat starts in that clef. But when
I have a repeated section that starts in tenor clef, then changes to
bass clef (before the repeat). I want to show a tenor clef at the end
of the 1st ending, just before the repeat sign, as a reminder that the
repeat starts in that clef. But when I put '\clef "tenor"' in the first
\alternative, t
Am Mo., 2. Nov. 2020 um 11:32 Uhr schrieb Pierre Perol-Schneider
:
>
> Done! Thanks for the reminder Harm.
> Cheers
> Pierre
>
> Le ven. 30 oct. 2020 à 22:19, Thomas Morley a
> écrit :
>>
>> To the author (Pierre?) of
>> lsr.di.unimi.it/LSR/Item?u=1&id=1119
>>
>> Many thanks for your snippet, tho
Ok Aaron.
Cheers,
Pierre
Le ven. 30 oct. 2020 à 23:45, Aaron Hill a
écrit :
> On 2020-10-30 2:19 pm, Thomas Morley wrote:
> > To the author (Pierre?) of
> > lsr.di.unimi.it/LSR/Item?u=1&id=1119
> >
> > Many thanks for your snippet, though, please add a description to it.
> > ;)
>
> Would this w
Done! Thanks for the reminder Harm.
Cheers
Pierre
Le ven. 30 oct. 2020 à 22:19, Thomas Morley a
écrit :
> To the author (Pierre?) of
> lsr.di.unimi.it/LSR/Item?u=1&id=1119
>
> Many thanks for your snippet, though, please add a description to it. ;)
>
> Thanks,
> Harm
>
>
Am Fr., 30. Okt. 2020 um 23:45 Uhr schrieb Aaron Hill
:
>
> On 2020-10-30 2:19 pm, Thomas Morley wrote:
> > To the author (Pierre?) of
> > lsr.di.unimi.it/LSR/Item?u=1&id=1119
> >
> > Many thanks for your snippet, though, please add a description to it.
> > ;)
>
> Would this work better to avoid th
On 2020-10-30 2:19 pm, Thomas Morley wrote:
To the author (Pierre?) of
lsr.di.unimi.it/LSR/Item?u=1&id=1119
Many thanks for your snippet, though, please add a description to it.
;)
Would this work better to avoid the hidden note showing up in MIDI?
\grace s4
\once \override Staff.Cl
To the author (Pierre?) of
lsr.di.unimi.it/LSR/Item?u=1&id=1119
Many thanks for your snippet, though, please add a description to it. ;)
Thanks,
Harm
Hi Harm,
Le lun. 29 juin 2020 à 09:59, Thomas Morley a
écrit :
> Hi Pierre,
>
> I've now approved it as
> lsr.di.unimi.it/LSR/Item?u=1&id=1116
> with some slight changes.
>
> I deleted another instance of \hideNotes and changed
> \once\override Staff.Clef.space-alist =
> #'((key-canc
Am So., 28. Juni 2020 um 09:37 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi Harm,
>
> Le sam. 27 juin 2020 à 10:39, Thomas Morley a
> écrit :
> ...
>>
>> Some Remarks:
>> (a) Your override
>> \once\override Staff.TimeSignature.space-alist =
>> #'((first-note . (fixed-space . 0)))
>> will
Hi Harm,
Le sam. 27 juin 2020 à 10:39, Thomas Morley a
écrit :
...
> Some Remarks:
> (a) Your override
> \once\override Staff.TimeSignature.space-alist =
> #'((first-note . (fixed-space . 0)))
> will replace the default space-alist with your setting, i.e. the other
> default settings (s
Am Fr., 26. Juni 2020 um 12:06 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi Harm,
> Thank you for your suggestion. Definitly better.
> Ultimately, I've created a new snippet:
> http://lsr.di.unimi.it/LSR/Item?u=1&id=1116
> If you're ok with it, I'll delete snippet #1110
> Cheers,
> Pierre
Hi Pierr
Hi Harm,
Thank you for your suggestion. Definitly better.
Ultimately, I've created a new snippet:
http://lsr.di.unimi.it/LSR/Item?u=1&id=1116
If you're ok with it, I'll delete snippet #1110
Cheers,
Pierre
Le jeu. 25 juin 2020 à 22:21, Thomas Morley a
écrit :
> Am Do., 25. Juni 2020 um 10:55 Uhr
Am Do., 25. Juni 2020 um 10:55 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi Harm,
>
> Le mer. 24 juin 2020 à 23:26, Thomas Morley a
> écrit :
>>
>> To the author of said snippet.
>> lsr.di.unimi.it/LSR/Item?u=1&id=1110
>>
>> I will not approve it in it's current state.
>
>
> Ok.
>
>> This sounds l
Le mer. 24 juin 2020 à 23:26, Thomas Morley a
écrit :
...
> Please check whether there's an issue about it already, if not report
> it on the bug-list.
>
Done:
http://lilypond.1069038.n5.nabble.com/Clef-change-and-repeat-sign-td234226.html
Cheers,
Pierre
Hi Harm,
Le mer. 24 juin 2020 à 23:26, Thomas Morley a
écrit :
> To the author of said snippet.
> lsr.di.unimi.it/LSR/Item?u=1&id=1110
>
> I will not approve it in it's current state.
>
Ok.
This sounds like default LilyPond being wrong in this regard. If so,
> it's a bug, needed to be reported
To the author of said snippet.
lsr.di.unimi.it/LSR/Item?u=1&id=1110
I will not approve it in it's current state.
It shows how to change BreakAlignment.break-align-orders, ok, though
this is covered in the docs already.
It's description says "Here's a workaround to get a traditional output
when cl
Thanks Aaron, great example!
JM
> Le 4 févr. 2020 à 06:05, Aaron Hill a écrit :
>
> On 2020-02-03 1:54 pm, Rutger Hofman wrote:
>> I would also welcome this feature. How difficult is it to write a
>> [Scheme] engraver?
>
> The mechanics of defining and using a Scheme engraver are relatively si
On 2020-02-03 1:54 pm, Rutger Hofman wrote:
I would also welcome this feature. How difficult is it to write a
[Scheme] engraver?
The mechanics of defining and using a Scheme engraver are relatively
simple:
\version "2.19.83"
Custom_engraver = #(lambda (context)
;; The let block can d
-User Mailing List
Subject: Re: Clef change placement
Is there a way to achieve this placement automatically, other than by
specifying explicit system breaks?
Did you ever get an answer to this?
Seems like a perfect job for a [Scheme] engraver…
Nope. Yours is the first response I've g
> -Original Message-
> From: Kieren MacMillan [mailto:kieren_macmil...@sympatico.ca]
> Sent: Saturday, February 01, 2020 11:15 AM
> To: Daniel Rosen
> Cc: Lilypond-User Mailing List
> Subject: Re: Clef change placement
>
> > Is there a way to achieve this pla
Hi Daniel,
> From Elaine Gould's "Behind Bars" (p. 9):
>
>> Where an instrument rests for more than a system, it is usual to return it
>> to its commonest clef... Place
>> the clef change at the end of the system after the player has finished: this
&g
>From Elaine Gould's "Behind Bars" (p. 9):
> Where an instrument rests for more than a system, it is usual to return it to
> its commonest clef... Place
> the clef change at the end of the system after the player has finished: this
> is the least disruptive positi
Hi Aaron,
Wow, that technique for overriding end-of-system / begin-of-system grobs
*independently of one another* fills in an extremely important LilyPond gap
for me.
I've modified your example for the archives; everyone should know this
technique.
%%% INDEPENDENT LINE-BREAK OVERRIDES %%%
\vers
On 07/31, Pierre Perol-Schneider wrote:
> \version "2.21.0"
> % Option 1:
> \score {
> <<
> \new Staff \relative c' {
> c4 c c c |
> \stopStaff
> s1 |
> \startStaff
> c4 c c c |
> }
> \new Staff \relative c' {
> c4 c c c |
> c4 c c c |
>
Yep thank you Simon.
This morning I came up to those 2 options, but couldn't go further:
\version "2.21.0"
% Option 1:
\score {
<<
\new Staff \relative c' {
c4 c c c |
\stopStaff
s1 |
\startStaff
c4 c c c |
}
\new Staff \relative c' {
c4 c c c |
On 31.07.19 08:42, Pierre Perol-Schneider wrote:
\once\override Staff.Clef.stencil = ##f
AKA \once\omit Staff.Clef ;-)
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
fs.F_change" |
> \once\override Staff.Clef.stencil = ##f
> \clef "bass" c4 c c c |
> }
> >>
> }
>
> Cheers,
> Pierre
>
> Le mer. 31 juil. 2019 à 00:53, a écrit :
>
>> When a staff that has previously been sto
\once\override Staff.Clef.stencil = ##f
\clef "bass" c4 c c c |
}
>>
}
Cheers,
Pierre
Le mer. 31 juil. 2019 à 00:53, a écrit :
> When a staff that has previously been stopped with \stopStaff is
> restarted with \startStaff on the first beat of a measur
When a staff that has previously been stopped with \stopStaff is
restarted with \startStaff on the first beat of a measure, and this
coincides with a clef change in another staff, the first staff begins at
the clef instead of the barline.
%%% begin MWE %%%
\version "2.21.0&quo
Perfect, thanks once again!
Evan
On Wed, Jun 26, 2019 at 11:54 PM Aaron Hill
wrote:
> On 2019-06-26 9:27 pm, Evan Driscoll wrote:
> > I've got the example document below. There's a bit too little space for
> > me
> > between the last note in the last measure of the first line and the new
> > cle
On 2019-06-26 9:27 pm, Evan Driscoll wrote:
I've got the example document below. There's a bit too little space for
me
between the last note in the last measure of the first line and the new
clef.
I found a mailing list entry that showed how to put some extra space
before
the clef (the comment
I've got the example document below. There's a bit too little space for me
between the last note in the last measure of the first line and the new
clef.
I found a mailing list entry that showed how to put some extra space before
the clef (the commented-out override) and that looks great -- except
On 07.09.2018 03:17, Simon Albrecht wrote:
Hello everybody,
here’s two suggestions for the LSR snippets dealing with an initial
clef change before the first note of a piece:
#956 <http://lsr.di.unimi.it/LSR/Item?id=956> works with a hidden
grace note; this creates an unsightly gap th
On 07.09.2018 03:17, Simon Albrecht wrote:
Hello everybody,
here’s two suggestions for the LSR snippets dealing with an initial
clef change before the first note of a piece:
#956 <http://lsr.di.unimi.it/LSR/Item?id=956> works with a hidden
grace note; this creates an unsightly gap th
Hello everybody,
here’s two suggestions for the LSR snippets dealing with an initial clef
change before the first note of a piece:
#956 <http://lsr.di.unimi.it/LSR/Item?id=956> works with a hidden grace
note; this creates an unsightly gap that can be avoided by using a
grace-timed
On 15.09.2016 22:25, Malte Meyn wrote:
Am 15.09.2016 um 21:46 schrieb Simon Albrecht:
if in a piano score the right hand begins in bass clef, it is customary
to write a treble clef first and change to bass clef after the time
signature, presumably to draw more attention. Is there any more elegan
Am 15.09.2016 um 21:46 schrieb Simon Albrecht:
if in a piano score the right hand begins in bass clef, it is customary
to write a treble clef first and change to bass clef after the time
signature, presumably to draw more attention. Is there any more elegant
way than this kind of fake in LilyPo
Hello,
if in a piano score the right hand begins in bass clef, it is customary
to write a treble clef first and change to bass clef after the time
signature, presumably to draw more attention. Is there any more elegant
way than this kind of fake in LilyPond?
\version "2.19.47"
{
\clef treb
Hello David,
Fine, you hit the point, and the following code avoids the non-appearing notes
problem:
% Music to be used by CueDuring has to start at the same point in time
% as the music that incorporates it!
HautboisAvantChiffreSept = \relative gis' {
\voiceOne
% \tweak staff-position #-1
On Mon 09 Nov 2015 at 17:00:51 (+0100), Menu Jacques wrote:
> Hello David,
>
> The docs say that the part that « receives » a Cue is usually made of rests,
> but not what happens if they contain actual notes.
> Removing the last eight in the Cue avoids the problem, of course.
>
> I tried with cu
Hello the other David,
I’ve found that \compressFullBarRests is too much just before I got your
message, thanks for that one.
And yes, I forgot to comment out:
a8 )
s
at the end of HautboisAvantChiffreSept, hence the difference in length.
But doing so doesn’t solve the problem: the first f
On Mon 09 Nov 2015 at 17:00:51 (+0100), Menu Jacques wrote:
> Hello David,
>
> The docs say that the part that « receives » a Cue is usually made of rests,
> but not what happens if they contain actual notes.
> Removing the last eight in the Cue avoids the problem, of course.
>
> I tried with cu
Le 8 nov. 2015 à 10:44, David Kastrup a écrit :
>
> Menu Jacques writes:
>
>> Hello folks,
>>
>> In the following, from Poulenc, I added a CueVoice to help the bassonnist
>> (i.e.
>> myself). The example is a bit long, sorry for that.
>>
>
Menu Jacques writes:
> Hello folks,
>
> In the following, from Poulenc, I added a CueVoice to help the bassonnist
> (i.e.
> myself). The example is a bit long, sorry for that.
>
> The critial point is on the second beat of the bar at the « 1 » rehearsal
> mark:
>
Hello folks,
In the following, from Poulenc, I added a CueVoice to help the bassonnist (i.e.
myself). The example is a bit long, sorry for that.
The critial point is on the second beat of the bar at the « 1 » rehearsal mark:
the clef change to « bass » for the bassoon takes effect also for the
clefs: one to revert the cue
clef (smaller) and one to make the actual clef change. Attached is a
minimal example.
I have tried everything, like \hide CueClef etc, but I have not found
any way to prevent the second cue clef (to unset the treble cue clef)
from appearing...
Any idea how I can
> Message: 5
> Date: Thu, 09 Apr 2015 13:45:39 +0200
> From: Reinhold Kainhofer
> To: LilyPond User Mailinglist
> Subject: Double clef when using cueDuringWithClef with a simultaneous
> clefchange
> Message-ID: <5523.7040...@kainhofer.com>
> Content-
) and one to make the actual clef change. Attached is a minimal
example.
I have tried everything, like \hide CueClef etc, but I have not found
any way to prevent the second cue clef (to unset the treble cue clef)
from appearing...
Any idea how I can suppress the bass cue clef in this example
Nolan:
Place an “\acciaccatura s8” after the clef change and before the “e.” See below.
Mark
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Nolan
Winter
Sent: Saturday, April 04, 2015 11:13 AM
To
cciaccatura c,8-. c1-- |
}
>>
On Sat, Apr 4, 2015 at 2:12 PM, Nolan Winter wrote:
> Like the title says. What is strange is that the clef change isn't even on
> the same staff yet the grace note causes it to be placed incorrectly. In
> the actual music that I am encountering this
Like the title says. What is strange is that the clef change isn't even on
the same staff yet the grace note causes it to be placed incorrectly. In
the actual music that I am encountering this problem, there is a line break
which will cause a problem with reading because the reader won
Try :
\version "2.18.2"
up = { \change Staff = "up" }
down = { \change Staff = "down" }
\new PianoStaff <<
\new Staff = "up" {
\clef bass
\time 6/8
s4.
\clef treble \up 8 \down \up
}
\new Staff = "down" {
\clef bass
8 \up \down
\clef treble
s4.
}
>>
C
I'm trying to transcribe Ravel's Alborada del Gracioso but when there are
clef changes there tends to be a collision between the clef and the notes.
How would I add space? And perhaps I'm writing it incorrectly, since I have
one staff doing all the work. I don't know how to have cross staff beaming
Added to the LSR : http://lsr.di.unimi.it/LSR/Item?id=956
<http://http://lsr.di.unimi.it/LSR/Item?id=956>
-
~Pierre
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Clef-change-at-the-beginning-of-a-staff-tp168090p168114.html
Sent from the User mailing list a
That's also good. I thought the grace note causes problems if it is
different in different staves but this also works:
\version "2.18.2"
<<
\relative c'' { c c c c c1 }
\new Staff \relative c' {
%% Start with a bass clef :
\clef bass
%% Use a hidden grace note (avoid any wrong calculation
1 - 100 of 185 matches
Mail list logo
