Last modified: 2013-04-24 08:55:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49536, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47536 - \cadenzaOn Lilypond command does not work
\cadenzaOn Lilypond command does not work
Status: UNCONFIRMED
Product: MediaWiki extensions
Classification: Unclassified
Score (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-23 10:00 UTC by Braeburn
Modified: 2013-04-24 08:55 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Braeburn 2013-04-23 10:00:03 UTC
The \cadenzaOn Lilypond command for creating unmetered music[1] does not work. For instance, the following (fairly minimal) snippet throws an error:

     <score>\relative c' { \cadenzaOn c1 \cadenzaOff }</score>

Messages:

     Unable to compile LilyPond input file:

     Processing `.../file.ly'
     Parsing...
     Interpreting music... 
     warning: cannot find or create `Timing' called `'
     warning: cannot find or create `Timing' called `'
     Preprocessing graphical objects...
     Interpreting music... 
     warning: cannot find or create `Timing' called `'
     warning: cannot find or create `Timing' called `'

     exited with status: 139

1. http://lilypond.org/doc/v2.17/Documentation/notation/displaying-rhythms#unmetered-music
Comment 1 Sam Reed (reedy) 2013-04-23 21:05:43 UTC
status 139 seems ghostscript related
Comment 2 Peter Gervai (grin) 2013-04-23 21:17:55 UTC
Try
<score>\relative c' { \time 4/4 \cadenzaOn c1 \cadenzaOff }</score>

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links