On Fri, Nov 8, 2013, at 03:07 AM, Tom Breton (Tehom) wrote: > Fundamentally, the idea is to have a bulletproof bar rewriter (Rewriter) > that takes as much time as it needs to notate everything nicely.
Sounds like an excellent principle. On first test it looks a bit too eager to override decisions the user has already made elsewhere in the bar. For example, try opening the Ravel test piece, finding the section with 12-tuplets in the right hand and then selecting and deleting one note from within any of the tuplet groups. In trunk, when a note is deleted, the rest of the group remains intact as a 12-tuplet (as do the other groups in the bar). However, the note that is deleted is replaced with "un-tupleted" rests, whose displayed duration is therefore not correct (this is one of the many things that makes an overhaul a good idea in principle). In the new branch, the rest that replaces the deleted note is calculated correctly, but at the same time the whole bar is rewritten into triplets, which isn't desirable either. It's a mistake to assume there is any one canonical structure for the notes in a bar and that they can be automatically rewritten correctly based only on their timings. If the user has introduced groupings already, they should be respected. Chris ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
