[FFmpeg-user] Some guidence on finding this problem.

JULIAN GARDNER joolzg at btinternet.com
Wed Aug 3 12:47:01 EEST 2016


Well I have managed to copy a .ts which has the problem, had to record over 8 hours of tv just for this.
Run the command line and around 8.02 seconds it fails.
Now this is with version ffmpeg version N-78956-g920f592 and ffmpeg version 3.0.2


MEGA

|   |
|   |  |   |   |   |   |   |
| MEGAMEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 50GB now! |
|  |
| View on mega.nz | Preview by Yahoo |
|  |
|   |


minimum command line is
ffmpeg -i failure_chomped.ts -c:v libx265 -c:a libfaac -async 1 -y -f failure.ts
or add a scale for faster testffmpeg -i failure_chomped.ts -c:v libx265 -vf 'scale=640x360' -c:a libfaac -async 1 -y -f failure.ts
output gives
encoder at encoder:~$ ffmpeg -i failure_chomped.ts -c:v libx265 -c:a libfaac -y -f mpegts a.ts
ffmpeg version N-78956-g920f592 Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
  configuration: --bindir=/home/encoder/bin --enable-gpl --enable-version3 --enable-nonfree --disable-ffserver --disable-dxva2 --disable-vaapi --disable-vda --disable-vdpau --disable-libxcb --enable-libmp3lame --enable-postproc --enable-libfaac --enable-libzvbi --enable-libx264 --enable-libx265 --cc='ccache cc'
  libavutil      55. 19.100 / 55. 19.100
  libavcodec     57. 28.100 / 57. 28.100
  libavformat    57. 28.100 / 57. 28.100
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 39.102 /  6. 39.102
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc    54.  0.100 / 54.  0.100
[h264 @ 0x2c33b40] Increasing reorder buffer to 2
Input #0, mpegts, from 'failure_chomped.ts':
  Duration: 00:00:20.09, start: 0.009744, bitrate: 9985 kb/s
  Program 1 
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
    Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 50 tbr, 90k tbn, 50 tbc
    Stream #0:1[0x101](NAR): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s
    Stream #0:2[0x102](eng): Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo, fltp, 384 kb/s
x265 [info]: HEVC encoder version 1.9+54-291beccb6760
x265 [info]: build info [Linux][GCC 4.8.4][64 bit] 8bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x265 [info]: Main profile, Level-4 (Main tier)
x265 [info]: Thread pool created using 8 threads
x265 [info]: frame threads / pool features       : 3 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut       : 25 / 250 / 40
x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
x265 [info]: References / ref-limit  cu / depth  : 3 / 1 / 1
x265 [info]: AQ: mode / str / qg-size / cu-tree  : 1 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress            : CRF-28.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 signhide tmvp strong-intra-smoothing
x265 [info]: tools: lslices=6 deblock sao
[hls,mpegts @ 0x2c36dc0] HLS Enabled 0
Output #0, hls,mpegts, to 'a.ts':
  Metadata:
    encoder         : Lavf57.28.100
    Stream #0:0: Video: hevc (libx265), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 25 fps, 90k tbn, 25 tbc
    Metadata:
      encoder         : Lavc57.28.100 libx265
    Stream #0:1(NAR): Audio: aac (libfaac), 48000 Hz, stereo, s16, 128 kb/s
    Metadata:
      encoder         : Lavc57.28.100 libfaac
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
  Stream #0:1 -> #0:1 (mp2 (native) -> aac (libfaac))
Press [q] to stop, [?] for help
[hls,mpegts @ 0x2c36dc0] Packets poorly interleaved, failed to avoid negative timestamp -5280 in stream 0.   
Try -max_interleave_delta 0 as a possible workaround.
[hls,mpegts @ 0x2c36dc0] Packets poorly interleaved, failed to avoid negative timestamp -1680 in stream 0.
Try -max_interleave_delta 0 as a possible workaround.
[h264 @ 0x2f13640] left block unavailable for requested intra4x4 mode -1 at 0 0/s dup=7 drop=1 speed=0.718x    
[h264 @ 0x2f13640] error while decoding MB 0 0, bytestream 90043
[h264 @ 0x2d225a0] Reference 2 >= 2
[h264 @ 0x2d225a0] error while decoding MB 20 0, bytestream 12154
[h264 @ 0x2d69500] Reference 2 >= 2
[h264 @ 0x2d69500] error while decoding MB 20 1, bytestream 11501
[h264 @ 0x2db0460] Reference 2 >= 2
[h264 @ 0x2db0460] error while decoding MB 68 12, bytestream 5526
[h264 @ 0x2df73c0] Reference 4 >= 2
[h264 @ 0x2df73c0] error while decoding MB 99 13, bytestream 5991
[h264 @ 0x2e3e460] Reference 2 >= 2
[h264 @ 0x2e3e460] error while decoding MB 39 14, bytestream 5495
[h264 @ 0x2ecc5a0] Reference 2 >= 2
[h264 @ 0x2ecc5a0] error while decoding MB 1 0, bytestream 22016
[h264 @ 0x2f13640] Reference 4 >= 2
[h264 @ 0x2f13640] error while decoding MB 2 1, bytestream 17445
[h264 @ 0x2d225a0] top block unavailable for requested intra4x4 mode -1 at 1 1
[h264 @ 0x2d225a0] error while decoding MB 1 1, bytestream 7127
[h264 @ 0x2d69500] top block unavailable for requested intra4x4 mode -1 at 10 0
[h264 @ 0x2d69500] error while decoding MB 10 0, bytestream 4482
[h264 @ 0x2df73c0] Reference 2 >= 2
[h264 @ 0x2df73c0] error while decoding MB 25 16, bytestream 4664
[h264 @ 0x2e3e460] Reference 2 >= 2
[h264 @ 0x2e3e460] error while decoding MB 85 13, bytestream 4554
[h264 @ 0x2e85500] Reference 8 >= 4
[h264 @ 0x2e85500] error while decoding MB 26 0, bytestream 11033
[h264 @ 0x2ecc5a0] Reference 5 >= 2
[h264 @ 0x2ecc5a0] error while decoding MB 7 1, bytestream 9995
[h264 @ 0x2f13640] Reference 2 >= 2
[h264 @ 0x2f13640] error while decoding MB 11 0, bytestream 6345
[h264 @ 0x2c6b040] Reference 2 >= 2
[h264 @ 0x2c6b040] error while decoding MB 22 1, bytestream 5825
[h264 @ 0x2d69500] Reference 2 >= 2  344kB time=00:00:09.13 bitrate= 308.7kbits/s dup=7 drop=1 speed=0.719x    
[h264 @ 0x2d69500] error while decoding MB 81 11, bytestream 2716
[h264 @ 0x2db0460] Reference 3 >= 2
[h264 @ 0x2db0460] error while decoding MB 118 12, bytestream 2138
[h264 @ 0x2e3e460] top block unavailable for requested intra mode at 45 0
[h264 @ 0x2e3e460] error while decoding MB 45 0, bytestream 10651
[h264 @ 0x2ecc5a0] Reference 2 >= 2
[h264 @ 0x2ecc5a0] error while decoding MB 11 0, bytestream 5889
[h264 @ 0x2f13640] Reference 2 >= 2
[h264 @ 0x2f13640] error while decoding MB 6 1, bytestream 5593
[h264 @ 0x2d225a0] Reference 2 >= 2
[h264 @ 0x2d225a0] error while decoding MB 94 13, bytestream 2835

 Joolz 

    On Tuesday, 2 August 2016, 14:11, JULIAN GARDNER <joolzg at btinternet.com> wrote:
 
 

 Im reporting this as a decoding issue due to the fact that 2 different machines using 2 different encoding backends fail the EXACT same way, and when they fail the encoded picture looks EXACTLY the same on both outputs.

I will start a TS Recording and then try and chop this up to get a small TS with the failure but as the stream is HD at source will be a big recording.
The command lines for the 2 encodings are different as one use x265 and the other a bought in hardware encoder.
Joolz 

    On Tuesday, 2 August 2016, 14:05, Carl Eugen Hoyos <ceffmpeg at gmail.com> wrote:
 
 

 Hi!

2016-08-02 11:05 GMT+02:00 JULIAN GARDNER <joolzg at btinternet.com>:
> I have 2 machines running ffmpeg, one is doing normal transcoding the 2nd is using a bought in h265 hardware encoder.
> Software HEVC encoding is based onffmpeg N-78956-g920f592x265 1.9_54-291beccb6760
> Hardware HEVC encoding is based onffmpeg 3.0.2

If the issue you see is not reproducible with current FFmpeg, there is
nothing that we can fix.

> Now I am sure that x265 and the hardware encoding are not to blame and believe that the software decoding is at fault as BOTH versions fail at the same time and show the exact same video output once they have failed.

Sorry, I am not a native speaker and I find this difficult to understand:
Are you reporting a decoding issue? How is it related to the encoding
properties you describe above?

> My problem is that this happens once every 2-5 days so my question is how do i capture what will be needed to give you guys a good stream to try and fix this problem.

How does the command look that you are currently using to decoder? If
you provide it, it should be easy to know how to capture.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user at ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".

 
   

 
  


More information about the ffmpeg-user mailing list