On Wed, 14 Dec 2022 at 14:48, Jean Abou Samra wrote:
>
> Werner's commit merely documented a deprecation that had been
> going on for much longer. The rationale is given here:
>
> https://gitlab.com/lilypond/lilypond/-/issues/4078#note_339812107
>
> and I found this thread:
>
> https://lists.gnu.o
Hi Jean,
> Yeah, we're discussing two things that have been deprecated
> together but are separate. One is \addInstrumentDefinition
> + \instrumentSwitch, which sounds like it helps with switching
> instruments but is actually both completely generic and
> close to useless, the other is instrument
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
>
> \addInstrumentDe
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 t
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
https://github.com/openlilylib/s
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 discussio
> 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 codi
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 players
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
\k
>> 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 \majo
> 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 ou
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 low-gr
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 "InstrumentSwit
Just noting here that I will reply on the -devel list only.
OpenPGP_signature
Description: OpenPGP digital signature
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 "InstrumentSwitch" and the music
functions instrumentSwitch and a
18 matches
Mail list logo
