Abstract: The techniques disclosed herein enable a guest operating system (OS) to access and use a color space conversion component on a host OS. The guest OS provides, via an application programming interface, a request for the host OS to generate media data in a color space format that is used by the guest OS. To generate the media data, the host OS uses a color space conversion component on the host OS, which is more performant than a corresponding color space conversion component on the guest OS because the color space conversion component on the host OS has access to hardware-accelerated functionality. Accordingly, the color space conversion component on the host OS converts media data into the color space format that is used by the guest OS, and stores the media data in memory that is accessible to the guest OS.

Abstract: The techniques disclosed herein enable a guest operating system (OS) to access and use a media processing component configured on a host OS. The guest OS provides, via an API, a request to create an instance of the media processing component (e.g., a codec, an encryption/decryption component, a DRM component). In association with the request, the guest OS allocates space in memory for media data that is to be processed by the instance of the media processing component configured on the host OS. The guest OS stores the input media data in the allocated memory and provides, via the API, reference(s) to locations of the allocated memory. The reference(s) to the locations of the allocated memory enable the host OS to retrieve the input media data and process the input media data using the instance of the media processing component configured on the host OS.

Abstract: The techniques disclosed herein enable a guest operating system (OS) to access and use a color space conversion component on a host OS. The guest OS provides, via an application programming interface, a request for the host OS to generate media data in a color space format that is used by the guest OS. To generate the media data, the host OS uses a color space conversion component on the host OS, which is more performant than a corresponding color space conversion component on the guest OS because the color space conversion component on the host OS has access to hardware-accelerated functionality. Accordingly, the color space conversion component on the host OS converts media data into the color space format that is used by the guest OS, and stores the media data in memory that is accessible to the guest OS.

Abstract: The techniques disclosed herein enable a guest operating system (OS) to access and use a media processing component configured on a host OS. The guest OS provides, via an API, a request to create an instance of the media processing component (e.g., a codec, an encryption/decryption component, a DRM component). In association with the request, the guest OS allocates space in memory for media data that is to be processed by the instance of the media processing component configured on the host OS. The guest OS stores the input media data in the allocated memory and provides, via the API, reference(s) to locations of the allocated memory. The reference(s) to the locations of the allocated memory enable the host OS to retrieve the input media data and process the input media data using the instance of the media processing component configured on the host OS.

Abstract: The techniques disclosed herein enable a guest operating system (OS) to access and use a color space conversion component on a host OS. The guest OS provides, via an application programming interface, a request for the host OS to generate media data in a color space format that is used by the guest OS. To generate the media data, the host OS uses a color space conversion component on the host OS, which is more performant than a corresponding color space conversion component on the guest OS because the color space conversion component on the host OS has access to hardware-accelerated functionality. Accordingly, the color space conversion component on the host OS converts media data into the color space format that is used by the guest OS, and stores the media data in memory that is accessible to the guest OS.

Abstract: The techniques disclosed herein enable a guest operating system (OS) to access and use a media processing component configured on a host OS. The guest OS provides, via an API, a request to create an instance of the media processing component (e.g., a codec, an encryption/decryption component, a DRM component). In association with the request, the guest OS allocates space in memory for media data that is to be processed by the instance of the media processing component configured on the host OS. The guest OS stores the input media data in the allocated memory and provides, via the API, reference(s) to locations of the allocated memory. The reference(s) to the locations of the allocated memory enable the host OS to retrieve the input media data and process the input media data using the instance of the media processing component configured on the host OS.

Abstract: A switching module is adapted to configure switches between source buffers and rendering pipelines. Each of the switches has one or more selection inputs each representing encoded data for a media track from one of the source buffers. Each of the switches also has a selection output associated with one of the rendering pipelines for decoding and rendering. The switching module is further adapted to use the switches to manage which of the media tracks, if any, have encoded data routed to the rendering pipelines during media streaming. The rendering pipelines can include a video rendering pipeline and one or more audio rendering pipelines, where the switching module is part of a media engine adapted to determine a clock source in one of the audio rendering pipeline(s), and the clock source is used to drive synchronization of the media tracks.

Abstract: A timed data component is implemented within an operating system to provide parsing and data conversion of multiple timed data formats. The timed data component supports multiple formats of closed caption data and timed metadata, generating structured cue objects that include the data and timing information. Applications using proprietary or non-supported formats can pre-format the timed data as structured cue objects before sending the timed data to the timed data component. Structured cue objects output from the timed data component may be processed by a single text renderer to provide a consistent look and feel to closed caption data originating in any of multiple formats.

Abstract: A switching module is adapted to configure switches between source buffers and rendering pipelines. Each of the switches has one or more selection inputs each representing encoded data for a media track from one of the source buffers. Each of the switches also has a selection output associated with one of the rendering pipelines for decoding and rendering. The switching module is further adapted to use the switches to manage which of the media tracks, if any, have encoded data routed to the rendering pipelines during media streaming. The rendering pipelines can include a video rendering pipeline and one or more audio rendering pipelines, where the switching module is part of a media engine adapted to determine a clock source in one of the audio rendering pipeline(s), and the clock source is used to drive synchronization of the media tracks.