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

[FFmpeg]

#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: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.
 I tried to increase the MAX_SLICES size and compile it but it is behaving
 in the same way.
 > Please note that both "-b:v 512k -r 30" and "-b:v 512k -x264opts
 sar=352:288" are useless options: You cannot define a bitrate for the
 input sample, you cannot define a frame rate for a h264 input file, you
 cannot define a bitrate for yuv files and x264 options will not work for
 raw video output.
 > (-r 30 for output yuv files is ok, but redundant for your test case
 afaict.)
 > And please post command lines that actually work in this issue tracker
 (your command line uses variables that are not defined, please do not
 define them, use the file names instead).
 >
 >
 > The reference decoder only decodes 220 frames (bit-identical with
 FFmpeg), does your problem occur before or after? Is it possible to
 reproduce your problem with a smaller sample (for example three GOPs, with
 the error in the second)?
 > Is there a reason why you are intentionally producing h264 samples with
 high slice number without increasing MAX_SLICES in the FFmpeg source?

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