On Monday 06 October 2003 1:53 pm, Chris Cannam wrote: > Well, either you store the whole tempo map or else you have to go > back to the GUI to ask for more at some point.
Not if the GUI is just pushing values into the Control block whenever it changes. So the sequencer just relys on the information in the control block as being what's current to generate its sync clock or metronome. > Current and next could work as a tolerable hack if we were confident > we weren't going to get tempo changes really frequently, but I'm not > sure I'd want to bet on that particularly if they were generated in > some continuous way. Better than nothing, but it might be just as > easy to store the whole lot. Well I'm only thinking of efficacy here - in other words I think I get how the ControlBlock maps 'cos it's nice and simple, mapping the whole lot (and ensuring it's refreshed at the right time) might be a tortuous path for me at the moment (not least the refresh cycle which I've never really got even from the gui refresh work). Anyway, further thoughts appreciated. R ------------------------------------------------------- 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
