Bug 505534 - Green webcam capture - gstreamer settings not "sticking"
Summary: Green webcam capture - gstreamer settings not "sticking"
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer
Version: 11
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-06-12 09:43 UTC by Chris Nolan
Modified: 2009-09-19 13:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-09-19 13:46:41 UTC
Type: ---

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 349255 0 None None None Never

Description Chris Nolan 2009-06-12 09:43:54 UTC
Description of problem:

gstreamer is using the wrong default settings for video input when using an iSight camera on a MacBook (tested on MacBook 4,1 but reported on other MacBook models too - see ubuntu bug). This results in a green image displayed from the webcam. 

Additionally, when selecting "custom" settings in gstreamer-properties and correcting the issue the settings do not "stick" and are not read by applications that use gstreamer.

This also happened exactly the same in F10.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. On a MacBook with iSight camera installed run "gstreamer-properties"
2. For "Video Input" select v4l2 plugin and built-in isight device.
3. Press Test (or run "cheese" or any other app that uses gstreamer for webcam)
Actual results:

Green picture.

Expected results:

Normal colours.

Additional info:

The gstreamer-properties "Test" works just fine if you select "Custom" plugin under "Video Input" and use the following pipeline:

v4l2src device="/dev/video0" ! videoscale

However, when you close gstreamer-properties and reopen it, the "Custom" settings do not stick, and applications such as "Cheese" that use gstreamer do not pick up or use the custom settings.

Please let me know if I can provide more info.

Comment 1 Chris Nolan 2009-09-19 13:46:41 UTC
This appears to be fixed, in cheese at least. Changing status to CLOSED CURRENTRELEASE.

Note You need to log in before you can comment on or make changes to this bug.