Hi i'm just wondering where the time stretchers shall receive their keyframes from. all of these considerations will only affect the accurateness of time-stretched wave parts/events.
basically there are two ways: 1. always conform to the tempo map. this will work very fine when the tempomap is actually used, and is not changed "live". this will also work fine when MusE is running on external tempo sync, but the external tempo hasn't changed. MusE would then, during the last (full!) playback, record the externally supplied tempo, and use this (old) tempomap for the new playback. this WILL glitch when the external tempo changed. because then, MusE still adheres to the *old* tempo map, which is out-of-date. this MIGHT glitch when the user edits the tempo near the playing position *while playing*. Or uses the 200% / 50% button. 2. do weird guesswork, resulting in un-understandable code, and non- optimal timings whenever there's a tempo slope. especially this will also happen when there's a tempomap available, and while the final downmix! 3. even weirder hybrid of both. Basically, i want and probably will go with 1. But is it okay for the user, that "unexpected" tempo changes might cause a single glitch during playback? Playing back a second time won't glitch any more, because muse knows about the new tempo map then. Just say "yes" :) greetings, flo
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
