Re: Midi playback trim

Thanks, but Timothy Lanfear already provided a perfect solution via the set command: https://lilypond.org/doc/v2.24/Documentation/notation/skipping-corrected-music It does exactly what I was looking for. On Mon, 9 Jun 2025 at 21:31, Lucas Cavalcanti wrote: > EDIT: Please, ignore the last two ema

Re: Midi playback trim

EDIT: Please, ignore the last two emails... they contain faulty code I've seen some other PDF file and mistakenly sent broken results Em seg., 9 de jun. de 2025 às 15:22, Lucas Cavalcanti escreveu: > I've forgot to annex the PDFs... K.ly and K.pdf are the output of the bin > Konokaru sen

Re: Midi playback trim

Since you want to make an anacrusis in the midi part you must use another tag (I've named it Midi) to use the \partial command. No need for 12 tags. %%Code starts \version "2.24.4" \include "articulate.ly" \paper { #(set-default-paper-size "a4" 'landscape) } \header { title = "63" composer =

Re: Midi playback trim

On 09/06/2025 16:53, Konokaru Naru wrote: Is there any command that allows for the midi output to be trimed from a specific note in the score. I'm currently using a double score layout like this to generate both midi (and mp3 later) and score: Despite its name, the command \set Score.skipTypes

Re: Midi playback trim

> > You can't easily tag multiple measures in parallel music What do you mean? and even when you are tagging music you are only tagging it in one voice. Only if you are tagging a single voice... tags work with any music expression. To tag it in all voices you need to create a separate tag for e

Re: Midi playback trim

I could use tags to cull the start instead, which is a good point. But there is still the problem with parallel music. You can't easily tag multiple measures in parallel music, and even when you are tagging music you are only tagging it in one voice. To tag it in all voices you need to create a sep

Re: Midi playback trim

> > One is that I could use the \keepWithTag command, however it would keep > both the tagged section and the untagged section, so I can't quickly > separate the part that I want. You can use the \removeWithTag to remove specific music expressions. The second problem is with tagging itself I have

Re: Midi playback trim

Thanks! I looked into it, but it doesn't seem to be useful for what I'm trying to do. There are 2 issues with tag for what I'm doing. One is that I could use the \keepWithTag command, however it would keep both the tagged section and the untagged section, so I can't quickly separate the part that

Re: Midi playback trim

Check out the tag command. https://lilypond.org/doc/v2.25/Documentation/notation/using-tags Em seg., 9 de jun. de 2025, 13:31, Konokaru Naru escreveu: > Is there any command that allows for the midi output to be trimed from a > specific note in the score. > I'm currently using a double score lay

Re: Midi-channels in Frescobaldi (Newbie)

Am 30.04.25 um 14:46 schrieb Ben Engbers: My question is how (if possible) the characteristics (room, damp, width, level etc) can be adjusted. Is it only possible to change the characterics for all channels combined or is it also possible to adjust the channels separately? Should this be done i

Re: Midi in Frescobaldi 4.0.0. / 4.0.1

Hello, I’ve been running Frescobaldi (2.0 up to 4.0.1) with Qsyntth/Fluidsynth installed by MacPorts on an Intel MacBook Pro and never had a sound problem. Could this problem be related to Rosetta (an Intel CPU emulator running on Apple Silicon)? I mean, synthesizer software compiled for Intel

Re: Midi in Frescobaldi 4.0.0. / 4.0.1

Hi, now I have tested Fluidsynth with Frescobaldi 4.0.1: No sound. Back to Frescobaldi 3.3.0 both SimpleSynth and fluidsynth work. Anyone? Thanks, Thomas Mac M1 with MacOS 15.4 > Am 06.04.2025 um 17:22 schrieb Henning Hraban Ramm : > > Am 04.04.25 um 22:57 schrieb Stanton Sanderson: >> Sam

Re: Midi in Frescobaldi 4.0.0. / 4.0.1

Am 04.04.25 um 22:57 schrieb Stanton Sanderson: Same here with M2 Mac running 14.7.4- using qsynth (and refreshing the midi preferences). I can drag the midi file to qsynth and it plays. I can go back to Frescobaldi v3.3 and midi plays fine. -Stan On Apr 4, 2025, at 3:45 PM, Thomas Scharkows

Re: Midi in Frescobaldi 4.0.0. / 4.0.1

Same here with M2 Mac running 14.7.4- using qsynth (and refreshing the midi preferences). I can drag the midi file to qsynth and it plays. I can go back to Frescobaldi v3.3 and midi plays fine. -Stan > On Apr 4, 2025, at 3:45 PM, Thomas Scharkowski > wrote: > > Hi, > > I still get no Midi s

Re: MIDI format and MIDI resolution

I know this is late, but there are plenty of tools to convert between format 0 and 1, including timidity. `timidity input.mid -Om -o output.mid` will convert format 1 to format 0, for example.

Re: MIDI format and MIDI resolution

_ From: lilypond-user-bounces+giles.boardman=hotmail.co...@gnu.org on behalf of Martin Tarenskeen Sent: 10 May 2024 10:06 To: lilypond-user@gnu.org Subject: Re: MIDI format and MIDI resolution Op donderdag 9 mei 2024 om 16:33:02 +00:00:00 schreef Giles Boardman : > He

Re: MIDI format and MIDI resolution

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 and the va

Re: MIDI format and MIDI resolution

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

Re: MIDI format and MIDI resolution

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 format and MIDI resolution

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 is not the one ou

Re: MIDI Drums to lilypond

Yes, sorry. I did find that after typing the email... It is the GM mapping, it's just that I didn't want to retype it all by hand, if I could parse it from somewhere, you see Thanks! L On Fri, Nov 17, 2023 at 11:05 AM Mark Knoop wrote: > You'll find it in drumpitch-init.ly, I believe it's jus

Re: MIDI Drums to lilypond

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` script I have > (2.22.

Re: MIDI, dynamics and expression

On Fri, Apr 7, 2023 at 2:02 AM Dario Marrini wrote: > Hi lilypond people, > I tried adding these : > > midiMinimumVolume = #0.05 > midiMaximumVolume = #0.95 > > but I got no so different results; > Hmm, with the code below, I got very noticable results: %%% \version "2.24.1" \score { \new Vo

Re: MIDI, dynamics and expression

Hi lilypond people, I tried adding these : midiMinimumVolume = #0.05 midiMaximumVolume = #0.95 but I got no so different results; at this point, I should know how to set a specific output volume to a specific dynamic signs; even because I don't know default values regards Il giorno ven 7 apr 20

Re: Midi: tremolo vs n:m

Great - thanks for the quick response and work-around. Ben > On 16 Oct 2022, at 21:12, Jean Abou Samra wrote: > >  > >> Le 16/10/2022 à 21:20, Benjamin Tordoff a écrit : >> Hi all, >> >> My understanding is that "\repeat tremolo 4 {c16}" and "c4:16" should be >> equivalent, the latter just

Re: Midi: tremolo vs n:m

Le 16/10/2022 à 21:20, Benjamin Tordoff a écrit : Hi all, My understanding is that "\repeat tremolo 4 {c16}" and "c4:16" should be equivalent, the latter just being a (welcome) shortcut for the former. In the PDF output (without expanding repeats) they look identical however in the midi pl

Re: midi de percussion dans une Staff

Je m'explique mal ... C'est dans la sortie midi que je souhaite avoir un handclap et non un woodblock or le handclap ne sort qu'en DrumStaff ou bien je ne trouve pas le biais. Merci d'avance -- Martial Rameaux

Re: midi de percussion dans une Staff

Yes, sorry. Le ven. 23 sept. 2022 à 11:40, Jean Abou Samra a écrit : > Hi Martial, > > I suppose you meant to send this to lilypond-user-fr, not lilypond-user, > right? > > Best, > Jean > > >

Re: midi de percussion dans une Staff

Hi Martial, I suppose you meant to send this to lilypond-user-fr, not lilypond-user, right? Best, Jean

Re: MIDI & repeats

Just to close the loop on this, the snippet below seems to work and doesn't directly modify the midi limits 9which might be hard to set back). I suspect this can still be simplified by someone more knowledgable than me. Along the way I discovered two things: Changing the midiMaximumVolume / midi

Re: MIDI & repeats

I’ll give that a go - thanks for both suggestions. Ben > > On 2 Aug 2022, at 19:25, Lukas-Fabian Moser wrote: > > Hi Benjamin, > >> Am 02.08.22 um 18:10 schrieb Benjamin Tordoff: >> Hi all, I’m wondering if there’s a smart way to make the midi output for a >> particular part do the followin

Re: MIDI & repeats

Hi Benjamin, Am 02.08.22 um 18:10 schrieb Benjamin Tordoff: Hi all, I’m wondering if there’s a smart way to make the midi output for a particular part do the following two things (both common in Sousa marches): 1. Have a part play only on 2nd time through the repeat. 2. Have different dynamic

Re: MIDI & repeats

Am 02.08.22 um 18:10 schrieb Benjamin Tordoff: Hi all, I’m wondering if there’s a smart way to make the midi output for a particular part do the following two things (both common in Sousa marches): 1. Have a part play only on 2nd time through the repeat. 2. Have different dynamic for 1st and 2n

Re: MIDI and fermata

Hi Mark, theoretically it should work to do something like \once\set Score.tempoWholesPerMinute = 10 to have a single step played slower (but I have not tried if this actually works). The value would then of course depend on your tempo and how much slower you want the step to be. Cheers, Valent

Re: MIDI and fermata

Sorry, \tag, with a backslash of course. On Fri, 1 Jul 2022, 13:22 Adam M. Griggs, wrote: > I use /tag #'midi { *tempo changes* }. > > If you don't want to use tags, you can /omit Score.MetronomeMark to keep > your score tidy. > > On Fri, 1 Jul 2022, 08:56 Mark Probert, wrote: > >> Hi, all. >>

Re: MIDI and fermata

I use /tag #'midi { *tempo changes* }. If you don't want to use tags, you can /omit Score.MetronomeMark to keep your score tidy. On Fri, 1 Jul 2022, 08:56 Mark Probert, wrote: > Hi, all. > > I wondering how people deal with adding a fermata into MIDI output. The > most obvious way I can think o

Re: MIDI Program Change and Control Change messages

John, You cannot embed midi messages directly in a Lilypond score such that they become encoded in the midi output file and Lilypond comments will have no affect on the output midi file. The links provided in the first reply to your list email detail how Lilypond can be used to create midi message

Re: MIDI Program Change and Control Change messages

I didn't see what I'm looking for in there. Maybe this ain't music notation, but what I'm trying to notate is that I have a synth with a built in sequencer which has a number of patterns you save to and select to during play back. The patterns are in a number of banks, each containing a number of p

Re: MIDI Program Change and Control Change messages

> On 5 Dec 2021, at 15:30, John Whitmore wrote: > >  > Hello all, just discovered LilyPond and finding my feet. > > I'm trying to find a way to notate MIDI messages in the music score, is that > possible, in a standard way, or do people just add comments to the score? Hi John, did you alr

Re: midi sound quality help needed

Hi Guy; May I converse with you regarding this off-list? I feel quite dense :-( Thanks, Ken On Tue, Sep 14, 2021 at 6:02 PM Hwaen Ch'uqi wrote: > > Oh, brilliant!!! Thanks so much, Guy! I wish I knew this a long time ago! > > Hwaen Ch'uqi > > > On 9/14/21, Guy Stalnaker wrote: > > Sorry,

Re: midi sound quality help needed

Oh, brilliant!!! Thanks so much, Guy! I wish I knew this a long time ago! Hwaen Ch'uqi On 9/14/21, Guy Stalnaker wrote: > Sorry, that's not terribly clear ... > > Add "--output-24bit" to the TIMIDITY commandline (there may be a way to > put it in the timidity config, but I just used the CLI an

Re: midi sound quality help needed

Sorry, that's not terribly clear ... Add "--output-24bit" to the TIMIDITY commandline (there may be a way to put it in the timidity config, but I just used the CLI anyway) %> timidity --output-24bit -Ow Sorry about that. Guy On 9/14/21 6:54 PM, Guy Stalnaker wrote: Yes!! I used to have t

Re: midi sound quality help needed

Yes!! I used to have that all the time when using timidity from the CLI to play MIDI and then convert to WAV/FLAC. Now to see if I can remember how to fix it. AH! This ... From: https://henkelmann.eu/2013/03/fixing-timidity-crackling-output-in-gnu-solfege/ add |--output-24bit| to the option

Re: midi sound quality help needed

Oh, that's all right! That overall placement of folder did look a bit "interesting" to me. But since we are on the subject of midi/timidity, I wonder if you or someone else could address this: I have noticed that there is much more crackling (not sure how else to describe it) going on in the sound

Re: midi sound quality help needed

I did not intend to contradict what you wrote, simply to show that kubuntu has a more complicated set of configuration files that all interact with each other, rather than using a single timidity.cfg file (which was all that there was many years ago). I apologize if I gave the impression I was

Re: midi sound quality help needed

Greetings Guy, Perhaps I am missing something, but the folder contents that you display don't seem to contradict what I wrote. Hwaen Ch'uqi On 9/14/21, Guy Stalnaker wrote: > Thanks Hwaen Ch'uqi! That's not at all how kubuntu does this: > > √ /mnt/NAS326_Music/music/Radio Drama > ll /etc/timid

Re: midi sound quality help needed

Thanks Hwaen Ch'uqi! That's not at all how kubuntu does this: √ /mnt/NAS326_Music/music/Radio Drama > ll /etc/timidity/ total 480K -rw-r--r-- 1 root root 230K Nov 11  2016 fluidr3_gm.cfg -rw-r--r-- 1 root root 4.7K Nov 11  2016 fluidr3_gs.cfg -rw-r--r-- 1 root root 4.6K Sep 22  2006 freepats.cfg

Re: midi sound quality help needed

Greetings Ken, I do not use a mac; I use linux. However, I have a feeling that the principle for this is the same. Timidity reads its settings from a file called /etc/timidity.cfg, and those settings can be changed. Whatever soundfont you wish to use, you should be able to download it and tell ti

Re: midi sound quality help needed

Ken, You are S close :-) The issue is neither Lilipond nor its midi output. MIDI is simply a specification for musical "events" describing pitch, duration, etc. It's up to a program that understands MIDI to make actual sound. That is typically done via a synthesizer (dedicated synth modul

Re: Midi Instrument: change?

Understood and thanks for the clarification. Guy On 9/4/21 5:09 PM, David Kastrup wrote: Guy Stalnaker writes: David and Jerry, I've been using the "method" shown on that Lilypond doc page for years. I confirm that it does work for me. I can put \set midiInstrument = #"" anywhere in a voi

Re: Midi Instrument: change?

Guy Stalnaker writes: > David and Jerry, > > I've been using the "method" shown on that Lilypond doc page for > years. I confirm that it does work for me. I can put > > \set midiInstrument = #"" > > anywhere in a voice and LP will change the midi instrument. Which is > why I suggested it to Jerry

Re: Midi Instrument: change?

Thanks, David. This works a lot easier. Jerry On Sat, Sep 4, 2021 at 4:51 PM David Kastrup wrote: > Guy Stalnaker writes: > > > See > > > http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping > > > > Where the method is shown. Basically, you put the instrument into the > > V

Re: Midi Instrument: change?

David and Jerry, I've been using the "method" shown on that Lilypond doc page for years. I confirm that it does work for me. I can put \set midiInstrument = #"" anywhere in a voice and LP will change the midi instrument. Which is why I suggested it to Jerry. But there is no denying that Da

Re: Midi Instrument: change?

Guy Stalnaker writes: >> On Sat, Sep 4, 2021, 3:51 PM David Kastrup wrote: >> >>> Guy Stalnaker writes: >>> >>> > See >>> > >>> http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping >>> > >>> > Where the method is shown. Basically, you put the instrument into the >>> > Voice

Re: Midi Instrument: change?

Just following the docs (per the link provided). Should the docs be updated? Guy On Sat, Sep 4, 2021, 3:51 PM David Kastrup wrote: > Guy Stalnaker writes: > > > See > > > http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping > > > > Where the method is shown. Basically, you

Re: Midi Instrument: change?

Guy Stalnaker writes: > See > http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping > > Where the method is shown. Basically, you put the instrument into the > Voice context: > > %%% Code > >   \midi { >     \context { >   \Staff >   \remove "Staff_performer" >     } >

Re: Midi Instrument: change?

1. Midi Instrument: change? (JxStarks) 2. Re: Midi Instrument: change? (Guy Stalnaker) GuyS I too wanted to know how to do this. Since I have limited experience with the latest versions of lilypond due to total confusion of the new syntax's. I did find this example you linked t

Re: Midi Instrument: change?

This is great! Thanks for your help. Jerry On Fri, Sep 3, 2021 at 8:46 PM Guy Stalnaker wrote: > See > http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping > > Where the method is shown. Basically, you put the instrument into the > Voice context: > > %%% Code > > \midi {

Re: Midi Instrument: change?

See http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping Where the method is shown. Basically, you put the instrument into the Voice context: %%% Code   \midi {     \context {   \Staff   \remove "Staff_performer"     }     \context {   \Voice   \consists

Re: Midi file is quiet???

On Fri, Sep 3, 2021 at 3:28 PM wrote: > > On 3 Sep 2021 at 14:49, Knute Snortum wrote: > > > On Fri, Sep 3, 2021 at 1:56 PM wrote: > > > > > > I have an engraving of a Vivaldi piece that has a ChoirStaff with three > > > staffs within it, then a > > > separate staff, then a PianoStaff with the n

Re: Midi file is quiet???

On 3 Sep 2021 at 14:49, Knute Snortum wrote: > On Fri, Sep 3, 2021 at 1:56 PM wrote: > > > > I have an engraving of a Vivaldi piece that has a ChoirStaff with three > > staffs within it, then a > > separate staff, then a PianoStaff with the normal two parts. The last two > > lines in the \score

Re: Midi file is quiet???

On Fri, Sep 3, 2021 at 1:56 PM wrote: > > I have an engraving of a Vivaldi piece that has a ChoirStaff with three > staffs within it, then a > separate staff, then a PianoStaff with the normal two parts. The last two > lines in the \score > block are: > > \layout {} > \midi {\tempo 4 = 70 }

Re: MIDI Position Markers

Sorry about that post guys. It was to a student about a completely different thing! I've just got a new mouse and it seems I've not got the hang of using it yet! On Thursday, 15 July 2021 17:37:34 BST Dr Nicholas Bailey wrote: > Also looking good. Well-formed user stories. > > Helping each othe

Re: MIDI Position Markers

Le 15/07/2021 18:37, Dr Nicholas Bailey a écrit : Also looking good. Well-formed user stories. Helping each other is fine. You are going to have to allocate a %effort though

Re: MIDI Position Markers

Also looking good. Well-formed user stories. Helping each other is fine. You are going to have to allocate a %effort though (sorry to be such an authoritarian, but as I explained it's not a group project). For this exercise, concentrate on the ideas when allocating effort. It's beautifully form

Re: Midi volume?

Aaron Hill writes: > On 2021-03-27 1:13 pm, David Kastrup wrote: >> When I do >> the result of >> lilymidi --pretty /tmp/test.midi >> [...] >> No volume change. What am I missing? > > That's odd. When I compiled your file, I got a MIDI that does have > velocities ranging from 86 to 101. > >

Re: Midi volume?

On 2021-03-27 1:13 pm, David Kastrup wrote: When I do the result of lilymidi --pretty /tmp/test.midi [...] No volume change. What am I missing? That's odd. When I compiled your file, I got a MIDI that does have velocities ranging from 86 to 101. For reference, I am using 2.22.0 to comp

Re: MIDI input [was Re: Nested transposition]

Hello everyone, As I do not have any midi keyboard, I have programmed for myself a web-piano-keyboard-entry (HTML-CSS-JavaScript). I use regularly for Lilypond - it combined different syntax, does Lylipond in relative mode. Actually, if was to be used for other systems also. You can find the fi

Re: MIDI input [was Re: Nested transposition]

On Sun, Mar 14, 2021 at 12:41 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Ralph, > > >> 1. I use Frescobaldi. > > > > Wow. I missed this somehow. I can see why you use absolute values > exclusively, Kieren. I'm almost exclusively transcribing and transposing > fiddle tunes. I

Re: MIDI input [was Re: Nested transposition]

Hi Ralph, >> 1. I use Frescobaldi. > > Wow. I missed this somehow. I can see why you use absolute values > exclusively, Kieren. I'm almost exclusively transcribing and transposing > fiddle tunes. I do a lot of entry from sheet music, and do a lot of > proofreading, then transposing. Not terrib

Re: MIDI input [was Re: Nested transposition]

On Sat, Mar 13, 2021 at 9:14 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Carl! > > >> My music entry is done 99% by MIDI input, so I type almost no commas or > apostrophes. > > Can you tell me how you do your MIDI input? I'd like to do that, but I > don't have a good workflow

Re: MIDI ties

Le 22/10/2020 à 10:40, Andrew Bernard a écrit : Hmm. That example, using explicit ties like e.g. now works fine for me, exactly duplicating your MIDI piano roll. Needs further investigation by me. However, using ~ is the answer I was unaware of for years! I never thought to _not_ put a directi

Re: MIDI ties

Hmm. That example, using explicit ties like e.g. now works fine for me, exactly duplicating your MIDI piano roll. Needs further investigation by me. However, using ~ is the answer I was unaware of for years! I never thought to _not_ put a direction specifier. Andrew

Re: MIDI ties

On 2020-10-21 8:00 pm, Andrew Bernard wrote: And now I just found out something I never knew, as a result of my query. Just putting a tie with no up/down indication, a sole ~ after the chore <> construct puts the ties up and down musically correctly. Well I'll be. I have caused myself much extra

Re: MIDI ties

And now I just found out something I never knew, as a result of my query. Just putting a tie with no up/down indication, a sole ~ after the chore <> construct puts the ties up and down musically correctly. Well I'll be. I have caused myself much extra work for years by not knowing this. And of cour

Re: MIDI ties

On 2020-10-21 7:48 pm, Andrew Bernard wrote: More handholding for MIDI output. I notate ties in chords with individual ties up and down depending on the note position, not just using a tie for the whoie chord <> construct. These ties do not appear in the MIDI output. Is how I do the ties unsuppor

Re: midi via Scheme

On 2020-02-20 10:28 am, Lee Zipin wrote: But I can't find a Scheme way to run MIDI, like #(if (defined? 'includeMIDI) (midi (tempo 4=150))); clearly BAD CODE How to write that line? - to work properly in a \score block. \version "2.19.84" includeMIDI = ##t \score { { b'4 }

Re: MIDI and dynamics

On 2019-11-13 6:20 p.m., Carl Sorensen wrote: On 11/13/19, 1:54 PM, "Cam" wrote: Hello All, I'm trying to have dynamics affect the generated MIDI without success. The MWE below produces the MIDI shown even further below. The dynamic markings result in channel volume control m

Re: MIDI and dynamics

On 11/13/19, 1:54 PM, "Cam" wrote: Hello All, I'm trying to have dynamics affect the generated MIDI without success. The MWE below produces the MIDI shown even further below. The dynamic markings result in channel volume control messages being injected into the MIDI but always

Re: MIDI, rests and end-of-track

On Tue 22 Oct 2019 at 18:08:02 (+0200), Malte Meyn wrote: > Am 22.10.19 um 17:06 schrieb Cam: > > \version "2.18.2" > > > > […] > > > > My concern is that the track chunk which contains the actual notes > > is shown as ending immediately after the e8 note. You can tell it > > ends there because t

Re: MIDI, rests and end-of-track

Hi Cam, please start a new thread for a new topic. (You replied to a thread about double clefs. You changed the subject but the information that it’s a reply to that thread is still there so it will be shown as part of that thread.) Am 22.10.19 um 17:06 schrieb Cam: \version "2.18.2" […]

Re: midi instrument for ChordNames

Am 22.10.19 um 09:54 schrieb Sandro Santilli: On Mon, Oct 21, 2019 at 12:15:47PM +0200, Thomas Morley wrote: please always provide a MWE, with the lily-version in it. What's MWE ? A minimal working example, see http://lilypond.org/tiny-examples for why and how to create one. __

Re: midi instrument for ChordNames

> Le 22 oct. 2019 à 09:54, Sandro Santilli a écrit : > > On Mon, Oct 21, 2019 at 12:15:47PM +0200, Thomas Morley wrote: > >> please always provide a MWE, with the lily-version in it. > > What's MWE ? > A Minimal Working Example. JM ___ lilypon

Re: midi instrument for ChordNames

On Mon, Oct 21, 2019 at 12:15:47PM +0200, Thomas Morley wrote: > please always provide a MWE, with the lily-version in it. What's MWE ? > Anyway, I assume you're at 2.18.2 (it would have worked out of the box > with 2.19.83) Yes, it's 2.18.2 > For _Staff_ you do _Staff_.midiInstrument. > Why n

Re: midi instrument for ChordNames

Am Mo., 21. Okt. 2019 um 11:12 Uhr schrieb Sandro Santilli : > > I can't get anything but a piano rendering of ChordNames staff, > can other instruments be used ? If so, how ? > > This is my sheet snippet: > > << > \new ChordNames { > \set midiInstrument = "flute" % does not work here >

Re: MIDI file creation - or not?

Ben, It's your use of \markup in this example. If I comment out the \markup line, the \fill-line line, and the final two lines (the last two } ) then I get a midi file. If you want to center the output, there is perhaps a better way. Folks on this list can help with that (one approach is to set m

Re: MIDI file creation - or not?

On 2019-07-01 1:22 pm, Ben Potter wrote: I took the example chant and engraved it as a test - fine. I then added a \midi{} command in, I believe, the correct place but still get no MIDI file to play. I am stuck - please can someone help this beginner? I do not believe \midi can be used within a

Re: MIDI Output not working

"mu...@gmx.ch" writes: >> Am 03.06.2019 um 19:18 schrieb: >>> Nevermind, it is working now for some reason. Thank you. >>> >>> >>> Jun 3, 2019, 9:58 AM by anz...@tutanota.com: >>> >>> Hello, I added the following code to the score block: >>> >>>  \midi {} >>> >>> and in the log it say

Re: MIDI Output not working

Maybe the reason for your irritation could be the following: Lilypond renders its output to a temporary folder unless you save your ly-file, which brings lilypond to render all output files to the "official" / expected folder. So if you would like to find your most current output - be it pdf or m

Re: MIDI Output not working

Could you provide a minimal example of code that does not work? -- Phil Holmes - Original Message - From: Anzick To: lilypond-user@gnu.org Sent: Monday, June 03, 2019 5:58 PM Subject: MIDI Output not working Hello, I added the following code to the score block: \mi

Re: MIDI Output not working

Nevermind, it is working now for some reason. Thank you. Jun 3, 2019, 9:58 AM by anz...@tutanota.com: > Hello, I added the following code to the score block: > >  \midi {} > > and in the log it says: > > > MIDI output to `C Major.midi'... > > > But alas, the MIDI file does not appear beside the P

Re: MIDI instrument for oboe d'amore

>> The pitch to use for \transposition should correspond to the real >> sound heard when a c' written on the staff is played by the >> transposing instrument. This pitch is entered in absolute mode, so an >> instrument that produces a real sound which is one tone higher than >> the printed music s

Re: MIDI instrument for oboe d'amore

The LPNR: The pitch to use for |\transposition| should correspond to the real sound heard when a |c'| written on the staff is played by the transposing instrument. This pitch is entered in absolute mode, so an instrument that produces a real sound which is one tone higher than the printed m

Re: MIDI instrument for oboe d'amore

Jacques Menu writes: >> Le 1 mai 2019 à 10:01, David Kastrup a écrit : >> >> Jacques Menu writes: >> >>> Unfortunately, \transposition can only be used when the notes are written >>> in « >>> instrument » pitch, not concert pitch. >> >> Says who? > > The LPNR: > > The pitch to use for \tran

Re: MIDI instrument for oboe d'amore

> Le 1 mai 2019 à 10:01, David Kastrup a écrit : > > Jacques Menu writes: > >> Unfortunately, \transposition can only be used when the notes are written in >> « >> instrument » pitch, not concert pitch. > > Says who? The LPNR: The pitch to use for \transposition should correspond to the r

Re: MIDI instrument for oboe d'amore

Hi, Am 01.05.19 um 09:55 schrieb Jacques Menu: Unfortunately, \transposition can only be used when the notes are written in « instrument » pitch, not concert pitch. BTW, it could be better named as something like \transposingInstrument, it seems. I started by writing the code to obtain the sa

Re: MIDI instrument for oboe d'amore

Jacques Menu writes: > Unfortunately, \transposition can only be used when the notes are written in « > instrument » pitch, not concert pitch. Says who? > BTW, it could be better named as something like > \transposingInstrument, it seems. Why? > I started by writing the code to obtain the sam

Re: MIDI instrument for oboe d'amore

Unfortunately, \transposition can only be used when the notes are written in « instrument » pitch, not concert pitch. BTW, it could be better named as something like \transposingInstrument, it seems. I started by writing the code to obtain the same score as the manuscript I’m using, where the f

Re: MIDI instrument for oboe d'amore

David Kastrup writes: > Jacques Menu writes: > >> Thanks Lukas and Aaron for your help. >> >> In fact, my use case is merely to listen to the MIDI file from within >> Frescobaldi, to ear-proof the score. I don’t have any MIDI equipment, >> and organ sound is fine for that purpose. >> >> I got th

Re: MIDI instrument for oboe d'amore

Jacques Menu writes: > Thanks Lukas and Aaron for your help. > > In fact, my use case is merely to listen to the MIDI file from within > Frescobaldi, to ear-proof the score. I don’t have any MIDI equipment, > and organ sound is fine for that purpose. > > I got the surprise that transposing a voic

  1   2   3   4   5   6   7   >