BUG: The streaming netcam feature doesn't appear to work with Raytalk RTAV700

The streaming netcam feature used with a Raytalk RTAV700 produces errors. Its JPEG URL is: and it works. At startup it works. But after a few minutes Motion streaming netcam stops and produces some errors as described below.

A similar RTAV600 works well but it has a MJPEG streaming url.

Relevant output is:

[HTTP/1.1 200 OK] Netcam: thread 1: jpeg file Netcam stream : thread 2: Content-length supported

and in fact at startup it works. But after a few minutes:

Netcam thread 1 : Error checking JPEG not start code Not a JPEG file: starts with 0x3c 0x21 Netcam thread 1 : Error checking JPEG not end code Netcam thread 1 : Error checking JPEG not end code Bogus Huffman table definition Thread 1 Condiction timeout Thread 1 Condiction timeout

My config is:

# motion.conf
daemon off
quiet on
framerate 25
quality 85
auto_brightness off
brightness 0
contrast 0
saturation 0
hue 0
ffmpeg_cap_new off
target_dir /var/www/motion
webcam_localhost off
webcam_quality 50
webcam_maxrate 8
webcam_motion off
output_normal off
thread /etc/motion/camera-intersiel.conf

# /etc/motion/camera-intersiel.conf
width 320 
height 240 
netcam_url http://cameraip/cgi-bin/video.jpg
netcam_userpass root:xxxxxxxxxx
webcam_port 8002

Environment

Motion version:	3.1.19-1
ffmpeg version:
Shared libraries:	ffmpeg, mysql, postgresql
Server OS:	Debian stable 2.4.27-2-386

-- AaBb - 31 May 2006

Follow up

You are using 3.1.19

That version is so old and so full of errors in netcam code that you will never get any success.

Please upgrade to 3.2.6 which is the current version. There is even a deb you can install.

-- KennethLavrsen - 31 May 2006

Follow up

Upgraded to 3.2.6. Errors are gone but motion loses connection to cameras very very often.

---

Many network cameras cannot handle serving too many jpeg files too fast.

If you try to fetch 25 frames per second you will fail all the time. Only a capture card can do that - that fast in practical. Try with 2-5 frames per second.

If your network camera supports mjpeg then that is a faster protocol where the connection is constant and it is the camera that decides the speed.

-- KennethLavrsen - 11 Jun 2006