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
At the moment, Sibmei exports Expression text as <dynam>. Is that actually sensible? I guess e.g. "dolce" should be an Expression text, but should it be output as <dynam>, or rather as <dir>?
Suggested solutions:
Export as <dir> and set @class to the style ID from Sibelius (with the leading text.staff. or text.system. stripped). Example for that: text.staff.technique => technique, text.staff.expression => expression.
Projects should define their own styles or style mappings and use a Sibmei extension or a postprocessing step to get their desired encoding.
The text was updated successfully, but these errors were encountered:
This is of course not the whole picture as all the dynamics (forte, piano, ...) are input as Expression. We therefore have to analyize the content to generate <dynam> for those cases.
At the moment, Sibmei exports Expression text as
<dynam>
. Is that actually sensible? I guess e.g. "dolce" should be an Expression text, but should it be output as<dynam>
, or rather as<dir>
?Suggested solutions:
<dir>
and set@class
to the style ID from Sibelius (with the leadingtext.staff.
ortext.system.
stripped). Example for that:text.staff.technique
=>technique
,text.staff.expression
=>expression
.The text was updated successfully, but these errors were encountered: