Data sources and sinks

A data source is an input parameter to a media object that specifies where a media object receives the multimedia data. A data sink is an input parameter to a media object that specifies where a media object sends the multimedia data. The locatorType parameter identifies where this data resides. The following diagrams illustrate the use of data sources and sinks in four examples.

Data flow diagram showing the audio and video playback use case.

Data flow diagram showing the audio recording use case.

Data flow diagram showing the access decoder use case.

Data flow diagram showing the access encoder use case.

The following tables identify the supported data locators.

XADataSource structure

Supported locatorType

Description

XA_DATALOCATOR_URI

Data resides at the specified URI.

XA_DATALOCATOR_ANDROIDBUFFERQUEUE

Data is generated or consumed by the app buffer. The Android/QNX buffer queue locator is an API extension added by BlackBerry 10.

XADataSink structure

Supported locatorType

Description

XA_DATALOCATOR_NATIVEDISPLAY

Data is rendered to the specified native display.

XA_DATALOCATOR_IODEVICE

Data is consumed by the specified IO drive.

XA_DATALOCATOR_OUTPUTMIX

Data is consumed by the specified audio output mix.

XAQ_DATALOCATOR_SCREENBUFFERQUEUE

Data in the buffer queue is a pointer to the BlackBerry 10 screen_buffer_t. Use this locatorType to get decoded video frames without memory copy.

XA_DATALOCATOR_QNXBUFFERQUEUE

Data in the buffer queue is a pointer. Use this locatorType to get decoded or encoded data without memory copy.

Last modified: 2014-11-17



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus