ffmpeg-2.4 creates grey screen, corrupted videos

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

ffmpeg-2.4 creates grey screen, corrupted videos

S Andreason
Hi,

After upgrading mplayer to 2.4, I was unable to play h264 videos with
the tag major_brand=qt made by several cameras.
I discovered that I could create a h264 file using ffmpeg-1.0.1 and x264
(yesterday's snapshot), and recreate the mplayer problem. Since this
version of ffmpeg is old (but very functional), I upgraded it today.

Unfortunately instead of fixing my problem, this made it worse. Now I
can't create _any_ videos that work correctly, even down to the mjpeg
codec. They are all grey with blocks drawn down from the top.
Screenshot:
http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990-f1.jpg

Exact command:
ffmpeg-2.4 -v 9 -loglevel 99 -i 20140128_pond-W_rec10990.mov -c:v h264
-s 640x360 -c:a copy 20140128_pond-W_rec10990-640x360.2x264.avi >
ffmpeg-2.4-rec10990.x264.log 2>&1

http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990.mov
http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990-640x360.2x264.avi
http://seahorseCorral.org/videos/tests/ffmpeg-2.4-rec10990.x264.log

Regression test: Exact command:
ffmpeg-1.0.1 -v 9 -loglevel 99 -i 20140128_pond-W_rec10990.mov -c:v h264
-s 640x360 -c:a copy 20140128_pond-W_rec10990-640x360.1x264.avi >
ffmpeg-1.0-rec10990.x264.log 2>&1

http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990-640x360.1x264.avi
http://seahorseCorral.org/videos/tests/ffmpeg-1.0-rec10990.x264.log

Results:
anything made with ffmpeg-2.4 is grey and corrupted with errors, whereas
the ffmpeg-1.0 videos are good.
Playing any file with ffplay-2.4 is grey and corrupted, even older
videos that are fine, now play as bad.

Playing the above files in an older mplayer or ffplay work fine with
older videos and the original video, but not the one made by ffmpeg-2.4,
or the ones made with ffmpeg-1.0 and x264.
Also confirmed when loading 20140128_pond-W_rec10990-640x360.2mjpeg.avi
into avidemux.

Looking at mplayer output:
http://seahorseCorral.org/videos/tests/mplayer-svn20110120-rec10990.2x264.log
http://seahorseCorral.org/videos/tests/mplayer-svn20110120-rec10990.1x264.log
The only real difference, is the line
Suggested BufferSize:

My system information can be found in my request for help from
Mplayer-users,
http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990.txt

I assume some library is too old, but not checked in the configure
script. What else could cause this?

Stewart

--
http://seahorseCorral.org

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg-2.4 creates grey screen, corrupted videos

Carl Eugen Hoyos
S Andreason <sandreas41 <at> gmail.com> writes:

> After upgrading mplayer to 2.4, I was unable to
> play h264 videos with the tag major_brand=qt
> made by several cameras.

What does 'upgrading mplayer to 2.4' mean?

[...]

> http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990.mov

I tested the following command line:
$ ffmpeg -i 20140128_pond-W_rec10990.mov -s 640x360
-qscale 2 -acodec copy out.avi
and the result plays fine here.

Please test current git head, releases are only
supported here if you are a distributor yourself.

Your configure line looks slightly broken (although
this shouldn't be the reason for a problem), please
test with './configure --enable-gpl --enable-libx264'
and your compiler is incredibly old.
I suggest you recompile, if this doesn't help, please
compile once without --enable-libx264 to rule that
out as a possible source of trouble.

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg-2.4 creates grey screen, corrupted videos

S Andreason
Carl Eugen Hoyos wrote:
> What does 'upgrading mplayer to 2.4' mean?
>
>  

Oops. Aspie made one typo.
Meant 1.1.1


>> http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990.mov
>>    
>
> I tested the following command line:
> $ ffmpeg -i 20140128_pond-W_rec10990.mov -s 640x360
> -qscale 2 -acodec copy out.avi
> and the result plays fine here.
>
> Please test current git head, releases are only
> supported here if you are a distributor yourself.
>
>  
Getting anything by git is impossible on dialup. 10Mb per hour, 4 hour
maximum connection.
Thus the act of getting stable releases does still have a purpose.


> Your configure line looks slightly broken (although
> this shouldn't be the reason for a problem), please
> test with './configure --enable-gpl --enable-libx264'
> and your compiler is incredibly old.
>  

Old compile arguments were holdovers from earlier versions.
Tried that, wasn't the problem.
Upgrading the compiler was a major task, but seeing the new precision
math modules now required, this problem I encountered makes complete
sense now.

Solved. Requirement of new gcc which requires mpfr,mpc, and gmp does
solve the problem.

Thank you,
Stewart

--
http://seahorseCorral.org

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg-2.4 creates grey screen, corrupted videos

Carl Eugen Hoyos
S Andreason <sandreas41 <at> gmail.com> writes:

> Carl Eugen Hoyos wrote:
> > What does 'upgrading mplayer to 2.4' mean?
>
> Oops. Aspie made one typo.
> Meant 1.1.1

Just to make sure:
MPlayer 1.1.1 is completely outdated, please do
not use it.

> >> http://seahorseCorral.org/videos/tests/20140128_pond-W_rec10990.mov
> >
> > I tested the following command line:
> > $ ffmpeg -i 20140128_pond-W_rec10990.mov -s 640x360
> > -qscale 2 -acodec copy out.avi
> > and the result plays fine here.
> >
> > Please test current git head, releases are only
> > supported here if you are a distributor yourself.
> >
> Getting anything by git is impossible on dialup.
> 10Mb per hour, 4 hour maximum connection.

Sounds like one more reason to use git.

> Thus the act of getting stable releases does still have a purpose.

We provide snapshots as well but I don't see how large
files are easier to download than small increasing
changes.

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user