FFmpeg

Commit Graph

Author	SHA1	Message	Date
Anton Khirnov	e0cd598bc4	pthread_frame: do not run hwaccel decoding asynchronously unless it's safe Certain hardware decoding APIs are not guaranteed to be thread-safe, so having the user access decoded hardware surfaces while the decoder is running in another thread can cause failures (this is mainly known to happen with DXVA2). For such hwaccels, only allow the decoding thread to run while the user is inside a lavc decode call (avcodec_send_packet/receive_frame). Merges Libav commit `d4a91e65`. Signed-off-by: wm4 <nfxjfg@googlemail.com> Tested-by: Michael Niedermayer <michael@niedermayer.cc>	8 years ago
Anton Khirnov	d4a91e6534	pthread_frame: do not run hwaccel decoding asynchronously unless it's safe Certain hardware decoding APIs are not guaranteed to be thread-safe, so having the user access decoded hardware surfaces while the decoder is running in another thread can cause failures (this is mainly known to happen with DXVA2). For such hwaccels, only allow the decoding thread to run while the user is inside a lavc decode call (avcodec_send_packet/receive_frame).	8 years ago
Philip Langdale	4e6d1c1f4e	avcodec/vdpau_hevc: Fix potential out-of-bounds write The maximum number of references is 16, so the index value cannot exceed 15. Fixes Coverity CID 1348139, 1348140, 1348141	8 years ago
Anton Khirnov	150c896a9e	hevcdec: split ff_hevc_diag_scan* declarations into a separate header This will be useful in the following commits.	8 years ago
Anton Khirnov	4abe3b049d	hevc: rename hevc.[ch] to hevcdec.[ch] This is more consistent with the rest of libav and frees up the hevc.h name for decoder-independent shared declarations.	8 years ago
Philip Langdale	8d34a2f803	vdpau: Support for VDPAU accelerated HEVC decoding Signed-off-by: Rémi Denis-Courmont <remi@remlab.net> Signed-off-by: Luca Barbato <lu_zero@gentoo.org>	9 years ago
Philip Langdale	f038bbd4ed	avcodec/vdpau_hevc: Properly signal the num_delta_pocs from the SPS RPS This is the same fix that Hendrik made to dxva2_hevc. It should be equally required here, although I don't see any visual difference. Nevertheless, best to stay consistent.	10 years ago
Philip Langdale	aa10f0aab0	avcodec/vdpau_hevc: Remove experimental flag The latest nvidia 355.06 drivers fixes the interleaving bug when video surfaces are rendered. It still seems to be broken for read-back with getBits but that's sufficiently uninteresting that I don't think we need to wait for it to remove the flag.	10 years ago
Philip Langdale	b11c3fce38	avcodec/vdpau_hevc: unbreak compilation after sps/pps changes There was some reorganisation in the HEVC headers so the sps and pps now live in a different place.	10 years ago
Philip Langdale	b69bea3ab8	avcodec: Add flag for experimental HWAccels and use it for VDPAU/HEVC This HWAccel isn't really usable right now due to an nvidia driver bug, so we don't want it selected by default. HWAccels have a capabilities field and there's a comment about flags, but no flags exist today, so let's add one for experimental hwaccels.	10 years ago
Philip Langdale	6e5e139fe3	avcodec/vdpau: Support for VDPAU accelerated HEVC decoding This change introduces basic support for HEVC decoding through vdpau. Right now, there are problems with the nvidia driver/library implementation that mean that frames are incorrectly laid out in memory when they are returned from the decoder, and it is normally impossible to recover the complete decoded frame due to loss of data from alignment inconsistencies. I obviously hope that nvidia will be fixing it in due course - I've verified the problems exist with their example application. As such, this support is not useful for any real world application, but I believe that it is correct (with the caveat that the mangled frames may hide problems) and will work properly once the nvidia problem is fixed. Right now it appears that any file encoded by x265 or nvenc is decoded correctly, but that's because these files don't use a bunch of HEVC features. Quick summary: Features that seem to work: 1) Short Term References 2) Scaling Lists 3) Tiling Features with known problems: 1) Long Term References It's hard to tell what's going on here. After I read the nvidia example app that does not set the IsLongTerm flag on LTRs, and changed my code, a bunch of frames using LTR started to display correctly, but there are still samples with glitches that are related to LTRs. In terms of real world files, both x265 and nvenc only use short term refs from this list. The divx encoder seems similar. Signed-off-by: Philip Langdale <philipl@overt.org>	10 years ago

13 Commits (ea627dc0949c91e3ee3f98ec3ad6b4df8e96a69e)