Controls the recording sink. The recording sink creates compressed audio/video files or compressed audio/video streams.
The IMFCaptureRecordSink interface inherits from IMFCaptureSink. IMFCaptureRecordSink also has these types of members:
The IMFCaptureRecordSink interface has these methods.
Gets the rotation that is currently being applied to the recorded video stream.
Sets a custom media sink for recording.
Specifies a byte stream that will receive the data for the recording.
Specifies the name of the output file for the recording.
Rotates the recorded video stream.
Sets a callback to receive the recording data for one stream.
The recording sink can deliver samples to one of the following destinations:
- Byte stream.
- Output file.
- Application-provided callback interface.
The application must specify a single destination. Multiple destinations are not supported. (However, if a callback is used, you can provide a separate callback for each stream.)
If the destination is a byte stream or an output file, the application specifies a container type, such as MP4 or ASF. The capture engine then multiplexes the audio and video to produce the format defined by the container type. If the destination is a callback interface, however, the capture engine does not multiplex or otherwise interleave the samples. The callback option gives you the most control over the recorded output, but requires more work by the application.
To start the recording, call IMFCaptureEngine::StartRecord.
Minimum supported client
|Windows 8 [desktop apps only]|
Minimum supported server
|Windows Server 2012 [desktop apps only]|
Build date: 11/16/2013