On 06/11/14 18:12, Carl Eugen Hoyos wrote:
Paulo Fidalgo gmail.com> writes:
mp3check -ve 2L38_01_96kHz-ffmpeg-256k.mp3
2L38_01_96kHz-ffmpeg-256k.mp3:
813 bytes of junk before first frame header
but with lame there's no errors.
Please confirm that you tested with "-write_xing 0"
and your res
Michael Heuberger binarykitchen.com> writes:
> All I want is to make the video compatible on *modern*
> browsers/players
Then you have to use "-pix_fmt yuv420p" which is
different from "yuvj420p" and I believe "good players"
are rare.
> I also want to make the warning disappear ffmpeg is
>
On 2014-11-10 11:43, Michael Heuberger wrote:
> Hello guys
>
> If you look at the bug report at https://trac.ffmpeg.org/ticket/4098 you
> can see that I am confused about the pix_fmt option.
>
> I am not sure what parameter to use for this option. All I want is to
> make the video compatible on *
Hello guys
If you look at the bug report at https://trac.ffmpeg.org/ticket/4098 you
can see that I am confused about the pix_fmt option.
I am not sure what parameter to use for this option. All I want is to
make the video compatible on *modern* browsers/players only and I also
want to make the wa
C E Macfarlane macfh.co.uk> writes:
> ./libavutil/libm.h:88: error: static declaration of
> 'fminf' follows non-static declaration
The code that was responsible for this compilation
problem was removed from the FFmpeg source.
Note that afaik, the error indicates that libm.h
and libm (the head
