In MuseScore 1.x, the tick2 value for an ottava was the end tick of the last affected note. Some time ago in the trunk this was changed to the start tick in of the last note. This leads to various forms of weird behavior. E.g., when replacing the last note in an octave by two smaller notes, only the first one is affected. Similarly, when a number of 1/4 notes are in an ottava, and a second voice containing 1/8 notes is added, the last 1/8 note is unexpected not affected by the ottava. Similar issues may be present in other elements with a start and end tick.
Furthermore, this has broken the MusicXML importer and exporter wrt the timing of a.o. octave shifts, as shown by issues in the regression test files testLines1.xml, testSlurs.xml and testWedge2.xml. Of course, this can be fixed in the MusicXML importer and exporter and I am perfectly OK with doing so. Given the, IMHO, somewhat illogical design of the tick2 value, I'd like to know first if this is the design we stick with for 2.0. To me, it seems a better idea to go back to the 1.x definition of tick2. If that will happen before 2.0, it is a waste of my time to fix the MusicXML importer and exporter for the current design. -- View this message in context: http://dev-list.musescore.org/ottava-tick2-weirdness-tp7578621.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
