Recently I have discovered pretty, but potentially dangerous, MFXReadWriteMid extension for mfxMemId essence.
It resides at current github.com/Intel-Media-SDK/samples, but was born ages ago, at pre-github epoch.
MFXReadWriteMid uses the upper bit of address variable to indicate it's extended interpretation (actual MemId + read_write flags, one more indirection level).
Which can lead to damages inside LARGEADDRESSAWARE/3GB/increaseuserva/etc applications.
So, my question concerns area of MFXReadWriteMid utilization.
Is it used inside samples code only?
Or, is "extended version" of mfxMemId can be passed into my mfxFrameAllocator::Lock() function from intel's mfx engine implementation (from libmfxhw.dll)?
Kind regards
Link Copied
Hi Alek,
This should sample only.
The code belongs to the common utility for the sample code and used for D3D11 allocator. This is out of the scope of Media SDK library which excludes the memory management and rendering.
Let me know if this answers your concerns.
Mark
Hi Alek,
This should sample only.
The code belongs to the common utility for the sample code and used for D3D11 allocator. This is out of the scope of Media SDK library which excludes the memory management and rendering.
Let me know if this answers your concerns.
Mark
Yes, this is exactly what I wanted to hear.
Thank you!
For more complete information about compiler optimizations, see our Optimization Notice.