A black screen and disabled camera buttons are present if the control is setup by Initialize method using the following code:

var devices = RadWebCam.GetVideoCaptureDevices();
var formats = RadWebCam.GetVideoFormats(devices[0]);
this.webcam.Initialize(devices[0], formats[0]); 

Add an API that allows you to hide the Start Recording and Take Snapshot buttons.

Currently, the RadWebCam control is using the video feed and it takes a snapshot from it. Some cameras can produce a still image separate from the video stream. The still image usually gives a better quality of the picture, than the video stream.

Add support for using the still image capturing to get the snapshot when the camera allows this.

When run over Remote Desktop the webcam does not render anything. This is because D3DImage does not render when WPF switches to software render mode which happens when running an app over Remote Desktop. There is a possible fix for it implemented in .NET 4.5 which allows D3DImage to also fall back to software rendering.

Allow rotation of the video feed from the webcam device.

Introduce an API that allows you to set the DPI that is used when creating the snapshot. Currently, the control uses the DPI currently applied to the monitor which changes the resolution of the produced picture.

Currently, the recording can be saved only to a file. Allow saving the recording into a Stream object hold in-memory.

Steps to reproduce:

1. Place a camera on a window

2. Have no camera plugged in the PC

3. Call the Start or Stop method

Expected behaviour: Nothing 

Actual behaviour: An exception is thrown

Add an event that allows you to get the current video frame from the camera device.

I have a WPF window containing a RadWebCam control and a CameraSettingsControl control associated with it (as shown in the online documentation). When I close the WPF window, no memory associated with that window is released. I implemented a Finalizer in the window and found that it wasn't getting called even after several GC.Collect() calls.  The culprit appears to be the CameraSettingsControl when it's associated with the RadWebCam control. In my application, it's not freeing about 80MB of memory after each window invocation.

I have included a full project sample which demonstrates the issue. Just set a BreakPoint on the finalizer ~TakePicture(). When the application is run, hit the 'Take Picture' button to launch the Camera window, and then close it.  To verify that it's not just a delay in garbage collection, hit the GCCollect button on the main window a couple of times. The Finalizer never gets called until you exit the app.

Here's the Telerik control WPF I'm using, but it's also in the sample.

<telerikWebCam:RadWebCam Grid.Column ="0" x:Uid="WebCamCaptureWindow_RadWebCam" x:Name="webCam" MinWidth="0" MinHeight="0" AutoStart="False" Margin="0 25 0, 0" 

                                       BorderThickness="0"
                                       Background="Black"
                                       PreviewSnapshots="True"
                                       RecordingButtonVisibility="Collapsed"
                                       Visibility="Visible"
                                       CameraError="OnWebCamCameraError" />

<telerikWebCam:CameraSettingsControl Grid.Column ="1" x:Uid="WebCamCaptureWindow_CameraControlSettings" x:Name="webCamSettingsControl" WebCam="{Binding ElementName=webCam}" 
                                                         Visibility="Visible"/>

If you forbid the app access to the camera via the Windows settings a System.Exception is thrown when you start the RadWebCam control. The exception message is 'MFCreateDeviceSource failed: E_ACCESSDENIED'

NullReferenceException is thrown in Telerik.Windows.Controls.RadWebCam.OnFlipHorizontallyChanged/OnFlipVerticallyChanged as webCam.player is not yet initialized.

NullReferenceException is thrown at Telerik.Windows.Controls.RadWebCam.GetCameraSettingsViewModel() 

Steps to reproduce:

1. Create a form with a webcam that calls Close and Dispose when closed.

2. Create a second form with a button that shows the first form.

3. Run the project and you will see an exception when closing the webcam form.

a call to StartRecording() results in an unhandled null reference exception when the webcam has been disabled. (this is not the case when other webcam errors occur, like when the webcam is taken by another application). 

Our application provides a fallback scenario to make an audio recording when the webcam is not available, in order for this to work it would be preferable to be able to call the StartRecording() method without causing a crash, and to still have the RecordingStarted event triggered, just like in the case of a "camera unavailable" error.

 

We can extend the API of the RadWebCam so that we can disable the flash of the currently running camera.

Add API like a Style or similar that allows customizing the appearance of the buttons (save, take snapshot, etc.) in the toolbar. For example, to change their icon, the tooltip, size, etc. 

Currently, if the camera supports zoom, you can control this using the CameraSettingsControl. However, there is no public API allows you to set the zoom programmatically.
Add a property or a method that can be used to manually change the zoom in code.

When you start the camera for the first time, the video feed is lagging. The frame rate seems to be very low. If you stop the camera at runtime and then start it again the video is running normally. 

This reproduces sometimes, but often works as expected.