"Frank 'Sigi' Luithle" wrote:
> As far as I understand it, one can invoke the tool with an infile/outfile,
> so that it copies some (default) settings into the GUI and sets the
> load/save paths accordingly.
So far correct.
> dvd::rip already seems to do this, since for a new project I get
> '~/.transcode/xvid4.cfg' as the load path and '$PATH_TO_PROJECT/xvid4.cfg'
> as the save path.
>
> Only, the values from '~/.transcode/' don't seem to get loaded into the GUI.
> On first invocation, I still have to press 'Load' manually to load the
> values from '.transcode' dir.
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
not, xvid4conf uses hardcoded initial values.
Once you saved your settings to $PROJECT/tmp/xvid4.cfg, dvd::rip uses
this file on subsequent invocations of xvdi4conf as the "infile"
parameter.
I just wanted to verify this and I think I found a bug in xvid4conf (at
least the version I use: 1.5). I tried to save to
"~/.transcode/xvid4.cfg". This failed: "Cannot save config to
~/.transcode/xvid4.cfg". I resolved ~ to /home/joern manually and it
works.
So it looks that xvid4conf cannot resolve ~ to the home directory of the
user, at least not for saving and probably for loading also.
When you call xvdi4conf manually using ~/.transcode/xvid4.conf, the
resolution of ~ is done by the shell and it works.
I didn't check recent version of xvid4conf, probably this bug got fixed
already. Otherwise: Tilmann, it's your turn ;)
Regards,
Joern
--
Joern Reder
Development Head ZYN! Coding Division - http://www.zyn.de/
pgp00017.pgp
Description: PGP signature
|