On Fri, 1 Mar 2019, at 22:21, D. Michael McIntyre wrote: > Come to think of it, I know there have been perennial problems with one > of the advanced timers that have caused endless mayhem. I ran lsmod and > I have snd_hrtimer loaded. I looked at the startup debug stream and see > that Rosegarden is picking "system timer." That sounds right. Vague > memory is that Chris would have preferred the HR timer, but it was > unstable, and given more recent discussion, it still is, so Rosegarden > defaults to something that usually works.
My rather faint recollection is it went something like - System timer: always available, but not always reliable because various power-saving things can mess with it - before those adaptive things appeared, we had the choice between reliable-but-jittery 100Hz stock kernel and reliable-and-clean fixed-rate 1000Hz timer settings available in multimedia kernels. I don't know whether multimedia kernels with such timers still exist - HR timer: good if working, but used to be very unreliable, able to lock up the whole system - soundcard timers: good if you have an audio stream running (e.g. if JACK is in use against the same soundcard) but of no use otherwise, which is why they can't be the default Who knows, things might have changed in the last couple of decades. And there must surely be better ways to do this in new code - this choice was always a crap one. > I wish time hadn't dulled my once sharp memory so much. Ah, yes. Welcome to the... wherever we are. Time goes faster as you get older, of course. So the things you're trying to remember, which you think of as recent, are more than a decade old - that would have been a while back at any age. Chris _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
