Replies: 3 comments
-
|
I created an issue and PR to support this. Regarding your question as to whether it's right or not, I'm not quite sure. It seems logical. You could ask on the MusicXML GitHub regarding representational correctness. I'm not sure if you saw this comment: #244 (comment) I'm wondering if I should promote In the meantime, as you come across features you need, we can most likely surface them pretty quickly now that we have LLMs for this stuff. |
Beta Was this translation helpful? Give feedback.
-
|
P.S. I'll have less time during the work week, but if you hit another missing feature you can cd into https://github.com/webern/mx/blob/main/.claude/skills/mx-api-add-feature/SKILL.md I might be a little picky about certain things if it doesn't follow existing patterns, but it could be worth a try to see what it comes up with for a missing feature. |
Beta Was this translation helpful? Give feedback.
-
|
I did see the comment you linked. Thanks so much for such a quick response and for making MX in the first place. It changed this project from being a sludge to kinda fun. The only other missing |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As you know, I am in the throes of creating a new musicxml export for Finale using MX. The goal is to be the best semantic export it can be, without getting bogged down in engraving details that are unlikely to port to any other program anyway.
I've got brackets working well, but part brackets do not seem to be supported by
mx::api. This is how a pipe organ part is supposed to look:My LLM is telling me I need to do that with
<part-symbol top-staff="1" bottom-staff="2">brace</part-symbol>which is not inmx::api. So my question is, is this correct? Is there another way, other than cheating? (FWIW: Finale cheats and creates a hidden extra pedal part.) How much trouble is it to add the part-symbol withmx::core?Beta Was this translation helpful? Give feedback.
All reactions