OK, I've just committed a feature into HEAD that I'd originally added on the new 1.1 unstable branch: latency compensation.
This is a wee bit risky, but I hope it shouldn't break anything, it doesn't add anything to the GUI, and seems like the sort of fundamental thing that ought to be in place for 1.0 in order to ensure it gets tested and people don't get confused if their composition timings suddenly change after 1.0. So, the principle is easy enough: each instrument has a certain processing latency which depends on the plugins (effects and synths -- not all plugins publish their latency timings, but some do; this is particularly useful for VST plugins wrapped by dssi-vst, which introduces quite high processing latency) on the instrument as well as the JACK output latency (dependent on the JACK period size). Rosegarden now adjusts the timings accordingly to try to ensure all your tracks match up in spite of this. Chris ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
