- From: Jeremy Sawruk <jeremy.sawruk@gmail.com>
- Date: Tue, 12 Jun 2018 11:42:18 -0400
- To: Joseph Berkovitz <joe@noteflight.com>
- Cc: "Good, Michael" <mgood@makemusic.com>, Music Notation Community Group <public-music-notation@w3.org>, James Sutton <jsutton@dolphin-com.co.uk>
- Message-ID: <CANRG7pRMZ18ji92Sh1LJnGG7auD2GfDEZEMR29AosB9bNWFhbw@mail.gmail.com>
That could work. It removes the pitch semantics associated with step/octave, while still constraining elements to correct visual positioning. On Tue, Jun 12, 2018 at 11:35 AM Joe Berkovitz <joe@noteflight.com> wrote: > If we did use Y -- and I am not saying it's a good idea yet -- then it > would be more than just saying "put this note glyph at this Y coordinate". > It would be a semantic attribute specifying the staff position of the note > as a Y coordinate restricted to multiples of 0.5. Ledger lines would be > implied of this placed the note on a line required their use. > > . . . . . ...Joe > > Joe Berkovitz > > > On Tue, Jun 12, 2018 at 11:25 AM, Jeremy Sawruk <jeremy.sawruk@gmail.com> > wrote: > >> Hi Joe, >> Quick question: if we used y coordinate on unpitched staffs, how would >> ledger lines be supported? Unpitched staffs can have ledger lines (e.g. >> crash cymbal), so this might be part of the rationale for using step/octave >> rather than Y coordinate. I can certainly see the way in which it does not >> make sense to have step/octave on an unpitched staff, but I just want to >> make sure we still support ledger lines in those situations. >> >> J. Sawruk >> >> On Tue, Jun 12, 2018 at 11:20 AM Joe Berkovitz <joe@noteflight.com> >> wrote: >> >>> Michael, >>> >>> Thinking about MNX here, what was the rationale behind using step/octave >>> rather than a Y coordinate for an unpitched staff? I am sure there is a >>> reason but I don't know it, and one point of view could be that step and >>> octave are not concepts that make sense on an unpitched staff. >>> >>> . . . . . ...Joe >>> >>> Joe Berkovitz >>> >>> >>> On Fri, Jun 8, 2018 at 4:43 PM, Michael Good <mgood@makemusic.com> >>> wrote: >>> >>>> HI James, >>>> >>>> Yes, the “if not present” refers to the unpitched element. And yes, it >>>> is an error to place pitched notes on a staff with a percussion clef, >>>> though I think many importers will handle that gracefully. >>>> >>>> Best regards, >>>> Michael >>>> >>>> >>>> On Jun 8, 2018, at 11:55 AM, James Sutton <jsutton@dolphin-com.co.uk> >>>> wrote: >>>> >>>> Thanks Michael, >>>> >>>> Just for complete clarity. >>>> >>>> 1. "If not present". Does this refer to the percussion clef or the >>>> display-step elements? >>>> 2. Is it an error to place pitched notes on a staff with percussion >>>> clef? >>>> >>>> best regards >>>> James Sutton >>>> Dolphin Computing >>>> http://www.dolphin-com.co.uk >>>> http://www.seescore.co.uk <http://www.dolphin-com.co.uk/> >>>> http://www.playscore.co <http://www.dolphin-com.co.uk/> >>>> >>>> >>>> >>>> >>>> >>>> On 8 Jun 2018, at 17:15, Michael Good <mgood@makemusic.com> wrote: >>>> >>>> Hi James, >>>> >>>> This is documented in the MusicXML tutorial at >>>> http://www.musicxml.com/tutorial/percussion/staff-lines/. It is >>>> also in the XSD documentation for the display-step-octave group: "If >>>> percussion clef is used, the display-step and display-octave elements are >>>> interpreted as if in treble clef, with a G in octave 4 on line 2. If not >>>> present, the note is placed on the middle line of the staff, generally used >>>> for a one-line staff.” The tutorial includes some examples. >>>> >>>> Please let me know if this still seem unclear. >>>> >>>> Best regards, >>>> Michael >>>> >>>> Michael Good >>>> VP of MusicXML Technologies >>>> MakeMusic, Inc. >>>> >>>> On Jun 8, 2018, at 1:57 AM, James Sutton <jsutton@dolphin-com.co.uk> >>>> wrote: >>>> >>>> What is the rule for placing pitched notes on a staff with staff-lines >>>> < 5 with a percussion clef (not TAB)? >>>> I cannot find this anywhere in the documentation >>>> >>>> Thanks >>>> James Sutton >>>> Dolphin Computing >>>> http://www.dolphin-com.co.uk >>>> http://www.seescore.co.uk <http://www.dolphin-com.co.uk/> >>>> http://www.playscore.co <http://www.dolphin-com.co.uk/> >>>> >>>> >>>> >>>> >>>> >>> >
Received on Tuesday, 12 June 2018 15:42:57 UTC