virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-18 03:19:31 +02:00
Code Issues Releases Activity
3ea60c505f
FFmpeg/tests/ref/fate/ffprobe_default

684 lines
11 KiB
Plaintext
Raw Normal View History

tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[PACKET]
codec_type=audio
stream_index=0
pts=0
pts_time=0.000000
dts=0
dts_time=0.000000
duration=1024
duration_time=0.023220
convergence_duration=N/A
convergence_duration_time=N/A
size=2048
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=642
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=audio
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=0
pkt_pts_time=0.000000
pkt_dts=0
pkt_dts_time=0.000000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=0
best_effort_timestamp_time=0.000000
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration=1024
pkt_duration_time=0.023220
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=642
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 14:41:24 +03:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
nb_samples=1024
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 21:15:12 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/FRAME]
[PACKET]
codec_type=video
stream_index=1
pts=0
pts_time=0.000000
dts=0
dts_time=0.000000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=230400
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=2717
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=0
pkt_pts_time=0.000000
pkt_dts=0
pkt_dts_time=0.000000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=0
best_effort_timestamp_time=0.000000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=2717
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=320
height=240
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=video
stream_index=2
pts=0
pts_time=0.000000
dts=0
dts_time=0.000000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=30000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=233138
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=0
pkt_pts_time=0.000000
pkt_dts=0
pkt_dts_time=0.000000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=0
best_effort_timestamp_time=0.000000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=233138
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=100
height=100
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=audio
stream_index=0
pts=1024
pts_time=0.023220
dts=1024
dts_time=0.023220
duration=1024
duration_time=0.023220
convergence_duration=N/A
convergence_duration_time=N/A
size=2048
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=263143
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=audio
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=1024
pkt_pts_time=0.023220
pkt_dts=1024
pkt_dts_time=0.023220
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=1024
best_effort_timestamp_time=0.023220
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration=1024
pkt_duration_time=0.023220
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=263143
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 14:41:24 +03:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
nb_samples=1024
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 21:15:12 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/FRAME]
[PACKET]
codec_type=video
stream_index=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pts_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
dts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
dts_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=230400
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=265221
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_pts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_pts_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_dts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_dts_time=0.040000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=2048
best_effort_timestamp_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=265221
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=320
height=240
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=video
stream_index=2
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pts_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
dts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
dts_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=30000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=495645
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_pts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_pts_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_dts=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_dts_time=0.040000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=2048
best_effort_timestamp_time=0.040000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=495645
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=100
height=100
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=audio
stream_index=0
pts=2048
pts_time=0.046440
dts=2048
dts_time=0.046440
duration=1024
duration_time=0.023220
convergence_duration=N/A
convergence_duration_time=N/A
size=2048
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=525650
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=audio
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=2048
pkt_pts_time=0.046440
pkt_dts=2048
pkt_dts_time=0.046440
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=2048
best_effort_timestamp_time=0.046440
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration=1024
pkt_duration_time=0.023220
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=525650
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 14:41:24 +03:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
nb_samples=1024
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 21:15:12 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/FRAME]
[PACKET]
codec_type=audio
stream_index=0
pts=3072
pts_time=0.069660
dts=3072
dts_time=0.069660
duration=1024
duration_time=0.023220
convergence_duration=N/A
convergence_duration_time=N/A
size=2048
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=527721
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=audio
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=3072
pkt_pts_time=0.069660
pkt_dts=3072
pkt_dts_time=0.069660
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=3072
best_effort_timestamp_time=0.069660
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration=1024
pkt_duration_time=0.023220
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=527721
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 14:41:24 +03:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
nb_samples=1024
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 21:15:12 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/FRAME]
[PACKET]
codec_type=video
stream_index=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pts_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
dts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
dts_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=230400
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=529799
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_pts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_pts_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_dts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_dts_time=0.080000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=4096
best_effort_timestamp_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=529799
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=320
height=240
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=video
stream_index=2
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pts_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
dts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
dts_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=30000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=760223
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_pts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_pts_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_dts=4096
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_dts_time=0.080000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=4096
best_effort_timestamp_time=0.080000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=760223
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=100
height=100
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=audio
stream_index=0
pts=4096
pts_time=0.092880
dts=4096
dts_time=0.092880
duration=1024
duration_time=0.023220
convergence_duration=N/A
convergence_duration_time=N/A
size=2048
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=790228
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=audio
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=4096
pkt_pts_time=0.092880
pkt_dts=4096
pkt_dts_time=0.092880
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=4096
best_effort_timestamp_time=0.092880
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration=1024
pkt_duration_time=0.023220
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=790228
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 14:41:24 +03:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
nb_samples=1024
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 21:15:12 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/FRAME]
[PACKET]
codec_type=audio
stream_index=0
pts=5120
pts_time=0.116100
dts=5120
dts_time=0.116100
duration=1024
duration_time=0.023220
convergence_duration=N/A
convergence_duration_time=N/A
size=2048
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=792299
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=audio
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
pkt_pts=5120
pkt_pts_time=0.116100
pkt_dts=5120
pkt_dts_time=0.116100
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=5120
best_effort_timestamp_time=0.116100
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration=1024
pkt_duration_time=0.023220
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=792299
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 14:41:24 +03:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
nb_samples=1024
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 21:15:12 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/FRAME]
[PACKET]
codec_type=video
stream_index=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pts_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
dts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
dts_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=230400
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=794377
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_pts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_pts_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_dts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_dts_time=0.120000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=6144
best_effort_timestamp_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=794377
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=320
height=240
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[PACKET]
codec_type=video
stream_index=2
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pts_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
dts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
dts_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
duration_time=0.040000
convergence_duration=N/A
convergence_duration_time=N/A
size=30000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pos=1024801
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
flags=K
[/PACKET]
[FRAME]
media_type=video
ffprobe: print stream_index with frame data This makes it easier to relate frame data to its associated stream.
2015-05-26 02:46:12 +02:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
key_frame=1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_pts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_pts_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_dts=6144
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_dts_time=0.120000
ffprobe: show best_effort_timestamp in the frame section This is useful for debugging. Reference and ffprobe.xsd changes done and tested by Stefano Sabatini. Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-11-28 13:24:34 +03:00
best_effort_timestamp=6144
best_effort_timestamp_time=0.120000
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
pkt_duration_time=0.040000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
pkt_pos=1024801
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 22:18:57 +03:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
width=100
height=100
pix_fmt=rgb24
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
[/FRAME]
[STREAM]
index=0
codec_name=pcm_s16le
profile=unknown
codec_type=audio
codec_time_base=1/44100
nut: put nut PCM audio tags in front of avi tags. This fixes correctly storing and identifying PCM in nut. Based on patch by Luca Barbato Found-by: durandal_1707 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-11-28 03:32:22 +03:00
codec_tag_string=PSD[16]
codec_tag=0x10445350
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
sample_fmt=s16
sample_rate=44100
channels=1
ffprobe: print stream channel_layout when available Fix trac ticket #3006.
2013-10-02 00:42:07 +03:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
bits_per_sample=16
id=N/A
r_frame_rate=0/0
avg_frame_rate=0/0
time_base=1/44100
start_pts=0
start_time=0.000000
nutdec: Implement duration parsing for indexed nuts Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2013-05-02 19:44:22 +03:00
duration_ts=N/A
duration=N/A
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
bit_rate=705600
ffprobe: add rc_max_rate to stream output The value is used by some bitstream to mark the maximum bit rate. See thread: Subject: [FFmpeg-devel] [PATCH] Add rc_max_rate to ffprobe stream output Date: Sun, 1 Jun 2014 17:36:36 +0100 To: ffmpeg-devel@ffmpeg.org http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/178461 Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2014-06-01 19:36:36 +03:00
max_bit_rate=N/A
Print bits_per_raw_sample for ffprobe -show_streams. Fixes ticket #3919.
2014-09-08 18:45:57 +03:00
bits_per_raw_sample=N/A
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
nb_frames=N/A
nb_read_frames=6
nb_read_packets=6
ffprobe: extend disposition printing support This generalizes the previous work on disposition printing. Disposition flags are shown in a dedicated section, which should improve output intellegibility, extensibility and filtering operations. This breaks output syntax with the recently introduced disposition printing.
2012-09-26 13:30:08 +03:00
DISPOSITION:default=0
DISPOSITION:dub=0
DISPOSITION:original=0
DISPOSITION:comment=0
DISPOSITION:lyrics=0
DISPOSITION:karaoke=0
DISPOSITION:forced=0
DISPOSITION:hearing_impaired=0
DISPOSITION:visual_impaired=0
DISPOSITION:clean_effects=0
DISPOSITION:attached_pic=0
fate/ffprobe: add some stream metadata.
2012-09-27 10:49:56 +03:00
TAG:E=mc²
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
TAG:encoder=Lavc pcm_s16le
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/STREAM]
[STREAM]
index=1
codec_name=rawvideo
profile=unknown
codec_type=video
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
codec_time_base=1/51200
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
codec_tag_string=RGB[24]
codec_tag=0x18424752
width=320
height=240
Merge commit '7b9cb7b36543c2a0e46d99b0e41824b9e7dd0c8f' * commit '7b9cb7b36543c2a0e46d99b0e41824b9e7dd0c8f': avprobe: Export coded_{width,height} in -show_streams Conflicts: avprobe.c Merged-by: Michael Niedermayer <michaelni@gmx.at>
2015-03-09 00:43:40 +02:00
coded_width=320
coded_height=240
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
has_b_frames=0
sample_aspect_ratio=1:1
display_aspect_ratio=4:3
pix_fmt=rgb24
level=-99
ffprobe: add color_range and color_space to stream output Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-06-17 10:01:07 +03:00
color_range=N/A
color_space=unknown
ffprobe: Add support for color_trc/color_pri/chroma_loc Idea from: a2c00d22e71d13b72828147be86aa9e961c6cae6 Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-10-10 05:36:03 +03:00
color_transfer=unknown
color_primaries=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
timecode=N/A
ffprobe: Support extracting the number of reference frames Fixes Ticket3141 Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-12-29 13:23:02 +02:00
refs=1
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
id=N/A
r_frame_rate=25/1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
avg_frame_rate=25/1
time_base=1/51200
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
start_pts=0
start_time=0.000000
nutdec: Implement duration parsing for indexed nuts Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2013-05-02 19:44:22 +03:00
duration_ts=N/A
duration=N/A
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
bit_rate=N/A
ffprobe: add rc_max_rate to stream output The value is used by some bitstream to mark the maximum bit rate. See thread: Subject: [FFmpeg-devel] [PATCH] Add rc_max_rate to ffprobe stream output Date: Sun, 1 Jun 2014 17:36:36 +0100 To: ffmpeg-devel@ffmpeg.org http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/178461 Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2014-06-01 19:36:36 +03:00
max_bit_rate=N/A
Print bits_per_raw_sample for ffprobe -show_streams. Fixes ticket #3919.
2014-09-08 18:45:57 +03:00
bits_per_raw_sample=N/A
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
nb_frames=N/A
nb_read_frames=4
nb_read_packets=4
ffprobe: extend disposition printing support This generalizes the previous work on disposition printing. Disposition flags are shown in a dedicated section, which should improve output intellegibility, extensibility and filtering operations. This breaks output syntax with the recently introduced disposition printing.
2012-09-26 13:30:08 +03:00
DISPOSITION:default=0
DISPOSITION:dub=0
DISPOSITION:original=0
DISPOSITION:comment=0
DISPOSITION:lyrics=0
DISPOSITION:karaoke=0
DISPOSITION:forced=0
DISPOSITION:hearing_impaired=0
DISPOSITION:visual_impaired=0
DISPOSITION:clean_effects=0
DISPOSITION:attached_pic=0
fate/ffprobe: add some stream metadata.
2012-09-27 10:49:56 +03:00
TAG:title=foobar
TAG:duration_ts=field-and-tags-conflict-attempt
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
TAG:encoder=Lavc rawvideo
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/STREAM]
[STREAM]
index=2
codec_name=rawvideo
profile=unknown
codec_type=video
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
codec_time_base=1/51200
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
codec_tag_string=RGB[24]
codec_tag=0x18424752
width=100
height=100
Merge commit '7b9cb7b36543c2a0e46d99b0e41824b9e7dd0c8f' * commit '7b9cb7b36543c2a0e46d99b0e41824b9e7dd0c8f': avprobe: Export coded_{width,height} in -show_streams Conflicts: avprobe.c Merged-by: Michael Niedermayer <michaelni@gmx.at>
2015-03-09 00:43:40 +02:00
coded_width=100
coded_height=100
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
has_b_frames=0
sample_aspect_ratio=1:1
display_aspect_ratio=1:1
pix_fmt=rgb24
level=-99
ffprobe: add color_range and color_space to stream output Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-06-17 10:01:07 +03:00
color_range=N/A
color_space=unknown
ffprobe: Add support for color_trc/color_pri/chroma_loc Idea from: a2c00d22e71d13b72828147be86aa9e961c6cae6 Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-10-10 05:36:03 +03:00
color_transfer=unknown
color_primaries=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
timecode=N/A
ffprobe: Support extracting the number of reference frames Fixes Ticket3141 Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-12-29 13:23:02 +02:00
refs=1
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
id=N/A
r_frame_rate=25/1
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-02 00:51:35 +03:00
avg_frame_rate=25/1
time_base=1/51200
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
start_pts=0
start_time=0.000000
nutdec: Implement duration parsing for indexed nuts Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2013-05-02 19:44:22 +03:00
duration_ts=N/A
duration=N/A
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
bit_rate=N/A
ffprobe: add rc_max_rate to stream output The value is used by some bitstream to mark the maximum bit rate. See thread: Subject: [FFmpeg-devel] [PATCH] Add rc_max_rate to ffprobe stream output Date: Sun, 1 Jun 2014 17:36:36 +0100 To: ffmpeg-devel@ffmpeg.org http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/178461 Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2014-06-01 19:36:36 +03:00
max_bit_rate=N/A
Print bits_per_raw_sample for ffprobe -show_streams. Fixes ticket #3919.
2014-09-08 18:45:57 +03:00
bits_per_raw_sample=N/A
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
nb_frames=N/A
nb_read_frames=4
nb_read_packets=4
ffprobe: extend disposition printing support This generalizes the previous work on disposition printing. Disposition flags are shown in a dedicated section, which should improve output intellegibility, extensibility and filtering operations. This breaks output syntax with the recently introduced disposition printing.
2012-09-26 13:30:08 +03:00
DISPOSITION:default=0
DISPOSITION:dub=0
DISPOSITION:original=0
DISPOSITION:comment=0
DISPOSITION:lyrics=0
DISPOSITION:karaoke=0
DISPOSITION:forced=0
DISPOSITION:hearing_impaired=0
DISPOSITION:visual_impaired=0
DISPOSITION:clean_effects=0
DISPOSITION:attached_pic=0
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
TAG:encoder=Lavc rawvideo
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
[/STREAM]
[FORMAT]
filename=tests/data/ffprobe-test.nut
nb_streams=3
ffprobe: add -show_programs option The option is used to sort the streams by program. Signed-off-by: Florent Tribouilloy <florent.tribouilloy@smartjog.com> Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
2013-07-25 13:55:40 +03:00
nb_programs=0
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
format_name=nut
start_time=0.000000
nutdec: Implement duration parsing for indexed nuts Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2013-05-02 19:44:22 +03:00
duration=0.120000
ffmpeg: prefix encoder with "Lavc " in bitexact mode This avoids misleading encoder names like "encoder = prores" Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-18 23:51:27 +03:00
size=1054882
bit_rate=70325466
fate: update fate tests after master:291ad12ea2d1: ffprobe: show probe_score in the format section Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2013-09-01 13:53:24 +03:00
probe_score=100
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
TAG:title=ffprobe test file
tests/fate-ffprobe: fix typo in metadata comment
2012-09-24 11:32:52 +03:00
TAG:comment='A comment with CSV, XML & JSON special chars': <tag value="x">
tests: add fate-ffprobe test
2012-09-17 22:08:46 +03:00
TAG:comment2=I ♥ Üñîçød€
[/FORMAT]
Reference in New Issue Copy Permalink