On Monday 06 Oct 2003 12:16 pm, Richard Bown wrote: > Each MidiDevice > _should_ have a MidiMetronome attached to it
Hmm... is that the case at the moment? I think they may often be null. I'm a little confused again though as it looks like the MidiDevice itself might only have a metronome if there's one in the .rg file... the presence of a metronome instrument (as created at the sequencer in AlsaDriver::addInstrumentsForDevice) doesn't seem to guarantee a corresponding MidiMetronome. Oh, my head. Certainly the metronome _instrument_ is only created for the first device, not for every device. (AlsaDriver.cpp:793) > Going forward with metronome and tempo/timesig etc - for > implementation of the new JACK transport correctly we'll need to > know (and to be able to control) tempo and timesig (potentially) > from the sequencer. Piss, then that _does_ mean we need to duplicate the whole tempo map at the sequencer. (See the "quid tempo?" thread of a few days ago in which I resisted that idea.) Otherwise the sequencer has no way to know the current tempo (i.e. tempo at current play time) without polling the GUI continuously during playback or having the GUI shove tempo changes continuously at it, and either way we'd be back where we started in terms of sequencer performance. If a tempo change comes in on the JACK transport during playback (is that a possible thing?) then do we want to drop a tempo change into the composition at the current point? I guess we have to. > Presumably something to do with the control block to define > "current tempo/timesig" should be enough? Sadly not. 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
