1 This document lists the differenced between camerabin and camerabin2 from
2 the API point of view and should be used to help on porting applications
3 from camerabin to camerabin2.
5 * Setting the location for the captures:
6 camerabin requires that the path of the file to save the captures is set before
7 each capture. Camerabin2 allows the application to use a multifilesink-like
8 approach, the application can set a file with a '%d' marker, this marker
9 will be automatically replaced by a number and be autoincremented after each
11 The property is now called 'location' instead of 'filename'
14 The signals were renamed from capture-start/stop to start/stop-capture as
15 this is the usual naming on actions.
16 Additionally, stop-capture is now async, the user should check 'idle' property
17 to be sure that it can shut camerabin2.
20 In camerabin, image-done is a signal, in camerabin2, it is a bus message
22 * video recording encoder/muxer
23 In camerabin, video/audio encoder/muxer are selected by passing GstElements to
24 camerabin properties. In camerabin2, a GstEncodingProfile is passed as a
25 property and encodebin manages to instantiate the elements for the format.
28 new "post-previews" property for enabling/disabling preview image posting
29 set location=NULL to skip writing image to file but to receive the preview,
30 useful for scenarios that wants the image in memory.
32 * Configuring resolution and framerate
33 Camerabin2 has new GstCaps type properties for configuring capture and