Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-macos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-macos
  • Issues
  • #99

Closed
Open
Created Jan 12, 2016 by RingBot@RingBotOwner

OSX: Camera not opening

Issue generated from Tuleap's migration script. Originally submitted by: Alexandre Lision (alision)

Some camera can't be opened, libav stacktrace:

[avfoundation @ 0x1049d2a00] Selected framerate (30.000000) is not supported by the device
[avfoundation @ 0x1049d2a00] device configuration failed
[avfoundation @ 0x1049d2a00] Supported modes:
[avfoundation @ 0x1049d2a00] 160x90@[30.000030 30.000030]fps
[avfoundation @ 0x1049d2a00] 160x90@[24.000038 24.000038]fps
[avfoundation @ 0x1049d2a00] 160x90@[20.000000 20.000000]fps
[avfoundation @ 0x1049d2a00] 160x90@[15.000015 15.000015]fps
[avfoundation @ 0x1049d2a00] 160x90@[10.000000 10.000000]fps
[avfoundation @ 0x1049d2a00] 160x90@[7.500002 7.500002]fps
[avfoundation @ 0x1049d2a00] 160x90@[5.000000 5.000000]fps
[avfoundation @ 0x1049d2a00] 160x120@[30.000030 30.000030]fps
[avfoundation @ 0x1049d2a00] 160x120@[24.000038 24.000038]fps
[avfoundation @ 0x1049d2a00] 160x120@[20.000000 20.000000]fps
[avfoundation @ 0x1049d2a00] 160x120@[15.000015 15.000015]fps
[avfoundation @ 0x1049d2a00] 160x120@[10.000000 10.000000]fps
[avfoundation @ 0x1049d2a00] 160x120@[7.500002 7.500002]fps
[avfoundation @ 0x1049d2a00] 160x120@[5.000000 5.000000]fps
[avfoundation @ 0x1049d2a00] 176x144@[30.000030 30.000030]fps
[avfoundation @ 0x1049d2a00] 176x144@[24.000038 24.000038]fps
[avfoundation @ 0x1049d2a00] 176x144@[20.000000 20.000000]fps
[avfoundation @ 0x1049d2a00] 176x144@[15.000015 15.000015]fps
[avfoundation @ 0x1049d2a00] 176x144@[10.000000 10.000000]fps
[avfoundation @ 0x1049d2a00] 176x144@[7.500002 7.500002]fps
[avfoundation @ 0x1049d2a00] 176x144@[5.000000 5.000000]fps
[avfoundation @ 0x1049d2a00] 320x180@[30.000030 30.000030]fps
[avfoundation @ 0x1049d2a00] 320x180@[24.000038 24.000038]fps
[avfoundation @ 0x1049d2a00] 320x180@[20.000000 20.000000]fps
[avfoundation @ 0x1049d2a00] 320x180@[15.000015 15.000015]fps
[avfoundation @ 0x1049d2a00] 320x180@[10.000000 10.000000]fps
[avfoundation @ 0x1049d2a00] 320x180@[7.500002 7.500002]fps
[avfoundation @ 0x1049d2a00] 320x180@[5.000000 5.000000]fps

This is an issue in libav introduced by me. I supposed the upper and lower boundaries of the framerates ranges were exclusive.

I'll patch my implementation

Assignee
Assign to
Time tracking