[XviD-devel] Better idea for transcode config
Edouard Gomez
xvid-devel@xvid.org
Sun, 26 Jan 2003 23:34:56 +0100
--vGgW1X5XWziG23Ko
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Christoph Lampert (chl@math.uni-bonn.de) wrote:
> Hi Edouard,
>=20
> maybe passing XVID options via transcode isn't too good
That's the conclusion i had when i proposed the xvid.cfg idea. If we
wanted to keep things human understandable and _usable_, i had to use a
file.
> but=20
> how about environment variables? That should be compatible and=20
> easy to check via getenv().
It's feasible.
> At least an alternative name instead of "xvid.cfg" would be good to
> support.=20
That one seems more logical, and someone proposed an option into
transcode to pass the config filename to modules. I did never
implemented it because the only thing i know in transcode internals is
the export module part. I never looked at other parts of transcode.
Btw, if you want to script things it's not that hard to generate a
config file the same way you generate a command line.
for i in `seq $number_of_tests` ; do
# Get here the parameters from somewhere
# ${FRAME_OPTIONS} ${FRAME_GENERAL} ... ${MAX_BFRAMES}
cat > ~/.xvidcvs.cfg << EOF
[quality0]
frame.motion =3D ${FRAME_OPTIONS}
frame.general =3D ${FRAME_GENERAL}
param.max_bframes =3D ${MAX_BFRAMES}
param.bquant_ratio =3D ${BQUANT_RATIO}
param.bquant_offset =3D ${BQUANT_OFFSET}
param.global =3D ${GLOBAL}
EOF
transcode -i ${input_file} -o ${output_file} -x ... -y xvidcvs,null -Q 0
done
Btw, if you tell me exactly what you want then i could adapt the module
for your needs.
--=20
Edouard Gomez
--vGgW1X5XWziG23Ko
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+NGKQR5dTYz5sWMcRAjidAKDqL77qX3+5JMfhja9IRxWOPccgHQCg1YG3
G+isg1FER6O57sK4mT+QqNo=
=py3T
-----END PGP SIGNATURE-----
--vGgW1X5XWziG23Ko--