Re: Cue clefs

On Mon, 26 Feb 2024 at 22:13, Gerardo Ballabio wrote: > > Thanks. It says this -- but it works: > > programming error: No spacing entry from BarLine to `cue-clef' > continuing, cross fingers Ah yes, I hadn't paid attention to that. In that case, let's add a spacing entry between BarLine and

Re: Cue clefs

Il giorno dom 25 feb 2024 alle ore 22:35 Xavier Scheuer ha scritto: > Add this before the \cueClef (I only moved the cue-clef after staff-bar): Thanks. It says this -- but it works: programming error: No spacing entry from BarLine to `cue-clef' continuing, cross fingers Just in case I need

Re: Cue clefs

On Sun, 25 Feb 2024 at 22:35, Xavier Scheuer wrote: > > By the way I would not remove the cue end clef. This is also standard practice: to "close" the cue clef (back to playing instrument clef). Actually in your example I would move the cue end clef to the end of the bar (just before the playing

Re: Cue clefs

On Sun, 25 Feb 2024 at 21:36, Gerardo Ballabio wrote: > > It does, thank you. > Any ideas for the other question (how to move the cue clef after the bar line)? Hello, Add this before the \cueClef (I only moved the cue-clef after staff-bar): \once \override

Re: Cue clefs

On Sun, Feb 25, 2024 at 12:36 PM Gerardo Ballabio < gerardo.balla...@gmail.com> wrote: > It does, thank you. > Any ideas for the other question (how to move the cue clef after the bar > line)? > Try this: \version "2.24.1" \new Staff { \clef "bass" R1 << \new CueVoice \relative {

Re: Cue clefs

It does, thank you. Any ideas for the other question (how to move the cue clef after the bar line)? Gerardo Il giorno sab 24 feb 2024 alle ore 01:17 Leo Correia de Verdier ha scritto: > > CueClef and CueEndClef are their own types of GROB, could \omit > Staff.CueEndClef work? > > (sorry for

Re: Cue clefs

CueClef and CueEndClef are their own types of GROB, could \omit Staff.CueEndClef work? (sorry for short untried answer, I’m on the phone) > 24 feb. 2024 kl. 00:27 skrev Gerardo Ballabio : > > Hello, please let me ask two questions on the example below: > 1. how can I move the cue treble clef

Cue clefs

Hello, please let me ask two questions on the example below: 1. how can I move the cue treble clef after the bar line? 2. how can I remove the closing bass clef? I tried \omit Staff.Clef but it doesn't work -- I guess because, indeed, that isn't the *staff* clef. Thank you Gerardo %%

Re: Is this a sensible interface for temporary multiple clefs?

Valentin Petzel writes: > Hello David, > > if I understand this correctly the intent here is to have different staff > behaviour in one staff. I believe that there might be a more general concept > here. Instead of creating a new context and mechanic to set additional clefs, &

Re: Is this a sensible interface for temporary multiple clefs?

Hello David, if I understand this correctly the intent here is to have different staff behaviour in one staff. I believe that there might be a more general concept here. Instead of creating a new context and mechanic to set additional clefs, maybe it would make sense to have a more general

Is this a sensible interface for temporary multiple clefs?

2.~ \break 2.~2. \oneVoice \extraClefEnd c''2. } >> } } } If made built-in, it would affect several files and introduce a new default context type. I don't think it covers multiple simultanous main clefs (like sometimes seen in compact mensural notation). I

Re: clefs, time signatures, and key signatures

> does the new proposed spacing mean that the time signatures are not > aligned across staves any more but were before? No, they are aligned as before. Werner

Re: clefs, time signatures, and key signatures

Hi Werner, does the new proposed spacing mean that the time signatures are not aligned across staves any more but were before? Best, Michael

Re: clefs, time signatures, and key signatures

>>> please have a look at Merge Request 2188 and comment there on how >>> to proceed with the new distances between clefs and time >>> signatures, together with the new distances between clefs and key >>> signatures. >>> >>> http

Re: clefs, time signatures, and key signatures

For what it's worth, I think the original suggestion (with the top-left clef adjusted by -4.4%) is the better of the two. I do understand that there's an argument to be made against adjusting clefs that aren't /too/ bad, but the adjusted versions of the treble clefs /are/ better imo

Re: clefs, time signatures, and key signatures

> Thanks, but I would like to know whether you prefer the top > (alto-based) or bottom (treble-based) image on > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 Top (alto-based) is 6 days ago and bottom (treble-based) is 4 days ago as of today? Of those two I prefer bottom as

Re: clefs, time signatures, and key signatures

> I’ve just looked at the images and especially w/r to the Alto clef I > strongly prefer the new spacing. For the others there are spots > where I’m not sure it is too tight but overall the new spacing > appears to be more balanced. > > I thus think the new spacing is better overall. Thanks,

Re: clefs, time signatures, and key signatures

Mobil gesendet > Am 09.12.2023 um 08:12 schrieb Werner LEMBERG : > >  >>> please have a look at Merge Request 2188 and comment there on how >>> to proceed with the new distances between clefs and time >>> signatures, together with the new distances

Re: clefs, time signatures, and key signatures

>> please have a look at Merge Request 2188 and comment there on how >> to proceed with the new distances between clefs and time >> signatures, together with the new distances between clefs and key >> signatures. >> >> https://gitlab.com/lil

Re: clefs, time signatures, and key signatures

>> please have a look at Merge Request 2188 and comment there on how >> to proceed with the new distances between clefs and time >> signatures, [...] > > FWIW, I think the Petrucci clef distances are a big improvement and > make incipits closer to what they usually

Re: clefs, time signatures, and key signatures

On Tue, 5 Dec 2023, 07:42 Werner LEMBERG, wrote: > > Folks, > > > please have a look at Merge Request 2188 and comment there on how to > proceed with the new distances between clefs and time signatures, > together with the new distances between clefs and key signatures. >

Re: clefs, time signatures, and key signatures

ith the new distances between clefs and time signatures, >> together with the new distances between clefs and key signatures. >> >> https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 >> >> The question is whether the new distances should be based on the &g

Re: clefs, time signatures, and key signatures

> please have a look at Merge Request 2188 and comment there on how to > proceed with the new distances between clefs and time signatures, > together with the new distances between clefs and key signatures. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 &g

clefs, time signatures, and key signatures

Folks, please have a look at Merge Request 2188 and comment there on how to proceed with the new distances between clefs and time signatures, together with the new distances between clefs and key signatures. https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 The question is whether

Re: using partcombine with different clefs, repeats, text

I think this sounds like a use case for a long text preface explaining what is to be performed in what order and why, just notating everything on a treble clef and doing manual octavations in the midi file. Maybe writing a reminding 1S,2B: or such (not sure I got it completely right from your

Re: using partcombine with different clefs, repeats, text

PS - you know what? I'm sorry: I'm making this guy's work much more complicated than it needs to be. This is really just a song for single voice and piano; I'll notate it that way and leave it to him to work out with the performers who sings which verse in which language. Sorry for the trouble! A

using partcombine with different clefs, repeats, text

Hi List, sigh … here we go again. I apologize in advance for my client, a hobbyist composer who thinks entirely in terms of cutting and pasting, moving things around manually, and not in terms of how to notate anything clearly. Here goes: He has a song for soprano, baritone, and piano. The song

Re: changing clefs in transposed variable

ef in the middle of the transposed music Please check your examples to actually run. In this case, simply music = \relative c' { c8 d e g, a b c4 } \score { \after 8*3 \clef "alto" \transpose c f, \music } works. In more complex cases it might be easier to use simultaneo

changing clefs in transposed variable

hello list, new here, i have the following simplified snippets: music = \relative c' { c8 d e g, a b c4 } \score \relative c' { \transpose c f, \music } is it possible to change clef in the middle of the transposed music lem

Re: peculiar behaviour with clefs when using acciaccatura on first note in a piece.

Maurits Lamers writes: > Hey all, > > I noticed some unexpected behavior when using an acciaciatura on the first > note of a piece: > > \version "2.20.0" > > \score { > << > \new Staff { > \clef treble > \new Voice { > \acciaccatura { g8 } > g1} > >

Fwd: peculiar behaviour with clefs when using acciaccatura on first note in a piece.

-- Forwarded message - From: Ralph Palmer Date: Tue, Sep 8, 2020 at 8:51 AM Subject: Re: peculiar behaviour with clefs when using acciaccatura on first note in a piece. To: Maurits Lamers On Tue, Sep 8, 2020 at 8:30 AM Maurits Lamers wrote: > Hey all, > > I not

peculiar behaviour with clefs when using acciaccatura on first note in a piece.

Hey all, I noticed some unexpected behavior when using an acciaciatura on the first note of a piece: \version "2.20.0" \score { << \new Staff { \clef treble \new Voice { \acciaccatura { g8 } g1} } \new Staff { \clef bass \new Voice

Re: New User: How can one separate voice share different clefs in a piano fugue?

Right, I did that quickly without checking the whole score. Also, as I use \fixed, I found it faster to type. But again, you're right, it's a single voice. Cheers, Pierre Le jeu. 21 mai 2020 à 18:29, Lukas-Fabian Moser a écrit : > Hi Pierre, > > Am 21.05.20 um 15:53 schrieb Pierre

Re: New User: How can one separate voice share different clefs in a piano fugue?

Okay, for number one: If you name the Staves, i.e. You got something like \new PianoStaff << \new Staff = "right" { ... } \new Staff = "left"{ ... } >> You can switch a voice between these staves by \change Staff = "right" Also see

Re: New User: How can one separate voice share different clefs in a piano fugue?

So here you go. Cheers, Pierre (typos possible) Le jeu. 21 mai 2020 à 19:09, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> a écrit : > Right, I did that quickly without checking the whole score. > Also, as I use \fixed, I found it faster to type. > But again, you're right, it's a

Re: New User: How can one separate voice share different clefs in a piano fugue?

Hi Pierre, Am 21.05.20 um 15:53 schrieb Pierre Perol-Schneider: Here's  a template, made as clear as possible, in a fixed mode (no relative). (First measures taken from: https://imslp.simssa.ca/files/imglnks/usimg/9/9b/IMSLP411479-PMLP05948-bach-wtk-ur-1.pdf) But what's the point in using

Re: New User: How can one separate voice share different clefs in a piano fugue?

Dear Mark Stephen Mrotek Pierre Perol-Schneider Hans Åberg Lukas-Fabian Moser Jacques Menu Wow, the extremely quick response here is more than anyone could expect. Thank you all for your very nice comments and suggestions. I have to do some homework to get it right. I am confident with your

RE: New User: How can one separate voice share different clefs in a piano fugue?

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of R.H. Sent: Thursday, May 21, 2020 5:53 AM To: lilypond-user Subject: New User: How can one separate voice share different clefs in a piano fugue? INTRO A big "Hello" to this list!

Re: New User: How can one separate voice share different clefs in a piano fugue?

Hi Roland, Here's a template, made as clear as possible, in a fixed mode (no relative). (First measures taken from: https://imslp.simssa.ca/files/imglnks/usimg/9/9b/IMSLP411479-PMLP05948-bach-wtk-ur-1.pdf ) HTH, Cheers, Pierre Le jeu. 21 mai 2020 à 15:34, Hans Åberg a écrit : > > > On 21 May

Re: New User: How can one separate voice share different clefs in a piano fugue?

> On 21 May 2020, at 14:53, R.H. wrote: > > I started to encode the Bach's Fugue Nr. IX in Lilypond. I stumbled over a > problem which I could not yet (as a beginner) solve. One way to learn is looking at examples, here is one for BWV 861 instead of BWV 854:

Re: New User: How can one separate voice share different clefs in a piano fugue?

Hi Roland, welcome! I started to encode the Bach's Fugue Nr. IX in Lilypond. I stumbled over a problem which I could not yet (as a beginner) solve. The music is polyphonic with three distinct voices. There is a bass voice, a soprano voice and an alt voice. The alt voice uses both clefs

Re: New User: How can one separate voice share different clefs in a piano fugue?

wly composed music. > > BEGINNER'S QUESTIONS > > I started to encode the Bach's Fugue Nr. IX in Lilypond. I stumbled over a > problem which I could not yet (as a beginner) solve. The music is polyphonic > with three distinct voices. There is a bass voice, a soprano voice and an alt

New User: How can one separate voice share different clefs in a piano fugue?

ting newly composed music. BEGINNER'S QUESTIONS I started to encode the Bach's Fugue Nr. IX in Lilypond. I stumbled over a problem which I could not yet (as a beginner) solve. The music is polyphonic with three distinct voices. There is a bass voice, a soprano voice and an alt voice. The alt voice uses

Re: Double clefs (or even triple) (Malte Meyn)

Malte, I just changed the musicglyph to the G_change and F_change. So, for a single code that could be applied to initial clefs and clef changes, it would be necessary to create such clefs as new clefs? doubleF = { \once \omit Staff.ClefModifier \once \override Staff.Clef.layer = -1

Re:Double clefs (or even triple) (Malte Meyn)

Beautiful. Thanks! -- Forwarded message -- > From: Malte Meyn > To: lilypond-user@gnu.org > Cc: > Bcc: > Date: Sat, 19 Oct 2019 15:23:48 +0200 > Subject: Re: Double clefs (or even triple) > > > Am 19.10.19 um 14:56 schrieb Alexandre Ficagna: > >

Re: Double clefs (or even triple)

Am 19.10.19 um 14:56 schrieb Alexandre Ficagna: Hi as Lilypond now have double G clefs with the \clef GG I'm wondering why there's no \clef FF or even more like \clef GGG and \clef FFF for 15a and 15b Hi Alexandre, I’ve never seen that, when are such clefs used? Cheers, Malte Still, I

Double clefs (or even triple)

Hi as Lilypond now have double G clefs with the \clef GG I'm wondering why there's no \clef FF or even more like \clef GGG and \clef FFF for 15a and 15b I say this old solution form here: http://lilypond.1069038.n5.nabble.com/Double-treble-and-alternative-percussion-clefs-td19406.html#a19408

Re: Double treble and (alternative) percussion clefs

Hi Caio, did you manage to find a Double Bass Clef? Lilypond now has a \clef GG, but still missing a \clef FF -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Percussion and tab clefs question

Hello Joram & Torsten, Fine, so both are right, thanks for the information. The file I used is not musically relevant actually, since it’s only a unit test for clefs handling. A nice w-e! JM > Le 23 juin 2018 à 12:22, Torsten Hämmerle a écrit : > > Hello Jacques, > > J

Re: Percussion and tab clefs question

ike in a treble clef for both the tab and > the percussion clef. Which is understandable as it is the closest to a > default clef. Yes. And LilyPond doen't have deliberate settings at all because these clefs don't make any sense (i.e. are undefined pitch-wise) in a Staff environment and inc

Re: Percussion and tab clefs question

Dear Jacques, I guess the pitches are undefined in both the tab clef and the percussion clef. The tab clef only makes sense on a tab-staff where the notes are denoted with numbers (frets) per string. The percussion clef might have some pitched instruments, but there is no universal definition

Re: \cadenzaOn: clefs, key signatures on line breaks

Robert Kubosz wrote > Still I have question refering the breaks: is there any other method for > line breaking (preferably auto-breaking)? I don't understand your question. In your exemple, the breakings are working because you have added the barlines in your \repeat command. Then LP

Re: \cadenzaOn: clefs, key signatures on line breaks

Hi Thomas! I added the post via web page with use of markup. It looks like the mail engine ignored it. Nevermind, I repost the example: \version "2.19.81" \relative f' { \clef treble \key f \major \repeat unfold 10 f4 \break \repeat unfold 10 g4

Re: \cadenzaOn: clefs, key signatures on line breaks

2018-05-13 18:30 GMT+02:00 Robert Kubosz : > The example below Hello, there is no code visible for me in your mail. Neither here: https://lists.gnu.org/archive/html/lilypond-user/2018-05/msg00317.html Please provide plain text mails or attach a file or a link to it.

Re: \cadenzaOn: clefs, key signatures on line breaks

in cadenza mode? > > With best regards > Robert Hi Robert. I don't understand your problem, cadenzaOn will produce the clefs and time signature after line breaks by default! I think your exemple is missing the "cadenzaOn" btw. \version "2.19.81" \relative f' { \c

\cadenzaOn: clefs, key signatures on line breaks

Hello! I write a music piece with \cadenzaOn and \cadenzaOff. The example below produces output without the clef and key signature after line break. Is there a possibility to display them? Also, I have second question: can the lines auto break in cadenza mode? With best regards Robert --

Re: Clefs

Ethan, I am transcribing some baroque canons. Does anyone know how to make upside down/backwards clefs? How about: \version "2.19.80" rotClef = #(define-music-function     (line cl)     (number? string?)     #{   \once \override Staff.Cl

Re: Clefs

6:18 PM, Ben <soundsfromso...@gmail.com> wrote: > > On 4/4/2018 6:04 PM, Ethan Sue wrote: > > Hello > I am transcribing some baroque canons. Does anyone know how to make upside > down/backwards clefs? > > > > Hello, > > Do you have a picture of what ex

Re: Clefs

ow how to make upside down/backwards clefs? Hello, Do you have a picture of what exactly you mean? Is the clef you want featured anywhere on this page? http://lilypond.org/doc/v2.19/Documentation/notation/clef-styles Do have you a photo of th

Re: Clefs

No it is a mirror image that indicates retrograde. Not on that page. S. On Wed, Apr 4, 2018 at 6:18 PM, Ben <soundsfromso...@gmail.com> wrote: > On 4/4/2018 6:04 PM, Ethan Sue wrote: > > Hello > I am transcribing some baroque canons. Does anyone know how to make upside >

Re: Clefs

On 4/4/2018 6:04 PM, Ethan Sue wrote: Hello I am transcribing some baroque canons. Does anyone know how to make upside down/backwards clefs? Hello, Do you have a picture of what exactly you mean? Is the clef you want featured anywhere on this page? http://lilypond.org/doc/v2.19

Clefs

Hello I am transcribing some baroque canons. Does anyone know how to make upside down/backwards clefs? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

t;lilypond-user@gnu.org> Subject: Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs 2018-03-11 0:58 GMT+01:00 Lucas Werkmeister <m...@lucaswerkmeister.de>: > Hi everyone, > > I found what I suspect is a LilyPond bug, but I’m not sure yet :

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

t;lilypond-user@gnu.org> Subject: Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs 2018-03-11 0:58 GMT+01:00 Lucas Werkmeister <m...@lucaswerkmeister.de>: > Hi everyone, > > I found what I suspect is a LilyPond bug, but I’m not sure yet :

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

2018-03-11 0:58 GMT+01:00 Lucas Werkmeister : > Hi everyone, > > I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal > example: > > \version "2.18.2" > > << > \new Staff { \grace c' c' } > \new Staff { \clef "bass" } >>> > > Instead of beginning

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

On 11.03.2018 01:29, Lucas Werkmeister wrote: > I’m not sure if the clef behavior would still qualify as a bug (in the > docs, the grace note isn’t at the very beginning of the score, so the > clef behavior doesn’t happen) And it turns out this has also been described [1]. I must just have been

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

On 11.03.2018 00:58, Lucas Werkmeister wrote: > (Or perhaps it’s simply expected that grace notes should be aligned > between staves? But that would surprise me.) Color me surprised, then – I just found this issue mentioned in the docs [1], with the same workaround I also discovered. I’m not sure

Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

Hi everyone, I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal example: \version "2.18.2" <<   \new Staff { \grace c' c' }   \new Staff { \clef "bass" } >> Instead of beginning with a bass clef, the lower staff begins with a violin clef and then has a bass clef right

Re: Placement of clefs at repeat bars

Thomas, That's a brilliant subversion of the \afterGrace command - I hadn't realised you could use it for anything but notes! I think I need a good course on lateral thinking. I'd come up with this, which puts the treble clef at the beginning of the repeated section - as I said earlier I

Re: Placement of clefs at repeat bars

2018-02-20 11:08 GMT+01:00 Peter Toye : > Mark, > > This works for my example as given, but not for the following one. Here > the problem is that two clef changes are needed: > > 1) for the repeat from bass to treble (bar 6 back to 4), and > 2) one for the continuation, from

RE: Placement of clefs at repeat bars

Peter, Got the measure numbers wrong. The snippet is correct. Mark From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Tuesday, February 20, 2018 7:01 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark,

RE: Placement of clefs at repeat bars

phen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, Thanks. This solves problem 2, but I've adapted it for no 1 (see below). I can't see any way of printing the clef change immediately before the closing repeat bar (for the repea

Re: Placement of clefs at repeat bars

tor 3 '(staff-bar clef )) \clef "bass" c } } } Mark From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Tuesday, February 20, 2018 2:09 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, This work

RE: Placement of clefs at repeat bars

ebruary 20, 2018 2:09 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, This works for my example as given, but not for the following one. Here the problem is that two clef changes are needed: 1) for the repeat f

Re: Placement of clefs at repeat bars

- Monday, February 5, 2018, 2:08:07 PM, Mark Stephen Mrotek wrote: Peter, You are welcome very much! Mark From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Monday, February 05, 2018 1:10 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org

RE: Placement of clefs at repeat bars

Peter, You are welcome very much! Mark From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Monday, February 05, 2018 1:10 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, I see what you mean! That

Re: Placement of clefs at repeat bars

.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, Thanks. You read my email correctly - the bass clef should be after the barline, not before. But your idea didn't change this. Should it have done so? Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.c

RE: Placement of clefs at repeat bars

rk From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Sunday, February 04, 2018 10:55 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, Thanks. You read my email correctly - the bass clef should be after the barli

Re: Placement of clefs at repeat bars

the perfect be the enemy of the good. Don’t look a gift horse in the mouth. From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Sunday, February 04, 2018 3:45 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars Mark, Your snippet

RE: Placement of clefs at repeat bars

Never let the perfect be the enemy of the good. Don't look a gift horse in the mouth. From: Peter Toye [mailto:lilyp...@ptoye.com] Sent: Sunday, February 04, 2018 3:45 AM To: Mark Stephen Mrotek <carsonm...@ca.rr.com>; lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars

Re: Placement of clefs at repeat bars

#(make-vector > 3 '(staff-bar clef )) >\clef "bass" | c c > } > Mark > -Original Message- > From: lilypond-user > [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of > ptoye > Sent: Saturday, February 03, 2018 11:08 A

Re: Placement of clefs at repeat bars

Saturday, February 3, 2018, 8:22:38 PM, you wrote: > Hi Peter, > 2018-02-03 20:08 GMT+01:00 ptoye : >> I've found that this is was reported as an "ugly" in 2011. > Plese provide the link. https://sourceforge.net/p/testlilyissues/issues/1862/ >> I think it's a bug >> as the

Re: Placement of clefs at repeat bars

Hi Peter, 2018-02-03 20:08 GMT+01:00 ptoye : > I've found that this is was reported as an "ugly" in 2011. Plese provide the link. > I think it's a bug > as the output is definitely incorrect. Look at the following examples (1) %\unfoldRepeats \new Staff { \time 4/4 \clef

RE: Placement of clefs at repeat bars

..@gnu.org] On Behalf Of ptoye Sent: Saturday, February 03, 2018 11:08 AM To: lilypond-user@gnu.org Subject: Re: Placement of clefs at repeat bars I've found that this is was reported as an "ugly" in 2011. I think it's a bug as the output is definitely incorrect. The reverse happens with the

Re: Placement of clefs at repeat bars

I've found that this is was reported as an "ugly" in 2011. I think it's a bug as the output is definitely incorrect. The reverse happens with the snippet below, where the change of clef is missing. \version "2.19.52" \language "english" \score { \new Staff { \time 4/4 \clef "treble" c''2

Placement of clefs at repeat bars

There seems to be a bug in the placement of clef change signs at repeats. The snippet below puts the bass clef sign before the repeat bar. It should be after! The score as engraved implies that the change to bass clef is for the repeated section, not the following bar. Very confusing for the

RE: tweaking clefs

From: Timothy Lanfear [mailto:timo...@lanfear.me] Sent: 06 March 2017 12:28 To: Peter Gentry <peter.gen...@sunscales.co.uk>; lilypond-user@gnu.org Subject: Re: tweaking clefs On 06/03/17 12:02, Peter Gentry wrote: From: Peter Gentry [mailto:peter.gen...@sunscales.co.uk] Se

Re: tweaking clefs

On 06/03/17 12:02, Peter Gentry wrote: *From:*Peter Gentry [mailto:peter.gen...@sunscales.co.uk] *Sent:* 05 March 2017 16:21 *To:* 'lilypond-user@gnu.org' <lilypond-user@gnu.org> *Subject:* Re:tweaking clefs Timothy Lanfear supplied a simple understandable way of achieving my aims. H

RE: Re:tweaking clefs

From: Peter Gentry [mailto:peter.gen...@sunscales.co.uk] Sent: 05 March 2017 16:21 To: 'lilypond-user@gnu.org' <lilypond-user@gnu.org> Subject: Re:tweaking clefs Timothy Lanfear supplied a simple understandable way of achieving my aims. However on reflection there is a dr

Re: tweaking Clefs

Hi David, >> The clef changes are fine… but the transposition doesn’t work as I >> would expect/hope it would. > > What did you expect/hope? This is just for Midi. Well, then… that explains it, since the visuals were therefore not critical. >> Is there a way to extend this music-function idea

Re: tweaking Clefs

Kieren MacMillan writes: > Hi David, > >> Uh, { ... \bassclarinet ... } ? >> >> With something like >> >> bassclarinet = { >> \clef F >> \transposition c, >> \set Staff.midiInstrument = "clarinet" >> \set Staff.instrumentCueName = \markup \bf "cl. B" >> \set

Re: tweaking clefs

\inherit-acceptability is documented in \version "2.19.56" which I have just downloaded. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tweaking Clefs

Hi David, > Uh, { ... \bassclarinet ... } ? > > With something like > > bassclarinet = { > \clef F > \transposition c, > \set Staff.midiInstrument = "clarinet" > \set Staff.instrumentCueName = \markup \bf "cl. B" > \set Staff.instrumentName = "bass clarinet" > \set

Re:tweaking clefs

Timothy Lanfear supplied a simple understandable way of achieving my aims. I was thrown headlong down the route of trying to modify the sequential music stream as was done for indicating/modifying pitches outside the "range" of each instrument. "range" being somewhat arbitrary as it depends on

Re: tweaking Clefs

Kieren MacMillan writes: > Hi David (et al.), > >>> No one picked up this one. Perhaps a way to tackle this problem would >>> be to define specific contexts for the instruments that automatically >>> have the right properties. It's worth reading through all the

Re: tweaking Clefs

Hi David (et al.), >> No one picked up this one. Perhaps a way to tackle this problem would >> be to define specific contexts for the instruments that automatically >> have the right properties. It's worth reading through all the context >> properties to see which you should set. > > Huh, this

Re: tweaking Clefs

me to proofread in the original clef, and I sometimes forget to change clefs after proofreading. However, I think there would be problems with doing an automatic clef change with transposition, at least in classical music. Viola uses both alto and treble clef, and cello uses bass and tenor. I suspect o

Re: tweaking Clefs

Timothy Lanfear writes: > On 01/03/17 18:02, Peter Gentry wrote: >> >> It would be nice to be able to change the clef at the same time as >> transposing. >> >> I often forget one or other and it is easier to input data in the >> original clef for checking input. >> >> Having

Re: tweaking Clefs

On 01/03/17 18:02, Peter Gentry wrote: It would be nice to be able to change the clef at the same time as transposing. I often forget one or other and it is easier to input data in the original clef for checking input. Having started down this road it has become a challenge…..Any help for

tweaking Clefs

Is it possible to tweak clef properties in the same way that you can tweak color and notehead style of a ly:pitch? Object. Ie ;rebuild the pitch and if a changed pitch add the color tweak (if (ly:pitch? p) (let ((new-pitch (naturalize-instrument-range p instrument)))

  1   2   3   >