You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
release v4.7.5-engine.4
Metadata gains lyricSyllables and noteSpellings. ScoreView needs both for
reading on a phone: a lyrics-only view that highlights the sung syllable,
and note names over the noteheads with "tap a note to hear it". The SVG
draws lyrics only as glyph references, without text or verse, and the
stock CLI's flat "lyrics" string loses which syllable belongs to which
verse, staff and segment - so the data can only come from here.
lyricSyllables lists every visible syllable as {elid, staff, voice,
verse, syllabic, text, melisma}; elid is the same ChordRest segment index
as in timing.json and the SVG seg-N class. Score::lyrics() is not used, it
changes playbackCount. Above 20000 syllables the field is omitted.
noteSpellings lists every drawn notehead per (elid, staff, voice) as
[pitch, tpc] in SVG document order, including grace notes and ornament
auxiliary notes, so a client can match them one-to-one with the SVG
noteheads. pitch is ppitch() (what the MIDI plays), tpc the spelling the
SVG shows. Over the vtest corpus (838 files, 14254 notes) the counts match
the SVG Note elements for every key.
The corpus comparison against the frozen Qt baseline allows the two new
keys; native and wasm still compare them exactly. The MuseScore core stays
unpatched.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HR7wyuvffSuWkRYxv9D5kL