Re: Re: [PATCH] ffmpeg preset support

--nextPart1610756.mJVyPB0ZAR
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Sunday 11 July 2010 21:17:37 Andrew Church wrote:
> >> Using transcode with ffmpeg+h264 causes some trouble with libx264
> >> erroring out with "broken ffmpeg default settings detected". libx264
> >> further suggests: "use an encoding preset (vpre)".
> >>
> >>=3D20
> >>
> >> The attached patch adds two config parameters to ffmpeg.cfg, "vpre" and
> >> "ffmpeg_datadir".
> >
> >Any news on this? Was the patch accepted, or are there any issues with i=
t?
>=20
> I'm afraid transcode development is currently dormant at best, as
> Francesco is no longer working on it and I have other priorities as well.
> With regard to this particular issue, however, transcode does have a
> native x264 interface (use e.g. -y x264,lame,avi -N h264,mp3) so there's
> no need to go through ffmpeg.

IIRC I was actually using some other application which in turn used=20
transcode+ffmpeg as a "backend".

--nextPart1610756.mJVyPB0ZAR
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEABECAAYFAkw5ti0ACgkQjqfyF1DtJW7mqgCfXfJVJ4Y6Rx/PKqUsYce4OLgK
V9wAoI+c+tRprKHwZwS14RYRa8+HxWky
=ElvF
-----END PGP SIGNATURE-----

--nextPart1610756.mJVyPB0ZAR--