Discussion on a bug report about how HEAD is starting a "generating audio
preview" thread for every audio segment simultaneously got me thinking in
This doc has 250 audio segments, a couple of huge ones and a whole bunch of
little ones. They haven't changed in a month. Why is RG generating audio
previews? Isn't that what these silly .pk files all over my hard disk are
I haven't looked at what .pk files actually do, or how they're used by the
code, but this is what my intuition tells me they must be. (Do correct, if
So if the .pk files are already there, and the audio file hasn't changed since
the last time the .pk file was generated, why generate a new one?
One reason I can see to generate .pk files at every load is to catch files
that have been edited by other applications between loads. I have an ancient
bug outstanding about how RG fails to react when using the "open in external
editor" option. Regenerating at file load prevents another variation of that
bug from emerging.
But surely there must be some middle ground? Keep track of what the creation
time and size of the file were before, and if it hasn't changed, don't
regenerate the preview? Something?
I don't know, maybe this isn't really the issue I think it is. I never really
noticed any of this before because Rosegarden never really called my
attention to it. I created this file with an earlier post-segment-canvas
Rosegarden, and I loaded this file lots of times. This current horrible
state is a new thing, and at this point I'm not sufficiently aware of what
has changed when (since June 23) to know what to blame for this.
Michael McIntyre ---- Silvan <dmmcintyr@...>
Linux fanatic, and certified Geek; registered Linux user #243621
Get latest updates about Open Source Projects, Conferences and News.