Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

MusicXML import ignores `<sound tempo>` when the direction also has a `<metronome>`

Abierto
  • ¿Algo no está bien?
#2,080 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
data

Línea de trabajo

Start in MeasureParser.xmlDirection, where a direction's sound is only passed to setSound when no metronome was already created. Run the reproduction script and check what numberSounding holds for the sound tempo="90" case. Done when that case yields (60, 90) and matching tempos don't add a redundant numberSounding. Comparing against getQuarterBPM() is the approach the issue suggests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

music21 version

10.5.0

Problem summary

When a <direction> has both a <metronome> and a <sound tempo>, the importer creates the MetronomeMark from the <metronome> and skips the <sound>. Usually the two agree, but they can differ: the metronome mark is what's printed, and <sound tempo> is the tempo for playback, for example a printed "♩ = 60" played at 90.

Steps to reproduce

from music21 import converter, tempo

xml = '''<score-partwise version="4.0">
  <part-list><score-part id="P1"><part-name>Music</part-name></score-part></part-list>
  <part id="P1"><measure number="1">
    <attributes><divisions>1</divisions></attributes>
    <direction>
      <direction-type>
        <metronome><beat-unit>quarter</beat-unit><per-minute>60</per-minute></metronome>
      </direction-type>
      <sound tempo="90"/>
    </direction>
    <note><pitch><step>C</step><octave>4</octave></pitch><duration>4</duration><type>whole</type></note>
  </measure></part>
</score-partwise>'''

marks = converter.parse(xml, format='musicxml').flatten().getElementsByClass(tempo.MetronomeMark)
print([(mark.number, mark.numberSounding) for mark in marks])

Expected vs. actual behavior

Expected [(60, 90)], with the printed tempo as number and the playback tempo as numberSounding. Actual:

[(60, None)]

The 90 is lost.

More information

MeasureParser.xmlDirection only passes a direction's <sound> on to setSound if the direction didn't already have a <metronome>, to avoid making two MetronomeMarks.

<sound tempo> is always in quarter notes per minute, while <metronome> uses its own beat unit, so a dotted quarter = 60 with <sound tempo="90"/> agrees. A comparison would need to go through getQuarterBPM(), and numberSounding only needs setting when they really differ.

This matters most when <per-minute> isn't a plain number. It holds text, and scores often write "c. 60" or "60-72". Then the MetronomeMark has no number, even when exporters write the tempo in <sound tempo="60"/> right next to it:

<per-minute>c. 60</per-minute> with <sound tempo="60"/>  →  number None, getQuarterBPM() None

Reading <sound tempo> would give these marks a usable tempo.

Lenguaje dominante
Python
Estrellas
2.6k
Forks
459
Merge medio
1 d 7 h
PR fusionados (30 d)
40

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cuthbertLab/music21

Todos los issues de cuthbertLab/music21

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.