Le 15/01/2023 à 05:47, Saul Tobin a écrit :
\version "2.24.0"
\score {
\new Staff {
\key f \major
c'1
\key \default
c'1
}
\midi {}
}
This crashes with "In procedure cdar: Wrong type (expecting pair): ()" as
far back as 2.14.2.
Thanks, this is now
https://gitla
\version "2.24.0"
\score {
\new Staff {
\key f \major
c'1
\key \default
c'1
}
\midi {}
}
This crashes with "In procedure cdar: Wrong type (expecting pair): ()" as
far back as 2.14.2.
%In the first bar the MIDI-output is as desired.
%In the second bar, the first a'4 is changed to a'8 a'8.
%The created PDF is fine.
%However, the MIDI-output cuts the following Note, a'2, down to a quater.
%I.e. it ends, where the a'2 from voiceTwo ends.
\s
> I'm not top posting.
%----
% Midi output for \appoggiatura is not timed properly
% in articulated mode. Same bug appears in Ver 2.19.16
%
\include "articulate.ly"
\versi
Heikki,
On 09/08/14 22:14, Heikki Tauriainen wrote:
Hi,
In response to
<http://lists.gnu.org/archive/html/lilypond-devel/2014-08/msg00060.html>,
here's some new documentation for Section 3.5 ("MIDI output") of the
Notation Reference (v2.19.11). The main goal of the pro
Hi,
In response to
<http://lists.gnu.org/archive/html/lilypond-devel/2014-08/msg00060.html>,
here's some new documentation for Section 3.5 ("MIDI output") of the
Notation Reference (v2.19.11). The main goal of the proposed additions
is to describe the MIDI context prop
2014-02-23 19:18 GMT+01:00 Thomas Morley :
>
> I'd suggest to delete:
> http://lsr.di.unimi.it/LSR/Item?id=438
>
>
OK
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
2014-02-23 19:08 GMT+01:00 Phil Holmes :
> "Pierre Perol-Schneider" wrote in message
> news:caphotuvtgw9czm8stzzea8nhfhmzv3ehjzkobipngrpjaio...@mail.gmail.com...
>
>> Hi Bug squad,
>>
>> See :
>>
>> http://lsr.di.unimi.it/LSR/Search?q=Changing+MID
"Pierre Perol-Schneider" wrote in message
news:caphotuvtgw9czm8stzzea8nhfhmzv3ehjzkobipngrpjaio...@mail.gmail.com...
Hi Bug squad,
See :
http://lsr.di.unimi.it/LSR/Search?q=Changing+MIDI+output+to+one+channel+per+voice
"Changing MIDI.." appears twice :
http://lsr.di.unim
Hi Bug squad,
See :
http://lsr.di.unimi.it/LSR/Search?q=Changing+MIDI+output+to+one+channel+per+voice
"Changing MIDI.." appears twice :
http://lsr.di.unimi.it/LSR/Item?id=438
http://lsr.di.unimi.it/LSR/Item?id=766
What's weired is that it's not duplicated in the tarball I
Il 04/02/2013 07:06, Javier Ruiz-Alma ha scritto:
Requesting adding the ability to state a filename for midi output from within
score's midi block (or other score-specific block).
\book{
\bookpart{
...some markup
\score{
.music for ScoreOne
\l
Requesting adding the ability to state a filename for midi output from within
score's midi block (or other score-specific block).
\book{
\bookpart{
...some markup
\score{
.music for ScoreOne
\layout{}
\midi{ \set midifilename = "chap1
On Mon, Jul 09, 2012 at 01:15:27AM +0200, David Kastrup wrote:
> Colin Hall writes:
>
> > On Sun, Jul 08, 2012 at 06:27:04PM +, Micha wrote:
> >> In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo.
> >>
> >> In the sentence "
Colin Hall writes:
> On Sun, Jul 08, 2012 at 06:27:04PM +, Micha wrote:
>> In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo.
>>
>> In the sentence "Standard MIDI oputput is somewhat crude" it should
>> say "output"
On Sun, Jul 08, 2012 at 06:27:04PM +, Micha wrote:
> In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo.
>
> In the sentence "Standard MIDI oputput is somewhat crude" it should say
> "output".
Thanks for reporting that problem, Micha.
Micha writes:
> In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo.
>
> In the sentence "Standard MIDI oputput is somewhat crude" it should
> say "output".
Pushed to staging as
commit 199b1b921ccddca6901b1e012465bc966128fc4e
Author: David
In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo.
In the sentence "Standard MIDI oputput is somewhat crude" it should say
"output".
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/
On Fri, May 11, 2012 at 09:31:14PM +0200, David Kastrup wrote:
> I have receive in private communication the information that indeed the
> event chord wrapping workaround solved this problem, so it was not at
> all related to our Midi code.
Thanks for your help, David.
Cheers,
Colin.
--
Colin
Graham Percival writes:
> On Fri, May 11, 2012 at 10:20:37PM +0700, Michael Pozhidaev wrote:
>> I have tried the 2.15.38 on my scores and have found that the result is
>> not correct. I don't know should it be considered as critical bug or no so
>> writing this message. Please, take a look at fil
On Fri, May 11, 2012 at 10:20:37PM +0700, Michael Pozhidaev wrote:
> I have tried the 2.15.38 on my scores and have found that the result is
> not correct. I don't know should it be considered as critical bug or no so
> writing this message. Please, take a look at files in attachment.
That file is
Hello, David!
> Can you tell _what_ about the midi output you consider incorrect?
The two dynamics command, \fff and \ff, used in 6th measure actually
applies in 4th measure in midi file. It is easy to check if remove \fff
and \ff from the snippet and listen again. The volume increasing in
three files: short snippet, proper midi output by
> lilypond-2.14.2 and incorrect midi output by 2.15.38.
>
> The 2.15.38 is installed in linux-x86_64 and downloaded as binary
> package. Thanks!
I just read the code: the problem is not likely related to Midi. There
is a music function
three files: short snippet, proper midi output by
> lilypond-2.14.2 and incorrect midi output by 2.15.38.
>
> The 2.15.38 is installed in linux-x86_64 and downloaded as binary
> package. Thanks!
Can you tell _what_ about the midi output you
Hello!
I have tried the 2.15.38 on my scores and have found that the result is
not correct. I don't know should it be considered as critical bug or no so
writing this message. Please, take a look at files in attachment.
There are three files: short snippet, proper midi output by
lilypond-2
Updates:
Labels: Type-Defect
Comment #1 on issue 2151 by philehol...@gmail.com: add-grace-note usage
interferes with MIDI output in same score block
http://code.google.com/p/lilypond/issues/detail?id=2151
(No comment was entered for this change
Status: Accepted
Owner:
New issue 2151 by idragos...@gmail.com: add-grace-note usage interferes
with MIDI output in same score block
http://code.google.com/p/lilypond/issues/detail?id=2151
add/remove-grace-property does not cooperate with midi in the same score
block. Compile produces
Updates:
Status: Verified
Comment #9 on issue 1591 by k-ohara5...@oco.net: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
Can this be verified a simple way?
It was a documentation item, and I just confirmed that the one-paragraph
change
Comment #8 on issue 1591 by philehol...@gmail.com: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
Can this be verified a simple way?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Updates:
Labels: -Patch-new
Comment #6 on issue 1591 by percival.music.ca: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
sigh
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
"m...@apollinemike.com" writes:
> On Oct 10, 2011, at 9:22 AM, lilyp...@googlecode.com wrote:
>
>>
>> Comment #5 on issue 1591 by d...@gnu.org: doc: midi output is channel-voice
>> http://code.google.com/p/lilypond/issues/detail?id=1591
>>
>>
On Oct 10, 2011, at 9:22 AM, lilyp...@googlecode.com wrote:
>
> Comment #5 on issue 1591 by d...@gnu.org: doc: midi output is channel-voice
> http://code.google.com/p/lilypond/issues/detail?id=1591
>
> More like "second stab at getting Percival mad". Let me guess: you
Comment #5 on issue 1591 by d...@gnu.org: doc: midi output is channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
More like "second stab at getting Percival mad". Let me guess: you are
using the new git-cl to automagically post to both issue list an
Updates:
Labels: Patch-new
Comment #4 on issue 1591 by mts...@gmail.com: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591#c4
First stab at getting script offsets right.
http://codereview.appspot.com/5235052
Updates:
Labels: -Patch-new
Comment #3 on issue 1591 by percival.music.ca: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
what on earth does this have to do with script offsets?
Don't type issue numbers manually. You should have the
Updates:
Labels: Patch-new
Comment #2 on issue 1591 by mts...@gmail.com: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591#c2
First stab at getting script offsets right.
http://codereview.appspot.com/5235052
Hi Heikki,
2011/9/25 Janek Warchoł :
> I will add a tracker issue for this bug tomorrow.
Added as issue 1938 http://code.google.com/p/lilypond/issues/detail?id=1938
> I'll also test your patch against current master.
I've checked that your patch can be applied to current master and that it work
, trying to move the Dynamic_performer to a
> different context such as the Staff context did not help: after trying
> \midi {
> \context {
> \Voice
> \remove "Dynamic_performer"
> }
> \context {
> \Staff
> \consists "
Comment #5 on issue 1592 by k-ohara5...@oco.net: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592
We certainly don't want to depend on the midi2ly loop. Midi output bugs in
dynamics are not caught this way, nor were the disastrous issues we had
this S
Comment #4 on issue 1592 by reinhold...@gmail.com: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592
We don't need to go the midi2ly loop, we can directly dump the midi as
human-readable output (using "lilymidi --pretty") and compare this output
"PaulvdM" wrote in message
news:32202992.p...@talk.nabble.com...
When I add
\midi { \context { \Score tempoWholesPerMinute = #(ly:make-moment 56 2)
} }
to the score part, I only get a midi file (no pdf), when I comment that
part
I get the expected pdf
I use lilypond 2.14.1 on Ubuntu.
} within your \score block.
This is explained in NR 3.5.1 Creating MIDI files
If there is a \midi block in a \score with no \layout block, only
MIDI output will be produced. When notation is needed too, a
\layout block must also be present.
\score {
...music...
\m
-Either-Midi-output-or-pdf-tp32202992p32202992.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Jon Toohill gmail.com> writes:
> If I'm mistaken, and Lilypond DOES follow segnos and codas in the MIDI
> output (and I'm just doing it wrong), then please let me know!
>
You are correct, Lilypond makes no attempt to follow segnos and codas.
I know of no good way to r
Hi,
I've been using Lilypond quite a bit lately, and noticed codas aren't followed
in the MIDI output. I tried using \unfoldRepeats, and while it worked fine for
normal volta repeats, it didn't solve the coda problem. I'd be happy to provide
a small snippet to illustrate th
Updates:
Labels: partcombine
Comment #2 on issue 645 by reinhold...@gmail.com: midiInstrument +
\transposition + \partcombine = wrong MIDI output
http://code.google.com/p/lilypond/issues/detail?id=645
(No comment was entered for this change
Updates:
Status: Verified
Comment #6 on issue 1646 by colinpkc...@gmail.com: MIDI output on incorrect
channels (using GUB build)
http://code.google.com/p/lilypond/issues/detail?id=1646
Verified 2.13.62 using GUB build
___
bug-lilypond
Updates:
Labels: -backport firxed_2_13_62
Comment #4 on issue 1646 by carl.d.s...@gmail.com: MIDI output on incorrect
channels (using GUB build)
http://code.google.com/p/lilypond/issues/detail?id=1646
Backported
___
bug-lilypond mailing
Updates:
Labels: -fixed_2_13_62 backport
Comment #3 on issue 1646 by k-ohara5...@oco.net: MIDI output on incorrect
channels (using GUB build)
http://code.google.com/p/lilypond/issues/detail?id=1646
Found it. The first commit to fix issue 1620 caused this problem, but
commit
Updates:
Status: Fixed
Labels: fixed_2_15_0 fixed_2_13_62
Comment #1 on issue 1646 by k-ohara5...@oco.net: MIDI output on incorrect
channels (using GUB build)
http://code.google.com/p/lilypond/issues/detail?id=1646
Fixed in git (and I can't find any point where it was b
Status: Accepted
Owner: k-ohara5...@oco.net
Labels: Type-Defect Priority-Critical Regression
New issue 1646 by k-ohara5...@oco.net: MIDI output on incorrect channels
(using GUB build)
http://code.google.com/p/lilypond/issues/detail?id=1646
% Using the mingw build on windows XP, the following
Updates:
Status: Verified
Comment #5 on issue 1593 by colinpkc...@gmail.com: midi output eats rests
when absolute dynamics are used
http://code.google.com/p/lilypond/issues/detail?id=1593
Verified the .ly -> midi part, using Rosegarden to see the rest event and
the velocity cha
Comment #3 on issue 1592 by percival.music.ca: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592
I see the same problem; it's a midi problem. Maybe an uninitalized
variable somewhere, causing undetermined vo
Comment #2 on issue 1592 by colinpkc...@gmail.com: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592
Midi-related files have been popping up in all the times I run make check
recently, particularly partcombine-midi.ly and a handful of logs. This
happens even
Comment #5 on issue 1548 by jan.nieuwenhuizen: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
Having voices mapped to channels would be ideal from a musical pov and this
is what
the first implementation (8dc343b) did.
Now, it can be
Comment #4 on issue 1548 by k-ohara5...@oco.net: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
and for the record,
The code as of version 2.13.55 does *not* assign each voice to its own midi
channel.
Instead, each uniquely-named voice
Comment #1 on issue 1591 by k-ohara5...@oco.net: doc: midi output is
channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
Since issue 1548 was opened, the code has come back closer to the existing
documentation. Specifically :
1) we *no* *longer* have, with default
lilyp...@googlecode.com writes:
> Comment #4 on issue 1593 by microbo...@gmail.com: midi output eats
> rests when absolute dynamics are used
> http://code.google.com/p/lilypond/issues/detail?id=1593
>
> So how to fix?
To repeat:
http://permalink.gmane.org/gmane.comp.gnu.lily
Comment #4 on issue 1593 by microbo...@gmail.com: midi output eats rests
when absolute dynamics are used
http://code.google.com/p/lilypond/issues/detail?id=1593
So how to fix?
Or only workaround?
___
bug-lilypond mailing list
bug-lilypond
Comment #3 on issue 1593 by janesclu...@gmail.com: midi output eats rests
when absolute dynamics are used
http://code.google.com/p/lilypond/issues/detail?id=1593
So is there a workaround?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
Updates:
Labels: Priority-Critical
Comment #2 on issue 1593 by percival.music.ca: midi output eats rests when
absolute dynamics are used
http://code.google.com/p/lilypond/issues/detail?id=1593
(No comment was entered for this change
Werner LEMBERG writes:
>> I can't make a much smaller example, but this correctly produces
>> portion of the midi problem in 2.13.57. In a large orchestral piece,
>> the situation becomes even worse, all instruments sounds at once like
>> a pan of boiling water.
>
> Here is a minimal examp
Updates:
Status: Fixed
Comment #1 on issue 1593 by jan.nieuwenhuizen: midi output eats rests when
absolute dynamics are used
http://code.google.com/p/lilypond/issues/detail?id=1593
Fixed in f114e3c
___
bug-lilypond mailing list
bug
Status: Accepted
Owner:
Labels: Type-Defect Regression
New issue 1593 by jan.nieuwenhuizen: midi output eats rests when absolute
dynamics are used
http://code.google.com/p/lilypond/issues/detail?id=1593
See attached file
Attachments:
bug.ly 95 bytes
Comment #1 on issue 1592 by jan.nieuwenhuizen: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592
The input/regression/midi directory is now included in the regtest. While
this
does not do the text-diffing, which may be nifty, it does give us a way to
track
Status: Accepted
Owner:
Labels: Type-Build Priority-Medium Maintainability
New issue 1592 by percival.music.ca: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592
See comments 4 and 5 of issue 1586.
___
bug-lilypond
Updates:
Status: Verified
Comment #3 on issue 1548 by percival.music.ca: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
I've added issue 1591 for the doc changes.
___
bug-lilypond ma
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Low
New issue 1591 by percival.music.ca: doc: midi output is channel-voice
http://code.google.com/p/lilypond/issues/detail?id=1591
According to issue 1548, we now output midi with one voice per channel.
This apparently requires
> I can't make a much smaller example, but this correctly produces
> portion of the midi problem in 2.13.57. In a large orchestral piece,
> the situation becomes even worse, all instruments sounds at once like
> a pan of boiling water.
Here is a minimal example which exhibits the problem
Hello,
I can't make a much smaller example, but this correctly produces portion of
the midi problem in 2.13.57. In a large orchestral piece, the situation becomes
even worse, all instruments sounds at once like a pan of boiling water.
Haipeng
\version "2.13.57"
\header {
tagline =
I'm forwarding this to the bug-lilypond@gnu.org, so our Bug Squad won't miss
it.
cheers,
Janek
2011/3/31 胡海鹏 - Hu Haipeng
> Hello,
> I found a problem of Midi output in 2.13.56. If you write a timpani roll
> like this:
> \repeat tremolo 4 c32\mp\< \repeat tremolo 8
er
> Sent: Wednesday, March 30, 2011 11:18 PM
> Subject: Critical bug of midi output
>
>
> Hello,
> I found a problem of Midi output in 2.13.56. If you write a timpani roll
> like this:
> \repeat tremolo 4 c32\mp\< \repeat tremolo 8 c c8\!f
> and use unfold in midi
--
Phil Holmes
- Original Message -
From: 胡海鹏 - Hu Haipeng
To: lilypond-user
Sent: Wednesday, March 30, 2011 11:18 PM
Subject: Critical bug of midi output
Hello,
I found a problem of Midi output in 2.13.56. If you write a timpani roll like
this:
\repeat tremolo 4 c32\mp
Mario Bolognani schreef op ma 14-03-2011 om 08:47 [+]:
> > I'm not top posting.
>
> % When simultaneous voices occur on a staff
> % the MIDI instrument switches to grand piano
>
> \version "2.13.54"
Thanks for the report; this is fixed in .55
I would appreciate a complete working example
ne
> I'm not top posting.
% When simultaneous voices occur on a staff
% the MIDI instrument switches to grand piano
\version "2.13.54"
\score {
{ <<
\new ChoirStaff <<
\new Staff \with {fontSize = #+1
\override StaffSymbol #'staff-space = #
Comment #2 on issue 1548 by k-ohara5...@oco.net: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
Do we want midi output to map voices to channels?
If anybody uses LilyPond to engrave orchestral scores, then there might be
more than 16
Updates:
Status: Fixed
Comment #1 on issue 1548 by jan.nieuwenhuizen: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
Fixed in e5380f2 and 8dc343b
___
bug-lilypond mailing list
bug
Status: Accepted
Owner: jan.nieuwenhuizen
Labels: Type-Defect
New issue 1548 by jan.nieuwenhuizen: midi output should map voices to
channels
http://code.google.com/p/lilypond/issues/detail?id=1548
lilypond merges all voices in one staff into one channel.
staffs are mapped to tracks and
On Fri, 01 Oct 2010 16:26:17 -0700, wrote:
% A workaround for issue 645
\version "2.12.3"
flute = {c''1 \cueDuring "horn2" #DOWN {c''}}
hornI = {
% Begin with horn in C
c'1
% Switch to horn in F.
% For use in parts, especially cue notes,
% let transposition affect the default staf
Comment #1 on issue 645 by k-ohara5...@oco.net: midiInstrument +
\transposition + \partcombine = wrong MIDI output
http://code.google.com/p/lilypond/issues/detail?id=645
While testing a template, which I hoped would avoid such issues, I happened
to find that midiInstrument is not an
Updates:
Status: Accepted
Owner: ---
Comment #5 on issue 266 by percival.music.ca: midi output for crescendi on
skips fails
http://code.google.com/p/lilypond/issues/detail?id=266
Nobody is currently working on this issue.
___
bug
Hi Oleksandr,
On 30/05/10 21:05, Oleksandr Gavenko wrote:
On 2010-05-30 22:07, Xavier Scheuer wrote:
2010/5/30 Oleksandr Gavenko:
If I want generate many midi fragment I repeat text
\score { \new Staff { ... }
\layout { }
\midi { }
}
as many times as need. And when I run
$ lilypond my.ly
On 2010-05-30 22:07, Xavier Scheuer wrote:
2010/5/30 Oleksandr Gavenko:
If I want generate many midi fragment I repeat text
\score { \new Staff { ... }
\layout { }
\midi { }
}
as many times as need. And when I run
$ lilypond my.ly
I get a lot of my.midi, my-1.midi, ..., my-17.midi, ..
2010/5/30 Oleksandr Gavenko :
> If I want generate many midi fragment I repeat text
>
> \score { \new Staff { ... }
> \layout { }
> \midi { }
> }
>
> as many times as need. And when I run
>
> $ lilypond my.ly
>
> I get a lot of my.midi, my-1.midi, ..., my-17.midi, ...
>
> It is possible to cont
If I want generate many midi fragment I repeat text
\score { \new Staff { ... }
\layout { }
\midi { }
}
as many times as need. And when I run
$ lilypond my.ly
I get a lot of my.midi, my-1.midi, ..., my-17.midi, ...
It is possible to control names of generated midi files
in .ly source fi
Comment #4 on issue 266 by lemzwerg: midi output for crescendi on skips
fails
http://code.google.com/p/lilypond/issues/detail?id=266
With 2.13.10, the second note's volume value is still much smaller than the
first
note. Is this expected?
--
You received this message because yo
have the problem that one MIDI file
for a whole African rhythm is much too less. Therefore, I additionally add some
scores which only contain the MIDI output for all the pure voices.
Now, imagine you have singing, 2 accompaning Djembé, 3 basses and 1 solo Djembe
for the normal rhythm. Addi
the MIDI output for all the pure voices.
Now, imagine you have singing, 2 accompaning Djembé, 3 basses and 1 solo Djembe
for the normal rhythm. Additionally, the basses go into something called
echauffment very often, where the solo Djembe calls the basses and they change
their rhythm.
If the
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Low
New issue 769 by v.villenave: Enhancement: non-"volta" repeats should be
unfolded in MIDI output by default
http://code.google.com/p/lilypond/issues/detail?id=769
This feature was suggested on -user by Piero
Hello!
I have noticed something strange, looks like a bug
with producing midi files for piano pieces.
It appears in lilypond 2.11.61 and 2.12.1 built from sources for 64-bit linux
and lilypond 2.12.1 from the binary linux-x86_64 distribution.
Everything was OK in old lilypond-2.11.0 (but using \
Saturday, January 03, 2009 6:00 AM
Subject: Not every sustainOn command works properly in midi output
Hello!
I have noticed something strange, looks like a bug
with producing midi files for piano pieces.
It appears in lilypond 2.11.61 and 2.12.1 built from sources for 64-bit
linux
and lily
Hello!
I have noticed something strange, looks like a bug
with producing midi files for piano pieces.
It appears in lilypond 2.11.61 and 2.12.1 built from sources for 64-bit linux
and lilypond 2.12.1 from the binary linux-x86_64 distribution.
Everything was OK in old lilypond-2.11.0 (but using \
In this example, the MIDI output does not switch instruments properly at the
beginning of measure five. I'm sorry this is not a very simple example, but
small alterations make the problem disappear.
(Yes, I realize that this is an abuse of instrumentCueName, but I see no reason
why the
Issue 645: midiInstrument + \transposition + \partcombine = wrong MIDI output
http://code.google.com/p/lilypond/issues/detail?id=645
New issue report by v.villenave:
% Here's a weird one...
\version "2.11.50"
untransposed = \relative c'' {
c4 c d d
}
transposed = \
Issue 266: midi output for crescendi on skips fails
http://code.google.com/p/lilypond/issues/detail?id=266
Comment #3 by gpermus:
Mats reports:
Looking at the contents of the MIDI file, I noticed that in the MIDI file
included
with the bug report (i.e. generated by 2.11.14), the volume was set
t; to find the relevant bug reports.
However, note that this bug database has not been updated since
version 2.8.0 because Erik left as bug hunter and a new bug
tracking system is being planned.
/Mats
Quoting Arno Waschk <[EMAIL PROTECTED]>:
I can offer some hacking time for midi output
hunter and a new bug
tracking system is being planned.
/Mats
Quoting Arno Waschk <[EMAIL PROTECTED]>:
I can offer some hacking time for midi output if i am pointed towards
some problematic lily files like the mentioned below during the next
weeks.
Arno
On Sun, 25 Jun 2006 11:3
I can offer some hacking time for midi output if i am pointed towards some
problematic lily files like the mentioned below during the next weeks.
Arno
On Sun, 25 Jun 2006 11:37:59 +0200, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
This problem has been reported a number of tim
This problem has been reported a number of times but unfortunately
it seems that there's very little interest among the main hackers to
support the MIDI output.
/Mats
Quoting Robert Los <[EMAIL PROTECTED]>:
Dear sirs,
great package lilypond.
I installed in in Ubuntu breezy
Dear sirs,
great package lilypond.
I installed in in Ubuntu breezy badger and later on
ubuntu 6.06 dapper drake using the package manager.
This installed version 2.6.3
I upgraded to 2.8.5 by using the installation package
from your website and set
an alias in .bashrc to get the new version. (ali
Erlend Aasland gmail.com> writes:
> I suspect that this is because you haven't got any \repeat { } in the TB
> voices. Maybe you should do something like:
Hm, I had thought something like that before, but this one surely helped me out,
thanks.
Boobaa
__
1 - 100 of 143 matches
Mail list logo