Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Identical cameras ([email protected])
2. Re: Identical cameras (chuck elliot)
3. Re: Motion blockers (Rainer Dorsch)
----------------------------------------------------------------------
Message: 1
Date: Sat, 29 Feb 2020 17:20:27 +0200
From: "[email protected]" <[email protected]>
To: Motion discussion list <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [Motion-user] Identical cameras
Message-ID:
<nwb7wo-fdrmyv-nbqdk7x3bj5h6j6l3l9urhvc-tkhjpm-803hrufawdvfpj2nbt-v2gdhkekb3ib3pybrb-ykuuu0-wf7ruxvpolnm-903k8o-764zog-w4pmfo-3uunsc-14rmjwpobjt8-zb3knnfswood.1582989627...@email.android.com>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sat, 29 Feb 2020 16:25:50 +0000
From: chuck elliot <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Identical cameras
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Thanks for those suggestions.
The MJPEG option produced "corrupt JPG data".
There is not an option to use different USB ports (only 2 there).
However, the reduced resolution option did work,
although I have had to go down to 352x288 for that
to work. Oh well, it is a very old laptop so I suppose
I should be happy with that ;o).
On Sat, 2020-02-29 at 17:03 +0200, tosiara wrote:
> This is USB bandwidth issue. Check dmesg for related errors
> Solution is to use MJPEG or reduce resolution
>
> On Sat, Feb 29, 2020 at 12:51 PM chuck elliot <[email protected]>
> wrote:
> > Hi,
> >
> > I have a problem using 2 identical logitec cameras with motion 3.2
> > on Centos 6.10.
> >
> > Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
> > Bus 001 Device 006: ID 046d:0825 Logitech, Inc. Webcam C270
> >
> > I have created 2 thread files with the respective 'videodevice'
> > parameters but only one camera connects, the other giving a grey
> > image.
> >
> > Needless to say, both cameras work fine on their own.
> >
> > Debug level 9 output doesn't appear to help a lot.
> >
> > 'grateful for any suggestions.
> >
> > motion's output follows.
> >
> > [0] Processing thread 0 - config file /etc/motion/motion.conf
> > [0] Processing config file camera1.conf
> > [0] Processing config file camera2.conf
> > [0] Motion 3.2.12 Started
> > [0] ffmpeg LIBAVCODEC_BUILD 3348992 LIBAVFORMAT_BUILD 3343872
> > [0] Thread 1 is from camera1.conf
> > [0] Thread 2 is from camera2.conf
> > [2] Thread 2 started
> > [2] cap.driver: "uvcvideo"
> > [2] cap.card: "UVC Camera (046d:0825)"
> > [2] cap.bus_info: "usb-0000:00:03.3-2"
> > [2] cap.capabilities=0x04000001
> > [2] - VIDEO_CAPTURE
> > [2] - STREAMING
> > [1] Thread 1 started
> > [2] Test palette YUYV (1280x960)
> > [2] Using palette YUYV (1280x960) bytesperlines 2560 sizeimage
> > 2457600
> > colorspace 00000008
> > [2] found control 0x00980900, "Brightness", range 0,255
> > [2] "Brightness", default 128, current 128
> > [2] found control 0x00980901, "Contrast", range 0,255
> > [2] "Contrast", default 32, current 32
> > [2] found control 0x00980902, "Saturation", range 0,255
> > [2] "Saturation", default 32, current 32
> > [2] found control 0x00980913, "Gain", range 0,255
> > [2] "Gain", default 64, current 64
> > [2] mmap information:
> > [2] frames=4
> > [2] 0 length=2457600
> > [2] 1 length=2457600
> > [2] 2 length=2457600
> > [2] 3 length=2457600
> > [2] Using V4L2
> > [1] cap.driver: "uvcvideo"
> > [1] cap.card: "UVC Camera (046d:0825)"
> > [1] cap.bus_info: "usb-0000:00:03.3-1"
> > [1] cap.capabilities=0x04000001
> > [1] - VIDEO_CAPTURE
> > [1] - STREAMING
> > [2] Resizing pre_capture buffer to 1 items
> > [1] Test palette YUYV (1280x960)
> > [1] Using palette YUYV (1280x960) bytesperlines 2560 sizeimage
> > 2457600
> > colorspace 00000008
> > [1] found control 0x00980900, "Brightness", range 0,255
> > [1] "Brightness", default 128, current 128
> > [1] found control 0x00980901, "Contrast", range 0,255
> > [1] "Contrast", default 32, current 32
> > [1] found control 0x00980902, "Saturation", range 0,255
> > [1] "Saturation", default 32, current 32
> > [1] found control 0x00980913, "Gain", range 0,255
> > [1] "Gain", default 64, current 64
> > [1] mmap information:
> > [1] frames=4
> > [1] 0 length=2457600
> > [1] 1 length=2457600
> > [1] 2 length=2457600
> > [1] 3 length=2457600
> > [1] Error starting stream VIDIOC_STREAMON:
> > [1] ioctl (VIDIOCGCAP):
> > [1] Could not fetch initial image from camera
> > [1] Motion continues using width and height from config file(s)
> > [1] Resizing pre_capture buffer to 1 items
> > [1] Started stream webcam server in port 8081
> > [1] Resizing pre_capture buffer to 6 items
> > [2] Started stream webcam server in port 8082
> > [2] Resizing pre_capture buffer to 6 items
> > [1] Retrying until successful connection with camera
> > [1] cap.driver: "uvcvideo"
> > [1] cap.card: "UVC Camera (046d:0825)"
> > [1] cap.bus_info: "usb-0000:00:03.3-1"
> > [1] cap.capabilities=0x04000001
> > [1] - VIDEO_CAPTURE
> > [1] - STREAMING
> > [1] Error selecting input 0 VIDIOC_S_INPUT:
> > [1] ioctl (VIDIOCGCAP):
> > [1] Retrying until successful connection with camera
> > [1] cap.driver: "uvcvideo"
> > [1] cap.card: "UVC Camera (046d:0825)"
> > [1] cap.bus_info: "usb-0000:00:03.3-1"
> > [1] cap.capabilities=0x04000001
> > [1] - VIDEO_CAPTURE
> > [1] - STREAMING
> > [1] Error selecting input 0 VIDIOC_S_INPUT:
> > [1] ioctl (VIDIOCGCAP):
> > [1] Retrying until successful connection with camera
> > [1] cap.driver: "uvcvideo"
> > [1] cap.card: "UVC Camera (046d:0825)"
> > [1] cap.bus_info: "usb-0000:00:03.3-1"
> > [1] cap.capabilities=0x04000001
> > [1] - VIDEO_CAPTURE
> > [1] - STREAMING
> > [1] Error selecting input 0 VIDIOC_S_INPUT:
> > [1] ioctl (VIDIOCGCAP):
> >
> >
> >
> >
> > _______________________________________________
> > Motion-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > https://motion-project.github.io/
> >
> > Unsubscribe:
> > https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 3
Date: Sat, 29 Feb 2020 21:25:35 +0100
From: Rainer Dorsch <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Motion blockers
Message-ID: <1878914.9Gyg7B7d8T@nanette>
Content-Type: text/plain; charset="us-ascii"
Thanks for your reply. You are thinking of the mask_file option, correct?
I think what would make the lightswitch feature more powerful is a separate
lightswitch mask. In my case there are positions which allow easily to detect
a lightswitch, if I exclusively would apply lightswitch to these. I think this
would make it then also equivalent to the blocking feature of zoneminder.
Thanks
Rainer
On Dienstag, 25. Februar 2020 22:45:33 CET Colin Law wrote:
> Also there is the mask file feature that enables you to define down to
> pixel level which areas to watch.
>
> Colin
>
> On Tue, 25 Feb 2020 at 18:45, <[email protected]> wrote:
> > In the Configuration file (general, or individual camera)
> > lightswitch_percent and lightswitch_frames have worked pretty well for me.
> >
> > On 2/25/20 10:52 AM, Rainer Dorsch via Motion-user wrote:
> > > Hi,
> > >
> > > I used zoneminder some time back, but due to the much better and more
> > > reliable packaging for Debian I moved to motion.
> > >
> > > One nice feature which was very useful for me in zoneminder to reduce
> > > false
> > > motion positives, was to define a zone (mask in motion), which blocked
> > > motion if changes have been visible there.
> > >
> > > A typical example would be to block motion detection when e.g. sun
> > > illumination changes:
> > > - declare one or multiple zones at e.g. a wall at a height of e.g. 4 m,
> > > where you would never expect motion
> > > - if motion is detected there, then any detection in the areas to
> > > monitor is likely to be a false alarm as well.
> > >
> > > Are there any recommended options in motion to achieve something
> > > similar?
> > >
> > > How do you handle changing sun or other illumination in motion?
> > >
> > > Many thanks
> > > Rainer
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Motion-user mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > https://motion-project.github.io/
> > >
> > > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
> >
> > _______________________________________________
> > Motion-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > https://motion-project.github.io/
> >
> > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 164, Issue 46
********************************************
