Good morning, Jean,
thank you very much for your detailed explanation! This helps me to
understands things a bit better.
Jean Abou Samra schrieb am 21.01.22 um 19:30:
Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
- There is a point in processing when one has to convert every
Hi Lukas,
Lukas-Fabian Moser schrieb am 21.01.22 um 17:15:
Also note
[...]
The standard use case for make-XXX-markup is explained in:
http://lilypond.org/doc/v2.23/Documentation/extending/markup-construction-in-scheme.html
under "Known issues and warnings".
I had read that, and it seemed
Hello Kieren, that seems to be correct.
One could also try something like this.
Cheers,
Valentin
Am Samstag, 22. Jänner 2022, 03:22:42 CET schrieb Kenneth Wolcott:
> Hi;
>
> I have a piece of music from which I am engraving that confuses me.
>
> At bar #13 there is the Segno sign.
>
>
[Berhard]
Actually, the lilypond.org web server was very insistent that even
when I googled English, I should read German whenever it was
available; therefore I assumed the versions were on par. I will think
about configuring one browser / profile without language preferences
so that I can
Kieren MacMillan writes:
> p.s. Motivating use case:
>
> I'm cranking out scores for my newest musical
> (https://www.ccpacanada.com/the-quest/). Rehearsals started on
> Tuesday, and changes always come fast and furious during the
> workshopping of a brand new piece. Every time I send the
Hi David,
> What version control system are you using for your score? It will
> probably easiest to look at the source code diffs and do a manual
> summary from those.
The problem is that during various stages of composition / arranging /
engraving / coding:
1. there can be huge differences
Le 23/01/2022 à 00:14, Jean Abou Samra a écrit :
Le 22/01/2022 à 22:51, Kieren MacMillan a écrit :
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a
"diff file" describing the musical differences *as would be perceived
by a human reading the score*. For
Hi Kieren,
While it is theoretically possible to compare two streams of music events it
would also require lots of logic to properly do what we want.
One way to achieve what you want could be storing the whole history in the
source.
I have recently sent out this showcase example of how we can
Hi Jean,
> Minimal, but perhaps already usable?
Astounding! I think this is totally useable for my purposes!
Once this workshop is over, I'm going to dive in and see if I can turn this
into an 'update reporting framework'.
Thank you so much.
Kieren
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a "diff
file" describing the musical differences *as would be perceived by a human
reading the score*. For example, given
Score #1 = \score { \new Staff << { c'1 c' } >> }
Score # 2 = \score { \new Staff \new
Le 22/01/2022 à 14:27, Valentin Petzel a écrit :
Hello Kieren,
I think you meant someone else :-)
that seems to be correct.
One could also try something like this.
It deserves to be mentioned that \repeat segno has
been implemented by Dan Eble in the development
branch. It will be
Just thinking out loud -- could a diff in the midi events be helpful? The midi
events represent sounds, which is the most important output the musicians need
to know about, and they are virtually unaffected by tweaks, etc.
Ccarl
From: lilypond-user
Fugue! That comes from being shortsighted and not checking names twice. I
apologize!
As I see it putting something like this into the official release would be a
bit problematic, as the whole thing is might cause very weird behaviour.
There are probably cleaner ways to achieve this result.
p.s. Motivating use case:
I'm cranking out scores for my newest musical
(https://www.ccpacanada.com/the-quest/). Rehearsals started on Tuesday, and
changes always come fast and furious during the workshopping of a brand new
piece. Every time I send the Musical Director an updated score, I
Hi Valentin;
Although there might be better ways to achieve this I appreciate
your code snippet.
Ken
On Sat, Jan 22, 2022 at 1:28 PM Valentin Petzel wrote:
>
> Fugue! That comes from being shortsighted and not checking names twice. I
> apologize!
>
> As I see it putting something like this
Hi Valentin;
I feel too honored to be mistaken for Kieren :-)
Thank you so much for the "Jump" code; it is very interesting.
The details are ***WAY*** beyond my understanding, but it looks very
useful and usable.
I will experiment with it.
Is there a possibility that the next
Le 22/01/2022 à 22:51, Kieren MacMillan a écrit :
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a "diff
file" describing the musical differences *as would be perceived by a human reading
the score*. For example, given
Score #1 = \score { \new Staff << { c'1
17 matches
Mail list logo
