lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 4390 in lilypond: MusicXML: tremolo on an eigh


From: lilypond
Subject: Re: [Lilypond-auto] Issue 4390 in lilypond: MusicXML: tremolo on an eighth note creates a 32nd tremolo mark instead
Date: Mon, 11 May 2015 19:03:53 +0000


Comment #1 on issue 4390 by address@hidden: MusicXML: tremolo on an eighth note creates a 32nd tremolo mark instead
https://code.google.com/p/lilypond/issues/detail?id=4390

Hi Jörn,

On 03.05.2015, at 00:23, Jörn Eichler <address@hidden> wrote:

I'm not top posting.

For music XML input "<tremolo type="single">2</tremolo>" on an eighth note
of C, musicxml2ly creates "c8 :16" which, I think, is incorrect, because the
2 tremolo marks make it a 32th tremolo.

thanks for the report!

Yes, you are right, it’s a bug and all beamed notes are affected e.g.:

   MusicXML                              expected LP     wrong LP
  --------------------------------------------------------------------------
   eighth note with 1 stroke         c8:16               c8:8
   eighth note with 2 strokes       c8:32               c8:16
   ...
   sixteenth note with 1 stroke    c16:32             c16:8
   sixteenth note with 2 strokes  c16:64             c16:16
   ...


I cooked up some files to illustrate the expected output and the bug:

* https://github.com/Philomelos/PUMTS/blob/master/partwise/elements/tremolo/tremolo.xml (MusicXML supports up to 8 tremolo marks) * https://github.com/Philomelos/PUMTS/blob/master/partwise/elements/tremolo/tremolo--expected.ly * https://github.com/Philomelos/PUMTS/blob/master/partwise/elements/tremolo/tremolo--expected.svg * https://github.com/Philomelos/PUMTS/blob/master/partwise/elements/tremolo/tremolo_xml--musicxml2ly-2.19.15.ly (I had to comment out some lines) * https://github.com/Philomelos/PUMTS/blob/master/partwise/elements/tremolo/tremolo_xml--musicxml2ly-2.19.15.ly--lilypond-2.19.15.svg


hth
patrick


--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

reply via email to

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