[Top][All Lists]

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

musicxml2ly Pitch Changing Potential Bug

From: Alex Hansen
Subject: musicxml2ly Pitch Changing Potential Bug
Date: Sun, 3 May 2020 11:02:53 -0700

I think I have found a bug. The following musicXML, when run through
musicxml2ly, produces lilypond which has entirely different pitches. I've
cut out as much of the XML as possible to ensure it is a minimal example.
Note that the musicXML specifies a single D whole note, but when it goes
through to lilypond, it comes out as an A.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE score-partwise PUBLIC
    "-//Recordare//DTD MusicXML 3.0 Partwise//EN"
<score-partwise version="3.0">
        <score-part id="P1">
    <part id="P1">
        <measure number="1">

The lilypond that this produces:

\version "2.18.2"
% automatically converted by musicxml2ly from tmp.xml

\header {

\layout {
    \context { \Score
        autoBeaming = ##f
PartPOneVoiceNone =  \relative a' {
    a1 }

% The score definition
\score {
        \new Staff <<
            \set Staff.instrumentName = "P1"
            \context Staff <<
                \context Voice = "PartPOneVoiceNone" { \PartPOneVoiceNone }

    \layout {}
    % To create MIDI output, uncomment the following line:
    %  \midi {}


P.S. I saw the response to my last bug with the abc2ly script -- I couldn't
figure out how to respond directly, but I saw the note and I was able to
fix my usage of abc2ly.

reply via email to

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