From 0f2be803b4081a6f4dcffc44456a55d2e2f6d1d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tommi=20My=C3=B6h=C3=A4nen?= Date: Thu, 10 Sep 2009 15:16:23 +0300 Subject: [PATCH] camerabin: fix image queue parameter setting Camerabin incorrectly used G_GUINT64_CONSTANT macro for setting "max-size-buffers" and "max-size-bytes" properties in image queue, even when they aren't 64bit integers. --- gst/camerabin/gstcamerabin.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/gst/camerabin/gstcamerabin.c b/gst/camerabin/gstcamerabin.c index 31325f9193..301899f9cb 100644 --- a/gst/camerabin/gstcamerabin.c +++ b/gst/camerabin/gstcamerabin.c @@ -731,10 +731,8 @@ camerabin_create_elements (GstCameraBin * camera) /* To avoid deadlock, we won't restrict the image queue size */ /* FIXME: actually we would like to have some kind of restriction here (size), but deadlocks must be handled somehow... */ - g_object_set (G_OBJECT (camera->img_queue), - "max-size-time", G_GUINT64_CONSTANT (0), - "max-size-bytes", G_GUINT64_CONSTANT (0), - "max-size-buffers", G_GUINT64_CONSTANT (0), NULL); + g_object_set (G_OBJECT (camera->img_queue), "max-size-buffers", 0, + "max-size-bytes", 0, "max-size-time", G_GUINT64_CONSTANT (0), NULL); camera->pad_src_queue = gst_element_get_static_pad (camera->img_queue, "src");