Re: Windows users - Call for testing
I've compiled seven choral scores of varying complexity with no problems. My most complex instrumental scores will have to wait until I have time to update them manually - convert-ly can't cope with them. Paul From: Michael Käppler To: Lilypond-User Mailing List Sent: 27/06/2024 11:28 Subject: Windows users - Call for testing Hi all, I recently tried to fix some of the remaining problems that we have with Lilypond (or, more precisely, Guile) running under Windows, e.g. https://lists.gnu.org/archive/html/bug-lilypond/2024-04/msg7.html I made a experimental release based on an upgrade to Guile 3.0.10 and the bugfixes. I would really love to see it tested by Windows users before we incorporate the changes into our next development release. You can download the release here: https://drive.google.com/file/d/1yjXZ_2vUQeNi-3djbXQmyhUB_sInpxr3/view?usp=sharing Thanks, Michael
Re: Windows users - Call for testing
Le vendredi 28 juin 2024 à 22:22 +, bobr...@centrum.is a écrit : > Michael, > > I'm sorry, but I don't really understand what your code does, nor do > I know what to do with it in a real score. If you want to throw a > score at me using it I'll be happy to run LilyPond 2.25.17 (Guile > 3.0) and let you know the results. I think he was just asking you to try any real score that you have. Not somehow inserting the test code into it. signature.asc Description: This is a digitally signed message part
Re: Windows users - Call for testing
Michael, I'm sorry, but I don't really understand what your code does, nor do I know what to do with it in a real score. If you want to throw a score at me using it I'll be happy to run LilyPond 2.25.17 (Guile 3.0) and let you know the results. -David > From: "Michael Käppler" > To: "bobroff" , "Jean Abou Samra" > Cc: "Lillypond Users Mailing List" > Sent: Thursday, June 27, 2024 8:31:12 PM > Subject: Re: Windows users - Call for testing > Thanks, but could you give it a try on a real score? That would be very > helpful! > Michael > Am 27.06.2024 um 15:30 schrieb [ mailto:bobr...@centrum.is | > bobr...@centrum.is > ] : >> Tried again with the code 'massaged' by Jean. Here's the output: >> $ ./bin/lilypond.exe test.ly >> GNU LilyPond 2.25.17 (running Guile 3.0) >> Processing `test.ly' >> Parsing...1/2 >> -7/2 >> #f >> Success: compilation successfully completed >>> From: "Jean Abou Samra" [ mailto:j...@abou-samra.fr | ] >>> To: "Michael Käppler" [ mailto:xmichae...@web.de | ] , >>> "bobroff" [ mailto:bobr...@centrum.is | ] >>> Cc: "Lillypond Users Mailing List" [ mailto:lilypond-user@gnu.org | >>> ] >>> Sent: Thursday, June 27, 2024 1:24:14 PM >>> Subject: Re: Windows users - Call for testing >>> > Hmm, but that looks like syntax errors in your test.ly file that are >>> > unrelated >>> > to the Guile patches. >>> As can be seen in the list archives, Klaus' mail client inserted spurious >>> newlines >>> that turn parts of comments into non-comments. The correct code should be >>> #(define step 1) >>> #(define cnt -3) >>> #(define limit (+ cnt 0.3)) >>> #(display (/ step 2)) >>> #(newline) >>> #(display (- cnt (/ step 2))) >>> #(newline) >>> #(display (> (- cnt (/ step 2)) limit))
Re: "correct" key for the Clarinet solo from the Mozart Clarinet Concerto, 2nd movement, tanscribed for Piano.
On 28/06/2024 00:08, Kenneth Wolcott wrote:
Should I try to engrave a D Major transcription, transpose what I
aleady have to D major, or something else?
As someone who plays an instrument that is sometimes written in concert,
sometimes written in Bb (the trombone), my advice here would be 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 all my music is in concert internal to lilypond, but it also
tells me what part I input it from.
I can then output it in whatever key I like, but again I always wrap it
in a transpose. Let's say I want to output it as a bass clef (concert)
part, eg
\score { \transpose c c { \voiceTrombone }}
This gives me two things - firstly I can always EASILY check my input
against the version I copied it from. Whether comparing my voice
variable against the original part, or printing out a new part and
comparing it against the original.
And secondly, I can then easily output a part transposed to any pitch,
without having to worry about what pitch lilypond is using internally -
I know EVERYTHING inside lilypond is flying around as concert.
Cheers,
Wol
