[FFmpeg-trac] #4831(avcodec:reopened): Can't initialize h264_qsv encoder post Aug 29 2015 - Ivy Bridge CPU
FFmpeg
trac at avcodec.org
Mon Sep 21 16:57:35 CEST 2015
#4831: Can't initialize h264_qsv encoder post Aug 29 2015 - Ivy Bridge CPU
-------------------------------------+-------------------------------------
Reporter: babgvant | Owner: IvUs
Type: defect | Status: reopened
Priority: important | Component: avcodec
Version: git-master | Resolution:
Keywords: qsv | Blocked By:
regression | Reproduced by developer: 0
Blocking: |
Analyzed by developer: 1 |
-------------------------------------+-------------------------------------
Comment (by babgvant):
Replying to [comment:15 heleppkes]:
> So what happens when we request runtime 1.1 on a modern GPU?
> From what I can tell, nothing changes at all, since the actual runtime
version is still the same.
I think initializing at 1.1 is the correct approach (it's what I do in my
MSDK transcoder). Initializing at this level doesn't limit what the
application can support.
After init use m_pmfxSession->QueryVersion(&version) to retrieve the
client's level and cascade the encoder config based on that:
if(version.Major >= 1)
{
if(version.Minor >= 8)
{
// introduced in API 1.8
m_CodingOptions2.BRefType = MFX_B_REF_UNKNOWN; //default is
MFX_B_REF_UNKNOWN
m_CodingOptions2.RepeatPPS = MFX_CODINGOPTION_ON;
m_CodingOptions2.LookAheadDS = pInParams->nLADS;
//MFX_LOOKAHEAD_DS_UNKNOWN default
}
if(version.Minor >= 7)
{
m_CodingOptions2.Trellis = pInParams->nTrellis;
m_CodingOptions2.LookAheadDepth = pInParams->nLAD;
}
...
}
--
Ticket URL: <https://trac.ffmpeg.org/ticket/4831#comment:20>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list