[FFmpeg-user] Catching all error warnings via ffprobe
Kieran O Leary
kieran.o.leary at gmail.com
Mon Jul 6 10:39:34 EEST 2020
On Mon, Jun 29, 2020 at 11:12 AM Kieran O Leary <kieran.o.leary at gmail.com>
wrote:
> Hi - I've done some more tests and either I'm missing something here or
> perhaps this is a bug? It seems like only video errors appear in the JSON,
> not audio.
> I bumped up the loglevel, added and -show_error and I'm still not seeing
> the mp2 header issues appear in the json.
> For example this appears in the terminal:
>
> [mpegts @ 0000023d706538c0] Continuity check failed for pid 2069 expected
> 7 got 0
> [mpegts @ 0000023d706538c0] Continuity check failed for pid 2068 expected
> 10 got 9
> [mpegts @ 0000023d706538c0] PES packet size mismatch
> [mpegts @ 0000023d706538c0] Packet corrupt (stream = 1, dts = 203200560).
> [mp2 @ 0000023d70767e40] Header missing
>
> but I see no errors in the audio frames section of the JSON output:
> {
> "media_type": "audio",
> "stream_index": 1,
> "key_frame": 1,
> "pkt_pts": 203200560,
> "pkt_pts_time": "0:37:37.784000",
> "pkt_dts": 203200560,
> "pkt_dts_time": "0:37:37.784000",
> "best_effort_timestamp": 203200560,
> "best_effort_timestamp_time": "0:37:37.784000",
> "pkt_duration": 2160,
> "pkt_duration_time": "0:00:00.024000",
> "pkt_pos": "7371266244",
> "pkt_size": "1152",
> "sample_fmt": "s16p",
> "nb_samples": 1152,
> "channels": 2,
> "channel_layout": "stereo"
> },
>
> It seems that any errors for the audio streams are not making their way
> into the JSON, but the video errors are, as per my last email.
> Any guidance on how I can get these audio errors into the JSON - am I
> missing a command or is this a bug?
>
Just checking in again to see if anyone has any guidance here.
Best,
Kieran
>
More information about the ffmpeg-user
mailing list