Bug 127581 - Yahoo Video Stream Settings Not Initialized Properly
Summary: Yahoo Video Stream Settings Not Initialized Properly
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Unmaintained
Component: Audio/Video Plugin (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-18 14:06 UTC by Jesse Litton
Modified: 2008-01-22 03:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Litton 2006-05-18 14:06:34 UTC
Version:           0.12 beta2 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
Compiler:          gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5) 
OS:                Linux

Each time I start a Yahoo video chat, the brightness/contrast of my stream and preview window do not match what I previously set in the configuration dialog.  My stream starts out ultra-bright and washed out.

Going back into the configuration dialog corrects the issue, but it re-appears with each new test chat that I initiate (and has to be corrected via the configuration screen again).

I'm using a Logitech Quickcam Express II (SPCA561 input) on Kubuntu Dapper 6.06.

I do not see this problem when testing MSN video, so it seems to be specific to the Yahoo plugin.

Thanks,
Jesse
Comment 1 Cláudio da Silveira Pinheiro 2008-01-22 03:56:48 UTC
This bug is fixed somewhat, as I tested it with 8 different devices, and couldn't reproduce it.
spca5xx and gspca drivers have known issues with image controls. They act in some unpredictable manner, and a control changes others' values in some cases (notably with Creative Webcam NX aka PD-1130), so it's mostly a driver issue. sn9c102 devices have non-standard controls (like R-B Balance), and wrongly reports them as being standard ones. Work is being done to implement those non-standard controls, but it's out of the scope of this bug.