Here it is now in the right repository:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2483
I added some more changes to make the file at least a bit more readable.
> I looked a bit into it and it seems that it's an oversight when
> moving on to Python 3. In line 204, the division should be an
> integer division (note the double slash):
>
> o = self.pitch // 12 - 4
>
> https://github.com/lilypond/lilypond/blob/master/scripts/midi2ly.py#L204
Thanks! Can y
I looked a bit into it and it seems that it's an oversight when moving
on to Python 3. In line 204, the division should be an integer division
(note the double slash):
o = self.pitch // 12 - 4
https://github.com/lilypond/lilypond/blob/master/scripts/midi2ly.py#L204
Lucas Cavalcanti:
s = s + "'" * commas
In this script, commas should be an integer. I don't know why it is not,
but you could change it to:
s = s + "'" * int(round(commas))
for a quick workaround.
Hello. Everytime I invoke midi2ly with the absolute mode command it gives
me an error message (check "terminal.txt" log below). It doesn't matter if
the file is generated from Lilypond or any other software.
Is this behaviour expected? I've tried asking the lilypond mai
Hi,
Am 20.11.19 um 01:00 schrieb Aaron Hill:
> "SKIP: %s\n" % `e`
2to3 is the way to go as others said before. In this particular case,
rather than calling repr, the standard solution would be:
"SKIP: %r\n" % e
as %r uses the repr-form while %s the str-form.
Cheers,
Joram
Forwarding for visibility...
On 2019-11-20 12:57 pm, Артем Тартаковский wrote:
There is another problem with musicxml2ly. It gives me an error:
Traceback (most recent call last):
File "musicxml2ly.py", line 3297, in ?
main()
File "musicxml2ly.py", line 3279, in main
basefilename = a
A quick reminder for everyone to please keep all replies on the relevant
mailing lists.
Unless the topic is clearly a sensitive matter or someone has expressly
requested private communication, always reply to the mailing lis
On 2019-11-20 9:40 am, m.tarensk...@zonnet.nl wrote:
There are more python2 vs python3 issues in those scripts than just
that one. You can try to check ( and fix) using the 2to3 script.
Fair point. I was only intending to address Артем's question on that
specific bit of syntax.
Or use Pyth
Verzonden vanaf mijn Huawei mobiele telefoon
Oorspronkelijk bericht
Onderwerp: Re: Errors with midi2ly and musicxml2ly
Van: m.tarensk...@zonnet.nl
Aan: Aaron Hill
Cc:
There are more python2 vs python3 issues in those scripts than just
that one. You
On 2019-11-20 12:00 am, Артем Тартаковский wrote:
ср, 20 нояб. 2019 г., 2:00 Aaron Hill :
It's a compatibility issue between Python 2 and 3. The backtick
operator was removed [1] in Python 3, in favor of the repr()
procedure.
[1]:
https://portingguide.readthedocs.io/en/latest/syntax.html#ba
On 2019-11-19 3:29 pm, Артем Тартаковский wrote:
I've tried to convert a MIDI file into LilyPond (version 2-19.83-1)
using
the command prompt, but it gives me an error:
File "C:\Program Files (x86)\LilyPond\usr\bin\midi2ly.py", line 545
sys.stderr.write ("SKIP: %s\n" % `e`)
I've tried to convert a MIDI file into LilyPond (version 2-19.83-1) using
the command prompt, but it gives me an error:
File "C:\Program Files (x86)\LilyPond\usr\bin\midi2ly.py", line 545
sys.stderr.write ("SKIP: %s\n" % `e`)
^
SyntaxError: invalid syntax
On Sun, 16 Apr 2017, Christopher Heckman wrote:
I like the idea and really appreciate your efforts, but I tried your patch
and it doesn't seem to work (yet), at least not on my system. I can't
Hm. My Python might be a bit rusty, but the syntax doesn't differ from
the original code. However,
On Sun, Apr 16, 2017 at 9:00 AM, Martin Tarenskeen
wrote:
>
> On Thu, 13 Apr 2017, Christopher Heckman wrote:
>
>> I have written a patch to fix this. Inside of the class Duration (line
>> 129), replace the dump function with:
>
> Hi Chris, thanks for trying to impr
On Thu, 13 Apr 2017, Christopher Heckman wrote:
I have written a patch to fix this. Inside of the class Duration (line
129), replace the dump function with:
Hi Chris, thanks for trying to improve the midi2ly tool.
I like the idea and really appreciate your efforts, but I tried your patch
:
(1) When midi2ly is run, it will print fractions with large numerators
and denominators,
created issue https://sourceforge.net/p/testlilyissues/issues/5119/
Am 15.04.2017 um 12:10 schrieb Simon Albrecht:
Am 14.04.2017 um 02:18 schrieb Christopher Heckman:
(2) In line 181 of midi2ly.py, the
Dear fellow Bug Squad members,
unfortunately I can’t access my sourceforge account right now. Could
anyone please open tracker issues for this (I think three separate ones
would be in order)?
Am 14.04.2017 um 02:18 schrieb Christopher Heckman:
(1) When midi2ly is run, it will print
Christopher Heckman:
(1) When midi2ly is run, it will print fractions with large numerators
and denominators
I have written a patch to fix this.
Could you provide this as a git-formatted patch, please?
(In case of doubt, see
<http://lilypond.org/doc/v2.19/Documentation/contributor/working-w
Hi Chris,
thanks for your analyses and code.
Am 14.04.2017 um 02:18 schrieb Christopher Heckman:
(1) When midi2ly is run, it will print fractions with large numerators
and denominators
…
I have written a patch to fix this.
Could you provide this as a git-formatted patch, please?
(In case
(1) When midi2ly is run, it will print fractions with large numerators
and denominators, like
r4*361/120 e4*29/120 r4*31/120 e4*59/120 r4*361/120 e4*29/120
when the actual durations are more likely to be
r2. e4*1/4 r4*1/4 e4*1/2 r2. e4*1/4 r4*1/4 e4*1/2 r2. e4*1/4
I have written a patch to fix
> No idea if midi2ly figures into any displayed difference or just appears
> in the log output.
At the moment one could provide a minimal test.ly file and do the following:
- run lilypond to generate midi file test.midi
- run midi2ly on test.midi to generate test-midi.ly
- either compi
> No idea if midi2ly figures into any displayed difference or just appears
> in the log output.
At the moment one could provide a minimal test.ly file and do the following:
- run lilypond to generate midi file test.midi
- run midi2ly on test.midi to generate test-midi.ly
- either compi
Mojca Miklavec writes:
> On 27 July 2016 at 12:32, David Kastrup wrote:
>> Mojca Miklavec writes:
>>
>>> If I run midi2ly with -e, this is what I get as lilypond output:
>>> f,4 4 4
>>>
>>> The problem is that durations are not allowed ins
On 27 July 2016 at 12:32, David Kastrup wrote:
> Mojca Miklavec writes:
>
>> If I run midi2ly with -e, this is what I get as lilypond output:
>> f,4 4 4
>>
>> The problem is that durations are not allowed inside chords with
>> single "brackets".
Mojca Miklavec writes:
> If I run midi2ly with -e, this is what I get as lilypond output:
> f,4 4 4
>
> The problem is that durations are not allowed inside chords with
> single "brackets".
>
> This looks like a bug to me.
Tracker issue: 4945 (https://sourcefo
David Kastrup writes:
> Mojca Miklavec writes:
>
>> If I run midi2ly with -e, this is what I get as lilypond output:
>> f,4 4 4
>>
>> The problem is that durations are not allowed inside chords with
>> single "brackets".
>>
>> This l
Mojca Miklavec writes:
> If I run midi2ly with -e, this is what I get as lilypond output:
> f,4 4 4
>
> The problem is that durations are not allowed inside chords with
> single "brackets".
>
> This looks like a bug to me.
Not
If I run midi2ly with -e, this is what I get as lilypond output:
f,4 4 4
The problem is that durations are not allowed inside chords with
single "brackets".
This looks like a bug to me.
Mojca
___
bug-lilypond mailing list
bug-lilypo
2014-07-19 17:59 GMT+02:00 Francisco Vila :
> Yesterday I was messing with a MIDI imported in Rosegarden and edited
> a bass segment with the event editor, and one of the first events was
> a clef event. Let me look at it again tonight.
>
> Maybe the clef event was generated by Rosegarden on import
On 19/07/14 15:18, David Kastrup wrote:
> Jan Nieuwenhuizen writes:
>
>> James writes:
>>
>>> Does it also matter that the clef is different when you run it back
>>> through midi2ly (at least it was for me running 2.19.8)
>> Yes, for 2.16.2 also.
>>
Martin Tarenskeen writes:
> As far as I know there is not a commonly accepted MIDI file event for
> Clefs, like there is for Time Signature (FF 58 04) and Key Signature
> (FF 59 02). But I guess it is possible for a Sequencer like Rosegarden
> to put a special message in a "Sequencer Specific Meta
a special message in a "Sequencer Specific Meta-Event" (FF 7F). Or in a
text event (FF 01) which, according to the Standard MIDI-File Format Spec
1.1 that I'm looking into now, can contain "Any type of text containing
anything".
Personally I would not choose to let Li
Francisco Vila writes:
> Maybe the clef event was generated by Rosegarden on import?
That would not surprise me. There is a lot of smart heuristics you can
think of to amend midi2ly.
Greetings,
Jan
--
Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.
2014-07-19 16:19 GMT+02:00 David Kastrup :
> Francisco Vila writes:
>
>> El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió:
>>>
>>> If MIDI has a way to encode
>>> clef information, then it's a bug.
>>>
>>
>> Yes it has.
>
> Sure? I know there is a message for encoding the key signature, but th
Francisco Vila writes:
>> If MIDI has a way to encode
>> clef information, then it's a bug.
>>
>
> Yes it has.
That's nice. If you have documentation you can point at, that
would help.
Greetings, Jan
--
Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com
Francisco Vila writes:
> El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió:
>>
>> If MIDI has a way to encode
>> clef information, then it's a bug.
>>
>
> Yes it has.
Sure? I know there is a message for encoding the key signature, but the clef?
--
David Kastrup
___
Jan Nieuwenhuizen writes:
> James writes:
>
>> Does it also matter that the clef is different when you run it back
>> through midi2ly (at least it was for me running 2.19.8)
>
> Yes, for 2.16.2 also.
>
>> I assume so in which case that is a second bug report
El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió:
>
> If MIDI has a way to encode
> clef information, then it's a bug.
>
Yes it has.
> Greetings,
> Jan
>
> --
> Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
>
> __
James writes:
> Does it also matter that the clef is different when you run it back
> through midi2ly (at least it was for me running 2.19.8)
Yes, for 2.16.2 also.
> I assume so in which case that is a second bug report right?
If so, indeed a second report. For this one, the qualifi
On 17/07/14 22:08, 'Jan Nieuwenhuizen wrote:
> Hi,
>
> Running
>
> lilypond bug.ly
> midi2ly bug.midi
> grep fis bug-midi.ly
>
> produces
>
> fis1
> fis'4. d8*5
>
> While technically correct, duration-wise, in printed outp
Hi,
Running
lilypond bug.ly
midi2ly bug.midi
grep fis bug-midi.ly
produces
fis1
fis'4. d8*5
While technically correct, duration-wise, in printed output it
will look as if the d2 has been omitted. In other words
fis'4. d8 ~ d2
looks so much nicer! T
gt; runtime, and there are a lot of optimizations that can be done in
> midi2ly itself. (For example, memoizing the creation of Duration
> objects saves about 500 ms.) I think getting rid of the sole occupant
> of usr/lib/lilypond/current/python is worth it. Assuming you agree,
> where shou
I rewrote midi.c in Python and tested it on the largest midi file in
IMSLP [1]. On my laptop it takes about 200 ms instead of 50 ms to load
the file, but that's a small fraction of midi2ly's four-second
runtime, and there are a lot of optimizations that can be done in
midi2ly itself. (F
small,
>
> Go for it - the code was written in 2001, maybe at a time when
> Python/computers were slower than they are now. It's 500-ish lines,
> so good luck!
There was at least one previous version of midi2ly. I'm not sure if
that version was fully in Python or in C++. I
On 17 déc. 2012, at 18:13, Ben Rudiak-Gould wrote:
> On Sat, Dec 15, 2012 at 11:07 PM, m...@mikesolomon.org
> wrote:
>> ImportError:
>> dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so,
>> 2): no suitable image found. Did find:
>>
>> /Applicati
On Sat, Dec 15, 2012 at 11:07 PM, m...@mikesolomon.org
wrote:
> ImportError:
> dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so,
> 2): no suitable image found. Did find:
>
> /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/pytho
On Sun, Dec 16, 2012 at 10:56:57AM +0100, Mike Solomon wrote:
> On 16 déc. 2012, at 10:54, Colin Hall wrote:
>
> > On Sun, Dec 16, 2012 at 08:07:53AM +0100, Mike Solomon wrote:
> >> Hey all,
> >>
> >> A colleague of mine got the following error message whi
On 16 déc. 2012, at 10:54, Colin Hall wrote:
> On Sun, Dec 16, 2012 at 08:07:53AM +0100, Mike Solomon wrote:
>> Hey all,
>>
>> A colleague of mine got the following error message while running midi2ly on
>> his MacBook :
>>
>> macbook:~ vanhovef$
On Sun, Dec 16, 2012 at 08:07:53AM +0100, Mike Solomon wrote:
> Hey all,
>
> A colleague of mine got the following error message while running midi2ly on
> his MacBook :
>
> macbook:~ vanhovef$ /Applications/LilyPond.app/Contents/Resources/bin/midi2ly
> wil
> Tracebac
Hey all,
A colleague of mine got the following error message while running midi2ly on
his MacBook :
macbook:~ vanhovef$ /Applications/LilyPond.app/Contents/Resources/bin/midi2ly
wil
Traceback (most recent call last):
File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly"
Comment #15 on issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error
in regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
I'm checking them now.
mf/GNUmakefile put the -n in emmentaler-brace.fontname. I've fixed it.
scripts/build/in
Comment #13 on issue 2389 by d...@gnu.org: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Carl, what's up with the following?
git grep "echo -n"
mf/GNUmakefile: echo -n 'emmentaler-brace' > $
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_35
Comment #12 on issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error
in regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Pushed to staging as
Updates:
Labels: -Patch-countdown Patch-push
Comment #11 on issue 2389 by colinpkc...@gmail.com: Patch: Fix make error
in regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Counted down to 20120320, please push
Updates:
Labels: Patch-review
Comment #9 on issue 2389 by d...@gnu.org: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389#c9
Patchy the autobot says: LGTM.
___
bug
Updates:
Summary: Enhancement to midi2ly to allow for more than 4 voices without a
warning
Comment #1 on issue 2407 by philehol...@gmail.com: Enhancement to midi2ly
to allow for more than 4 voices without a warning
http://code.google.com/p/lilypond/issues/detail?id=2407
Correct typo in
Comment #8 on issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Oops. I meant it passes make check and make doc on my OSX system.
___
bug
Updates:
Labels: -Patch-needs_work Patch-new
Comment #7 on issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
New patchset uploaded. I've replaced echo with printf. Passes
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 2407 by philehol...@gmail.com: Enhancement to midi2ly to asllow
for more than 4 voices without a warning
http://code.google.com/p/lilypond/issues/detail?id=2407
Currently, if a midi file has up to 4 channels on a track, each is
Updates:
Status: Started
Labels: -fixed_2_15_34 Patch-needs_work
Comment #6 on issue 2389 by d...@gnu.org: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Backed out from staging since this lets echo turn
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_34
Comment #5 on issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Pushed to staging as
Updates:
Labels: -Patch-countdown Patch-push
Comment #4 on issue 2389 by colinpkc...@gmail.com: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Counted down to 20120313, please push
Updates:
Labels: Patch-review
Comment #2 on issue 2389 by d...@gnu.org: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389#c2
Patchy the autobot says: LGTM. Regtests show a change in several hashed
Midi filenames
Comment #1 on issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389#c1
Fix make error in regression tests coming from midi2ly
I have been unable to complete make test-baseline because of
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2389 by carl.d.s...@gmail.com: Patch: Fix make error in
regression tests coming from midi2ly
http://code.google.com/p/lilypond/issues/detail?id=2389
Fix make error in regression tests coming from midi2ly
I have been unable
On 9 Jan 2012, at 23:03, Ralph Palmer wrote:
>> The 2.14.2 version of Lilypond for Intel Macs running OS x 10.6 contains
>> the shared library midi.so, used by midi2ly. Unfortunately it contains
>> 32-bit code which is incompatible with Python 2.6 which by default runs
>
Status: Accepted
Owner:
Labels: Type-Enhancement OpSys-OSX
New issue 2208 by ralphbug...@gmail.com: Problem running midi2ly on Mac OS
X 10.6.8 : 32- vs. 64-bit code
http://code.google.com/p/lilypond/issues/detail?id=2208
Owen Saxton wrote :
The 2.14.2 version of Lilypond for Intel Macs
On Sun, Jan 8, 2012 at 2:29 AM, Owen Saxton wrote:
> >
>
> The 2.14.2 version of Lilypond for Intel Macs running OS x 10.6 contains
> the shared library midi.so, used by midi2ly. Unfortunately it contains
> 32-bit code which is incompatible with Python 2.6 which by default run
>
The 2.14.2 version of Lilypond for Intel Macs running OS x 10.6 contains
the shared library midi.so, used by midi2ly. Unfortunately it contains
32-bit code which is incompatible with Python 2.6 which by default runs
in 64-bit mode, and midi2ly fails with the error message:
ImportError:
dlo
Updates:
Status: Verified
Comment #9 on issue 1554 by brownian.box: update midi2ly version number
http://code.google.com/p/lilypond/issues/detail?id=1554
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond
Please cc the list, so that others can engage in the issue.
Hans
On 10 Jul 2011, at 10:55, Floris van Manen wrote:
>
> On Jul 10, 2011, at 00:20, Hans Aberg wrote:
>
>> On 9 Jul 2011, at 22:19, Floris van Manen wrote:
>>
>>> L.S.
>>> While trying to
On 9 Jul 2011, at 22:19, Floris van Manen wrote:
> L.S.
> While trying to launch the midi2ly app, it will fail to start:
>
> $/Applications/LilyPond.app/Contents/Resources/bin/midi2ly
> Traceback (most recent call last):
> File "/Applications/LilyPond.app/Contents/Resource
L.S.
While trying to launch the midi2ly app, it will fail to start:
$/Applications/LilyPond.app/Contents/Resources/bin/midi2ly
Traceback (most recent call last):
File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly",
line 54, in
import midi
ImportError:
dlopen(
/Ap
Comment #8 on issue 1318 by carl.d.s...@gmail.com: midi2ly broken on Mac OS
X
http://code.google.com/p/lilypond/issues/detail?id=1318
Worked for the latest master, too.
So we need to figure out what's the difference between my system and
Comment #7 on issue 1318 by carl.d.s...@gmail.com: midi2ly broken on Mac OS
X
http://code.google.com/p/lilypond/issues/detail?id=1318
I just did 'make all' on OS X 10.6.7, and it ran successfully (lilypond
2.13.57).
I'll try with the
Comment #6 on issue 1318 by harmathdenes: midi2ly broken on Mac OS X
http://code.google.com/p/lilypond/issues/detail?id=1318
Reproduced this when issuing 'make all' on OS X 10.6.7:
/Users/thsoft/Development/lilypond-translation/scripts/build/out/help2man
out/midi2ly >
Updates:
Labels: Priority-Medium
Comment #7 on issue 1534 by philehol...@googlemail.com: midi2ly does not
show \breve or if a note lasts longer than one bar
http://code.google.com/p/lilypond/issues/detail?id=1534
(No comment was entered for this change
Updates:
Labels: -Type-Defect -Priority-Critical Type-Enhancement Priority-Medium
Comment #2 on issue 1611 by percival.music.ca: Midi2ly doesn't convert
dynamics
http://code.google.com/p/lilypond/issues/detail?id=1611
I suspect there was just a misunderstanding about which fea
Comment #1 on issue 1611 by jan.nieuwenhuizen: Midi2ly doesn't convert
dynamics
http://code.google.com/p/lilypond/issues/detail?id=1611
Midi2ly never did this, and I figure this would quite hard to do right.
I don't see how this could be critical, it's a feature request of
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1611 by colinpkc...@gmail.com: Midi2ly doesn't convert dynamics
http://code.google.com/p/lilypond/issues/detail?id=1611
Given the midi file created from attached bug.ly, midi2ly creates
bug-midi.ly without t
Comment #6 on issue 1554 by k-ohara5...@oco.net: update midi2ly version
number
http://code.google.com/p/lilypond/issues/detail?id=1554
As implied by comment 3, midi2ly now writes
\version "2.13.53"
in the .ly files it produces.
It would make things even more tidy, when 2.14 is ou
Updates:
Status: Verified
Labels: fixed_2_13_57
Comment #3 on issue 1587 by percival.music.ca: midi2ly --key option only
reaches first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
It would have been helpful if the initial message actually had an attached
Updates:
Status: Fixed
Comment #2 on issue 1587 by jan.nieuwenhuizen: midi2ly --key option only
reaches first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
Fixed in 928bfc5.
___
bug-lilypond mailing list
bug-lilypond
Comment #1 on issue 1587 by jan.nieuwenhuizen: midi2ly --key option only
reaches first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
Here's the result
Attachments:
key-option-all-staves-midi.png 12.5 KB
___
bug-lil
Status: Accepted
Owner:
Labels: Type-Defect
New issue 1587 by jan.nieuwenhuizen: midi2ly --key option only reaches
first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
When setting the key in midi2ly using --key, this key
signature is only printed on the first staff.
See
Updates:
Status: Accepted
Owner: jan.nieuwenhuizen
Comment #6 on issue 1534 by percival.music.ca: midi2ly does not show \breve
or if a note lasts longer than one bar
http://code.google.com/p/lilypond/issues/detail?id=1534
But the whole notes have 1*2, which means that they
Comment #5 on issue 1534 by colinpkc...@gmail.com: midi2ly does not show
\breve or if a note lasts longer than one bar
http://code.google.com/p/lilypond/issues/detail?id=1534
AIUI, the input file should produce 3 notes: a breve followed by 2 wholes.
They should occupy 16 beats of space in
Updates:
Status: Verified
Comment #12 on issue 839 by percival.music.ca: Enhancement: improving
midi2ly conversion
http://code.google.com/p/lilypond/issues/detail?id=839
meh, ok.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
Comment #4 on issue 1534 by percival.music.ca: midi2ly does not show \breve
or if a note lasts longer than one bar
http://code.google.com/p/lilypond/issues/detail?id=1534
Right now, from this input file:
\score{
{ c'\breve d1 *2 e }
\midi{}
}
I get:
c'1*2 d, e
Is that c
Updates:
Status: Verified
Comment #2 on issue 1549 by percival.music.ca: midi2ly should output rests
by default
http://code.google.com/p/lilypond/issues/detail?id=1549
No test file, but to quote a great webcomic,
"so did I win the argument?"
"I don't
Updates:
Status: Verified
Comment #2 on issue 1575 by percival.music.ca: midi2ly --duration-quant=16
fails to display first duration
http://code.google.com/p/lilypond/issues/detail?id=1575
(No comment was entered for this change.)
___
bug
Updates:
Status: Verified
Comment #3 on issue 1580 by percival.music.ca: midi2ly creates invalid
LilyPond input for a staff with more than four voices
http://code.google.com/p/lilypond/issues/detail?id=1580
(No comment was entered for this change
Updates:
Status: Fixed
Comment #2 on issue 1580 by jan.nieuwenhuizen: midi2ly creates invalid
LilyPond input for a staff with more than four voices
http://code.google.com/p/lilypond/issues/detail?id=1580
Fixed in e76c6cb
___
bug-lilypond
Comment #1 on issue 1580 by jan.nieuwenhuizen: midi2ly creates invalid
LilyPond input for a staff with more than four voices
http://code.google.com/p/lilypond/issues/detail?id=1580
(No comment was entered for this change.)
Attachments:
883F6BAF-3BDE-40CF-BED1-C14FC0CA1AD9.mid 11.9
Status: Accepted
Owner:
Labels: Type-Defect
New issue 1580 by jan.nieuwenhuizen: midi2ly creates invalid LilyPond input
for a staff with more than four voices
http://code.google.com/p/lilypond/issues/detail?id=1580
See the attached file. Midi2ly produces stray `\voice' commands,
Comment #5 on issue 1554 by colinpkc...@gmail.com: update midi2ly version
number
http://code.google.com/p/lilypond/issues/detail?id=1554
There's an implication in Jan's comment that we now have an engraver
(completion_rest_engraver) which is explicitly denied in NR 1.2.3 Automa
Updates:
Status: Fixed
Comment #1 on issue 1575 by jan.nieuwenhuizen: midi2ly --duration-quant=16
fails to display first duration
http://code.google.com/p/lilypond/issues/detail?id=1575
Fixed in 0731fb9
___
bug-lilypond mailing list
bug
Status: Accepted
Owner: jan.nieuwenhuizen
Labels: Type-Defect
New issue 1575 by jan.nieuwenhuizen: midi2ly --duration-quant=16 fails to
display first duration
http://code.google.com/p/lilypond/issues/detail?id=1575
The attached midi file starts with (after quanting) a 16th,
but in the
2011/3/21 Dmytro O. Redchuk :
> On Mon 14 Mar 2011, 11:16 I wrote:
>>
>> It is http://code.google.com/p/lilypond/issues/detail?id=1073 , isn't it?
>>
>> Can anyone clarify, please?
> So, if "nobody knows", i am clearing importance flag from this thread, sorry.
>
> Thanks to all!-) I believe it will
1 - 100 of 255 matches
Mail list logo
