SmartMusic Finale Garritan MusicXML

Curve Continue

Moderator: Michael Good

Curve Continue

Postby Matthew.James.Briggs » Thu Nov 03, 2016 10:43 am

I am trying to understand the specification for curves (ties and slurs).

A slur continue defines a point with default/relative/x/y as well as two bezier points with bezier/x/y/offset/2.

So does the curve continue define a single point through which the curve passes as well as two bezier handles?

Also, why do we need both bezier-x as well as bezier-offset? Why two fields for controlling the x positioning?

Do others find the bezier attributeGroup documentation sufficient or could it be better?

“Now that things are so simple, there's so much to do.” - Morton Feldman
User avatar
Posts: 23
Joined: May, 2014
Location: Seattle, WA, USA
Reputation: 0
Software Owned:
Max OS X, Finale, Logic Pro, XCode, Xmplify, Sublime Text

Re: Curve Continue

Postby Michael Good » Fri Nov 04, 2016 6:33 pm

The continue curve points can be used in two different ways. One is to specify the position of the curve at a system break. The other is to allow multiple bezier curves to be combined together to form complex curves with many inflection points. I don't know any software that is using the latter case, though Dorico sounds like it could do that.

Perhaps it would make sense to differentiate those two cases in the semantics somehow, but that is probably something outside the scope of MusicXML 3.1.

The bezier-x and bezier-offset are there in case an application can specify in musical coordinates but not graphical, or vice versa. I think most everyone uses bezier-x though; bezier-offset may not have been the best idea.

Any suggestions for documentation improvement are most welcome at the W3C Music Notation Community Group!
Michael Good
VP of MusicXML Technologies
MakeMusic, Inc.
User avatar
Michael Good
Posts: 2197
Joined: March, 2014
Reputation: 0

Who is online

Users browsing this forum: No registered users and 2 guests