[FFmpeg-devel] [PATCH] ffmpeg: raise level for message printed in case of auto-select pixel format
Michael Niedermayer
michaelni at gmx.at
Thu Aug 1 03:30:40 CEST 2013
On Wed, Jul 31, 2013 at 02:46:22PM +0200, Stefano Sabatini wrote:
[...]
>
> Operating ffmpeg requires a varying level of sofistication depending
> on the performed task.
yes
> When interoperability is involved, you need to
> know what are the target device requirements, and there is no way
> ffmpeg can magically understand what they are but it is duty of the
> user to specify them.
>
> > and IMHO ffmpeg isnt different for other people
> > ffmpeg -i inputfile outputfile
> > should just work
>
> You just need an IA who asks questions to the users about what they
> want, and who is able to interpret their answers (as alternative, a
> knowledgeable human operator).
At the risk of repeating myself but the question is about the default
in the absence of additional information.
Or stated differently the user told you to encode to h264 and that
pretty much implies that he wants h264 that works for an UNSPECIFIED
target or ANY target.
like compiling C without extra switches generates a program that
works on ANY reasonable variant of the host platform
whats so hard on that so that we drift of in a discussion about
a-bombs and spaceships (not mass produced items intended to be used by
the general public currently)
We do want ffmpeg to be useable by the general public for genral tasks
the average joe might want to do.
like "hey i want to convert my ogg to mp3, target device huh i want to
share with friends no idea what they or their friends will use it on
...."
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- 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/20130801/c6d8d4c6/attachment.asc>
More information about the ffmpeg-devel
mailing list