SDK lifecycle
The SDK is created and initialised when the client application starts up (upon calling OTVSDK.load()) and is destroyed when the application terminates. Typically, the SDK is created by the following code within the application entry AppDelegate::application(application: didFinishLaunchingWithOptions:) method.
OTVSDK.load()
Enabling logging
SDK users can set the logging levels by calling OTVSDK.setLogging(level:) after the OTVSDK.load() is called. If OTVSDK.setLogging() is not called, the default level is .warning
OTVSDK.setLogging(level: .debug)
|
Level |
Description |
|---|---|
|
.error |
Indicates a situation requires investigation, which may or may not lead the application to abort. |
|
.warning |
Indicates a potentially harmful situation that may lead to an error. |
|
.info |
Designates information about data values or object states at a coarse-grained level. |
|
.debug |
Designates fine-grained informational events, especially the key APIs calling traces that are most useful to debug an application. |
Low latency support
As OTVAVPlayer uses the underlying Apple AVPlayer, SDK 5 supports HLS clear and encrypted low-latency playback. From an OTVAVPlayer perspective, nothing is required to enable low-latency playback when a low-latency-capable stream is encountered. For details on how to set up your HLS streams to enable low-latency playback, see the Apple document Enabling Low-Latency HTTP Live Streaming (HLS).
Low-latency extensions are defined in the HLS specification HTTP Live Streaming 2nd Edition revision 7 and later.