mirror of
https://github.com/FFmpeg/FFmpeg.git
synced 2025-02-04 06:08:26 +02:00
lavc/videotoolboxenc: better compat_keys docs
Added more specific docs about when to use compat_keys, and how to add new constants. Signed-off-by: Rick Kern <kernrj@gmail.com>
This commit is contained in:
parent
efdc6e8200
commit
902c949d30
@ -64,9 +64,19 @@ typedef OSStatus (*getParameterSetAtIndex)(CMFormatDescriptionRef videoDesc,
|
||||
int *NALUnitHeaderLengthOut);
|
||||
|
||||
/*
|
||||
* Keys that are not present in all versions of VideoToolbox need to be
|
||||
* accessed from compat_keys, or it will cause compiler errors when compiling
|
||||
* for older OS versions.
|
||||
* Symbols that aren't available in MacOS 10.8 and iOS 8.0 need to be accessed
|
||||
* from compat_keys, or it will cause compiler errors when compiling for older
|
||||
* OS versions.
|
||||
*
|
||||
* For example, kVTCompressionPropertyKey_H264EntropyMode was added in
|
||||
* MacOS 10.9. If this constant were used directly, a compiler would generate
|
||||
* an error when it has access to the MacOS 10.8 headers, but does not have
|
||||
* 10.9 headers.
|
||||
*
|
||||
* Runtime errors will still occur when unknown keys are set. A warning is
|
||||
* logged and encoding continues where possible.
|
||||
*
|
||||
* When adding new symbols, they should be loaded/set in loadVTEncSymbols().
|
||||
*/
|
||||
static struct{
|
||||
CFStringRef kCVImageBufferColorPrimaries_ITU_R_2020;
|
||||
|
Loading…
x
Reference in New Issue
Block a user