and flats will
be right there for me to see. I have actually found myself wishing for this on
occasion, so all is well.
From: David Kastrup
Sent: 14 May 2024 19:33
To: Giles Boardman
Cc: msk...@ansuz.sooke.bc.ca ; lilypond-user@gnu.org
Subject: Re: Key signatures
Giles Boardman writes:
> Hello,
>
> I have figured "it" out - Cakewalk expects Key Signature to be in
> Track 0 of a Midi file and Lilypond puts it in whichever track has it
> in, which is much more sensible. I realized this while compiling the
> cry for help below, so I've left my workings out
how data is brought into Lilypond won't change that.
From: David Kastrup
Sent: 11 May 2024 20:22
To: Giles Boardman
Cc: msk...@ansuz.sooke.bc.ca ; lilypond-user@gnu.org
Subject: Re: Key signatures in MIDI output
Giles Boardman writes:
> You are, of course,
On Sat 11 May 2024 at 15:14:47 (+), Giles Boardman wrote:
> You are, of course, right. Your evidence is clear. The position of the \key
> command seems a strong candidate but I can't get it into the .MID even in the
> simplest of snippet.
>
> As I mentioned I also have other behaviour I
Giles Boardman writes:
> You are, of course, right. Your evidence is clear. The position of the \key
> command seems a strong candidate but I can't get it into the .MID even in the
> simplest of snippet.
>
> As I mentioned I also have other behaviour I can't explain so it could also
> be
does the default rehearsal mark, which appears in the layout. I've also
failed in other attempts to get the same effect by other means (not necessarily
for MIDI) like instrumentName =
Thanks again for your support.
From: msk...@ansuz.sooke.bc.ca
Sent: 11 May 2024 15:
On Sat, 11 May 2024, Giles Boardman wrote:
> I have now been more systematic in my approach and conclude that \key is not
> reflected in MIDI output. I tried various positions for events and in each
Well, it definitely is reflected in the output in my own tests. The
example code I posted, when
msk...@ansuz.sooke.bc.ca writes:
> On Sat, 11 May 2024, Giles Boardman wrote:
>
>> When I create MIDI output from Lilypond, if I have imported a MIDI file and
>> then resaved it with changes made in LilyPond, the output is like that, too.
>
> Lilypond as such does not import MIDI files. I think
ardman
Cc: Hans Åberg ; lilypond-user@gnu.org
Subject: Re: Key signatures in MIDI output
On Sat, 11 May 2024, Giles Boardman wrote:
> When I create MIDI output from Lilypond, if I have imported a MIDI file and
> then resaved it with changes made in LilyPond, the output is like that
On Sat, 11 May 2024, Giles Boardman wrote:
> When I create MIDI output from Lilypond, if I have imported a MIDI file and
> then resaved it with changes made in LilyPond, the output is like that, too.
Lilypond as such does not import MIDI files. I think you must be using
some piece of software
> On 10 May 2024, at 22:21, msk...@ansuz.sooke.bc.ca wrote:
>
> On Fri, 10 May 2024, Hans Åberg wrote:
>
>>> signature. The MIDI file does not contain that information; it is up to
>>> whatever software reads the MIDI file, to display it appropriately.
>>
>> So to go back to staff notation
Giles Boardman writes:
> However, when I create new files, I am getting output that is as if I
> have chosen to write everything in C major, with all the flats and
> sharps shown explicitly. Nevertheless, the screen and pdf output are
> written in, for example G, with no sharps on the individual
the forum.
Thanks for your interest.
From: msk...@ansuz.sooke.bc.ca
Sent: 10 May 2024 21:21
To: Hans Åberg
Cc: Giles Boardman ; lilypond-user@gnu.org
Subject: Re: Key signatures in MIDI output
On Fri, 10 May 2024, Hans Åberg wrote:
> > signature. Th
Giles Boardman writes:
> Hello,
>
> I am reading that I can create MIDI output which is different from the
> printed output. For example, I can unfold repeats in the midi output
> but use alternative endings and double barlines in my score. Awesome!
>
> So, I tried it and I notice that my MIDI
On Fri, 10 May 2024, Hans Åberg wrote:
> > signature. The MIDI file does not contain that information; it is up to
> > whatever software reads the MIDI file, to display it appropriately.
>
> So to go back to staff notation from MIDI, one must know what enharmonic
> equivalences that have been
> On 10 May 2024, at 21:50, msk...@ansuz.sooke.bc.ca wrote:
>
> On Fri, 10 May 2024, Hans Åberg wrote:
>
>> Programs like ABC work so that one writes the music without accidentals,
>> and then apply a key signature to get them. It was my reading that the
>> OP asked for that.
>
> Okay. I
On Fri, 10 May 2024, Hans Åberg wrote:
> Programs like ABC work so that one writes the music without accidentals,
> and then apply a key signature to get them. It was my reading that the
> OP asked for that.
Okay. I didn't read it that way because the OP said he was getting
correct output in
> On 10 May 2024, at 20:18, msk...@ansuz.sooke.bc.ca wrote:
>
> On Fri, 10 May 2024, Hans Åberg wrote:
>
>> To change the MIDI output, you will need to change the notes, say by
>> transposing or something else.
>
> MIDI files can include events ("key-change meta messages") for key
>
On Fri, 10 May 2024, Hans Åberg wrote:
> To change the MIDI output, you will need to change the notes, say by
> transposing or something else.
MIDI files can include events ("key-change meta messages") for key
signatures, each specifying a root and whether it's major or minor (which
actually
> On 10 May 2024, at 16:26, Giles Boardman wrote:
>
> I am reading that I can create MIDI output which is different from the
> printed output. For example, I can unfold repeats in the midi output but use
> alternative endings and double barlines in my score. Awesome!
>
> So, I tried it and
Hello,
I am reading that I can create MIDI output which is different from the printed
output. For example, I can unfold repeats in the midi output but use
alternative endings and double barlines in my score. Awesome!
So, I tried it and I notice that my MIDI output doesn't reflect the key
21 matches
Mail list logo
