This sample demonstrates how to use the low latency feature to enable real-time communication applications.
Note This sample was created using one of the universal app templates available in Visual Studio. It shows how its solution is structured so it can run on both Windows 8.1 and Windows Phone 8.1. For more info about how to build apps that target Windows and Windows Phone with Visual Studio, see Build apps that target Windows and Windows Phone 8.1 by using Visual Studio.
Specifically, this sample contains:
-
A simple end-to-end video call client that demonstrates the low latency mode of the Windows Runtime capture engine. This is enabled using the msRealTime the video tag or RealTimePlayback on the MediaElement. The sample uses a custom network source and a custom sink extension to send and receive captured audio and video data between two computers.
-
A demonstration of the end-to-end latency of video captured using the Media Capture API and displayed using a video and MediaElement with low latency mode enabled. Two output windows are displayed. The first shows a camera preview window of the raw output from your camera. The second is a local host client window that shows the video from the camera when compressed, streamed, and received over machine's loopback network interface. This window demonstrates the end-to-end latency of video captured, streamed to, and displayed by a remote client minus network latency.
Important
This sample uses the Media Extension feature of Windows 8.1 to add functionality to the Microsoft Media Foundation pipeline. A Media Extension consists of a hybrid object that implements both Component Object Model (COM) and Windows Runtime interfaces. The COM interfaces interact with the Media Foundation pipeline. The Windows Runtime interfaces activate the component and interact with the Windows Store app.
In most situations, it is recommended that you use Visual C++ with Component Extensions (C++/CX ) to interact with the Windows Runtime. But in the case of hybrid components that implement both COM and Windows Runtime interfaces, such as Media Extensions, this is not possible. C++/CX can only create Windows Runtime objects. So, for hybrid objects it is recommended that you use Windows Runtime C++ Template Library to interact with the Windows Runtime. Be aware that Windows Runtime C++ Template Library has limited support for implementing COM interfaces.
For more info on creating a Media Foundation media extension in Windows Store app, see Walkthrough: Creating a Windows Store app using WRL and Media Foundation and the Media extension sample.
Important The binaries used by this sample have been included for proof of concept purposes only. They might have significant performance, reliability, and security issues and should not be used outside of a test environment. They are not licensed for use in a production environment or for use with sensitive data.
Important The URL passed to the code is not validated or authenticated. The application must perform these actions.
To obtain an evaluation copy of Windows 8.1, go to Windows 8.1.
To obtain an evaluation copy of Microsoft Visual Studio 2013, go to Visual Studio 2013.
Related topics
- Windows 8 app samples
- Roadmaps
- Roadmap for apps using C# and Visual Basic
- Roadmap for apps using C++
- Roadmap for apps using JavaScript
- Designing UX for apps
- Adding multimedia
- Tasks
- How to enable low-latency playback
- Creating a Windows Store app using WRL and Media Foundation
- Reference
- Windows.Media.Capture.MediaCapture
- MediaCapture
- msRealTime
- MediaExtensionManager
- Windows.Media.MediaProperties
Operating system requirements
| Client | |
|---|---|
| Server | |
| Phone |
Build the sample
- Start Microsoft Visual Studio 2013 Update 2 and select File > Open > Project/Solution.
- Go to the directory to which you unzipped the sample. Then go to the subdirectory named for the sample and double-click the Visual Studio 2013 Update 2 Solution (.sln) file.
- Follow the steps for the version of the sample you want:
-
To build the Windows version of the sample:
- Select SimpleCommunication.Windows in Solution Explorer.
- Press Ctrl+Shift+B, or use Build > Build Solution, or use Build > Build SimpleCommunication.Windows.
-
To build the Windows Phone version of the sample:
- Select SimpleCommunication.WindowsPhone in Solution Explorer.
- Press Ctrl+Shift+B or use Build > Build Solution or use Build > Build SimpleCommunication.WindowsPhone.
-
Run the sample
The next steps depend on whether you just want to deploy the sample or you want to both deploy and run it.
Deploying the sample
-
To deploy the built Windows version of the sample:
- Select SimpleCommunication.Windows in Solution Explorer.
- Use Build > Deploy Solution or Build > Deploy SimpleCommunication.Windows.
-
To deploy the built Windows Phone version of the sample:
- Select SimpleCommunication.WindowsPhone in Solution Explorer.
- Use Build > Deploy Solution or Build > Deploy SimpleCommunication.WindowsPhone.
Deploying and running the sample
-
To deploy and run the Windows version of the sample:
- Right-click SimpleCommunication.Windows in Solution Explorer and select Set as StartUp Project.
- To debug the sample and then run it, press F5 or use Debug > Start Debugging. To run the sample without debugging, press Ctrl+F5 or use Debug > Start Without Debugging.
-
To deploy and run the Windows Phone version of the sample:
- Right-click SimpleCommunication.WindowsPhone in Solution Explorer and select Set as StartUp Project.
- To debug the sample and then run it, press F5 or use Debug > Start Debugging. To run the sample without debugging, press Ctrl+F5 or use Debug > Start Without Debugging.