[ This article is for Windows Phone 8 developers. If you’re developing for Windows 10, see the latest documentation. ]
Used to save the video capture on Windows Phone to a file.
Assembly: System.Windows (in System.Windows.dll)
Public Class FileSink
public class FileSink
The FileSink type exposes the following members.
|FileSink||Initializes a new instance of the FileSink class.|
|CaptureSource||Gets or sets a capture source that is associated with this FileSink.|
|IsolatedStorageFileName||Gets the name of the associated isolated storage file.|
|Equals(Object)||Determines whether the specified Object is equal to the current Object. (Inherited from Object.)|
|Finalize||Allows an object to try to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.)|
|GetHashCode||Serves as a hash function for a particular type. (Inherited from Object.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|ToString||Returns a string that represents the current object. (Inherited from Object.)|
The 7x27a processor allows audio input on only one stereo bus at a time. This means applications cannot concurrently capture more than one audio source on these devices. If your application is using AudioSink along with FileSink on 7x27a devices, AudioSink will not get audio samples and AudioCaptureDevice will be set to null. FileSink works fine on the 7x27a processor. FileSink or AudioSink work correctly if used independently.
It is recommended to not use VideoSink (with ARBG format) if you intend to save the video to a file by collecting video data to a buffer and writing your own encoder. Use FileSink instead.
If you want to save video capture to an MP4 file in order to play back at a later time, it is recommended to use FileSink.
Windows Phone OS
Supported in: 8.1, 8.0, 7.1
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.