Motion - Support Question 2009x 06x 29x 184409

Motion on Freebsd


Thanks Florin:

When you say "Pick a different video source", do you mean try a different camera, or try a different port on the Capture Card?

Also, I don't know what you mean by: "Also happens sometimes if the tuner type is wrong, check the driver configuration".Do you mean the driver configuration for the capture card? I didn't install a driver, it jsut detected it. Or do I need a driver for the camera? It's not a netcam, webcam or usb camera. I can plug it into my TV and watch it just the way it is.



I'm new to motion. I've installed a bt878 4 port card that gets detected in Freebsd as /dev/bktr0. My problem is that the jpg's are just a blue box with the date and time in the lower right corner. I've checked the cabling (bnc) as well as the camera (Sharp 1/3" with IR).

What is it that I'm missing?

Any help would be appreciated.....


Paste in your error messages, config settings, terminal window output etc in this text field.
When I start motion I get this:

[0] Processing thread 0 - config file /usr/local/etc/motion.conf
[0] Thread 1 is from /usr/local/etc/motion.conf
[1] Thread started
[0] motion-httpd/3.2.8 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] VIDEO_PALETTE_YUV420P palette setting bufsize
[1] HUE [0]
[1] CONTRAST [108]
[1] VIDEO_PALETTE_YUV420P imgs.type
[1] Started stream webcam server in port 8081

When it takes a picture, I see this message on stdout:

[1] File of type 2 saved to: /usr/local/www/apache22/data/cam1/01-20090629150000-snapshot.jpg


Motion version: 3.2.11
ffmpeg version: FFmpeg version SVN-r10657
Libraries: ffmpeg, mysql
Server OS: FreeBSD 7.0 Release
-- FredSchnittke - 29 Jun 2009


- Read here :

- You say : I have a blue screen...

- Good, the overlay is working. A blue screen is what you get if the grabber chip has no input signal. You are probably using the wrong video source, pick another. Also happens sometimes if the tuner type is wrong, check the driver configuration.

-- FlorinAnton - 29 Jun 2009


- Well, first of all, BEFORE experimenting with Motion, you must be sure that your video camera + capture card + P.C. is working O.K. (you must see the video stream from your camera displayed on your monitor via xawtv program or similar).

- You will need drivers for capture card and not for video camera. Read here and here

- In fact, you must : connect video camera to one input source of capture card, install xawtv or similar program, check your video stream with xawtv or similar program on your monitor (change to another input port source of capture card - you have 4 inputs - if you still get blue images). Only after you see the video stream, enjoy your "journey" with Motion...

- Usefull linux commands to see what's going on with your capture card : dmesg | grep bttv , lspci -v, lsmod | grep bttv

- Also check your /var/log/messages log...


-- FlorinAnton - 30 Jun 2009

[0] motion-httpd/3.2.8 running, accepting connections

Are you sure motion-3.2.11 is running over there ?!

Please review carefully motion guide, and motion.conf you are running .

-- AngelCarpintero - 09 Jul 2009

Closed , no feedback probably issues fixed once user upgrade to 3.2.11 ( or ).

-- AngelCarpintero - 05 Aug 2009
Topic revision: r6 - 05 Aug 2009, AngelCarpintero
Copyright © 1999-2018 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.