To ChickenMan: Batch encode

[me@work]

Hello,
I just read you're doing lots of batch encodes with D2S. Well, so do I. One thing that always bugged me is that in my configuration the log files cumulate, i.e. the last logfile contains all the logging information of the previous encodes of this run.
Could you please be so kind and confirm this or, maybe even better, tell me about a way to circumvent that? Thanks in advance.

[ChickenMan]

To be honest I'd never really looked, but checking, you are correct. The log file just gets big and bigger with all previous logs included for that session.

How to get rid of them I would have no idea where to start. And to be honest, I really cant see any problem with it that way anyway. If there was ever a problem and things stop, then its always the last one anyway.

[me@work]

Well, you know, for some odd reason I'd like to include the logfile on the SVCD. It adds some info that's not in SVCDINFO.TXT like exact size of movie in frames etc.
Therefore, I prefer to have only the related logfile included onto the respective CD image ;-)

For the time being, I extended the batch file so that after every encode the logfile gets renamed in the processed folder. That gives a fresh logfile for every new run. But this, of course, leaves me with lots of manual work to be done if I have to correct some problems in the encode, like adjusting the length of the audio file, remux, etc.pp.

What I found out from manual recovery, is that if I change the working folder to the appropriate directory prior to loading the .d2s file, then the correct logfile gets info added to. If I simply load the .d2s file from the folder to be processed, then the folder change seems to happen afterwards, and the logfile from the previously used folder is written into the now working folder, thus deleting the 'old' (or 'correct') logfile.
For that reason it's not possible to automate the let's call it second run after my manual intervention.

Maybe it's on the wishlist for version 2.0 ...