Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(87)

Issue 220193006: Win DirectShow: connect antibanding/anti-flicker where supported. (Closed)

Created:
6 years, 8 months ago by mcasas
Modified:
6 years, 8 months ago
CC:
chromium-reviews, fischman+watch_chromium.org, jam, mcasas+watch_chromium.org, feature-media-reviews_chromium.org, darin-cc_chromium.org, wjia+watch_chromium.org, miu+watch_chromium.org, jansson
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Visibility:
Public.

Description

Win DirectShow: connect antibanding/anti-flicker where supported. Some Win UVC devices implement the PROPSETID_VIDCAP_VIDEOPROCAMP API [1]. For them, set the anti-banding/anti-flicker/power frequency rejection to the appropriate frequency (50/60Hz). This settings sinks all the way into the WebCam DSP so it's hard to know for sure what is being done, similarly to http://crrev.com/216263007, although is likely to avoid certain exposure rates non-multiples of the power frequency. IAMVideoProcAmp interface provides access to the same IKsPropertySet. [1] http://msdn.microsoft.com/en-us/library/windows/hardware/ff568122(v=vs.85).aspx BUG=357599 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=265646

Patch Set 1 : #

Total comments: 6

Patch Set 2 : tommi@s comments #

Total comments: 8

Patch Set 3 : tommi@s nits #

Unified diffs Side-by-side diffs Delta from patch set Stats (+39 lines, -3 lines) Patch
M media/video/capture/win/video_capture_device_win.h View 1 2 chunks +4 lines, -3 lines 0 comments Download
M media/video/capture/win/video_capture_device_win.cc View 1 2 3 chunks +35 lines, -0 lines 0 comments Download

Messages

Total messages: 13 (0 generated)
mcasas
tommi@ PTAL.
6 years, 8 months ago (2014-04-08 08:02:25 UTC) #1
tommi (sloooow) - chröme
https://codereview.chromium.org/220193006/diff/90001/media/video/capture/win/video_capture_device_win.cc File media/video/capture/win/video_capture_device_win.cc (right): https://codereview.chromium.org/220193006/diff/90001/media/video/capture/win/video_capture_device_win.cc#newcode597 media/video/capture/win/video_capture_device_win.cc:597: const int power_line_frequency = GetPowerLineFrequencyForLocation(); This function is getting ...
6 years, 8 months ago (2014-04-08 10:16:19 UTC) #2
mcasas
tommi@ PTAL. https://codereview.chromium.org/220193006/diff/90001/media/video/capture/win/video_capture_device_win.cc File media/video/capture/win/video_capture_device_win.cc (right): https://codereview.chromium.org/220193006/diff/90001/media/video/capture/win/video_capture_device_win.cc#newcode597 media/video/capture/win/video_capture_device_win.cc:597: const int power_line_frequency = GetPowerLineFrequencyForLocation(); On 2014/04/08 ...
6 years, 8 months ago (2014-04-08 10:33:31 UTC) #3
mcasas
ping.
6 years, 8 months ago (2014-04-22 14:13:17 UTC) #4
tommi (sloooow) - chröme
lgtm % nits https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win/video_capture_device_win.cc File media/video/capture/win/video_capture_device_win.cc (right): https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win/video_capture_device_win.cc#newcode759 media/video/capture/win/video_capture_device_win.cc:759: HRESULT hr; nit: define where you ...
6 years, 8 months ago (2014-04-22 14:55:27 UTC) #5
mcasas
The CQ bit was checked by mcasas@chromium.org
6 years, 8 months ago (2014-04-23 10:51:27 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/mcasas@chromium.org/220193006/170001
6 years, 8 months ago (2014-04-23 11:00:48 UTC) #7
commit-bot: I haz the power
The CQ bit was unchecked by commit-bot@chromium.org
6 years, 8 months ago (2014-04-23 11:49:42 UTC) #8
commit-bot: I haz the power
Try jobs failed on following builders: tryserver.chromium on linux_chromium_chromeos_rel
6 years, 8 months ago (2014-04-23 11:49:43 UTC) #9
mcasas
The CQ bit was checked by mcasas@chromium.org
6 years, 8 months ago (2014-04-23 13:13:07 UTC) #10
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/mcasas@chromium.org/220193006/170001
6 years, 8 months ago (2014-04-23 13:13:18 UTC) #11
commit-bot: I haz the power
Change committed as 265646
6 years, 8 months ago (2014-04-23 15:36:05 UTC) #12
mcasas
6 years, 8 months ago (2014-04-23 17:04:45 UTC) #13
Message was sent while issue was closed.
https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win...
File media/video/capture/win/video_capture_device_win.cc (right):

https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win...
media/video/capture/win/video_capture_device_win.cc:759: HRESULT hr;
On 2014/04/22 14:55:27, tommi wrote:
> nit: define where you need it

Done.

https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win...
media/video/capture/win/video_capture_device_win.cc:762: power_line_frequency ==
kPowerLine60Hz) {
On 2014/04/22 14:55:27, tommi wrote:
> nit: could also turn this into an early return to reduce the number of scopes.
> 
> if (power_line_frequency != kPowerLine50Hz &&
>     power_line_frequency != kPowerLine60Hz) {
>   return;
> }
> 
> ...

Done.

https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win...
media/video/capture/win/video_capture_device_win.cc:767:
KSPROPERTY_VIDEOPROCAMP_POWERLINE_FREQUENCY,
On 2014/04/22 14:55:27, tommi wrote:
> not sure about this indent... think it should be:
> 
> SUCCEEDED(...
>     KSPROPERTY_...

Done.

https://codereview.chromium.org/220193006/diff/130001/media/video/capture/win...
media/video/capture/win/video_capture_device_win.cc:779: DVLOG_IF(2, FAILED(hr))
<< "Anti-flicker setting failed.";
On 2014/04/22 14:55:27, tommi wrote:
> DLOG_IF(ERROR, FAILED(hr)) ?

Done.

Powered by Google App Engine
This is Rietveld 408576698