[FFmpeg-trac] #628(undetermined:new): Frame copy concealment is not working for h.264

FFmpeg trac at avcodec.org
Wed Nov 9 20:25:50 CET 2011


#628: Frame copy concealment is not working for h.264
-------------------------------------+-------------------------------------
             Reporter:               |                    Owner:  michael
  hardiksharma                       |                   Status:  new
                 Type:  defect       |                Component:
             Priority:  normal       |  undetermined
              Version:  git-master   |               Resolution:
             Keywords:  h264         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by hardiksharma):

 Replying to [comment:3 cehoyos]:The video streams which I am getting for
 my experiments are raw yuv 300 frame streams. The scheme I am trying to
 implement in post-processing need same number of frames as input. I don't
 think I can get more frames for same video sequence. In my other
 experiment with everything same, I am not facing this error and that is
 even for 150 frames because there is no frame which is included in one
 slice. Don't you think it's a failure of frame copy?

 I also agree with you that as this defect is only coming in probably last
 two gops only so if I can increase the number of gops by two and then
 delete them in the end probably I can recover from this error but I only
 have exact number of frame sequence for the implementation.

 I am totally agree that the output will look much nicer but in this
 particular version, it didn't compiled properly. I don't know the exact
 reason but I will try as soon as we can sort out this problem.
 > Replying to [comment:2 hardiksharma]:
 > > Replying to [comment:1 cehoyos]: My problem occurs after 220 frames
 because B frame with size lesser then my slice size (with only one slice)
 is coming in last gops only. It is reproducible anywhere if our frame size
 is lesser then slice size or one slice means one frame and if user dropped
 that slice to introduce error.
 >
 > Is there a reason you cannot add more frames (with even more slices if
 that is really necessary) and then cut away GOPs in the beginning of the
 streams so you have (for example) three (or five) GOPs with the error
 occurring in the middle of the sample?
 >
 > > I tried to increase the MAX_SLICES size and compile it but it is
 behaving in the same way.
 >
 > But don't you agree that the output looks significantly nicer?
 > (Although you should mention if you changed the source.)

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/628#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list