[FFmpeg-devel] CrystalHD and ffmpeg probe behaviour

Michael Niedermayer michaelni at gmx.at
Sun Jan 15 15:13:39 CET 2012


On Sat, Jan 14, 2012 at 09:20:08PM -0800, Philip Langdale wrote:
> On Sun, 15 Jan 2012 00:26:53 +0100
> Reimar Döffinger <Reimar.Doeffinger at gmx.de> wrote:
> 
> > And also, a possible solution might be to prefer the CrystalHD decoder
> > so it is always used when it would work (i.e. compiled in, hardware
> > available, compatible format), while a bit risky it would only
> > affect people who have such a decoder so at least I don't mind
> > the risk :-)
> 
> Unfortunately, the decoder is a terrible choice for transcode work.
> It can't go faster than realtime and only returns yuyv422 frames, so
> there's a lossy conversion happening - and the conversion wastes CPU
> too. In almost all cases you are better off with the usual software
> decoder. That's why I never cared about making the transcode path
> work properly before, but I was contacted by a user who's got very
> specific circumstances where the crystalhd hardware could help him;
> he's trying to do streaming transcodes and doesn't have enough CPU
> power to decode and encode at the same time. I'm not fully convinced
> that once the bugs are fixed it will work, but it's enough for me
> to try and get it working.

did you try ffmpeg -vcodec ...crystalhd -i file ... ?


[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I know you won't believe me, but the highest form of Human Excellence is
to question oneself and others. -- Socrates
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20120115/d7b7da09/attachment.asc>


More information about the ffmpeg-devel mailing list