The issue is in the ease-of-use category. Thanks! I’m looking forward to try the new iteration.I suspect if you did a comparison grid of whether or not the feature exists in an app, you would find a great deal of similarity-especially in the apps that are targeted for the same kinds of users. (Naturally, the “sharp” is on the keyboard anyway but of course there is no “natural” or “flat”.) Maybe this is Adobe’s fault but it works fine if I do the same from word processor. In fact, when printing to PDF, it will render only a text log, but no PDF. I’ve tried pasting a unicode flat into the text editor and the editor will take it, but the printer really hates to print it. (I do a lot of educational work.) Like, for instance, the note designation “Bb”… it’s customary to us a small case “b” as a substitute for a flat but much more professional to use an actual flat… ♭. One problem I hope you will address is this: Occasionally I need to put musical notation into the text editor… especially accidents but sometimes note symbols. Back then they would just report to me that others have already reported the same bugs… Over the years I’ve noticed a few bugs and reported them to the previous owners, so hopefully those, if not already fixed, have been brought to your attention. Hello, I’ve used Encore since it was MusicTime Deluxe and love it’s ease of use and professional looking print quality. Overture and Notion and Finale all handle 3.0 well while Dorico and MuseScore have issues but nothing insurmountable. Again, because it is a toolkit, do not expect it to be 100% compatible with other notation apps. I expect Encore 6 to support MusicXML 3.0 which has been around since 2011 or so with wide adoption. Sibelius just got v.4 in the form of a Dolet 8 plug-in from MM a few weeks ago and none of the other notation apps out there are even using v.3.1 (a major update) released in 2017 and first implemented in Finale in mid-2018. Version 2.0 was out in 2007, a year or so before Encore 5.Īlthough xml v.4 has been released by MakeMusic with Finale 27 last year, adoption has been slooooow. It’s not that xml 1 could not support these but MusicXML is a toolkit and it is up to the developer to decide what is implemented and how-and the developer for GVOX used very few features. 1.x and does not support lyrics and expressions among its many failings.
I don’t believe that anyone agrees with that when it comes to MusicXML.Įncore’s current MusicXML is v. Undo absolutely sucks in the current versions.
0 kommentar(er)
