summaryrefslogtreecommitdiffstats
path: root/libavcodec/hwaccel.h
Commit message (Collapse)AuthorAgeFilesLines
* lavc: Make hardware config method support more explicit for hwaccelsThomas Guillem2017-12-101-23/+13
| | | | | | | | | This fixes the use of old ad-hoc methods which are still supported by some hwaccels which also support newer methods (DXVA2, VAAPI, VDPAU, videotoolbox) - without the method being visible here, ff_get_format() would refuse to use it. Signed-off-by: Mark Thompson <sw@jkqxz.net>
* lavc: Add hardware config metadata for decoders supporting hardware outputMark Thompson2017-11-261-0/+52
| | | | | | | | | This includes a pointer to the associated hwaccel for decoders using hwaccels - these will be used later to implement the hwaccel setup without needing a global list. Also added is a new file listing all hwaccels as external declarations - this will be used later to generate the hwaccel list at configure time.
* lavc: Add codec metadata to indicate hardware supportMark Thompson2017-11-261-0/+18
|
* lavc/hwaccel: fix header copyrightClément Bœsch2017-03-211-1/+1
| | | | | | | | | It was done on a whim because of the FATE header check and was actually meant to be removed before pushing. Also, nobody in review spotted it. Reviewed-by: wm4
* pthread_frame: do not run hwaccel decoding asynchronously unless it's safeAnton Khirnov2017-03-211-0/+24
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>
OpenPOWER on IntegriCloud