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