Package: motion Version: 4.0-1 Severity: normal This is an bug for posterity. I've already fixed the issue myself.
After upgrading from binary version 3.4.1 to 4.0, I noticed that my video capture was blocky and very poor quality. There was no change in my configuration prior or during this upgrade. After playing with settings, I noticed that if I commented out "ffmpeg_variable_bitrate 2", the issue went away and quality was once again good. The default for ffmpeg_variable_bitrate is 0. Playing with this setting didn't seem to have any effect on video quality, other than making it bad. I suspect this knob has been broken somewhere. FYI I have "ffmpeg_video_codec mpeg4" set. My ffmpeg installation was also upgraded at the same time, so this may simply be an issue in ffmpeg and not have anything to do with motion. Feel free to close after reading. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages motion depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.59 ii libavcodec57 10:3.2-dmo1 ii libavformat57 10:3.2-dmo1 ii libavutil55 10:3.2-dmo1 ii libc6 2.24-5 ii libjpeg62-turbo 1:1.5.1-2 ii libmariadbclient18 10.0.28-1 ii libpq5 9.6.1-2 ii libsqlite3-0 3.15.1-1 ii libswscale4 10:3.2-dmo1 ii lsb-base 9.20161101 ii zlib1g 1:1.2.8.dfsg-2+b3 Versions of packages motion recommends: ii ffmpeg 10:3.2-dmo1 Versions of packages motion suggests: pn default-mysql-client <none> pn postgresql-client <none> -- Configuration Files: /etc/default/motion changed [not included] /etc/motion/motion.conf changed [not included] -- debconf information excluded
