| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
We need to set capture format at the beginning of line to
avoid useless conversations and reinits.
Currently we can't set it camerabin2, so we set it in cheese videofilter.
Signed-off-by: Oleksij Rempel <bug-track@fisher-privat.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/* The webcams can get unstable if we permanently turn them on and off.
* On other side we need it to find best possible format for our pipe line.
* Video filter need RGB, video encoders YUV/I420. Jpeg can work with RGB too.
* Currently there is no right solution, so we will try to get
* native format prioduced by webcam and try to do the best with it.
* v4l2src use rank system in wich native camera formats go on first
* plase. Most embeded cams support only one raw format (mostly YUY2),
* Most external cams support YUY2 and JPEG, and some expensive cams
* support all this and H264. Almost none of them support two different
* RAW formats, exept some logitech with hidden bayer stream.
* This is why we take first RAW format (with higest rank) and use it
* by default.
*/
Signed-off-by: Oleksij Rempel <bug-track@fisher-privat.net>
|
|
|
|
| |
Signed-off-by: Oleksij Rempel <bug-track@fisher-privat.net>
|
| |
|
|
|
|
|
| |
create webm profile and use it with camereabin2. Also use presets for
vp8enc.
|
|
|
|
| |
Wait for video-done message to signal that capture is over
|
|
|
|
|
| |
Camerabin2 is the element to post the image-done message, not
the camera source.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this the sink will issue a warning:
** (cheese:21655): WARNING **: Internal data flow problem.:
gstbasesink.c(3626): gst_base_sink_chain_unlocked ():
/GstCameraBin2:camerabin2/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
Received buffer without a new-segment. Assuming timestamps start from 0.
I'm not sure what the implications of this setting are. It might be
caused by the clock/time rewriting magic from camerabin2.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
camerabin2 sends the preview-image bus message through the
gstwrappercamerabinsrc.
camerabin2 treats location=NULL as a "don't write in a file just post
the buffer as a bus message".
|
|
|
|
|
| |
When taking a photo to pixbuf, sets post-preview to enable camerabin2 to
send the preview message.
|
| |
|
|
|
|
|
|
|
|
| |
Quote from camerabin2's PORTING guide:
In camerabin, image-done is a signal, in camerabin2, it is a bus message
Signed-off-by: Raluca Elena Podiuc <ralucaelena1985@gmail.com>
|
|
|
|
|
|
|
| |
#ifndef GST_USE_UNSTABLE_API
#warning "camerabin enums are unstable API and may change in future."
#warning "You can define GST_USE_UNSTABLE_API to avoid this warning."
#endif
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Camerabin2 creates a temporary file, writes data to it and in the end
it moves it to the destination path.
Without G_FILE_MONITOR_SEND_MOVED to g_file_monitor_directory, moves
would be sent as DELETE + CREATE.
Unfortunately, we would also get CREATE events when the temporary file
was created. We cannot listen for CREATE events as temporary files
would be CREATEd and then CHANGEd and the thumb-view creation code
would work with bad data.
By using G_FILE_MONITOR_SEND_MOVED we get a single event when the file
is moved. As the file monitor ignores files with unknown extensions
(as is the case for the temporary files created by camerabin2) we
could only just append the new file. But because the user might also
move a picture/video manually from the Pictures/Webcam or
Videos/Webcam directories, removing the old file from the thumb-view
keeps it up-to-date with the state of the file system.
If camerabin2 switches away from the create-temp+move approach, to the
camerabin one (create the destination file directly), we're prepared
to handle that code with G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT.
|
|
|
|
|
|
|
|
|
| |
Quote from camerabin2's PORTING guide:
[...] is now called 'location' instead of 'filename'
The signals were renamed from capture-start/stop to
start/stop-capture as this is the usual naming on actions.
|
|
|
|
|
| |
If the effect is applied on camera_source, the effect will be
available in viewfinder and image/video capture modes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are the minimal changes needed to integrate camerabin2.
Support for:
- viewfinder (Cheese's main window)
- effect previews
Porting details:
- obviously, the name has changed to camerabin2
- Camerabin2 requires something special from it's "camera-source".
We use the "wrappercamerabinsrc" module provided by camerabin2 which
creates a "camera-source" suitable for camerabin2 based on a regular
video source.
|
|
|
|
|
|
|
|
|
|
| |
Once we've set the related action, the label will have been synced, and
we won't be able to add an image to the button.
Setting "use-action-appearance" to False before setting the
related-action works around the problem. See GTK+ bug 671912.
https://bugzilla.gnome.org/show_bug.cgi?id=671913
|
|
|
|
| |
Fixes bug 599729.
|
|
|
|
|
|
| |
This allows compilation to succeed with
‘-Wdeclaration-after-statement -Werror=declaration-after-statement’
passed to GCC.
|
| |
|
|
|
|
|
|
|
| |
Metadata is important for search and management applications. These tags
should help to track files produced by Cheese.
Signed-off-by: Oleksij Rempel (Alexey Fisher) <bug-track@fisher-privat.net>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
As pointed out by Bastien Nocera in bug 671902, CheeseCamera overwrites
GError pointers. Avoid this by setting the error and returning
immediately afterwards.
|
|
|
|
|
|
| |
This allows compilation to succeed with
‘-Wdeclaration-after-statement -Werror=declaration-after-statement’
passed to GCC.
|
|
|
|
| |
Fixes bug 672311.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the last window is destroyed, GApplication will automatically exit
the main loop. Stops warnings like this on exit:
Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed
which occur with GTK+ versions 3.3.4 or greater, when GtkApplication was
changed to not override the GApplication mainloop.
https://bugzilla.gnome.org/show_bug.cgi?id=671904
|
| |
|