{"action":"closed","issue":{"url":"https://api.github.com/repos/Motion-Project/motion/issues/113","repository_url":"https://api.github.com/repos/Motion-Project/motion","labels_url":"https://api.github.com/repos/Motion-Project/motion/issues/113/labels{/name}","comments_url":"https://api.github.com/repos/Motion-Project/motion/issues/113/comments","events_url":"https://api.github.com/repos/Motion-Project/motion/issues/113/events","html_url":"https://github.com/Motion-Project/motion/issues/113","id":163572712,"number":113,"title":"Wrong range for ffmpeg_variable_bitrate option","user":{"login":"ccrisan","id":76639,"avatar_url":"https://avatars.githubusercontent.com/u/76639?v=3","gravatar_id":"","url":"https://api.github.com/users/ccrisan","html_url":"https://github.com/ccrisan","followers_url":"https://api.github.com/users/ccrisan/followers","following_url":"https://api.github.com/users/ccrisan/following{/other_user}","gists_url":"https://api.github.com/users/ccrisan/gists{/gist_id}","starred_url":"https://api.github.com/users/ccrisan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ccrisan/subscriptions","organizations_url":"https://api.github.com/users/ccrisan/orgs","repos_url":"https://api.github.com/users/ccrisan/repos","events_url":"https://api.github.com/users/ccrisan/events{/privacy}","received_events_url":"https://api.github.com/users/ccrisan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-07-03T18:01:45Z","updated_at":"2016-09-02T23:12:57Z","closed_at":"2016-09-02T23:12:57Z","body":"Playing with ffmpeg_variable_bitrate I noticed it had no effect whatsoever. Digging in deeper I discovered that the actual range for the quality used by ffmpeg/libav/whatever is 1 to 32767 (see [AVFrame::quality](https://www.ffmpeg.org/doxygen/3.0/structAVFrame.html#a791c071afd3e95fcae14cb781829754d) and [FF_LAMBDA_MAX](https://www.ffmpeg.org/doxygen/3.0/group__lavu__enc.html#gabc22a7ffbd4a73e81dd69e8c45e6cf8c)). Whereas the motion docs say valid values are 0 and 2 to 31.\r\n\r\nNow I have tested higher values and indeed, at say 31000, the movie quality is pretty bad (expected). I believe somehow, somewhere there's a missing factor of 1000.\r\n\r\nShould the docs be updated or should motion be patched to multiply the values by 1000 (or something)?\r\n\r\nI'm not sure if this is the best place to open/discuss this issue. Anyways, I believe however that @tosiara, @sackmotion and @Mr-Dave may have a good input on this matter."}}
{"actor":{"display_login":"Mr-Dave"}}