Re: motion: problem finding codec
On 10/20/2012 10:09 PM, H.S. wrote:
>>From my yesterday's logs, here is what I was getting when the camera worked:
> Oct 18 09:40:28 red motion: [0] Processing thread 0 - config file
> /etc/motion/motion.conf
> Oct 18 09:40:28 red motion: [0] Motion 3.2.12 Started
> Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368
> LIBAVFORMAT_BUILD 3478784
> Oct 18 09:40:28 red motion: [0] Thread 1 is from /etc/motion/motion.conf
> Oct 18 09:40:28 red motion: [1] Thread 1 started
> Oct 18 09:40:28 red motion: [1] cap.driver: "uvcvideo"
> Oct 18 09:40:28 red motion: [1] cap.card: "UVC Camera (046d:0990)"
>
>
> That "ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478784" appears
> to be missing now. I wonder whether something during today's upgrade?
>
> Thanks.
Here is what appears to have changed since my last night's upgrade:
[UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
[UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1
[UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3
[UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
[UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
[UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
[UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
Could this have broken motion?
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
Reply to: