summaryrefslogtreecommitdiffstats
path: root/src/plugins/avfoundation/mediaplayer/avfmediaplayersession.mm
diff options
context:
space:
mode:
authorVal Doroshchuk <valentyn.doroshchuk@qt.io>2020-01-02 14:22:07 +0100
committerVaL Doroshchuk <valentyn.doroshchuk@qt.io>2020-01-09 13:58:48 +0000
commita8123e737140719549252806e0e6a1c121359f79 (patch)
tree555a89058e4e2a74ad67201959a4b43f2c5cea2f /src/plugins/avfoundation/mediaplayer/avfmediaplayersession.mm
parenta8f83d4a3ebbe106a84183178b715bdff24768b3 (diff)
AVF: Don't apply settings if the camera is not active yet
In macOS, a capture session can still automatically configure the capture format after you make changes. If frame rates are applied to the capture device and the camera is still not active, these rates will be overridden by old values when the capture session will be started. For this purpose lockForConfiguration is currently used within startRunning method of capture session. But in case if the settings are already applied to the capture device, we don't call lockForConfiguration within starting of the capture session (since it is needed to be called only when the settings have been changed). Suggesting to postpone setting of the format (to the capture device) until the camera is started. This will lead to apply settings before startRunning method with proper configuration lock. Fixes: QTBUG-81048 Change-Id: I04664e7b63474ce28571e888e524170b995a38d6 Reviewed-by: Andy Shaw <andy.shaw@qt.io>
Diffstat (limited to 'src/plugins/avfoundation/mediaplayer/avfmediaplayersession.mm')
0 files changed, 0 insertions, 0 deletions