RepoMirrors
/
ffmpeg
mirror of https://git.ffmpeg.org/ffmpeg.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
ffmpeg/tests/ref/fate/ffprobe_default

780 lines
13 KiB
Plaintext
Raw Normal View History

tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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
size=2048
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=669
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=0
pts_time=0.000000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00:00
best_effort_timestamp=0
best_effort_timestamp_time=0.000000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration=1024
pkt_duration_time=0.023220
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=1024
duration_time=0.023220
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=669
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 11:41:24 +00:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 18:15:12 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=230400
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=2744
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=0
pts_time=0.000000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=2744
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=320
height=240
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=30000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=233165
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=0
pts_time=0.000000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=233165
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=100
height=100
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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
size=2048
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=263170
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=1024
pts_time=0.023220
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00:00
best_effort_timestamp=1024
best_effort_timestamp_time=0.023220
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration=1024
pkt_duration_time=0.023220
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=1024
duration_time=0.023220
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=263170
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 11:41:24 +00:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 18:15:12 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
pts=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
dts=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=230400
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=265248
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=2048
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-01 21:51:35 +00:00
pkt_dts=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=265248
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=320
height=240
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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-01 21:51:35 +00:00
pts=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
dts=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=30000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=495672
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=2048
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-01 21:51:35 +00:00
pkt_dts=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=495672
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=100
height=100
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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
size=2048
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=525677
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=2048
pts_time=0.046440
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00:00
best_effort_timestamp=2048
best_effort_timestamp_time=0.046440
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration=1024
pkt_duration_time=0.023220
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=1024
duration_time=0.023220
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=525677
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 11:41:24 +00:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 18:15:12 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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
size=2048
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=527748
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=3072
pts_time=0.069660
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00:00
best_effort_timestamp=3072
best_effort_timestamp_time=0.069660
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration=1024
pkt_duration_time=0.023220
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=1024
duration_time=0.023220
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=527748
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 11:41:24 +00:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 18:15:12 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
pts=4096
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
dts=4096
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=230400
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=529826
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=4096
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-01 21:51:35 +00:00
pkt_dts=4096
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=529826
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=320
height=240
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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-01 21:51:35 +00:00
pts=4096
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
dts=4096
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=30000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=760250
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=4096
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-01 21:51:35 +00:00
pkt_dts=4096
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=760250
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=100
height=100
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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
size=2048
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=790255
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=4096
pts_time=0.092880
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00:00
best_effort_timestamp=4096
best_effort_timestamp_time=0.092880
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration=1024
pkt_duration_time=0.023220
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=1024
duration_time=0.023220
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=790255
fate: update fate for 1a490df12fd9 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-15 11:41:24 +00:00
pkt_size=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 18:15:12 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/FRAME]
[PACKET]
codec_type=audio
stream_index=0
pts=5120
pts_time=0.116100
dts=5120
dts_time=0.116100
fate: update ffprobe stuff after dbc7f02a727286f3 Signed-off-by: Paul B Mahol <onemda@gmail.com>
2017-02-26 16:05:43 +00:00
duration=393
duration_time=0.008912
size=786
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=792326
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=5120
pts_time=0.116100
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 10:24:34 +00:00
best_effort_timestamp=5120
best_effort_timestamp_time=0.116100
fate: update ffprobe stuff after dbc7f02a727286f3 Signed-off-by: Paul B Mahol <onemda@gmail.com>
2017-02-26 16:05:43 +00:00
pkt_duration=393
pkt_duration_time=0.008912
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=393
duration_time=0.008912
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=792326
fate: update ffprobe stuff after dbc7f02a727286f3 Signed-off-by: Paul B Mahol <onemda@gmail.com>
2017-02-26 16:05:43 +00:00
pkt_size=786
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
sample_fmt=s16
fate: update ffprobe stuff after dbc7f02a727286f3 Signed-off-by: Paul B Mahol <onemda@gmail.com>
2017-02-26 16:05:43 +00:00
nb_samples=393
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
channels=1
lavc: do not init frame with guessed layout. It is breaking support from files with unknown layout.
2013-03-14 18:15:12 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
pts=6144
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
dts=6144
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=230400
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=793142
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=1
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=6144
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-01 21:51:35 +00:00
pkt_dts=6144
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=793142
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=230400
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=320
height=240
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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-01 21:51:35 +00:00
pts=6144
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
dts=6144
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
duration_time=0.040000
size=30000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pos=1023566
ffprobe: report the corrupt flag on packets Signed-off-by: Anton Khirnov <anton@khirnov.net>
2023-01-11 01:55:32 +00:00
flags=K__
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/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 00:46:12 +00:00
stream_index=2
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
key_frame=1
ffprobe: remove references to frame->pkt_pts The field was removed during the last major bump. Signed-off-by: James Almer <jamrial@gmail.com>
2021-07-14 15:48:10 +00:00
pts=6144
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-01 21:51:35 +00:00
pkt_dts=6144
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:24:34 +00: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-01 21:51:35 +00:00
pkt_duration=2048
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
pkt_duration_time=0.040000
ffprobe: print AVFrame.duration
2022-07-11 08:31:47 +00:00
duration=2048
duration_time=0.040000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
pkt_pos=1023566
avcodec/utils: ff_decode_frame_props: set pkt_size Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-05-01 19:18:57 +00:00
pkt_size=30000
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
width=100
height=100
fftools/ffprobe: print crop_* frame fields Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2023-03-26 19:28:38 +00:00
crop_top=0
crop_bottom=0
crop_left=0
crop_right=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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
ffprobe: Print color properties from show_frames Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
2017-07-20 12:37:44 +00:00
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=unspecified
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/FRAME]
[STREAM]
index=0
codec_name=pcm_s16le
profile=unknown
codec_type=audio
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 00:32:22 +00:00
codec_tag_string=PSD[16]
codec_tag=0x10445350
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
sample_fmt=s16
sample_rate=44100
channels=1
ffprobe: print stream channel_layout when available Fix trac ticket #3006.
2013-10-01 21:42:07 +00:00
channel_layout=unknown
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
bits_per_sample=16
fftools/ffprobe: Report initial and trailing padding Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
2022-09-01 12:42:00 +00:00
initial_padding=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
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 16:44:22 +00:00
duration_ts=N/A
duration=N/A
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 16:36:36 +00:00
max_bit_rate=N/A
Print bits_per_raw_sample for ffprobe -show_streams. Fixes ticket #3919.
2014-09-08 15:45:57 +00:00
bits_per_raw_sample=N/A
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:30:08 +00: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
lavf: add AV_DISPOSITION_TIMED_THUMBNAILS Reviewed-By: Michael Niedermayer <michael@niedermayer.cc>
2016-10-24 10:47:05 +00:00
DISPOSITION:timed_thumbnails=0
ffprobe: print the non-diegetic stream disposition flag Signed-off-by: James Almer <jamrial@gmail.com>
2023-10-26 00:51:22 +00:00
DISPOSITION:non_diegetic=0
fftools/ffprobe: Add missing dispositions Reviewed-by: Marton Balint <cus@passwd.hu> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
2021-03-29 12:18:47 +00:00
DISPOSITION:captions=0
DISPOSITION:descriptions=0
DISPOSITION:metadata=0
DISPOSITION:dependent=0
DISPOSITION:still_image=0
fate/ffprobe: add some stream metadata.
2012-09-27 07:49:56 +00: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 20:51:27 +00:00
TAG:encoder=Lavc pcm_s16le
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/STREAM]
[STREAM]
index=1
codec_name=rawvideo
profile=unknown
codec_type=video
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-08 22:43:40 +00:00
coded_width=320
coded_height=240
fftools/ffprobe: show closed caption info in the stream dump Signed-off-by: vectronic <hello.vectronic@gmail.com> Signed-off-by: Marton Balint <cus@passwd.hu>
2020-04-29 16:14:33 +00:00
closed_captions=0
avcodec: add a Film Grain codec property flag Signed-off-by: James Almer <jamrial@gmail.com>
2021-08-16 15:08:56 +00:00
film_grain=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
has_b_frames=0
sample_aspect_ratio=1:1
display_aspect_ratio=4:3
pix_fmt=rgb24
level=-99
ffprobe: use consistent string for unspecified color_range value Makes the handling of unspecified/unknown color_range values on stream level consistent to the value used on frame level. Signed-off-by: Tobias Rapp <t.rapp@noa-archive.com>
2017-08-29 08:51:05 +00:00
color_range=unknown
ffprobe: add color_range and color_space to stream output Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-06-17 07:01:07 +00:00
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 02:36:03 +00:00
color_transfer=unknown
color_primaries=unknown
chroma_location=unspecified
ffprobe: report field order for video streams
2016-10-04 04:49:09 +00:00
field_order=unknown
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 11:23:02 +00:00
refs=1
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
avg_frame_rate=25/1
time_base=1/51200
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 16:44:22 +00:00
duration_ts=N/A
duration=N/A
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 16:36:36 +00:00
max_bit_rate=N/A
Print bits_per_raw_sample for ffprobe -show_streams. Fixes ticket #3919.
2014-09-08 15:45:57 +00:00
bits_per_raw_sample=N/A
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
nb_frames=N/A
nb_read_frames=4
nb_read_packets=4
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
DISPOSITION:default=1
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 10:30:08 +00:00
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
lavf: add AV_DISPOSITION_TIMED_THUMBNAILS Reviewed-By: Michael Niedermayer <michael@niedermayer.cc>
2016-10-24 10:47:05 +00:00
DISPOSITION:timed_thumbnails=0
ffprobe: print the non-diegetic stream disposition flag Signed-off-by: James Almer <jamrial@gmail.com>
2023-10-26 00:51:22 +00:00
DISPOSITION:non_diegetic=0
fftools/ffprobe: Add missing dispositions Reviewed-by: Marton Balint <cus@passwd.hu> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
2021-03-29 12:18:47 +00:00
DISPOSITION:captions=0
DISPOSITION:descriptions=0
DISPOSITION:metadata=0
DISPOSITION:dependent=0
DISPOSITION:still_image=0
fate/ffprobe: add some stream metadata.
2012-09-27 07:49:56 +00: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 20:51:27 +00:00
TAG:encoder=Lavc rawvideo
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
[/STREAM]
[STREAM]
index=2
codec_name=rawvideo
profile=unknown
codec_type=video
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-08 22:43:40 +00:00
coded_width=100
coded_height=100
fftools/ffprobe: show closed caption info in the stream dump Signed-off-by: vectronic <hello.vectronic@gmail.com> Signed-off-by: Marton Balint <cus@passwd.hu>
2020-04-29 16:14:33 +00:00
closed_captions=0
avcodec: add a Film Grain codec property flag Signed-off-by: James Almer <jamrial@gmail.com>
2021-08-16 15:08:56 +00:00
film_grain=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
has_b_frames=0
sample_aspect_ratio=1:1
display_aspect_ratio=1:1
pix_fmt=rgb24
level=-99
ffprobe: use consistent string for unspecified color_range value Makes the handling of unspecified/unknown color_range values on stream level consistent to the value used on frame level. Signed-off-by: Tobias Rapp <t.rapp@noa-archive.com>
2017-08-29 08:51:05 +00:00
color_range=unknown
ffprobe: add color_range and color_space to stream output Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2014-06-17 07:01:07 +00:00
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 02:36:03 +00:00
color_transfer=unknown
color_primaries=unknown
chroma_location=unspecified
ffprobe: report field order for video streams
2016-10-04 04:49:09 +00:00
field_order=unknown
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 11:23:02 +00:00
refs=1
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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-01 21:51:35 +00:00
avg_frame_rate=25/1
time_base=1/51200
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 16:44:22 +00:00
duration_ts=N/A
duration=N/A
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 16:36:36 +00:00
max_bit_rate=N/A
Print bits_per_raw_sample for ffprobe -show_streams. Fixes ticket #3919.
2014-09-08 15:45:57 +00:00
bits_per_raw_sample=N/A
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:30:08 +00: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
lavf: add AV_DISPOSITION_TIMED_THUMBNAILS Reviewed-By: Michael Niedermayer <michael@niedermayer.cc>
2016-10-24 10:47:05 +00:00
DISPOSITION:timed_thumbnails=0
ffprobe: print the non-diegetic stream disposition flag Signed-off-by: James Almer <jamrial@gmail.com>
2023-10-26 00:51:22 +00:00
DISPOSITION:non_diegetic=0
fftools/ffprobe: Add missing dispositions Reviewed-by: Marton Balint <cus@passwd.hu> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
2021-03-29 12:18:47 +00:00
DISPOSITION:captions=0
DISPOSITION:descriptions=0
DISPOSITION:metadata=0
DISPOSITION:dependent=0
DISPOSITION:still_image=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 20:51:27 +00:00
TAG:encoder=Lavc rawvideo
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 10:55:40 +00:00
nb_programs=0
fftools/ffprobe: add support for Stream Groups Reviewed-by: Stefano Sabatini <stefasab@gmail.com> Signed-off-by: James Almer <jamrial@gmail.com>
2024-03-02 19:03:20 +00:00
nb_stream_groups=0
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00: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 16:44:22 +00:00
duration=0.120000
ffmpeg: rewrite setting the stream disposition Currently, the code doing this is spread over several places and may behave in unexpected ways. E.g. automatic 'default' marking is only done for streams fed by complex filtergraphs. It is also applied in the order in which the output streams are initialized, which is effectively random. Move processing the dispositions at the end of open_output_file(), when we already have all the necessary information. Apply the automatic default marking only if no explicit -disposition options were supplied by the user, and apply it to the first stream of each type (excluding attached pics) when there is more than one stream of that type and no default markings were copied from the input streams. Explicitly document the new behavior. Changes the results of some tests, where the output file gets a default disposition, while it previously did not.
2021-11-12 16:22:57 +00:00
size=1053646
bit_rate=70243066
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 10:53:24 +00:00
probe_score=100
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
TAG:title=ffprobe test file
tests/fate-ffprobe: fix typo in metadata comment
2012-09-24 08:32:52 +00:00
TAG:comment='A comment with CSV, XML & JSON special chars': <tag value="x">
tests: add fate-ffprobe test
2012-09-17 19:08:46 +00:00
TAG:comment2=I ♥ Üñîçød€
[/FORMAT]