Motion - Support Question 2015x 06x 21x 075421

unrecognized image header, choppy image

Question

Hi

I have 3 IP cameras. 1 and 2 work flawlessly with motion as thread1 and thread2 and run at 720p. I'm using an up to date RPi2. The third camera is giving me problems.It works fine in 640x480 but in 720p the image is very choppy and breaks up continously. I have had it running on a second RPi2 to ensure the issue was not related to the Pi itself. It's not. It could be a camera fault I suppose but I want to check out Motion first before sending it back. What might this error log point to please?

Part of the log is copied below. When left running in 720p I just get the "Unrecognized image header" repeated.

Thanks for any help / pointers.

Jun 21 08:49:09 CCTVpi motion: [3] Unrecognized image header (1)
Jun 21 08:49:14 CCTVpi motion: [3] connect() failed (106): Transport endpoint is already connected
Jun 21 08:49:14 CCTVpi motion: [3] re-opening camera (streaming)ur error messages, config settings, terminal window output etc in this text field.

Environment

Motion version: 3.2.12
ffmpeg version: ffmpeg 0.8.17-6:0.8.17-1+rpi1
Libraries: ffmpeg, mysql, postgresql
Server OS: Raspian
-- DonAitken - 21 Jun 2015

Answer

Topic revision: r1 - 21 Jun 2015, DonAitken
Copyright © 1999-2017 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.