Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/FFmpeg/FFmpeg.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2015-08-04avcodec/vdpau_hevc: Properly signal the num_delta_pocs from the SPS RPSPhilip Langdale
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.
2015-08-04avcodec/vdpau_hevc: Remove experimental flagPhilip Langdale
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.
2015-07-13avcodec/vdpau_hevc: unbreak compilation after sps/pps changesPhilip Langdale
There was some reorganisation in the HEVC headers so the sps and pps now live in a different place.
2015-06-27avcodec: Add flag for experimental HWAccels and use it for VDPAU/HEVCPhilip Langdale
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.
2015-06-26avcodec/vdpau: Support for VDPAU accelerated HEVC decodingPhilip Langdale
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>