ffprobe reported data

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

ffprobe reported data

Alvaro Jimenez
Does FFPROBE report stream info by reading metadata or it actually decodes the stream to report media specs?

H:\>ffprobe -show_streams http://www.bok.net/dash/tears_of_steel/cleartext/stream.mpd >> ffprobe_results.txt
ffprobe version N-90866-g48330500ef Copyright (c) 2007-2018 the FFmpeg developers
  built with gcc 7.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
  libavutil      56. 17.100 / 56. 17.100
  libavcodec     58. 19.100 / 58. 19.100
  libavformat    58. 13.100 / 58. 13.100
  libavdevice    58.  4.100 / 58.  4.100
  libavfilter     7. 20.100 /  7. 20.100
  libswscale      5.  2.100 /  5.  2.100
  libswresample   3.  2.100 /  3.  2.100
  libpostproc    55.  2.100 / 55.  2.100
[AVIOContext @ 000001bcb8e39140] The "user-agent" option is deprecated: use the "user_agent" option instead
    Last message repeated 1 times
[http @ 000001bcb8e31100] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8e31100] The "user-agent" option is deprecated: use the "user_agent" option instead
[http @ 000001bcb8e5e940] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8e5e940] The "user-agent" option is deprecated: use the "user_agent" option instead
[http @ 000001bcb8e7c540] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8e7e600] The "user-agent" option is deprecated: use the "user_agent" option instead
[http @ 000001bcb8e8d540] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8e8d880] The "user-agent" option is deprecated: use the "user_agent" option instead
[http @ 000001bcb8ea2bc0] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8ea54c0] The "user-agent" option is deprecated: use the "user_agent" option instead
[http @ 000001bcb8ece600] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8ea8480] The "user-agent" option is deprecated: use the "user_agent" option instead
[http @ 000001bcb8ee9280] The "user-agent" option is deprecated: use the "user_agent" option instead
[dash @ 000001bcb8e2d7c0] Could not read complete fragment.
[http @ 000001bcb8ee9280] The "user-agent" option is deprecated: use the "user_agent" option instead
Input #0, dash, from 'http://www.bok.net/dash/tears_of_steel/cleartext/stream.mpd':
  Duration: 00:12:14.00, start: 0.000000, bitrate: 0 kb/s
  Program 0
    Stream #0:0: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 512x214 [SAR 535:534 DAR 640:267], 12 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc
    Metadata:
      variant_bitrate : 686685
      id              : video/1
    Stream #0:1: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 704x294 [SAR 980:979 DAR 640:267], 16 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc
    Metadata:
      variant_bitrate : 1116150
      id              : video/2
    Stream #0:2: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 512x214 [SAR 535:534 DAR 640:267], 12 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc
    Metadata:
      variant_bitrate : 686685
      id              : video/3
    Stream #0:3: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1024x428 [SAR 535:534 DAR 640:267], 23 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc
    Metadata:
      variant_bitrate : 1929169
      id              : video/4
    Stream #0:4: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1152x482 [SAR 2410:2403 DAR 640:267], 27 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc
    Metadata:
      variant_bitrate : 2362822
      id              : video/5
    Stream #0:5: Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1280x534 [SAR 1:1 DAR 640:267], 27 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc
    Metadata:
      variant_bitrate : 2470094
      id              : video/6
    Stream #0:6: Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 129 kb/s
    Metadata:
      variant_bitrate : 132348
      id              : audio/en





     [http://graphics.hotmail.com/emarrow_right.gif]   Alvaro Jimenez  [http://graphics.hotmail.com/emarrow_left.gif]

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: ffprobe reported data

Carl Eugen Hoyos-2
2018-05-18 22:27 GMT+02:00, Alvaro Jimenez <[hidden email]>:
> Does FFPROBE report stream info by reading metadata or it actually
> decodes the stream to report media specs?

That depends on what you mean with "stream info".
Some of the printed information is metadata (like "id", some information
(like resolution and pix_fmt) needs decoding.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: ffprobe reported data

Alvaro Jimenez
The issue that I have at hand is that I have some streams that are showing 5 Mbps for bitrate, but the engineers writing some code say that they are encoding at 1024 kbps. The 5 Mbps is being reported from metadata, but the encoding engine is just passing along an arbitrary metadata file with the stream, which is incorrect.

I use ffprobe thinking that it is actually probing the media stream. Decoding a segment and reporting the metrics that it finds.
I'd like to get the actual decoded data details. Specially bitrate.

Thanks for your help.

     [http://graphics.hotmail.com/emarrow_right.gif]   Alvaro C. Jimenez  [http://graphics.hotmail.com/emarrow_left.gif]

________________________________
From: ffmpeg-user <[hidden email]> on behalf of Carl Eugen Hoyos <[hidden email]>
Sent: Tuesday, May 22, 2018 1:37 PM
To: FFmpeg user questions
Subject: Re: [FFmpeg-user] ffprobe reported data

2018-05-18 22:27 GMT+02:00, Alvaro Jimenez <[hidden email]>:
> Does FFPROBE report stream info by reading metadata or it actually
> decodes the stream to report media specs?

That depends on what you mean with "stream info".
Some of the printed information is metadata (like "id", some information
(like resolution and pix_fmt) needs decoding.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: ffprobe reported data

Carl Eugen Hoyos-2
2018-06-29 21:53 GMT+02:00, Alvaro Jimenez <[hidden email]>:
> The issue that I have at hand is that I have some streams
> that are showing 5 Mbps for bitrate

To know the actual bitrate of a media stream (assuming a "real"
codec, not something that by definition has constant frame size),
you have to decode (or at least parse) the whole stream.

You forgot to show the command line you are using together
with the complete, uncut console output but I suspect the 5M
are the maximum bitrate reported by the stream.

Please do not top-post here, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".