[FFmpeg-trac] #2379(undetermined:new): FFmpeg produces broken h264 output.
FFmpeg
trac at avcodec.org
Sun Mar 24 13:47:24 CET 2013
#2379: FFmpeg produces broken h264 output.
-------------------------------------+-------------------------------------
Reporter: dodgexander | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: git-master | undetermined
Keywords: | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by dodgexander):
Yes,I think, but not sure yet the problem with the stuttering/juddering
frames was not using libx264, but instead the copy encoder.
I have opened a ticket on MCEBuddy's tracker about it and I will try
repeat the bug using ffmpeg directly too. Once I can repeat the problem
ill open a new ticket on here if needed, try to make it clearer that way.
The only remaining problems I have after this are:
[https://ffmpeg.org/trac/ffmpeg/ticket/2220]
{{{
av_interleaved_write_frame(): Invalid argument
}}}
<---- Preventing me from using the copy encoder with some h264 .wtv
recordings.
[https://ffmpeg.org/trac/ffmpeg/ticket/2227]
<---- And another case you are involved in, this case is stopping me from
using the copy encoder on a lot of mpeg2 .wtv files using MCEBuddy. They
remux, remux again and remux a third time, I guess because as ramit
explains, the detection by ffmpeg seems to conflict with other
applications.
If you're interested, you can take a look at my case open on the MCEBuddy
tracker related to this: [http://mcebuddy2x.codeplex.com/workitem/1478]
Thanks for your time and sorry for getting my information mixed up. These
kind of problems are a whole new level to me.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2379#comment:39>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list