run error Lilypond-book on Windows 10

2021-08-06 Thread Archer Endrich
s a conundrum.  It has always worked before, but I cannot find a 'pdflatex' file in the \user\bin of version 2.18.2 or 2.22.1.  It does not appear to be complaining about anything in my lytex file -- which I had previously compiled successfully with 2.18.2. Any help will be greatly appreciated. Archer Endrich archer...@gmail.com

Re: run error Lilypond-book on Windows 10

2021-08-06 Thread Archer Endrich
Thank you Knute and David!  I have downloaded and installed MiKTeX and rerun my batch file (without the .py added to lilypond-book). It appears to have called lilypond-book successfully and also pdflatex.  However, it still reports an error in lilypond-book.ly which is preventing compilation.

Re: run error Lilypond-book on Windows 10

2021-08-06 Thread Archer Endrich
;ve replied properly to yourself and to the user-group. On 06/08/2021 16:55, Aaron Hill wrote: On 2021-08-06 8:46 am, Archer Endrich wrote: [ . . . ] C:\P3L\lpbk>lilypond-book --output=out --pdf ALMdurasnumber.lytex   File "C:\Lilypond2221\usr\bin\lilypond-book.py", line 376     exc

Re: run error Lilypond-book on Windows 10

2021-08-06 Thread Archer Endrich
the .py extension to allow Windows to choose the application for that extenstion, and it may be another python somewhere in your system. HTH, Carl On 8/6/21, 10:22 AM, "lilypond-user on behalf of Archer Endrich" wrote: Hello Aaron, Thank you for your reply.

Re: run error Lilypond-book on Windows 10

2021-08-06 Thread Archer Endrich
On 06/08/2021 18:32, Knute Snortum wrote: On Fri, Aug 6, 2021 at 9:35 AM Carl Sorensen wrote: You might check the following: Is there a python.exe that is somewhere in the path ahead of Lilypond's python? This can be checked using the Windows "where" command: C:\> where python -- Knute Snor

Re: run error Lilypond-book on Windows 10

2021-08-06 Thread Archer Endrich
Dear David, Carl and Knute, Thank you for all your replies and information.  I'll work on the file-association suggestion tomorrow and let you know if the problem is solved. Thanks again, Archer

success with lilypond-book

2021-08-07 Thread Archer Endrich
To David, Knute and Carl, I am happy to report success with running lilypond-book on Windows 10.  For users' info, these are the steps I took, as guided by David, Knute and Carl.  It is hard to tell at this point whether it would have worked if one or the other of these steps had been omitted.

Re: is this a slashed grace?

2022-09-16 Thread Archer Endrich
Hello Ken, I have a workaround for this problem, namely to create an oblique line and move it onto the beam.  I did not use \acciaccatura but rather smaller notes because I wanted to control the spacing of the notes. See the attached slashedacciaccworkaround.pdf and .ly. I hope this may be o

Re: Separate a tuplet from the rest under a common beam

2022-12-14 Thread Archer Endrich
Hello, I often have varied groupings under one beam and have used the solution given by Michael Werner.  However, I have also created the following to simplify entering the commands and the look of the score file: bcLnone = \set stemLeftBeamCount = #0 bcRone = \set stemRightBeamCount = #1 bcL

Cues and Rest Collision Warning

2023-03-14 Thread Archer Endrich
Dear Lilypond User Group, First of all, thanks for the great discussion about variables and Bookpart.  I had very recently come across that problem, though in simpler form:  just putting a variable definition directly into a file that used \book (for assembling several short scores). Placing t

Re: Cues and Rest Collision Warning

2023-03-14 Thread Archer Endrich
~ |   } } Thanks again, Archer On 14/03/2023 12:13, Xavier Scheuer wrote: On Tue, 14 Mar 2023 at 12:55, Archer Endrich wrote: > > The reason I used c'1\rest was so that the rest would be placed on the > bottom line of the Staff.  I would really like a centered rest (R1) but >

Re: Cues and Rest Collision Warning

2023-03-14 Thread Archer Endrich
Thank you, Jean, for these very detailed explanations about how the voices are to be used -- and the alternate way to achieve the same result.  I hugely appreciate your input. Archer On 14/03/2023 19:09, Jean Abou Samra wrote: Le mardi 14 mars 2023 à 14:36 +, Archer Endrich a écrit

Re: String pressure notation

2024-04-16 Thread Archer Endrich
Hello Richard, Your bow-pressure graphic looks great, and I hope your question about horizontal proportions can be answered soon. Another feature of your illustration is relevant to my wish list:  the downward-pointing brackets with 9" in the middle.  I've been trying to find a way to do thi

Re: String pressure notation

2024-04-16 Thread Archer Endrich
Thank you, Aaron.  I'm absolutely delighted to know how to do this now as it occurs in several of my earlier scores that I'm re-engraving with Lilypond. Archer On 16/04/2024 12:03, Aaron Hill wrote: On 2024-04-16 3:59 am, Aaron Hill wrote: What you are looking for, however, can be done with

Re: Feathered Beam Timing

2024-05-11 Thread Archer Endrich
Hello, I have frequently encountered the situation where I want to have feathered durations within a specified duration -- e.g., a crotchet, or a minim, or a breve.  This is the code I've come up with: \once \override Beam.grow-direction = #RIGHT   \featherDurations #(ly:make-moment 1/2)   \t

layout problem

2024-05-12 Thread Archer Endrich
Hello, I've been given a short item to realise in Lilypond and it includes a layout problem that I haven't been able to solve. Basically, it is a piano piece in which, after a bit, a part for chimes is added:  i.e., another staff above the piano's treble part a few bars in as in my MWE.  I h

Re: layout problem

2024-05-12 Thread Archer Endrich
wrote: On 12/05/2024 12:41, Archer Endrich wrote: Hello, I've been given a short item to realise in Lilypond and it includes a layout problem that I haven't been able to solve. Basically, it is a piano piece in which, after a bit, a part for chimes is added:  i.e., another staff abov

Re: layout problem - new issue

2024-05-14 Thread Archer Endrich
Thank you, Jean.  Of course!  The broader issue for me is that I hadn't grasped that it was actually a << {...} \\ {...} >> construction in the newer, simpler format. I'm so grateful for your help.  I was going around in circles, knowing that the solution had to be something straightforward.