On Saturday 27 Sep 2003 4:13 pm, Guillaume Laurent wrote: > Er, there doesn't seem to be any reference in the sequencer about > tempo... was that only a UI-side setting which was working on the > slices the sequencer would get ?
One of the principal differences between Events and MappedEvents is that Events store time in timeT values and MappedEvents store time in RealTime values. The tempo comes into play when converting from timeT to RealTime to create the MappedEvents. This is a fairly complicated calculation, which in the current code is invoked at mmapper.cpp:441 through a call to Composition::getElapsedRealTime to get the RealTime corresponding to a timeT. In other words, the data received by the sequencer should already have the tempo taken into account. And since Composition::addTempo and friends already call updateRefreshStatuses, any change to tempo should be reflected in the sequencer already. I realise that may not help much. Chris ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
