wide-dashed slurs in stable release (and printing issues)
I'm wondering when the next stable release will be that includes wide-dashed slurs (and also about some printing issues).
I made wide-dashed slurs using the Nightly Build Revision 84d4d73 (which is from about 10 days ago). But with that I encountered some issues with printing (all upward stems become slightly horizontally separated from noteheads their noteheads). So today I downloaded the new stable release MuseScore 6 aka v.2.3.2 and find that the it cannot properly read the file in which I made the wide-dashed slurs via last week's nightly build.
I guess I am confused on how nightly builds and stable releases coordinate. But more urgently, are there any suggestions on how can I have wide-dashed slurs AND have the score print properly?
Thanks,
Josh
| Attachment | Size |
|---|---|
| example of separated upstems.pdf | 141.55 KB |
Comments
MuseScore 6 ???
wide dashes are only in master, which will become 3.0 one day, scores produced with development builds from the master branch will not open in MuseScore 2.x , not without compatibility issues at least
See also https://musescore.org/en/handbook/developers-handbook/comparison-stable…
In reply to wide dashes are only in… by Jojo-Schmitz
I guess "MuseScore 6" is what the Mac Finder named the app file when I installed it into the Applications folder.
To be perfectly clear: do not use the nightly builds of master for real work. They are for testing only. Chances are very good the nightly builds will crash or produce bad results, and it is 100% certain that files created with them will not open in 2.3.2, and extremely likely they won't even open correctly in future nightly builds of master or 3.0 itself when it releases.
So it's all well and good to test out the wide dash feature in a nightly and provide feedback on how well it works, but don't expect more than that.
In reply to To be perfectly clear: do… by Marc Sabatella
Got it. Sadly in this case it's too late for me, as I already did the "real work," and need to complete it for a publication project. I knew the nightly build would be unstable; I just didn't realize that basic functionality that works on the last stable release might be broken in the nightly builds.
In reply to Got it. Sadly in this case… by jmailman
Depending on how far down this road you've gone, you might get be exporting to MusicXML with a nightly then importing that into 2.3.2 better than starting over.