Hi
I'm trying to export a midi file using the harp instrument.
Orhestral harp is listed as #47 midi instrument,
http://www.midi.org/techspecs/gm1sound.php .
Unfortunately I get an error when I state this intrument in my lilypond source
score. I can use some other intruments (listed in the lily doc
On Sun, Apr 1, 2012 at 5:33 PM, Valentin Villenave
wrote:
> Hello folks,
> you may have noticed that there **isn't** a new LilyPond Report out today.
>
> Nope. None at all. Sorry.
>
> And if anything, you will certainly **not** find it here:
>
> http://news.lilynet.net/?The-LilyPond-Report-25
>
>
Inspired by David K's joke, I announced to all my facebook friends that I'm
engaged :)
On Sun, Apr 1, 2012 at 5:33 PM, Valentin Villenave
wrote:
> Hello folks,
> you may have noticed that there **isn't** a new LilyPond Report out today.
>
> Nope. None at all. Sorry.
>
> And if anything, you will
Hello all,
A query about MIDI export, which relates to a feature request I have in mind but
would like to confirm is feasible.
Lilypond's MIDI export has problems with partial opening measures. This means
that import into other programs will fail to place barlines correctly, and that
MIDI p
On Mon, 02 Apr 2012 17:12:46 +0200
Joseph Rushton Wakeling wrote:
> Hello all,
>
> A query about MIDI export, which relates to a feature request I have in mind
> but
> would like to confirm is feasible.
>
> Lilypond's MIDI export has problems with partial opening measures. This
> means
> t
On Sun, 1 Apr 2012, LeGrosMario wrote:
\set Staff.midiInstrument = #"orchestral strings" works but \set
Staff.midiInstrument = #"orchestral harp" fails. I tried #"47', which did not
help.
Strange. I just tried, and it works for me. My "orchestral harp" sounds
fine Could you give more info?
Le 02/04/2012 23:28, Martin Tarenskeen a écrit :
On Sun, 1 Apr 2012, LeGrosMario wrote:
\set Staff.midiInstrument = #"orchestral strings" works but \set
Staff.midiInstrument = #"orchestral harp" fails. I tried #"47', which
did not
help.
Strange. I just tried, and it works for me. My "orche
On Tue, 03 Apr 2012 00:35:30 +0200
Roland HAMON wrote:
> Le 02/04/2012 23:28, Martin Tarenskeen a écrit :
> >
> > On Sun, 1 Apr 2012, LeGrosMario wrote:
> >
> >> \set Staff.midiInstrument = #"orchestral strings" works but \set
> >> Staff.midiInstrument = #"orchestral harp" fails. I tried #"47', w
Valentin, you sneaky bastard! Tried to deceive us, huh? But i see
the new LilyPond Report announced on Lily website, mwahahahaha!
http://news.lilynet.net/?The-LilyPond-Report-25&lang=en
Janek ;-)
___
lilypond-user mailing list
lilypond-user@gnu.org
htt
On Tue, Apr 3, 2012 at 12:07 AM, Janek Warchoł wrote:
> Valentin, you sneaky bastard! Tried to deceive us, huh? But i see
> the new LilyPond Report announced on Lily website, mwahahahaha!
> http://news.lilynet.net/?The-LilyPond-Report-25&lang=en
> Janek ;-)
Yeah, that's me all right :-)
Cheers
Hello list
Starting with 2.14 (that's the version I used after 2.12 anyway), the order of
tracks in the MIDI file has changed. While 2.12 ordered them as their contexts
appeared in the score (notes, text, notes, text, and so on, see code example
below), 2.14 puts all music tracks first, then foll
On 02/04/12 22:55, Nils wrote:
Midi understands time signatures:
What I did in Laborejo.org is to start with a measure which has a timesignature
of the length of the upbeat and after that place the original timesig.
Ahh, from a playback point of view that's a nicer tweak than rests at the star
Indeed, Valentin! Our chiwawa JSB lives for that
report and, seeing your joke, nearly had kittens.
Janek Warchoł wrote:
Valentin, you sneaky bastard! Tried to deceive us, huh? But i see
the new LilyPond Report announced on Lily website, mwahahahaha!
http://news.lilynet.net/?The-LilyPond-Repor
13 matches
Mail list logo
