efine-scheme-function () ()
>> (if TrackPerVoice #{ \context { \Staff \remove "Staff_performer" } #}))
>
>
> Ah, that proves me wrong. I didn't recall the parser was smart enough for
> this.
>
>
>> Although, I don't understand why the contents of the scheme functions cannot
>
Jean Abou Samra writes:
> Alternatively, you can do it more like you were envisioning, but for
> technical reasons, you have to start the Scheme code with $ , not # ,
> and you also have to include an extra \midi { } around the \context
> blocks (basically because \context out
Am So., 19. Mai 2024 um 21:28 Uhr schrieb Carolyn Beeton
:
>
> I would like to include some Staff and Voice context settings in the \midi
> block only if a flag is set to ##t and I have not been able to figure out how
> to do this. When I try to wrap the \context blocks in
cheme functions cannot
> be placed directly into the midi block like this
>
> \midi {
> #(if TrackPerVoice #{ \context { \Staff \remove "Staff_performer" } #})
> #(if TrackPerVoice #{ \context { \Voice \consists "Staff_performer" } #})
> }
It works with $ ins
> I would like to include some Staff and Voice context settings in the
> \midi block only if a flag is set to ##t and I have not been able to
> figure out how to do this. When I try to wrap the \context blocks
> in a code block with #{…#} I get this error:
> trackPerVoiceMWE.
On 19/05/2024 20:27, Carolyn Beeton wrote:
I would like to include some Staff and Voice context settings in the \midi
block only if a flag is set to ##t and I have not been able to figure out how
to do this. When I try to wrap the \context blocks in a code block with #{…#}
I get this error
I would like to include some Staff and Voice context settings in the \midi
block only if a flag is set to ##t and I have not been able to figure out how
to do this. When I try to wrap the \context blocks in a code block with #{…#}
I get this error:
trackPerVoiceMWE.ly:31:16: error: syntax
Yes - that would be the way to go. However, the midi notes will play correctly
anyway, and the Lilypond output is far better than the staff view in my
sequencer. There is even a virtue to it as when I am playing along to the
sequencer and I forget what key I am playing in, all my sharps
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,
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 in the message, but
Yes, this fixes the problem! By adding \layout {} inside my \score next to
\midi I now get both outputs. Thank you.
From: William Rehwinkel
Sent: Sunday, May 12, 2024 9:22 PM
To: Peter Baughman; lilypond-user@gnu.org
Subject: Re: Can I output PNG and midi from
On Mon 13 May 2024 at 03:21:35 (+), Peter Baughman wrote:
> I have a few .ly files that work great and produce lovely pictures when I
> build then with a command like:
>
> lilypond --png my_song.ly
>
> I started to play around with midi output and was a little suprised
Dear Peter,
Assuming you wrote something like
% -
\version "2.25.7"
\score {
c'4
\midi {}
}
% -
and then ran lilypond --PNG midi.ly, then there would be no PNG output.
This is because if you only include the \midi block, then lilypond
produces no visual output at all.
Greetings,
I have a few .ly files that work great and produce lovely pictures when I build
then with a command like:
lilypond --png my_song.ly
I started to play around with midi output and was a little suprised to find
that I needed to add a \midi code block to my file (instead of some other
quot;1K002-1a-_WILLIE_SHAW" = { \mark "1K002-1a-" \time 4/4 \key d\major { \time
> 1/8 \partial 8 g''8 \time 4/4 fis''16 d''8. b'8. d''16 a'4 fis'4 fis'16 a'8.
> d''8. fis''16 g''16 e''8. e''8. g''16 fis''16 d''8. b'8. d''16 a'4 fis'4
> \time 7/8 f
"1K002-1a-" \time 4/4 \key d\major { \time
> 1/8 \partial 8 g''8 \time 4/4 fis''16 d''8. b'8. d''16 a'4 fis'4 fis'16 a'8.
> d''8. fis''16 g''16 e''8. e''8. g''16 fis''16 d''8. b'8. d''16 a'4 fis'4
> \time 7/8 fis'16 a'8. d''8. e''16 fis''16 d''8. d''8 \bar ":|." }
'8. fis''16 g''16 e''8. e''8. g''16 fis''16 d''8. b'8. d''16 a'4 fis'4 \time
7/8 fis'16 a'8. d''8. e''16 fis''16 d''8. d''8 \bar ":|." } }
\score {
{
\key d\major
\"1K002-1a-_WILLIE_SHAW"
}
\layout { }
\midi { }
}
or without the variable, but with the includes ac
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
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 imp
done it manually and they don't have
names I would have chosen.
I absolutely understand that LilyPond is not intended as a MIDI editor, but
it's a pretty good one in a lot of ways. I am more productive on the MIDI side
as well as the publishing side when using some of its features, hence my
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 so
> 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.
>>
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 issue is consistency and I'm perhaps not using the terms precisely enough
to describe what I am seeing.
I understand about MIDI notes and that they are neither sharpened not
flattened, but each has their own value.
In my sequencer (Cakewalk ProAudio 9), if my piece has a Key Signature
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
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
> equiva
asked for that.
>
> Okay. I didn't read it that way because the OP said he was getting
> correct output in the PDF, and if he'd misunderstood the input format in
> the way you describe, then the PDF would be wrong too.
>
> But something else that occurred to me is that there ma
ct output in the PDF, and if he'd misunderstood the input format in
the way you describe, then the PDF would be wrong too.
But something else that occurred to me is that there may be a further
misunderstanding of MIDI format in play here: MIDI never contains
"accidentals" at all. It only co
> 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 ("
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
> 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!
&
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
Indeed, Martin. But I am more of a troubadour than a musician and more of a
business analyst than a programmer, so I have cobbled together some "utilities"
that help me make music from assorted midi files and long before I understood
the role I might make LilyPond play I cho
Op donderdag 9 mei 2024 om 16:33:02 +00:00:00 schreef Giles Boardman
:
Hello,
Can anyone tell me if it is possible to generate Midi format 0 files
and whether it is possible to control the resolution setting. I have
been standardising resolution for midi files from different sources
Giles Boardman writes:
> Is that "no, you can't tell me" or "no, it can't be done? (Just
> kidding). Thanks very much. It will save me spending time looking.
It is "it is hardwired into the source code to a degree where it would
require some really heavy lifting to make it adaptable".
It would
Is that "no, you can't tell me" or "no, it can't be done? (Just kidding).
Thanks very much. It will save me spending time looking.
From: David Kastrup
Sent: 09 May 2024 18:41
To: Giles Boardman
Cc: lilypond-user@gnu.org
Subject: Re: MIDI
Giles Boardman writes:
> Hello,
> Can anyone tell me if it is possible to generate Midi format 0 files
No.
> and whether it is possible to control the resolution setting.
No.
> I have been standardising resolution for midi files from different
> sources and the value I chose
Hello,
Can anyone tell me if it is possible to generate Midi format 0 files and
whether it is possible to control the resolution setting. I have been
standardising resolution for midi files from different sources and the value I
chose is not the one output by Lilypond.
Thanks
Giles
Hi.
Le mer. 8 mai 2024 à 06:54, Alasdair McAndrew a écrit :
>
> Hello,
>
> I've set various instruments for my MIDI output (from an early 18th century
> piece), but I have a new soundfont with better instruments. Is there any way
> I can get lilypond to pick up, as it we
Hello,
I've set various instruments for my MIDI output (from an early 18th century
piece), but I have a new soundfont with better instruments. Is there any
way I can get lilypond to pick up, as it were, the instrument from this
soundfont? As it is, I just set the Staff.midiInstrument to one
Jean Abou Samra writes:
> Le lundi 29 avril 2024 à 06:31 -0500, Jason Yip a écrit :
>> Hi,
>>
>> Does anyone know how to manually set the midi channel # for a staff to
>> something other than the default of channel 0/1? Without having to
>> create dummy sta
On 2024-04-29 06:48, Jean Abou Samra - jean(a)abou-samra.fr wrote:
You can do \set Score.midiChannelMapping = #'voice as an alternative to that.
Also \new Voice { } should work (untested) instead of \new Voice { s256 }.
I don't think there's a better way.
Setting midiChannelMapping property
Le lundi 29 avril 2024 à 06:31 -0500, Jason Yip a écrit :
> Hi,
>
> Does anyone know how to manually set the midi channel # for a staff to
> something other than the default of channel 0/1? Without having to
> create dummy staffs with just `s256` as the voice content preceding
Hi,
Does anyone know how to manually set the midi channel # for a staff to
something other than the default of channel 0/1? Without having to
create dummy staffs with just `s256` as the voice content preceding the
desired staff? The staff in question usually only has one voice, so I
modified
nes and line breaks into the midi output.
>
> There are some general purpose midi control change messages that
> could
> be abused for this purpose. These general purpose control change
> messages have id's of 80-84. I don't see a way to use them in the
> lilypond documentation though.
Hello list,
I'd like to encode bar lines and line breaks into the midi output.
There are some general purpose midi control change messages that could
be abused for this purpose. These general purpose control change
messages have id's of 80-84. I don't see a way to use them in the
lilypond
I mentioned previously that I wrote a program to convert MIDI files to LilyPond
files. That program is called MidiToLily and it’s now freely available on
GitHub. It’s a console app, doesn’t have an installer, and doesn’t store things
in the registry or anywhere else. It does have command line
Karlin High wrote:
FluidSynth can do it. I use VLC Player which I think contains it.
Prior post explains:
<https://lists.gnu.org/archive/html/lilypond-user/2017-04/msg00764.html>
My contribution to that thread is outdated:
midi returned to VLC with version 3.0.8
Cheers,
Robin
On 12/7/2023 12:48 PM, Stefano Antonelli wrote:
Is downloading soundfonts 'standard practice' for working with midi on
Windows? Would anyone wanting to use ly2video on windows already know
this if they are familiar with midi?
I doubt it is common for Windows users to interact with soundfonts
On Thu, 2023-12-07 at 12:37 -0600, Karlin High wrote:
> On 12/7/2023 12:30 PM, Stefano Antonelli wrote:
> > It's the same deal for fluidsynth which doesn't come with sound
> > fonts.
> > What's the windows way to convert midi to wav?
>
> FluidSynth can do it. I u
On 12/7/2023 12:30 PM, Stefano Antonelli wrote:
It's the same deal for fluidsynth which doesn't come with sound fonts.
What's the windows way to convert midi to wav?
FluidSynth can do it. I use VLC Player which I think contains it.
Prior post explains:
<https://lists.gnu.org/archive/h
ailing until timidity. l2video uses timidity to process
the midi file into wav. And that works fine on linux. Odd because it
was originally developed for windows.
I can find timidity for windows, but it's not a nice installable
package complete with soudfonts. And it's missing timidity.cfg whi
On Thu, 2023-12-07 at 02:43 +, Chris Korda wrote:
> Doesn’t LilyPond already contain python? There’s a python.exe in the
> bin folder, and it appears to run the python scripts that come with
> LilyPond, can I just use that to run ly2video? I’m guessing not
> because that would be too easy.
guessing not because that would be too
easy.Chris
On Thursday, December 7, 2023 at 01:05:38 AM GMT+1, Stefano Antonelli
wrote:
On Wed, 2023-12-06 at 17:21 +, Chris Korda wrote:
> I spent much of the last week converting my compositions from MIDI
> files to Lily format. I tried m
the different phases of
compilation. You want grob callbacks, which is what that code does.
Re MusicXML, can you recommend a FOSS MIDI to MusicXML converter that runs on
Windows?
Have you tried MuseScore's import then export? Last time I looked, this seemed
to be the most accurate.
On Wed, 2023-12-06 at 17:21 +, Chris Korda wrote:
> I spent much of the last week converting my compositions from MIDI
> files to Lily format. I tried midi2ly first, but found it lacking,
> and decided to roll my own in C++. I gather there are other
> converters around, as I saw
ypond-s-inner-workings-and-how-you-might-hook-in-them)
if you want to understand the different phases of compilation. You want grob
callbacks, which is what that code does.
> Re MusicXML, can you recommend a FOSS MIDI to MusicXML converter that runs on
> Windows?
Have you tried MuseSco
.
Re MusicXML, can you recommend a FOSS MIDI to MusicXML converter that runs on
Windows? I looked around, but didn’t find one. I tried one that was available
on GitHub, and it generated Neutrino output, which musicxml2ly did not like.
Converting MIDI to Lily is a messy process at best, and the best
Hi,
> I spent much of the last week converting my compositions from MIDI files to
> Lily format. I tried midi2ly first, but found it lacking, and decided to roll
> my own in C++. I gather there are other converters around, as I saw at least
> one on GitHub. I may put mine on GitHu
converting my compositions from MIDI files to
Lily format. I tried midi2ly first, but found it lacking, and decided to roll
my own in C++. I gather there are other converters around, as I saw at least
one on GitHub. I may put mine on GitHub too, after its code settles down a bit.
It assumes the MIDI
t's just the
> standard General MIDI percussion keymap.
>
> At 10:52 on 17 Nov 2023, Luca Fascione wrote:
> > Hi,
> > I'm converting a MIDI file to lilypond with a drumset track.
>
> > My process goes through MusicXML, but the `musicxml2ly` script I have
> > (2.22
You'll find it in drumpitch-init.ly, I believe it's just the
standard General MIDI percussion keymap.
At 10:52 on 17 Nov 2023, Luca Fascione wrote:
> Hi,
> I'm converting a MIDI file to lilypond with a drumset track.
> My process goes through MusicXML, but the `musicxml2ly` scri
Hi,
I'm converting a MIDI file to lilypond with a drumset track.
My process goes through MusicXML, but the `musicxml2ly` script I have
(2.22.2) emits pitches instead of percussion notes.
I can write a script to map those, but if anyone had a starting point,
that'd be grand.
In my mind
> Would it be possible to reformulate a bit to make it even more clear
> that this is analogous to how \layout blocks behave (the only
> difference being that a \score block that contains nor a layout
> neither a midi block implicitly contains a layout block). For
> exampl
On 2023-11-12 14:31, Werner LEMBERG
wrote:
MIDI settings can be changed globally (or in a book or bookpart), but
the generation of an actual MIDI file is only triggered when a \midi
block is encountered inside of a \score .
Thanks
> MIDI settings can be changed globally (or in a book or bookpart), but
> the generation of an actual MIDI file is only triggered when a \midi
> block is encountered inside of a \score .
Thanks for the idea and wording.
https://gitlab.com/lilypond/lilypond/-/merge_requ
Werner LEMBERG writes:
> +A @code{@bs{}midi} block outside of @code{@bs{}score} does
> +@emph{not} create a MIDI file.}
MIDI settings can be changed globally (or in a book or bookpart), but
the generation of an actual MIDI file is only triggered when a \midi
block is encountered
> Thanks. I'll add this information to the NR.
>
>
> Right now, the NR says the following
> (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html).
> What
> do you think needs to be clarified?
>
> To create a MIDI output file from a
Thanks. I'll add this information to the NR.
Right now, the NR says the following (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html). What do you think needs to be clarified?
To create a MIDI
>> I wonder whether it is expected that this simple input
>>
>> ```
>> { c' }
>> \midi{}
>> ```
>>
>> doesn't create a MIDI file.
>
>
> Yes. [...]
Thanks. I'll add this information to the NR.
Werner
> I wonder whether it is expected that this simple input
>
> ```
> { c' }
> \midi{}
> ```
>
> doesn't create a MIDI file.
Yes. Otherwise you could not do
```
\midi { global MIDI settings ... }
fooMusic = ...
\score { \fooMusic \layout { } }
\score { \unfol
[2.24.2, 2.25.10]
I wonder whether it is expected that this simple input
```
{ c' }
\midi{}
```
doesn't create a MIDI file. I have to explicitly put everything into
a `\score` block to get that.
For me, this looks odd, and I couldn't find a hint in the
documentation for that behaviour
is this comment in elisp/lilypond-song.el:
;; We can't use midi files in ecasound directly, because setpos
;; doesn't work on them.
Apparently its output is being used as some intermediate format,
but don't ask me about it. The whole lilysong stuff is not documented
either and I
output of lilymidi documented?
A quick `git grep lilymidi` confirms that there is is no documentation
for lilymidi. Zero, zilch, nada.
It is installed with other binaries and is used by
elisp/lilypond-song.el (but what for?). I'd have expected it to be used
as part of 'make check' for comp
On Wed 27 Sep 2023 at 10:22:04 (+0200), David Kastrup wrote:
> David Wright writes:
> > On Wed 27 Sep 2023 at 01:13:09 (+0200), Jean Abou Samra wrote:
> >> After replacing “ ... ” with “ c' ”, I got the expected MIDI output with
> >> LilyPond 2.24.2, i.e., lots
ly ignoring
> the quiet bits.
I have no idea why anybody would consider that a sensible default, to be
honest. I have a hard time imagining a sensible use case at all.
Possibly skipping initial silences in manually recorded MIDI files that
aren't edited at all in a sequencer?
But that does not really sound all that sensible.
--
David Kastrup
Jean Abou Samra writes:
> Le mercredi 27 septembre 2023 à 08:22 -0400, Kevin Cole a écrit :
>> And... we have a winner! It's a timidity problem!
>
>
> From what I can read, it is the expected behavior of timidity, but there
> is a --preserve-silence option to change it.
I don't have timidity
On Wed, Sep 27, 2023 at 8:28 AM Jean Abou Samra wrote:
> Le mercredi 27 septembre 2023 à 08:22 -0400, Kevin Cole a écrit :
> > And... we have a winner! It's a timidity problem!
>
> From what I can read, it is the expected behavior of timidity, but there
> is a --preserve-silence option to change
Le mercredi 27 septembre 2023 à 08:22 -0400, Kevin Cole a écrit :
> And... we have a winner! It's a timidity problem!
From what I can read, it is the expected behavior of timidity, but there
is a --preserve-silence option to change it.
signature.asc
Description: This is a digitally signed
, like
> before, seems to be that timidity as a player skips initial rests.
>
And... we have a winner! It's a timidity problem!
Try fluidsynth -ia pulseaudio -n on your MIDI file as an alternative (on
> my system, I get inexplicable problems with -ia pipewire or -ia alsa)
> instead.
>
Thanks!
> }
> PartFour = \relative a {
> \global
> \clef "treble"
> \partial 4 a4
> }
> \score {
> \new Voice = "PartFour" {
> R1*32 R1*24
> \repeat unfold 4 {
> \transpose c c,, { \PartFour }
> }
> }
> \midi { }
>
a {
\global
\clef "treble"
\partial 4 a4
}
\score {
\new Voice = "PartFour" {
R1*32 R1*24
\repeat unfold 4 {
\transpose c c,, { \PartFour }
}
}
\midi { }
}
$ lilypond mwe.ly
GNU LilyPond 2.24.2 (running Guile 2.2)
Processing `mwe.ly'
Parsing...
Interpre
\partial 4 a4
}
\score {
\new Voice = "PartFour" {
R1*32 R1*24
\repeat unfold 4 {
\transpose c c,, { \PartFour }
}
}
\midi { }
}
$ lilypond mwe.ly
GNU LilyPond 2.24.2 (running Guile 2.2)
Processing `mwe.ly'
Parsing...
Interpreting music...
MIDI output to `mwe.mi
David Wright writes:
> On Wed 27 Sep 2023 at 01:13:09 (+0200), Jean Abou Samra wrote:
>> After replacing “ ... ” with “ c' ”, I got the expected MIDI output with
>> LilyPond 2.24.2, i.e., lots of silence and four C notes at the end.
>
> I did the same, and I attach a sc
Hi Sandro
>
> I'm not a member of the news list where you posted this (five years ago)
>
> but this is what I would have answered,
>
> I have found either all on or all off midi settings kind of awkward myself.
>
> Use the \with command when you start a new voice or staff
On Wed 27 Sep 2023 at 01:13:09 (+0200), Jean Abou Samra wrote:
> After replacing “ ... ” with “ c' ”, I got the expected MIDI output with
> LilyPond 2.24.2, i.e., lots of silence and four C notes at the end.
I did the same, and I attach a screenshot of audacious playing the
file, called mi
R1*32 R1*8
> \repeat unfold 4 {
> \transpose c c' { \PartTwo }
> }
> }
> }
>
> \midi { }
> }
> %%%
Is it possible your player is set to skip leading/trailing silence,
which is quite usual.
Cheers,
David.
After replacing “ ... ” with “ c' ”, I got the expected MIDI output with
LilyPond 2.24.2, i.e., lots of silence and four C notes at the end.
signature.asc
Description: This is a digitally signed message part
THIS time?
%%%
\version "2.24.2"
PartTwo = \relative a { ... }
\score {
\unfoldRepeats {
\new Voice = "PartTwo" {
R1*32 R1*8
\repeat unfold 4 {
\transpose c c' { \PartTwo }
}
}
}
\midi { }
}
%%%
e duplicates? (I only want it in the MIDI part, as the
>printed part would only need to display the basic melody once.)
Assign the music to a variable, and reuse it multiple times:
myMusic = {
... % music notes here
}
% Printed score
Am 20.09.23 um 15:37 schrieb Kevin Cole:
I'm not quite sure how to ask the question.
Is there a way to play the same melody as different voices with
different time offsets -- i.e. without duplicating it and adding rests
at the beginnings of the duplicates? (I only want it in the MIDI part
I'm not quite sure how to ask the question.
Is there a way to play the same melody as different voices with different
time offsets -- i.e. without duplicating it and adding rests at the
beginnings of the duplicates? (I only want it in the MIDI part, as the
printed part would only need to display
I use Frescobaldi that essentially creates skeletons for that.
Mobil gesendet
> Am 28.07.2023 um 12:20 schrieb Stephan Schöll :
>
> Hi all
>
> Years ago I stumbled upon a script that generates midi rehearsal files
> for each voice of an SATB choir e.g. and I missed the
It’s in Frescobaldi. Choose the SATB choir template and make sure the
rehearsal midi checkbox is checked.
HTH,
Carl
> On 28 Jul 2023, at 16:15, Stephan Schöll wrote:
>
> Hi all
>
> Years ago I stumbled upon a script that generates midi rehearsal files
> for each voice of an SATB choir e.g. and I missed the chance to bookmark
> or save it somehow.
>
> After registering
Hi all
Years ago I stumbled upon a script that generates midi rehearsal files
for each voice of an SATB choir e.g. and I missed the chance to bookmark
or save it somehow.
After registering each voice with the script, it iterates through all
the voices. Each file contains all the voices keeping
On Sun, 9 Jul 2023, Knute Snortum wrote:
> note out of the other hand. This is why I suggested that the MIDI performer
> could ignore \parenthesize notes. Would this create a pile of workarounds
> for you?
Not as long as I don't use \parenthesize. But I think it's preferable no
On Sun, Jul 9, 2023 at 7:54 AM wrote:
> On Sun, 9 Jul 2023, David Wright wrote:
>
> > players. But that's the problem here. When two real voices happen on
> > the same note, the result doesn't sound like one louder voice, yet
> > that's the effect you get from MIDI,
the effect you get from MIDI,¹ where the "two" voices are
>
> Not on *my* MIDI synthesizer. Two notes are two notes! I'm inclined to
> be concerned by this because I do a lot of doubling of notes between
> different MIDI channels. Each channel plays on a different patc
Knute Snortum writes:
> On Sun, Jul 9, 2023 at 6:57 AM wrote:
>
>> On Sun, 9 Jul 2023, Knute Snortum wrote:
>>
>> > I'm not sure exactly how one would deal with this problem, other than
>> with
>> > tags. Maybe \parenthesize could not
1 - 100 of 3334 matches
Mail list logo
