Motion - Support Question 2005x 05x 11x 161256

what's mean? only YUV420 is supported


[root@fedora3 r]# ./mostart
Processing thread 0 - config file /etc/motion/motion.conf
Thread0 device: /dev/video0 input: 8
[mpeg4 @ 0x37ee330]only YUV420 is supported
./mostart: line 1:  4452 segmentation error motion -c /etc/motion/motion.conf
[root@fedora3 r]#

I'm using Linux fedora3 2.6.11-1.14_FC3 very well.

after upgrade new kernel 2.6.11-8, happen error above.

but, using Linux fedora3 2.6.11-1.14_FC3, don't work.

-- ParkCh - 11 May 2005


Motion version: Please fill out this
ffmpeg version: and this
Libraries: curl, xmlrpc, ffmpeg, mysql, postgresql remove those not used!
Server OS: fedora3 2.6.11-1.14_FC3

-- JamesPhipps - 10 May 2005


I changed your Feature request to a support request.

You have given FAR to little information for anyone to help you.

We need to know

Motion version

Which camera?

What is your motion.conf?

Any other errors?

Does your camera work in other programs?

-- KennethLavrsen - 11 May 2005


Motion: 3.1.19 ffmpeg: 0.4.9-pre1 and 0.4.9-0 Libraries: ffmpeg OS: Fedora Core 3 2.6.11-20_FC3

I had the same problem when I upgraded ffmpeg 0.4.9-pre1 through yum and I'm using an older Phillips webcam (PCVC 740K) and the pwc drivers. From what I've been able to find on the web, the images produced by this set up have a palette of YUV420p, which from the error message appears to not be supported by the ffmpeg verison I got from I grabbed sources for ffmpeg 0.4.9-pre1 and recompiled, then linked motion to this version of ffmpeg, now everything works great.

Hopefully this will help anyone who like me has this problem and runs across this support request.

-- DavidBoerema - 16 May 2005

I have the same problem. Here are some details:

Exact Error:

# motion -n
Processing thread 0 - config file motion.conf
Thread 0 started
motion-httpd/3.2.1 running, accepting connections
motion-httpd: waiting for data on port TCP 8080
[mpeg4 @ 0x3fbf10]only YUV420 is supported
avcodec_open - could not open codec: Success
Segmentation fault

NOTE: I can view the live images by going to localhost:8081 and it is fine until the camera sees motion, once the camera sees motion it crashes with the above error.

Fedora Core 3: 2.6.11-1.14_FC3
ffmpeg version 0.4.9-pre1, build 4755, Copyright (c) 2000-2004 Fabrice Bellard
  built on May 18 2005 11:40:15, gcc: 3.4.3 20050227 (Red Hat 3.4.3-22.fc3)
ffmpeg      0.4.9-pre1
libavcodec  4755
libavformat 4624
Camera: Sony XC999
Capture Card: Brooktree Corporation Bt878 Video Capture (rev 11)

No other errors and the camera works in programs like xawtv just fine.

motion.conf (comments removed):

daemon on
setup_mode off
videodevice /dev/video0
input 0
norm 1
frequency 0
rotate 0
width 320
height 240
framerate 100
auto_brightness off
brightness 0
contrast 0
saturation 0
hue 0
roundrobin_frames 1
roundrobin_skip 1
switchfilter 0
threshold 1500
threshold_tune off
noise_level 32
noise_tune on
night_compensate off
despeckle EedDl
smart_mask_speed 0
lightswitch 0
minimum_motion_frames 1
pre_capture 0
post_capture 3000
gap 60
minimum_gap 0
max_mpeg_time 0
low_cpu 0
output_all off
output_normal on
output_motion off
quality 75
ppm off
fmpeg_cap_new on
ffmpeg_cap_motion off
ffmpeg_timelapse 0
ffmpeg_timelapse_mode daily
ffmpeg_bps 500000
ffmpeg_variable_bitrate 0
ffmpeg_video_codec mpeg4
snapshot_interval 0
locate on
text_right %Y-%m-%d\n%T-%q
text_left 'Room 301'
text_changes off
target_dir /var/security/cam301
snapshot_filename %v-%Y%m%d%H%M%S-snapshot
jpeg_filename %v-%Y%m%d%H%M%S-%q
ffmpeg_filename %v-%Y%m%d%H%M%S
timelapse_filename %Y%m%d-timelapse
webcam_port 8081
webcam_quality 50
webcam_motion off
webcam_maxrate 20
webcam_localhost off
webcam_limit 0
control_port 8080
control_localhost on
control_html_output on
control_authentication security,security
track_type 0
track_motorx -1
track_maxx 0
track_iomojo_id 0
track_speed 255
track_stepsize 40
quiet on
sql_log_image on
sql_log_snapshot on
sql_log_mpeg off
sql_log_timelapse off

Nick (nniehoff at uccs dot edu)

-- NickNiehoff - 18 May 2005

I also tried msmpeg4, same error, just with msmpeg4v2 of course.


-- NickNiehoff - 18 May 2005

Did you try reinstalling a newer or older version of ffmpeg?

You probably have a badly working version. Ffmpeg is almost never releasing anything properly. It is always semi-tested shit CVS releases that they do. The ffmpeg have no release discipline what so ever unfortunately.

You can also download a source RPM and rebuild it. It fixed a problem for me. The RPMs from Dag and others often only works with specific other RPMs. A rebuild of the RPM from source RPM can fix dependencies.

-- KennethLavrsen - 18 May 2005

Ok, problem solved. The CVS version of ffmpeg is flawed. I downloaded the stable 0.4.9-pre1 version compiled and installed it. I then had to recompile and install motion but it all works now. Thanks,


-- NickNiehoff - 20 May 2005
Topic revision: r7 - 21 May 2005, KennethLavrsen
Copyright © 1999-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.