- 24 Nov, 2016 5 commits
-
-
Wan-Teh Chang authored
This is a follow-up to commit d84a2120, which added the libavutil/tests/cpu_init.c. Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Wan-Teh Chang authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
James Almer authored
Fixes make checkheaders on systems without the Cuda Toolkit, which was broken after the dynlink changes. Signed-off-by:
James Almer <jamrial@gmail.com>
-
Paul B Mahol authored
Move global thread variables to better place. Use correct variable for simple and complex filtergraphs. This makes number of threads set per filter work again. Signed-off-by:
Paul B Mahol <onemda@gmail.com>
-
Andreas Cadhalpun authored
Rects with positive w/h/linesize but no data are invalid. Reviewed-by:
Petri Hintukainen <phintuka@gmail.com> Signed-off-by:
Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
- 23 Nov, 2016 11 commits
-
-
Moritz Barsnick authored
Expands the parser to also accept the separator '-' in addition to '+', and take the negative sign into consideration. The optional sign for the first factor in the expression is already covered by parsing for an integer. Signed-off-by:
Moritz Barsnick <barsnick@gmx.net> Reviewed-by:
Nicolas George <george@nsup.org> Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Jun Zhao authored
scaling list is already transfered to raster scan during head parsing, so no need to transfer it again. And after this fix, FATE test SLIST_A_Sony_4/SLIST_B_Sony_8/ SLIST_C_Sony_3/SLIST_D_Sony_9 will pass in i965/Skylake. Signed-off-by:
Wang, Yi A <yi.a.wamg@intel.com> Signed-off-by:
Jun Zhao <jun.zhao@intel.com> Signed-off-by:
Mark Thompson <sw@jkqxz.net>
-
Wan-Teh Chang authored
avutil/tests: Add cpu_init.c to check whether the one-time initialization in av_get_cpu_flags() has data races. Co-author: Dmitry Vyukov of Google Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Wan-Teh Chang authored
Remove the |checked| variable because the invalid value of -1 for |flags| can be used to indicate the same condition. Also rename |flags| to |cpu_flags| because there are a local variable and a function parameter named |flags| in the same file. Co-author: Dmitry Vyukov of Google Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Philip Langdale authored
I moved this into the handle_video_sequence callback because that's the earliest time you can make an accurate decision as to what the format should be. However, transcoding requires that the decision between using the accelerated PIX_FMT_CUDA vs a normal pix format happen at init() time. There is enough information available to make that decision and things work out with the underlying format only being discovered in the sequence callback.
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com>
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
Sam Hocevar authored
This patch moves the av_frame_make_writable() call from fill_yuv_image to get_video_frame so that its argument can be the actual frame that will be sent to the encoder. This fixes data corruption issues in codecs that keep references on one or several previous frames. Signed-off-by:
Sam Hocevar <sam@hocevar.net> Reviewed-by: wm4 Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Michael Niedermayer authored
Requested-by: wm4 ([FFmpeg-devel] [PATCH] avutil/opt: Support max > INT64_MAX in write_number() with AV_OPT_TYPE_INT64) Requested-by: ronald ([FFmpeg-devel] [PATCH] avutil/opt: Support max > INT64_MAX in write_number() with AV_OPT_TYPE_INT64) Reviewed-by:
Andreas Cadhalpun <andreas.cadhalpun@googlemail.com> Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Andreas Cadhalpun authored
Reviewed-by:
Josh de Kock <josh@itanimul.li> Signed-off-by:
Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
- 22 Nov, 2016 22 commits
-
-
Andreas Cadhalpun authored
This fixes division by zero crashes. Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
Andreas Cadhalpun authored
This fixes segmentation faults due to stack-overflow caused by too deep recursion. Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
Michael Niedermayer authored
Fixes: _ij.mp3 Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Andreas Cadhalpun authored
Metadata streams have priv_data set to NULL. Reviewed-by:
Josh de Kock <josh@itanimul.li> Signed-off-by:
Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
Alex Converse authored
Levels are specified at https://www.webmproject.org/vp9/levels/
-
Philip Langdale authored
The nvidia 375.xx driver introduces support for P016 output surfaces, for 10bit and 12bit HEVC content (it's also the first driver to support hardware decoding of 12bit content). The cuvid api, as far as I can tell, only declares one output format that they appear to refer to as P016 in the driver strings. Of course, 10bit content in P016 is identical to P010, and it is useful for compatibility purposes to declare the format to be P010 to work with other components that only know how to consume P010 (and to avoid triggering swscale conversions that are lossy when they shouldn't be). For simplicity, this change does not maintain the previous ability to output dithered NV12 for 10/12 bit input video - the user will need to update their driver to decode such videos.
-
Philip Langdale authored
CUVID is now capable of returning 10bit and 12bit decoded content in P010/P016. Let's support transfering those formats.
-
Philip Langdale authored
P016 is the 16-bit variant of NV12 (planar luma, packed chroma), using two bytes per component. It may, and in fact is most likely to, be used in situations where there are less than 16 bits of data. It is the responsibility of the writer to zero out any unused LSBs.
-
Timo Rothenpieler authored
Currently, it forces IDR frames for both true and false. Not entirely sure what the original idea behind the tri-state bool option is. Reviewed-by:
Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
Miroslav Slugen authored
Signed-off-by:
Timo Rothenpieler <timo@rothenpieler.org>
-
Miroslav Slugeň authored
User selectable surfaces are not working correctly, if you set number of surfaces on cmdline, it will always use minimum 32 or 48 depends on selected resolution, but in nvenc it is not necessary to use so many surfaces. So from now you can define as low as 1 surface and nvenc will still work, it will ofcourse lower GPU memory usage by 95% and async_delay to zero That was the easy part, now littlebit more... Next part of this patch is to always prefer rc_lookahead to be more important for number of surfaces, than user defined surfaces value. Maximum rc_lookahead from nvidia documentation is 32, but could increase in future generations so there is no limit for this yet. Value async_depth is still accepted and prefered over rc_lookahead. There were also bug when you request more than rc_lookahead > 31, it will always set maximum 31, because surface numbers recalculation was after setting lookahead, which is now fixed. Results: If you set -rc_lookahead 32 and -bf 3 it will now use only 40 surfaces and lower GPU memory usage by 20%, also it will now increase PSNR by 0.012dB Two more comments: 1. from my internal test, i don't understand addition of 4 more surfaces when lookahead is calculated, i didn't used this and everything works as with those 4 more extra surfaces, does anybody know what is going on there? I looks like it was used for B frames which are calculated separately, because B frames maximum is 4. 2. rc_lookahead is defined default to -1, but in test condition if (ctx->rc_lookahead) which sets lookahead it will be always true, i don't know if this is intended behavior, so in default behavior is lookahead always on! This is default condition when rc_lokkahead is -1 (not defined on cmdline), whis is maybe something that is not intended: ctx->encode_config.rcParams.enableLookahead = 1; ctx->encode_config.rcParams.lookaheadDepth = 0; ctx->encode_config.rcParams.disableIadapt = 0; ctx->encode_config.rcParams.disableBadapt = 0; Signed-off-by:
Timo Rothenpieler <timo@rothenpieler.org>
-
Miroslav Slugeň authored
Maximum usable surfaces is limited to MAX_REGISTERED_FRAMES constant in nvenc.h Signed-off-by:
Timo Rothenpieler <timo@rothenpieler.org>
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
And remove the now obsolete compat headers.
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Steven Liu authored
some flv have no metadata, ffmpeg will same with the source flv stream. Signed-off-by:
Steven Liu <lingjiujianke@gmail.com>
-
James Almer authored
Found-by:
Neil Birkbeck <neil.birkbeck@gmail.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 21 Nov, 2016 2 commits
-
-
Mark Thompson authored
Same as e0df56f2. This was accidentally reintroduced while merging c8241e73.
-
Jun Zhao authored
when meeting IDR frame, vaapi_encode_h264 poc number don't reset, now fix this issue based on h264 spec. Some decoder don't care this case, but this fix will enhance the encoder action. Before this fix, poc number is negative in some case. Reviewed-by:
Jun Zhao <jun.zhao@intel.com> Signed-off-by:
Wang, Yi A <yi.a.wang@intel.com> Signed-off-by:
Mark Thompson <sw@jkqxz.net>
-