On Sat, Mar 1, 2014 at 6:54 AM, Lieven Moors <[email protected]> wrote:

> On Thu, Feb 20, 2014 at 11:47:12PM +0100, Lieven Moors wrote:
> > > > Yes. The only reason the snapshot would be out of sync with the
> history is
> > > > if non-timeline is closed abnormally. If this happens, upon the next
> > > > opening, non-timeline will load by replaying the entire history
> instead of
> > > > utilizing the outdated snapshot. You can detect this scenario in your
> > > > scripts by comparing the file timestamps.
> >
> > Sorry to reply to myself, but wouldn't it be best to add this to the
> > remove-unused-sources script? I had a quick look, but it doesn't seem to
> > compare file timestamps, in order to decide for $ONLY_COMPACTED...
>
> When thinking about it, this still wouldn't solve my problem.
> I've been making commits in git while non-timeline was running.
> In that case the history file would contain information that is
> needed to clean up unused sources.
>
> So for me it would be very useful if there would be an option to the
> non programs, that would just replay the journal, make a snapshot, and
> quit.
> Also, that would make it possible to use the remove-unused-sources script
> in all circumstances.
>
> But I can understand if you wouldn't care too much for this specific
> use case.
>
>
So, are you hoping to do this after every time you close a session or
something? Personally, I only use the remove-unused-sources script on
session that A) I know involved a lot of extra takes and B) is completely
finished to the point where I feel complete confidence in deleting the
unused takes and their sources. And this brings up another point. If you
have old takes, their sources will still be 'used' until you delete the
takes (but if you're not using the 'takes' feature, then what you see on
the timeline is all that will be considered 'used' after compaction).

I should also point out that the format of the 'history' file is very
simple and it would be fairly easy for someone to write e.g. a perl script
that parses it line by line and tracks the creation/deletion of regions to
identify the final set of in-use files.

I might be able to add a commandline option to run the compaction operation
and then exit, but ensuring that it works without opening the GUI might
take some effort.

Reply via email to