Re: Probably a bug in xvid4conf (was: Re: [dvd::rip] Loading of xvid4conf presets)

["Frank 'Sigi' Luithle" <sigi@xxxxxxxxxxxxxxxxxxx>]

On Sat, Jan 24, 2004 at 01:00:52PM +0100, it was written by Jörn Reder:

> dvd::rip maintains a xvid4.cfg file per project 
> ($PROJECT/tmp/xvid4.cfg). On first invocation no $PROJECT/tmp/xvid4.cfg
> exists, so dvd::rip omits the "infile" parameter of xvid4conf and 
> xvid4conf internally sets ~/.transcode/xvid4.cfg as the default load 
> filename. If it exists, xvid4conf should initialize the GUI from it. If

Paths/filenames are there, but loading does not happen.

> not, xvid4conf uses hardcoded initial values.

It does use defaults, and only when I press "Load settings", my settings out
of '~/.transcode/xvid4.cfg' are being loaded.  I just checked that again
with a freshly created dvd::rip project.

Although, if I run xvid4conf *by hand* with infile/outfile, the settings are
being loaded.

I've just had a look at 'TranscodeTab.pm'.  There, you invoke 'xvid4conf'
with only an outfile, for the case when there is not project-specifig
xvid4.cfg yet.  Probably xvid4conf interprets that as not to load any
config from file (it still fills in the default load path, which I think is
a bit confusing here).

See my attached patch for 'TranscodeTab.pm' that fixes the problem.

> Once you saved your settings to $PROJECT/tmp/xvid4.cfg, dvd::rip uses 
> this file on subsequent invocations of xvdi4conf as the "infile" 
> parameter.

That does work.

> So it looks that xvid4conf cannot resolve ~ to the home directory of the
> user, at least not for saving and probably for loading also.

This bug is fixed, as Tillmann pointed out already (and it wasn't my
problem).

--Frank

workaround-xvid4conf.patch
Description: Text document