Re: Moving key signatures

2025-07-05 Thread Brent Annable
Knute, >> >> Thanks! Interesting epilogue: Lilypond automatically placed this >> particular key change at the end of a line, and then all the key signatures >> at the beginning of the next system are kicked off the staves to the left: >> >> ... > >> I can force

Re: Moving key signatures

2025-07-04 Thread Knute Snortum
On Fri, Jul 4, 2025 at 3:52 PM Brent Annable wrote: > Hey Knute, > > Thanks! Interesting epilogue: Lilypond automatically placed this > particular key change at the end of a line, and then all the key signatures > at the beginning of the next system are kicked off the sta

Re: Moving key signatures

2025-07-04 Thread Brent Annable
Hey Knute, Thanks! Interesting epilogue: Lilypond automatically placed this particular key change at the end of a line, and then all the key signatures at the beginning of the next system are kicked off the staves to the left: \version "2.24.4" \score { \new StaffGroup <<

Re: Moving key signatures

2025-07-04 Thread Knute Snortum
On Fri, Jul 4, 2025 at 2:55 PM Brent Annable wrote: > Hi all, > > Rather than having a key-signature change appear at the start of the bar > where it takes effect, I'm trying to move it to the end of the previous bar > (see example). The problem is that Lilypond still re

Moving key signatures

2025-07-04 Thread Brent Annable
Hi all, Rather than having a key-signature change appear at the start of the bar where it takes effect, I'm trying to move it to the end of the previous bar (see example). The problem is that Lilypond still reserves space for the key signature in all other staves at the start of the bar whe

Re: Question about color key signature

2025-07-04 Thread Lukas-Fabian Moser
The whole approach blows up as soon as someone rewrites ly:key-signature-interface::print in lily/key-signature-interface.cc (which of course might not happen for quite some time). But if Carren confirms that the snippet works in a production score, I agree that I should turn this into a

Re: Question about color key signature

2025-07-04 Thread Lukas-Fabian Moser
r person's ugly hack :-). The whole approach blows up as soon as someone rewrites ly:key-signature-interface::print in lily/key-signature-interface.cc (which of course might not happen for quite some time). But if Carren confirms that the snippet works in a production score, I agree that I s

Re: Question about color key signature

2025-07-02 Thread Werner LEMBERG
>> I don't see another possibility. But I'm willing to implement 2) if >> it fits your need. > > Maybe something like this? [...] Very nice! I think this would be a good snippet for the LSR. Werner

Re: Question about color key signature

2025-07-02 Thread Lukas-Fabian Moser
translation (cons 'combine-stencil coloured-accidentals))    keysig-xext    keysig-yext    #}) {   \colouredKeySignature \keysig-colors   \key des \major   c'1   \clef bass \break   c1 }

Re: Question about color key signature

2025-07-02 Thread Lukas-Fabian Moser
Hi Carren, Am 01.07.25 um 23:29 schrieb Carren Carlsen: I have an unusual question.  I am working on a special project and I need to color code key signatures in a specific way.  For example:  Key D the sharp for F will be blue and the sharp for C will be green.  Is this possible to

Re: Question about color key signature

2025-07-01 Thread Tom Brennan
t I may be misremembering. Hopefully, someone will guide you how to make this happen in lilypond directly, though. Best wishes Tom On Tue, Jul 1, 2025, 5:45 PM Carren Carlsen wrote: > Good Afternoon, > > I have an unusual question. I am working on a special project and I need > to color co

Question about color key signature

2025-07-01 Thread Carren Carlsen
Good Afternoon, I have an unusual question. I am working on a special project and I need to color code key signatures in a specific way. For example: Key D the sharp for F will be blue and the sharp for C will be green. Is this possible to accomplish? Thank you, Carren Carlsen

Question about Key Signature Colors

2025-07-01 Thread Carren Carlsen
Good Afternoon, I have an unusual question. I am working on a special project and I need to color code key signatures in a specific way. For example: Key D the sharp for F will be blue and the sharp for C will be green. Is this possible to accomplish? Thank you, Carren Carlsen

Re: time signature and key change at end of line

2025-03-07 Thread Timothy Lanfear
On 06/03/2025 20:50, Paul Scott wrote: I posted before about time signatures and/or key changes repeated at the end of the previous line and was shown that it works correctly. I finally saw the problem that occasionally effects my normal code structure. Could the \endSpanners music

Re: time signature and key change at end of line

2025-03-06 Thread Carl Sorensen
On Thu, Mar 6, 2025 at 3:52 PM Paul Scott wrote: > Hi, > > I posted before about time signatures and/or key changes repeated at the > end of the previous line and was shown that it works correctly. > > I finally saw the problem that occasionally effects my normal code > st

Re: time signature and key change at end of line

2025-03-06 Thread Knute Snortum
On Thu, Mar 6, 2025 at 12:52 PM Paul Scott wrote: > Hi, > > I posted before about time signatures and/or key changes repeated at the > end of the previous line and was shown that it works correctly. > > I finally saw the problem that occasionally effects my normal code > st

time signature and key change at end of line

2025-03-06 Thread Paul Scott
Hi, I posted before about time signatures and/or key changes repeated at the end of the previous line and was shown that it works correctly. I finally saw the problem that occasionally effects my normal code structure. I always separate notes and time and dynamics to be able to use all or

Re: key and/or time signature at end of line

2025-01-28 Thread Valentin Petzel
unfold 32 { 8 \noBreak } \break \key ceses\major \compoundMeter #'((6 8) (7 16)) 8 } { \repeat unfold 16 { 8 \noBreak } \break \key ceses\major \compoundMeter #'((6 8) (7 16)) 8 } ``` Cheers, Valentin signature.asc Description: This is a digitally signed message part.

Re: key and/or time signature at end of line

2025-01-28 Thread William Rehwinkel via LilyPond user discussion
compress the music in the last measure of the line. I haven't been able to find one of my examples or create a MWE. Thank you, Paul On 1/25/25 11:33 AM, Hans Aikema wrote: On 25 Jan 2025, at 00:35, Paul Scott wrote: When a time signature or key change happens at the beginnin

Re: key and/or time signature at end of line

2025-01-27 Thread waterhorsemusic
Sent from my Galaxy Original message From: Tim's Bitstream via LilyPond user discussion Date: 1/28/25 12:03 AM (GMT-07:00) To: lily Pond Subject: Re: key and/or time signature at end of line So you want Lilypond to take that space equally from all the measures in that

Re: key and/or time signature at end of line

2025-01-27 Thread Tim's Bitstream via LilyPond user discussion
:35, Paul Scott wrote: When a time signature or key change happens at the beginning of a line it is repeated at the end of the previous line. This is good and normal. The space needed for this is take

Re: key and/or time signature at end of line

2025-01-27 Thread Paul Scott
gnature or key change happens at the beginning of a line it is repeated at the end of the previous line. This is good and normal. The space needed for this is taken from the last  measure on that previous line often making that last measure very cramped . Is there a way to change this? Of cou

Re: key and/or time signature at end of line

2025-01-27 Thread Hans Aikema
All the examples I sent on the list have the change exactly at the break, not one measure before the end. You can put as many measures before the \break as you want, the code addresses the changeover to another key and time-signature at the measure directly after the break. So if it's not

Re: key and/or time signature at end of line

2025-01-27 Thread Paul Scott
ikema wrote: On 25 Jan 2025, at 00:35, Paul Scott wrote: When a time signature or key change happens at the beginning of a line it is repeated at the end of the previous line. This is good and normal. The space needed for this is taken from the last measure on that previous line often m

Re: key and/or time signature at end of line

2025-01-25 Thread Hans Aikema
> On 25 Jan 2025, at 19:33, Hans Aikema wrote: > > > >> On 25 Jan 2025, at 00:35, Paul Scott wrote: >> >> When a time signature or key change happens at the beginning of a line it is >> repeated at the end of the previous line. This is good and normal.

Re: key and/or time signature at end of line

2025-01-25 Thread Hans Aikema
> On 25 Jan 2025, at 00:35, Paul Scott wrote: > > When a time signature or key change happens at the beginning of a line it is > repeated at the end of the previous line. This is good and normal. > > The space needed for this is taken from the last measure on that prev

Re: key and/or time signature at end of line

2025-01-25 Thread Carl Sorensen
On Fri, Jan 24, 2025 at 6:37 PM Paul Scott wrote: > When a time signature or key change happens at the beginning of a line > it is repeated at the end of the previous line. This is good and normal. > > The space needed for this is taken from the last measure on that > previous li

key and/or time signature at end of line

2025-01-24 Thread Paul Scott
When a time signature or key change happens at the beginning of a line it is repeated at the end of the previous line. This is good and normal. The space needed for this is taken from the last  measure on that previous line often making that last measure very cramped . Is there a way to

Re: Key signature and clef break-visibility exception for page breaks?

2024-12-03 Thread Eric Benson
th at the same place I could just combine them > with my explicit \pageBreak. > > On Tue, Dec 3, 2024 at 2:27 PM David Kastrup wrote: > >> Eric Benson writes: >> >> >> On Fri, Nov 29, 2024 at 1:13 PM Eric Benson >> wrote: >> >> >> >>

Re: Key signature and clef break-visibility exception for page breaks?

2024-12-03 Thread Eric Benson
29, 2024 at 1:13 PM Eric Benson > wrote: > >> > >>> I'm making lead sheets, where, unlike common practice, the key > signature > >>> and clef are not usually shown at the beginning of each line. LilyPond > >>> makes this easy to

Re: Key signature and clef break-visibility exception for page breaks?

2024-12-03 Thread David Kastrup
Eric Benson writes: >> On Fri, Nov 29, 2024 at 1:13 PM Eric Benson wrote: >> >>> I'm making lead sheets, where, unlike common practice, the key signature >>> and clef are not usually shown at the beginning of each line. LilyPond >>> makes

Re: Key signature and clef break-visibility exception for page breaks?

2024-12-03 Thread Eric Benson
Any thoughts? Anyone? On Fri, Nov 29, 2024 at 1:13 PM Eric Benson wrote: > I'm making lead sheets, where, unlike common practice, the key signature > and clef are not usually shown at the beginning of each line. LilyPond > makes this easy to control, with > > \overr

Key signature and clef break-visibility exception for page breaks?

2024-11-29 Thread Eric Benson
I'm making lead sheets, where, unlike common practice, the key signature and clef are not usually shown at the beginning of each line. LilyPond makes this easy to control, with \override Score.Clef.break-visibility = #all-invisible and \override Score.KeySignature.break-visibility =

Re: Key cancellation moving key signatures rightwards

2024-07-31 Thread Werner LEMBERG
> I have a situation with a lot of transposing instruments and some > key changes. I have disabled key cancellations, but of course they > are necessary if the new key has no sharps or flats. When naturals > are required, they push key signatures to the right, even though the >

Key cancellation moving key signatures rightwards

2024-07-31 Thread Vaughan McAlley
Hi, I have a situation with a lot of transposing instruments and some key changes. I have disabled key cancellations, but of course they are necessary if the new key has no sharps or flats. When naturals are required, they push key signatures to the right, even though the two will never appear

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-28 Thread Wols Lists
simple. Firstly, write the music in the key of the copy you have! In my case, if I have a Bb part I write the Bb notes. Secondly, all this goes into a music variable, wrapped in a transpose so that the variable is always in concert, eg voiceTrombone = \transpose c bf, { notes } This means

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread David Wright
On Thu 27 Jun 2024 at 16:49:22 (-0700), Kenneth Wolcott wrote: > All she wants is the very short Clarinet solo, not the entire piece, > transcribed for Piano, in the "correct key"; so I guess that would > mean writing it in F? > > Here's the engraving that I made bas

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Kenneth Wolcott
Thanks everyone! Ken On Thu, Jun 27, 2024 at 5:46 PM Vaughan McAlley wrote: > > On Fri, 28 June 2024, 09:50 Kenneth Wolcott, wrote: >> >> All she wants is the very short Clarinet solo, not the entire piece, >> transcribed for Piano, in the "correct key"; so

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Vaughan McAlley
On Fri, 28 June 2024, 09:50 Kenneth Wolcott, wrote: > All she wants is the very short Clarinet solo, not the entire piece, > transcribed for Piano, in the "correct key"; so I guess that would > mean writing it in F? > > Here's the engraving that I made bas

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Adam M. Griggs
I would do it in its original key of D major. I'm a stickler for original keys when possible. On Fri, 28 Jun 2024 at 08:50, Kenneth Wolcott wrote: > All she wants is the very short Clarinet solo, not the entire piece, > transcribed for Piano, in the "correct key"; so I gu

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Kenneth Wolcott
All she wants is the very short Clarinet solo, not the entire piece, transcribed for Piano, in the "correct key"; so I guess that would mean writing it in F? Here's the engraving that I made based on the 8notes transcription (attached). Thanks so much for your help! Ken On Thu,

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Knute Snortum
On Thu, Jun 27, 2024 at 4:29 PM Kenneth Wolcott wrote: > Hi Knute; > > Thank you! (I already knew about IMSLP!) But the 2nd movement is > not in A, I think think it is in D. Does that matter? > You're correct. The second movement is in D. I don't know if it matters -- do you want to change

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Kenneth Wolcott
> >> What is the "correct" key for the Clarinet solo from the Mozart >> Clarinet Concerto, 2nd movement, transcribed for Piano? > > > According to the IMSLP.org website, it's written in A: > > https://imslp.org/wiki/Clarinet_Concerto_in_A_major%2C_K.622_(Mozart%2C_Wolfgang_Amadeus) > > > > -- > Knute Snortum > >

Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Knute Snortum
On Thu, Jun 27, 2024 at 4:09 PM Kenneth Wolcott wrote: > Hi; > > What is the "correct" key for the Clarinet solo from the Mozart > Clarinet Concerto, 2nd movement, transcribed for Piano? > According to the IMSLP.org website, it's written

"correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.

2024-06-27 Thread Kenneth Wolcott
Hi; What is the "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, transcribed for Piano? My wife rreally likes the piano transcription I found on 8notes.com in C Major. She has found versions in D Major. She wonders what the "correct&quo

Re: Key signatures in MIDI output

2024-05-14 Thread Giles Boardman
Yes - that would be the way to go. However, the midi notes will play correctly anyway, and the Lilypond output is far better than the staff view in my sequencer. There is even a virtue to it as when I am playing along to the sequencer and I forget what key I am playing in, all my sharps and

Re: Key signatures in MIDI output

2024-05-14 Thread David Kastrup
Giles Boardman writes: > Hello, > > I have figured "it" out - Cakewalk expects Key Signature to be in > Track 0 of a Midi file and Lilypond puts it in whichever track has it > in, which is much more sensible. I realized this while compiling the > cry for help below,

Re: Key signatures in MIDI output

2024-05-14 Thread Giles Boardman
Hello, I have figured "it" out - Cakewalk expects Key Signature to be in Track 0 of a Midi file and Lilypond puts it in whichever track has it in, which is much more sensible. I realized this while compiling the cry for help below, so I've left my workings out in the message, bu

Re: Key signatures in MIDI output

2024-05-11 Thread David Wright
On Sat 11 May 2024 at 15:14:47 (+), Giles Boardman wrote: > You are, of course, right. Your evidence is clear. The position of the \key > command seems a strong candidate but I can't get it into the .MID even in the > simplest of snippet. > > As I mentioned I also ha

Re: Key signatures in MIDI output

2024-05-11 Thread David Kastrup
Giles Boardman writes: > You are, of course, right. Your evidence is clear. The position of the \key > command seems a strong candidate but I can't get it into the .MID even in the > simplest of snippet. > > As I mentioned I also have other behaviour I can't expla

Re: Key signatures in MIDI output

2024-05-11 Thread Giles Boardman
You are, of course, right. Your evidence is clear. The position of the \key command seems a strong candidate but I can't get it into the .MID even in the simplest of snippet. As I mentioned I also have other behaviour I can't explain so it could also be version related. I reins

Re: Key signatures in MIDI output

2024-05-11 Thread mskala
On Sat, 11 May 2024, Giles Boardman wrote: > I have now been more systematic in my approach and conclude that \key is not > reflected in MIDI output. I tried various positions for events and in each Well, it definitely is reflected in the output in my own tests. The example code I posted

Re: Key signatures in MIDI output

2024-05-11 Thread David Kastrup
msk...@ansuz.sooke.bc.ca writes: > On Sat, 11 May 2024, Giles Boardman wrote: > >> When I create MIDI output from Lilypond, if I have imported a MIDI file and >> then resaved it with changes made in LilyPond, the output is like that, too. > > Lilypond as such does not import MIDI files. I think y

Re: Key signatures in MIDI output

2024-05-11 Thread Giles Boardman
e" engraver! I have now been more systematic in my approach and conclude that \key is not reflected in MIDI output. I tried various positions for events and in each case I got Time Signature information in my MID file but not Key Signature when viewed in Staff View. But the conclusive eviden

Re: Key signatures in MIDI output

2024-05-11 Thread mskala
ftware other than Lilypond, and that is relevant to the issues you're experiencing. On the off chance that you might be using midi2ly, I tried round-tripping my example code through that, and got suggestive results. I take this code: \score { \new Voice { \key c \major c'4 d'

Re: Key signatures in MIDI output

2024-05-11 Thread Hans Åberg
> On 10 May 2024, at 22:21, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 May 2024, Hans Åberg wrote: > >>> signature. The MIDI file does not contain that information; it is up to >>> whatever software reads the MIDI file, to display it appropriately. >> >> So to go back to staff notation f

Re: Key signatures in MIDI output

2024-05-11 Thread David Kastrup
Giles Boardman writes: > However, when I create new files, I am getting output that is as if I > have chosen to write everything in C major, with all the flats and > sharps shown explicitly. Nevertheless, the screen and pdf output are > written in, for example G, with no sharps on the individual

Re: Key signatures in MIDI output

2024-05-11 Thread Giles Boardman
The issue is consistency and I'm perhaps not using the terms precisely enough to describe what I am seeing. I understand about MIDI notes and that they are neither sharpened not flattened, but each has their own value. In my sequencer (Cakewalk ProAudio 9), if my piece has a Key Sign

Re: Key signatures in MIDI output

2024-05-10 Thread David Kastrup
I notice that my MIDI output doesn't reflect the > key signatures (everything is in C with accidentals) while my > on-screen preview (even when I only have a midi block and no layout > block) and the .pdf have sharps and flats at the beginning of the > staff. > > The snippet abo

Re: Key signatures in MIDI output

2024-05-10 Thread mskala
On Fri, 10 May 2024, Hans Åberg wrote: > > signature. The MIDI file does not contain that information; it is up to > > whatever software reads the MIDI file, to display it appropriately. > > So to go back to staff notation from MIDI, one must know what enharmonic > equivalences that have been app

Re: Key signatures in MIDI output

2024-05-10 Thread Hans Åberg
> On 10 May 2024, at 21:50, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 May 2024, Hans Åberg wrote: > >> Programs like ABC work so that one writes the music without accidentals, >> and then apply a key signature to get them. It was my reading that the >> OP

Re: Key signatures in MIDI output

2024-05-10 Thread mskala
On Fri, 10 May 2024, Hans Åberg wrote: > Programs like ABC work so that one writes the music without accidentals, > and then apply a key signature to get them. It was my reading that the > OP asked for that. Okay. I didn't read it that way because the OP said he was getting cor

Re: Key signatures in MIDI output

2024-05-10 Thread Hans Åberg
> On 10 May 2024, at 20:18, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 May 2024, Hans Åberg wrote: > >> To change the MIDI output, you will need to change the notes, say by >> transposing or something else. > > MIDI files can include events ("

Re: Key signatures in MIDI output

2024-05-10 Thread mskala
On Fri, 10 May 2024, Hans Åberg wrote: > To change the MIDI output, you will need to change the notes, say by > transposing or something else. MIDI files can include events ("key-change meta messages") for key signatures, each specifying a root and whether it's major or

Re: Key signatures in MIDI output

2024-05-10 Thread Hans Åberg
t; So, I tried it and I notice that my MIDI output doesn't reflect the key > signatures (everything is in C with accidentals) while my on-screen preview > (even when I only have a midi block and no layout block) and the .pdf have > sharps and flats at the beginning of the staff. &g

Key signatures in MIDI output

2024-05-10 Thread Giles Boardman
Hello, I am reading that I can create MIDI output which is different from the printed output. For example, I can unfold repeats in the midi output but use alternative endings and double barlines in my score. Awesome! So, I tried it and I notice that my MIDI output doesn't reflect th

Re: Minimize flats or sharps in transposed key signature?

2024-04-08 Thread Jean Abou Samra
> I'm using \transpose pretty heavily, and I'm running into an issue I don't > quite know how to solve. I'm aware of the \naturalizeMusic hack described > in the LilyPond documentation. I'm looking for something similar, but for > key signatures. This was

Minimize flats or sharps in transposed key signature?

2024-04-08 Thread Eric Benson
I'm using \transpose pretty heavily, and I'm running into an issue I don't quite know how to solve. I'm aware of the \naturalizeMusic hack described in the LilyPond documentation. I'm looking for something similar, but for key signatures. When a \key specification gets tr

Re: remove key change at end of line

2024-03-25 Thread bobr...@centrum.is
That did the trick! Thank you, Xavier. > From: "Xavier Scheuer" > To: "bobroff" > Cc: "Lillypond Users Mailing List" > Sent: Monday, March 25, 2024 9:37:38 PM > Subject: Re: remove key change at end of line > On Mon, 25 Mar 2024 at 22:19, [ m

Re: remove key change at end of line

2024-03-25 Thread Xavier Scheuer
On Mon, 25 Mar 2024 at 22:19, bobr...@centrum.is wrote: > > I want to remove a key change from the ends of lines/systems. I am *not* referring to just key cancellation, which I do also want. I mean, at the end of a line the new key should not appear before the new line. I haven't wo

Re: remove key change at end of line

2024-03-25 Thread Aaron Hill
On 2024-03-25 2:18 pm, bobr...@centrum.is wrote: I want to remove a key change from the ends of lines/systems. I am *not* referring to just key cancellation, which I do also want. I mean, at the end of a line the new key should not appear before the new line. I haven't worked i

remove key change at end of line

2024-03-25 Thread bobr...@centrum.is
I want to remove a key change from the ends of lines/systems. I am *not* referring to just key cancellation, which I do also want. I mean, at the end of a line the new key should not appear before the new line. I haven't worked it out. -David

Re: Transpose from major to minor key

2024-01-12 Thread Lukas-Fabian Moser via LilyPond user discussion
e information, namely octave, "note name" and alteration. Wol's remarks (I think) alluded to the difference between LilyPond and, e.g., MuseScore, in that in LilyPond the meaning of naked note names does not change when selecting a new key signature: In MuseScore, if I switch to e

Re: Transpose from major to minor key

2024-01-11 Thread mskala
On Thu, 11 Jan 2024, Wol wrote: > You need to remember lilypond thinks in terms of pitch, not note names. Unlike > some (most?) other music software. So "\transpose g e" says "transpose EVERY > note up A TONE". I'm not sure it's quite right to say that Lilypond thinks in terms of pitch, not note

Re: Transpose from major to minor key

2024-01-11 Thread Wol
On 10/01/2024 21:26, Butter Cream wrote: Hi, I have a piece of music written in the key of G major and I want the pitches to transpose to e minor. How do I do this. When I use the command \transpose g e it changes to E major (all g notes are sharped) You need to remember lilypond thinks in

Re: Transpose from major to minor key

2024-01-10 Thread Aaron Hill via LilyPond user discussion
-transformations On Wed, Jan 10, 2024 at 5:20 PM Aaron Hill via LilyPond user discussion < lilypond-user@gnu.org> wrote: On 2024-01-10 1:26 pm, Butter Cream wrote: > Hi, I have a piece of music written in the key of G major and I want > the pitches to transpose to e minor. How do I do this

Re: Transpose from major to minor key

2024-01-10 Thread Aaron Hill via LilyPond user discussion
On 2024-01-10 1:26 pm, Butter Cream wrote: Hi, I have a piece of music written in the key of G major and I want the pitches to transpose to e minor. How do I do this. When I use the command \transpose g e it changes to E major (all g notes are sharped) I think you'll need t

Transpose from major to minor key

2024-01-10 Thread Butter Cream
Hi, I have a piece of music written in the key of G major and I want the pitches to transpose to e minor. How do I do this. When I use the command \transpose g e it changes to E major (all g notes are sharped) Steve

Re: clefs, time signatures, and key signatures

2023-12-22 Thread Werner LEMBERG
> 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

2023-12-22 Thread Michael Dietz
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

2023-12-18 Thread 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 between clefs and key >>> signatures. >>> >>> http

Re: Continuation slur and key signature with many sharps

2023-12-13 Thread Knute Snortum
On Wed, Dec 13, 2023 at 12:03 PM Jean Abou Samra wrote: > See issue #6639 . > Thanks. I searched for "continued" but not "broken." I'll know better next time (maybe). -- Knute Snortum

Re: Continuation slur and key signature with many sharps

2023-12-13 Thread Jean Abou Samra
See [issue #6639](https://gitlab.com/lilypond/lilypond/-/issues/6639). signature.asc Description: This is a digitally signed message part

Continuation slur and key signature with many sharps

2023-12-13 Thread Knute Snortum
Hi List, Here is something that pops up now and then when I'm engraving with LilyPond: if a key signature has a lot of sharps, like the key of e major, sometimes a continuation slur will be too close to the key signature. Here is a snippet: %%% \version "2.25.11" \paper { rag

Re: clefs, time signatures, and key signatures

2023-12-09 Thread Jakob Pedersen
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. With ae

Re: clefs, time signatures, and key signatures

2023-12-09 Thread Michael Gerdau
> 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 it

Re: clefs, time signatures, and key signatures

2023-12-08 Thread Werner LEMBERG
> 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, bu

Re: clefs, time signatures, and key signatures

2023-12-08 Thread Michael Gerdau
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

2023-12-08 Thread 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 between clefs and key >> signatures. >> >> https://gitlab.com/lilypond/lilyp

Re: clefs, time signatures, and key signatures

2023-12-05 Thread 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, [...] > > FWIW, I think the Petrucci clef distances are a big improvement and > make incipits closer to what they usually look like in sources. Yes, th

Re: clefs, time signatures, and key signatures

2023-12-05 Thread Vaughan McAlley
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

2023-12-05 Thread Leo Correia de Verdier
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 >>

Re: clefs, time signatures, and key signatures

2023-12-04 Thread 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 between clefs and key signatures. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 >

clefs, time signatures, and key signatures

2023-12-04 Thread Werner LEMBERG
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: Overwrite key signature with numbers

2023-10-13 Thread Robert Mengual
Alright, thanks for your time. I really appreciate it. Robert El vie, 13 oct 2023 18:41, Jean Abou Samra escribió: > From what you say, I believe you are worried about chords, am I right? > > > > It's more fundamental than that: there is only *one* StaffSymbol per > staff, for the duration of t

Re: Overwrite key signature with numbers

2023-10-13 Thread Jean Abou Samra
> From what you say, I believe you are worried about chords, am I right? It's more fundamental than that: there is only *one* StaffSymbol per staff, for the duration of the *entire* score. That StaffSymbol has a ledger-extra property that applies to *all* ledger lines on that staff anywhere in th

Re: Overwrite key signature with numbers

2023-10-13 Thread Robert Mengual
Thanks for your response Jean, So, the music notation system I am writing has assimetrical staves with only 4 lines, which means there is a blank space wider than the other two white spaces. For notes that fall into the wider blank space, I want a ledger line value of 2, but for the note that fall

Re: Overwrite key signature with numbers

2023-10-13 Thread Jean Abou Samra
Le vendredi 13 octobre 2023 à 15:36 +0200, Robert Mengual a écrit : > In the example below, I am receiving the following error:  Wrong type argument > in position 1 (expecting Stream_event): #f > > I think I am not receiving a grob in this case. You are, but this grob doesn't have an event cause

Re: Overwrite key signature with numbers

2023-10-13 Thread Robert Mengual
Thank you again Valentin, this is extremely helpful for me. In fact, I have been able to override other properties based on the solution you provided. I'm slowly making progress. However there is something I am stuck with, based on your response above: > If an overriden property expects a number

Re: Overwrite key signature with numbers

2023-10-03 Thread David Kastrup
Valentin Petzel writes: > Damn it, turns out the key engraver has an hardcoded path to always create > Key > Cancellations for keys with no alteration. > > So one would need to do > > \override KeyCancellation.stencil = ##f > > which is of course a bit wonky as comp

  1   2   3   4   5   6   7   8   9   10   >