Here is the current countdown report.
The next countdown will begin on December 16th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1578 New margins by default - Martín Rincón Botero
Le 14/12/2022 à 21:39, Kieren MacMillan a écrit :
You can *always* convert any use of \addInstrumentDefinition
/ \instrumentSwitch by turning
\addInstrumentDefinition "x" #`((prop1 . val1) (prop2 . ,val2) ...)
\instrumentSwitch "x"
into
x = {
\set Staff.prop1 = #'val1
\set Staff.prop2 =
Hi Jean,
> Yes. Don't you find
>
> ebClarinet = \displayMusic {
> \clef "treble"
> \transposition ees
> \set Staff.shortInstrumentName = "Es-Kl"
> \set Staff.midiInstrument = "clarinet"
> \set Staff.instrumentCueName = "Es-Kl"
> }
>
> easier to write and read than
>
>
Le 14/12/2022 à 21:00, Kieren MacMillan a écrit :
Hi Jean,
I totally agree that the \instrumentSwitch and \addInstrumentDefinition
functions are useless. Just use variables. (Contrary to what its
name suggests, \instrumentSwitch isn't directly related to
Instrument_switch_engraver.)
Please
Hi Jean,
> I totally agree that the \instrumentSwitch and \addInstrumentDefinition
> functions are useless. Just use variables. (Contrary to what its
> name suggests, \instrumentSwitch isn't directly related to
> Instrument_switch_engraver.)
Please take a look at
Hi Werner (et al.),
> What about defining functions that emit the instrument name and do the
> transposition? You would have a set of definitions for the
> parts (with transposition), and another set of definitions for the
> score (without transposition).
Just to recall and gather past
> My pit players sometimes have to play, in the same piece, five or
> more instruments of different transposition (e.g., flute, Alto Sax,
> Tenor Sax, Bb clarinet, Eb clarinet) — breaking every piece down
> into multiple chunks is not only inefficient, time-consuming, and
> error-prone from a
Hi Werner,
> Do you want this?
No… the first four measures should appear in concert pitch (because the flute
doesn’t transpose), but the second four measures need to be transposed
(including the key signature). My follow-up email, sent just before this, shows
the output I want.
My pit
Hi again,
> It's not clear to me what exactly the output should look like.
> Please show an image or some pseudo notation.
Sorry. Snippet below includes the kind of extra work I generally [believe I]
need to do.
Thanks,
Kieren.
%%% SNIPPET BEGINS
\version "2.23.14"
global = {
%% v1
>> Please show (images of) typical examples of what you want to see.
>> I can imagine that such a feature would be worth adding.
Do you want this?
```
\version "2.23.14"
global = {
%% v1
\key c \major
s1*4
\bar "||"
%% v2
\key d \major
s1*4
\bar "|."
}
%% NOTE:
> %% PART (TRANSPOSED)
> %% What’s the least amount of work required
> %% to make this transposed part, with correct key signature?
It's not clear to me what exactly the output should look like. Please
show an image or some pseudo notation.
Werner
Hi Werner,
> Please show (images of) typical examples of what you want to see.
> I can imagine that such a feature would be worth adding.
Here’s the fundamental problem:
%%% SNIPPET BEGINS
\version "2.23.14"
global = {
%% v1
\key c \major
s1*4
\bar "||"
%% v2
\key d
> Will that handle the automatic switching of key signatures, etc.?
No.
> As someone who writes multi-instrumentalist parts [for musical pit
> orchestras], this has been a low-grade PITA for almost 20 years — it
> would be really great if we could use this “deprecation” moment[um]
> to figure
Hi all,
> I totally agree that the \instrumentSwitch and \addInstrumentDefinition
> functions are useless. Just use variables.
Will that handle the automatic switching of key signatures, etc.? As someone
who writes multi-instrumentalist parts [for musical pit orchestras], this has
been a
Le 13/12/2022 à 10:55, Xavier Scheuer a écrit :
Hello,
While replying to a query on the French-speaking list I realized that in
the latest versions of LilyPond the instrumentCueName property was
considered deprecated (as well as the engraver
"Instrument_switch_engraver", the grob
On Tue, Dec 13, 2022 at 10:44:26PM +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> I also realized that I forgot to send a draft release announcement
> text, which I originally wanted to share during the weekend. I went
> with the standard text, copying from the previous
> I also realized that I forgot to send a draft release announcement
> text, which I originally wanted to share during the weekend. I went
> with the standard text, copying from the previous stable release:
> [...]
LGTM, thanks!
Werner
Just noting here that I will reply on the -devel list only.
OpenPGP_signature
Description: OpenPGP digital signature
Le 14/12/2022 à 08:13, Jonas Hahnfeld a écrit :
Yes, good idea. I will list them on GitLab and in the announcement
email, I think the news item on lilypond.org should stay short.
Agreed.
Linux and Windows binaries seem to work fine in a smoke test
on my machine, tested on two scores,
19 matches
Mail list logo
