Mac, you're wrong:
BiaB generates the MusicXML file,
not Sinsy.
I'm not entirely clueless here. After all, I'm the one who pointed out
Sinsy in the first place. I've even
made a song with it before it was added to BiaB. Even PG Music says so in their own instruction on how to manually create output.
So trust me: The
only thing sent
to is the
Sinsy website
Sound.XML file, and the only thing received
from the
Sinsy website is the
.wav file.
BiaB --> Sound.XML --> Sinsy website --> result.wav
You're fundamentally mis-understanding XML. It's a hierarchical, structured tag-based markup language.
Before arguing that this is a malformed MusicXML file, you might first want to look at the
MusicXML tutorial.Everything
between a
<tag> and
</tag> is
part of that tag. If the tag contains nothing between the start and end, it can be abbreviated with the form
<tag/>.
So in your screenshot, everything between the start
<note> tag and the closing
</note> tag is part of the same note.
The top
<note> tag contains a
<pitch>,
<duration> and
<lyric> tag.
The
<pitch> contains a
<step> and
<octave> tag. If there were an accidental, you'd also see a
<alter> tag. So the pitch of the note is
G5, with a duration of
64 ticks (relative to the song's
division, set in the first measure).
The same note also has a
<lyric> tag, which indicates it has a syllabic type of
single, with the lyric of
la.
All this information pertains to the same
<note>.
The
next <note> contains a
<rest/> tag, indicating that it's a rest. Notice the form of the tag is
<tag/>, indicating it is both an opening
and a closing tag, so there is no enclosed element. The duration of this rest is
16.
This is followed by a
G5 note of duration
96 ticks.
Your screenshot demonstrates
exactly what I said: the MusicXML file (generated by BiaB) contains rests following notes.