Aaron Hill writes:
> On 2023-03-11 3:55 am, David Kastrup wrote:
>> Hi,
>> just a heads-up for a talk about LilyPond happening at 5pm MET
>> (UTC+1).
>> It's being streamed (and there will be a recording available a few
>> weeks
>> later).
>> Essentially I will talk a bit about what LilyPond is a
I found a tool in the procmail suite to split mbox archives into
individual messages. I upped the available swap space on the server to
13GB (thanks to David Kstrup for suggesting this idea). There are 156457
items in the archive up to last month or so. That number is from the
first message eve
You can get various stats from Discourse. There are over 6.5K users who
have posted over the years and consequently have been created. An
amazing community.
Andrew
Hi David,
one important thing this talk has taught us is that you are not too fluent with
Frescobaldi :). Thanks for the great talk!
Valentin
Am Samstag, 11. März 2023, 12:55:27 CET schrieb David Kastrup:
> Hi,
>
> just a heads-up for a talk about LilyPond happening at 5pm MET (UTC+1).
>
> It
Great news! Talking about pricing: How much does your current virtual server
cost? Maybe I can chime in something.
The flaws I personally see with the mailing list is that it is a bit hard to
organize. I think the mailing list is great as a discussion structure, but not
as a database for soluti
Valentin Petzel writes:
> Hi David,
>
> one important thing this talk has taught us is that you are not too
> fluent with Frescobaldi :).
You bet. But I still considered it a saner choice to showcase compared
to Emacs (which is what I use).
Maybe someone™ should just use all of the libraries F
> By chance, I read the announcing email at 16:59, just in time to
> start the stream and to follow David's lecture on Lilypond and
> Frescobaldi. It was a refreshing experience to watch and listen to
> one of those friendly people involved in the development, [...]
Yeah, David did a good job!
That’s what I’ve got from this too :). Personally I think the greatest thing
with Frescobaldi is the great integration between editor and viewer, with fast
forward and reverse search and even marking selected source code in the
viewer. This makes syncing between parts much easier. I do not care
Valentin Petzel writes:
> Regarding midi support: Personally I’d do this externally. Create an
> external program that records midi, either quantised real time or
> stepwise, and returns the output as Lilypond code. This then has the
> advantage that it is easier to maintain and can easily be use
Hello Ralph,
while Pierre’s solution works with some adaptation I think your approach is
wrong.
Tempo is something that is created at the Score level, while TextScripts are
created at the Staff level. This means that it should be expected for
TextScripts to be closer to the Staff. Rather use t
Yes, but an external program could do that too, without being tied to a single
specific editor.
Am Sonntag, 12. März 2023, 13:24:01 CET schrieb David Kastrup:
> Valentin Petzel writes:
> > Regarding midi support: Personally I’d do this externally. Create an
> > external program that records midi
Valentin Petzel writes:
>> Am Sonntag, 12. März 2023, 13:24:01 CET schrieb:
>>> Valentin Petzel writes:
>>> > Regarding midi support: Personally I’d do this externally. Create an
>>> > external program that records midi, either quantised real time or
>>> > stepwise, and returns the output as Lil
On Sun, Mar 12, 2023 at 5:36 AM Valentin Petzel wrote:
> Hello Ralph,
>
> while Pierre’s solution works with some adaptation I think your approach
> is
> wrong.
>
> Tempo is something that is created at the Score level, while TextScripts
> are
> created at the Staff level. This means that it shou
Jean Abou Samra,
Thank you.
Mark
-Original Message-
From: Jean Abou Samra [mailto:j...@abou-samra.fr]
Sent: Saturday, March 11, 2023 10:47 PM,
To: Mark Stephen Mrotek
Cc: Werner LEMBERG ; lilypond-user@gnu.org
Subject: Re: Installing 2.24.1
> Le 12 mars 2023 à 06:39, Mark Stephen M
On Sat, 2023-03-11 at 19:03 +0100, Jean Abou Samra wrote:
> Le vendredi 10 mars 2023 à 14:35 +, Richard Shann a écrit :
> > sorry, yes, I just assumed it had been shortened not lengthened.
> It was renamed because LilyPond gained other “mark formatters”, such
> as segnoMarkFormatter and codaMar
Hello,
Each movement of a piano piece has a separate file. In each movement the
various voices are identified by a variable, e.g., ArightOne, BleftTwo. Each
file compiles perfectly individually.
When the file is copied into
\bookpart {
\header {
}
Copied here
}
It does not compile cor
Le dimanche 12 mars 2023 à 11:16 -0700, Mark Stephen Mrotek a écrit :
> Hello,
>
> Each movement of a piano piece has a separate file. In each movement the
> various voices are identified by a variable, e.g., ArightOne, BleftTwo. Each
> file compiles perfectly individually.
> When the fil
Jean Abou Samra,
Thank you.
Yes variables must (and are) placed before the \score in each individual
movement. That is why each complies perfectly when done individually.
The error appears when the code for the movement (that compiles) is copied and
pasted into the \bookpart.
Your kind
> On 12 Mar 2023, at 20:38, Mark Stephen Mrotek wrote:
>
> Jean Abou Samra,
>
> Thank you.
> Yes variables must (and are) placed before the \score in each individual
> movement. That is why each complies perfectly when done individually.
> The error appears when the code for the movement (tha
If I’m thinking correctly what Mark attempts to do is to have multiple files
containing scores and then to
\bookpart {
\include ...
}
to combine these scores. The problem here is quite simple: The notation
name = value
is something that is evalutated by the parser and will generally evaluate
A slightly nicer syntax to workaround this limitation is to use the
function:
parserDefine =
#(define-void-function (name val)(symbol? scheme?)
(ly:parser-define! name val))
Then instead of var = { ... } you can write \parserDefine var { ... }.
I believe this was posted on the list a few yea
Le lundi 13 mars 2023 à 00:24 +0100, Valentin Petzel a écrit :
> (by the way this also allows us to define bindings the parser does not handle
>
> well such as e.g. \c: c = ... will not be allowed, as c is a note name, but
> #(define c ...) works).
You can write
```
"c" = ...
```
though.
Le dimanche 12 mars 2023 à 16:34 -0700, Saul Tobin a écrit :
> A slightly nicer syntax to workaround this limitation is to use the function:
>
> parserDefine =
> #(define-void-function (name val)(symbol? scheme?)
> (ly:parser-define! name val))
>
> Then instead of var = { ... } you can
Hans,
Thank you for your advice.
That format is not what is given in the manual.
\bookpart {
\header { … }
\score { … }
}.
An what is the advantage of being able to code separate files (for individual
movements) if the variables for each must be copied into the book part?
If i
For what it's worth my use case was that I use the same variable names for
each instrument in a separate file for each movement of a piece. I
therefore need to \include the music for each movement immediately before
the \score for that movement, in order to redefine the variables with the
music for
Le dimanche 12 mars 2023 à 16:54 -0700, Mark Stephen Mrotek a écrit :
> Hans,
>
> Thank you for your advice.
> That format is not what is given in the manual.
>
> \bookpart {
> \header { … }
> \score { … }
> }.
I find this fascinating, because the user who asked this ques
Le dimanche 12 mars 2023 à 17:06 -0700, Saul Tobin a écrit :
> For what it's worth my use case was that I use the same variable names for
> each instrument in a separate file for each movement of a piece. I therefore
> need to \include the music for each movement immediately before the \score
>
Valentin,
Thank you for your input.
Note that my knowledge of programming and programming language does not exceed
what I learned In FORTRAN as the foreign language requirement of my Master's
degree.
My question then is, what file structure is used by others to combine multiple
movements into o
That really only addresses the full score, not the parts, since in the
parts multiple movements share the same bookpart.
On Sun, Mar 12, 2023 at 5:19 PM Jean Abou Samra wrote:
> Le dimanche 12 mars 2023 à 17:06 -0700, Saul Tobin a écrit :
>
> For what it's worth my use case was that I use the sa
Jean,
Shall follow you explicit structure printed at the bottom.
Please consider including it in the Learning Manual.
Thank you is inadequate for your efforts.
Mark
From: Jean Abou Samra [mailto:j...@abou-samra.fr]
Sent: Sunday, March 12, 2023 5:10 PM
To: Mark Stephen Mrotek ; 'H
On 3/11/2023 10:37 PM, Mark Stephen Mrotek wrote:
My experience installing Lilypond is with the Windows Installer.
I know what a Zip file is yet I have never used one to install a
program. Is there some more detailed instructions than what is
provided in The Graphical Setup for Windows?
Quoti
Jeff,
Thank you for the detailed instructions suited for a non-programmer!
Shall work on it in the morning.
Mark
From: Jeff Olson [mailto:jjoca...@gmail.com]
Sent: Sunday, March 12, 2023 7:57 PM
To: Mark Stephen Mrotek
Cc: Jean Abou Samra ; lilypond-user@gnu.org
Subject: Re: RE: Inst
On 3/12/23 12:25 AM, Aaron Hill wrote:
On 2023-03-11 11:04 pm, Paul Scott wrote:
On 3/11/23 11:40 PM, Aaron Hill wrote:
On 2023-03-11 10:34 pm, Paul Scott wrote:
This still gives the warning and I don't want any repeats there.
As the warning is indicating, you are trying to start a new vol
> use:
>
> ```
> % movement1.ly
> variable = \relative c'' { ... }
> bookpartI = \bookpart { \score { \variable } }
>
> % movement2.ly
> variableII = \relative c'' { ... }
> bookpartII = \bookpart { \score { \variableII } }
>
> % main.ly
> \include "movement1.ly"
> \include "movement2.ly"
> \bo
34 matches
Mail list logo
