generic-library/ffmpeg
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
8bf16e677f
ffmpeg/tests/ref/lavfi/pixfmts_pixdesctest

102 lines
5.2 KiB
Plaintext
Raw Normal View History

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 23:51:35 +02:00
0bgr 2b46a6ce47a19ffc240e4e93f498f491
0rgb e90e5d377a3e5af69fdf7b60cbf88f51
abgr 1a147fa04ed70b9a7e67a4c89052f630
argb 997df0b5c268a0d8f9c611cae4e01e05
bgr0 b61591a68252e66c576b9bb074a9eaed
bgr24 d6370f6dc34df2ea66e1718baf74137b
bgr444be aba6dfea008ae12c2120a95f54293904
bgr444le cfb5401e8f076cc8675e17ed1114a3df
bgr48be ab65229b64606f6408cd732b967c0b01
bgr48le f1b4e718cadee9bd2978289153ce43de
bgr4_byte de96505ef9ad7078f87b4dfdf6fe4b61
bgr555be 8d5de9e9200d622f27dc73958a85045c
bgr555le 74eb9837706143a40e26305a16a79369
bgr565be 13a36d6502be88fc0c2aec05b8d2d501
bgr565le ed027571692aecd522aa65a90cc7e09b
bgr8 71ef789609c746c2e7e4be9dec29062c
bgra 0364b074268682ea46168742a8239f7d
gray 1e5e2b8548843a6898eedd9c974c422c
gray16be 389f4e5a8ab413b3af32767b59ed7f9e
gray16le a1f912941247e45b394b9cf4f0e81130
monob 309b5785a36bd988d17e15d88f4ffad1
monow 8809a02bc69b58d1114b09ca79ebffad
nv12 75e90c54d858b993e99f4ee6d2a2a38f
nv21 8831a3f411015d45fbc5dd191245ba9c
pal8 13de2a1c3c80cb64d14e2bc4f6f461d0
rgb0 5774780b3c532896300fa326fcde01a8
rgb24 c71ba90f69f15c8275232bb3f62d0ced
rgb444be 26eaec65d7efd2b0c9c13b47dfd9b241
rgb444le 5f29863553107110ea817f52151d77b7
rgb48be a3bc81c46c21818a989f23104a599ab0
rgb48le e87c661ac49aea1f1e93939802883d92
rgb4_byte 293b1b84f01efd90bde40cb3faffc127
rgb555be 5229183fa64d4e5c7e3703d8263ee6ae
rgb555le c3e9978cb2a4129a5575935e8cbc433a
rgb565be bc123b962629ead1a06af0c18cbb6e5f
rgb565le 20757fafe4756e62d845b2ab4c0b8f93
rgb8 e01614f5416dcc8ad365ad7a57afc9fb
rgba 53796fa4c392a1b2659595b6a284f8c4
uyvy422 3f411f947e3ac8f842c88e717d68bd9a
yuv410p 7dcf3f4770c8b494290ceacd2c2ce6db
yuv411p 9461b188dab6f8b90d9a27e353a89f58
yuv420p 61fffd2d8425759a33ae07e718d0242d
yuv420p10be 2abf90242cb021cb6fcf9f2c3c92f6a7
yuv420p10le 180b7e4de684c7225d2fb37614f842cb
yuv420p12be 256c9e6cfc878a8abf681b30777c0620
yuv420p12le 8dc8b86c4790da3769d4a62e87608623
yuv420p14be 8d22756c5d2b9e501924c082bfb22a6c
yuv420p14le c9da19d4818bcb119ad6481b75778f7e
yuv420p16be 4ccdcca6dd6a960f9a3333f0aee095bd
yuv420p16le 9c5847d9b0de258a10ee906dc47e24ea
yuv420p9be fa7ad4f73232aac0e35def62af1e2c39
yuv420p9le 3720ba1786b56c8f4913e67dddebbb07
yuv422p eee223e92f1f2e5ad4186b411ebf5816
yuv422p10be 80fa87750491dcc3e93d175b64835654
yuv422p10le e1640cd315bd96c6b59f7753825a7306
swscale: fix 12 and 14 bit YUV planar output with scaling. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-01 03:31:48 +01:00
yuv422p12be 5c6d86e919515d1af71f8004a6252f9e
yuv422p12le 7f331cadb0ab75d07656d29f47bd8bd9
yuv422p14be 4f4e186ba683b90fe990cccc4db7e521
yuv422p14le d78016c9119b1f1d1c922bd5aaf47732
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 23:51:35 +02:00
yuv422p16be 1f3c216927d17966a009a42def124bba
yuv422p16le 90adbdffaeea9b09398339c8a1322b02
yuv422p9be e46446534dd0821029d3b831c9c1d1b0
yuv422p9le 520e418a2429f7efee511b7fcbf45ab6
yuv440p 456d83524b299f2fa1bb988e421554d9
yuv444p 068bc09d282d18c9fa35c2787943fc2a
yuv444p10be 9f6e1490080a454243daee9229425e1e
yuv444p10le cc183e51041351d9ac06c4df6e8ad5f7
swscale: fix 12 and 14 bit YUV planar output with scaling. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-12-01 03:31:48 +01:00
yuv444p12be 34f63ac6a47ac681016105d3bfb3e118
yuv444p12le 7964701bfe8d718edf97f6e0002935bd
yuv444p14be 4ad3a9d52fe9c050150c0f7d2f3cf63d
yuv444p14le 69575e5a94b978f159c4fdb1a61587b0
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 23:51:35 +02:00
yuv444p16be 4000b12fa88ed0feef182da31c7e6b96
yuv444p16le 96a857dba8dc6792c58daec872825b32
yuv444p9be 07727e5c9040b7f0a17d591288ac330d
yuv444p9le 4d12d20a68dc28618594c96c2ade4ff4
yuva420p 3a8c5c142e051367c196f95696e0e2c3
sws: fix BE/LE handling for fillPlane16() Based on fill_plane9or10() by luca barbato Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-30 18:11:52 +01:00
yuva420p10be 1b7c5ec6691498e24676ce6ed97f62f8
Merge remote-tracking branch 'qatar/master' * qatar/master: pixfmt: support more yuva formats swscale: support gray to 9bit and 10bit formats configure: rewrite print_config() function using awk FATE: fix (AD)PCM test dependencies broken in e519990 Use ptrdiff_t instead of int for intra pred "stride" function parameter. x86: use PRED4x4/8x8/8x8L/16x16 macros to declare intrapred prototypes. Conflicts: libavcodec/h264pred.c libavcodec/h264pred_template.c libavutil/pixfmt.h libswscale/swscale_unscaled.c tests/ref/lavfi/pixdesc tests/ref/lavfi/pixfmts_copy tests/ref/lavfi/pixfmts_null tests/ref/lavfi/pixfmts_scale tests/ref/lavfi/pixfmts_vflip Merged-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-30 17:41:17 +01:00
yuva420p10le ad2d0424033e7acbafa6d58f59b4487e
yuva420p16be 6afcf758f4b66c0b4173c942d42212d7
yuva420p16le 13e195aa96329eb49921b6f9f07b875c
sws: fix BE/LE handling for fillPlane16() Based on fill_plane9or10() by luca barbato Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-30 18:11:52 +01:00
yuva420p9be 05a78390de312dfd21ac666a9da05fbd
Merge remote-tracking branch 'qatar/master' * qatar/master: pixfmt: support more yuva formats swscale: support gray to 9bit and 10bit formats configure: rewrite print_config() function using awk FATE: fix (AD)PCM test dependencies broken in e519990 Use ptrdiff_t instead of int for intra pred "stride" function parameter. x86: use PRED4x4/8x8/8x8L/16x16 macros to declare intrapred prototypes. Conflicts: libavcodec/h264pred.c libavcodec/h264pred_template.c libavutil/pixfmt.h libswscale/swscale_unscaled.c tests/ref/lavfi/pixdesc tests/ref/lavfi/pixfmts_copy tests/ref/lavfi/pixfmts_null tests/ref/lavfi/pixfmts_scale tests/ref/lavfi/pixfmts_vflip Merged-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-30 17:41:17 +01:00
yuva420p9le 78f5593bf51a31841ef83df41d0316eb
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 23:51:35 +02:00
yuva422p 45ae66d6f69fd5b77e6831e98d228bf4
Merge remote-tracking branch 'qatar/master' * qatar/master: pixfmt: support more yuva formats swscale: support gray to 9bit and 10bit formats configure: rewrite print_config() function using awk FATE: fix (AD)PCM test dependencies broken in e519990 Use ptrdiff_t instead of int for intra pred "stride" function parameter. x86: use PRED4x4/8x8/8x8L/16x16 macros to declare intrapred prototypes. Conflicts: libavcodec/h264pred.c libavcodec/h264pred_template.c libavutil/pixfmt.h libswscale/swscale_unscaled.c tests/ref/lavfi/pixdesc tests/ref/lavfi/pixfmts_copy tests/ref/lavfi/pixfmts_null tests/ref/lavfi/pixfmts_scale tests/ref/lavfi/pixfmts_vflip Merged-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-30 17:41:17 +01:00
yuva422p10be 90ce250a517843b3e8a1ac0f4fdad733
yuva422p10le c74cfda8934e3bf86940b7a08c809b35
yuva422p16be c3f7354b6013b43439e02aa02be5fe69
yuva422p16le a7ccc43820683ab15061d14cf8efce6c
yuva422p9be 14c55a16d19499b54b4341f135d3e558
yuva422p9le a8bf168e5d2709222192d0aff46b1373
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 23:51:35 +02:00
yuva444p 86b05da54db8c7e8cf5b6638e19c6fc5
Merge remote-tracking branch 'qatar/master' * qatar/master: pixfmt: support more yuva formats swscale: support gray to 9bit and 10bit formats configure: rewrite print_config() function using awk FATE: fix (AD)PCM test dependencies broken in e519990 Use ptrdiff_t instead of int for intra pred "stride" function parameter. x86: use PRED4x4/8x8/8x8L/16x16 macros to declare intrapred prototypes. Conflicts: libavcodec/h264pred.c libavcodec/h264pred_template.c libavutil/pixfmt.h libswscale/swscale_unscaled.c tests/ref/lavfi/pixdesc tests/ref/lavfi/pixfmts_copy tests/ref/lavfi/pixfmts_null tests/ref/lavfi/pixfmts_scale tests/ref/lavfi/pixfmts_vflip Merged-by: Michael Niedermayer <michaelni@gmx.at>
2012-10-30 17:41:17 +01:00
yuva444p10be bea827ff82f229145a016954120b731f
yuva444p10le c51b0554cfba0fabacf979683dceee95
yuva444p16be 52a9591ec0d5059e49b1b2803f8582aa
yuva444p16le a9272ac197e4a4195662ce90f533976c
yuva444p9be f72f646ef07cdab613420585aba041ac
yuva444p9le 6d431b0a27bf4f86ea44ef5f14247a01
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 23:51:35 +02:00
yuvj420p 73661456012f20cda81207b14bb0c0a5
yuvj422p aa97862b57f47c5a6506156e9aaf129a
yuvj440p ff8b9884a49d546b035f5d2ac1e673df
yuvj444p b8142888d80b8065c54045839e79b331
yuyv422 f06a4fbbdb32807d05de825daa2c3a1b
Reference in New Issue Copy Permalink