motion is unable to use ffmpeg library

Bug #281436 reported by Jan de Wal
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
motion (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

root@Joh-c:/home/jan# motion -c /etc/motion/motion.conf
[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion 3.2.9 Started
[0] ffmpeg LIBAVCODEC_BUILD 3355136 LIBAVFORMAT_BUILD 3409664
[0] Thread 1 is from /etc/motion/motion.conf
[1] Thread 1 started
[0] motion-httpd/3.2.9 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] cap.driver: "pwc"
[1] cap.card: "Philips 675 webcam"
[1] cap.bus_info: "usb-0000:00:10.1-2.1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PWC2 (Raw Philips Webcam)
[1] 1: YU12 (4:2:0, planar, Y-Cb-Cr)
[1] Test palette YU12 (320x240)
[1] Using palette YU12 (320x240) bytesperlines 480 sizeimage 115200 colorspace 00000000
[1] found control 0x00980900, "Brightness", range 0,128
[1] "Brightness", default 64, current 63
[1] found control 0x00980901, "Contrast", range 0,64
[1] "Contrast", default 0, current 63
[1] found control 0x00980902, "Saturation", range -100,100
[1] "Saturation", default 0, current 0
[1] found control 0x0098090e, "Red Gain", range 0,256
[1] "Red Gain", default 0, current 96
[1] found control 0x0098090f, "Blue Gain", range 0,256
[1] "Blue Gain", default 0, current 96
[1] found control 0x00980910, "Gamma", range 0,32
[1] "Gamma", default 0, current 27
[1] found control 0x00980911, "Shutter Speed (Exposure)", range 0,256
[1] "Shutter Speed (Exposure)", default 200, current 0
[1] found control 0x00980912, "Auto Gain Enabled", range 0,1
[1] "Auto Gain Enabled", default 1, current 1
[1] found control 0x00980913, "Gain Level", range 0,256
[1] "Gain Level", default 0, current -41
[1] found control 0x08000000, "Save User Settings", range 0,0
[1] "Save User Settings", default 0, current 0
[1] found control 0x08000001, "Restore User Settings", range 0,0
[1] "Restore User Settings", default 0, current 0
[1] mmap information:
[1] frames=2
[1] 0 length=462848
[1] 1 length=462848
[1] Using V4L2
[1] Started stream webcam server in port 8081
[1] Codec not found: Invalid argument
[1] ffopen_open error creating (new) file [/home/jan/webcam/221731-20081010.avi]: Invalid argument
[1] Thread exiting
[0] Motion terminating
[0] httpd - Finishing: Success
[0] httpd Closing
root@Joh-c:/home/jan#

Revision history for this message
Jan de Wal (jan-dewal) wrote :

Ubuntu 8.10 - installed (upgraded) 10 okt. (using that beta/alpha)

Revision history for this message
DataPath (compenguy) wrote :

I have been experiencing this problem as well. It is still present after updating as of October 20.

Revision history for this message
Kirk Bridger (kbridger) wrote :

I upgraded from Hardy to Intrepid Nov 6 and this problem now occurs for me as well. This essentially breaks the motion software, unless there's a workaround?

Revision history for this message
Karl.S (jalik7) wrote :

Same for me on Ubuntu 8.10 with all gstreamers's codecs installed, motion works with FLV and SWF but not with MPEG4 and MSMPEG4..
where is the problem? FFMPEG or MOTION ?

Revision history for this message
Jan de Wal (jan-dewal) wrote :

Found a sollution, this bug is sitting here way to long, ok here's what i did :
Install the following packages:

libavcodec-unstripped-51
libavformat-unstripped-52

Might need both might need one of these, either way i have installed this and now motion works.

Please note that these are multiverse packages and i dont know how it impacts the rest of the packages maintained by ubuntu, because this removes the stripped versions as they conflict with each other.

Please let me know if it did the trick for you to :)

Greetings Jan

Revision history for this message
Beetle (snowballpuffington) wrote :

Installing those packages did the trick for me. Thanks :)

Revision history for this message
Tony Brown (bonybrown) wrote :

This was all working in 8.04, and broke immediately after upgrade to 8.10
Installation of the unstripped libraries got it working for me as well.

Revision history for this message
Brian (bschoen) wrote :

Works for me too but I had to compile "motion" with the stripped versions and then install the unstripped libraries.

Jan de Wal (jan-dewal)
Changed in motion:
status: New → Confirmed
Revision history for this message
Pekka Vuorela (pvuorela-iki) wrote :

Looks like this is still present in Jaunty.

Revision history for this message
Pekka Vuorela (pvuorela-iki) wrote :

Further details:
- installing libavcodec-unstripped-52 is enough for workaround.

- the problems seems to result from unstripped and normal libavcodec compiled with different dependency flags. The unstripped version depends on libfaac0, libfaad0, libx264-65 and libxvidcore4 where the normal version doesn't.

- libavcodec is in main, unstripped and the above dependencies are in multiverse.

- Motion depends on libavcodec52 (>= 3:0.svn20081101-1) | libavcodec-unstripped-52 (>= 3:0.svn20081101-1), looks like it should only depend on the latter.

- Motion lives in universe. Does this allow depending on multiverse?

Revision history for this message
Peter Grandi (pg-8) wrote :

This page:

https://forums.gentoo.org/viewtopic-t-963876.html?sid=49af6a7ab765b3c4c4a9652504a8794d

has a complete discussion of this problem with the solution.

It happens to be under 14.04 too.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.