lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond and rosegarden : control track (?) in midi output? (linux u


From: Federico Bruni
Subject: Re: lilypond and rosegarden : control track (?) in midi output? (linux user)
Date: Mon, 09 Jan 2017 17:43:03 +0100

Il giorno lun 9 gen 2017 alle 16:24, Dario Marrini <address@hidden> ha scritto:
I'm trying to create a orchester midi file using lilypond as source notation and rosegarden; I have some trouble using rosegarden jack and so on (I'm using linux), but I came to a working two strings tracks with two fluidsynth instances, so I can manage Violin I on the left and Violin II on the right.

I can't figure out the presence of a 'control track' when I import the midi files (outputted by lilypond) in rosegarden, as there is a staff only in lilypond, so do I have a single midi channel, right? I dont' know if it is a lilypond or rosegarden way of working.
Please help

What you see is the sequence name. In 2.18.2 "control track" was the default:

$ timidity test.midi
Playing test.midi
MIDI file: test.midi
Format: 1 Tracks: 2 Divisions: 384
Sequence: control track
Text: creator:
Text: GNU LilyPond 2.18.2

If you use the last development version (2.19), you'll see the text assigned to the title in your \header (you won't see anything if it's not set).

As you can read in the Changes:
http://lilypond.org/doc/v2.19/Documentation/changes/index.html

"When outputting MIDI, LilyPond will now store the title defined in a score’s \header block (or, if there is no such definition on the \score level, the first such definition found in a \header block of the score’s enclosing \bookpart, \book, or top-level scope) as the name of the MIDI sequence in the MIDI file. Optionally, the name of the MIDI sequence can be overridden using the new midititle \header field independently of title (for example, in case title contains markup code which does not render as plain text in a satisfactory way automatically)."

Don't know how to work around this in version 2.18.2.
This was the discussion which lead to the patch:
http://lists.gnu.org/archive/html/lilypond-user/2015-08/msg00062.html






reply via email to

[Prev in Thread] Current Thread [Next in Thread]