Motion - Feature Request 2005x 10x 20x 210336

Feature Request: Unique Camera Identifier


There are Modifiers for THREAD numbers, but I consider that threads are numbered not in the order they appear in motion.conf. Between restarts, you never can tell whether thread 1 really picks up cam 1 and so on. Therefor it would be great to have a camera identifier in the thread confs which is unique and can be used as modifier in filenames. This has been posted once by an unlucky guy which obviously never get back to his postings, therefor I repeat this request.

-- AxelAmthor - 20 Oct 2005

Follow up


The new %t conversion specifier numbers each thread in the order the thread options are found in motion.conf.

The thread may take more or less time to start up and report themselves alive depending on how fast the camera responds but the %t specifier is counting correctly.

The FeatureRequest2005x08x07x134844 was not very clear. He wrote "A new conversion specifier to indicate which camera has detected motion in a multi-cam setup would be useful for defining per camera behaviour/alert lists." and this still does not make sense to me.

The %t specifier does not really add any feature you could not do before. The only new is that you can specify an option such as

text_left CAMERA %t

in motion.conf without having to repeat it in each thread file.

When you boot a machine you may not always know which camera device gets which video device number. No options and conversion specifier inside Motion can solve that issue.

Video capture cards using bttv are predictable. They load in an order given by the PCI bus.

The Philips Web Cam (PWC) driver has a dev_hint option which is very useful for loading video devices in a controlled way. Example from my /etc/modprobe.conf

options pwc dev_hint=740.01690000C8C07101:8,740.01530000A43A0001:9,740.01680000531A0101:10,11,12,13,14,15,16 size=sif

This ensures that my Logitechs and Philips camera load in a predictable order and always at device numbers higher then 8. My bttv based 8 input card then loads from video0 to video7 and since it is PCI bus based this order is predictable too. So I always get my cameras in the right sequence after a boot.

And my new %t specifier works great with my 9 cameras and always shows the same number on the same camera given by the order of the thread options in motion.conf.

-- KennethLavrsen - 20 Oct 2005

Feature already there. Submitter did not have any follow ups.

-- KennethLavrsen - 14 Nov 2005
Topic revision: r3 - 14 Nov 2005, KennethLavrsen
Copyright © 1999-2024 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.