BUG: Need to set norm to NTSC in xawtv for threads beyond 0

4 identical cameras (NTSC) connected to a 4 port/4 processor capture card. To get threads 1 through 3 functioning in NTSC, you must first set each individual input to NTSC through xawtv. Not doing so will result in PAL video output for threads 1 through 3.

here are my config files:

motion.conf:

auto_brightness off
daemon off

ffmpeg_cap_new on
ffmpeg_deinterlace on
despeckle EedDl
framerate 30
width 320
height 240

hue 180
saturation 100
brightness 200
contrast 100

max_mpeg_time 3600
low_cpu 30

#number of pixels changed before recording
threshold 500

#number of frames after motion to continue recording
post_capture 30

webcam_localhost off
webcam_maxrate 2
webcam_port 8001
webcam_quality 30
output_normal off
input 1
norm 1

control_html_output on
control_port 8000

thread /etc/motion/thread0.conf
thread /etc/motion/thread1.conf
thread /etc/motion/thread2.conf
thread /etc/motion/thread3.conf

---
thread0.conf:

videodevice /dev/video0
movie_filename %m-%d-%Y-%H-%M_Camera1
target_dir /home/camera/security/Camera1

---
thread1.conf:

videodevice /dev/video1
movie_filename %m-%d-%Y-%H-%M_Camera2
target_dir /home/camera/security/Camera2

---
thread2.conf:

videodevice /dev/video2
movie_filename %m-%d-%Y-%H-%M_Camera3
target_dir /home/camera/security/Camera3

---
thread3.conf:

videodevice /dev/video3
movie_filename %m-%d-%Y-%H-%M_Camera4
target_dir /home/camera/security/Camera4

Environment

Motion version:	3.2.9
ffmpeg version:	unknown
Shared libraries:	ffmpeg, mysql, postgresql
Server OS:	Ubuntu 7.10 current

-- WillBuddenberg - 27 Nov 2007

Follow up

Interesting observation. We have had several reports that people had to use another program before using Motion.

-- KennethLavrsen - 27 Nov 2007

---

Still happening with 3.2.10.1 ?

-- AngelCarpintero - 15 Jun 2008

Fix record