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: Pi & Logitech C920 (tosiara)
2. Re: Pi & Logitech C920 (Dave Howorth)
3. Re: Pi & Logitech C920 (tosiara)
4. Re: [Explain like i am five] the Motion detection algorithm /
technology (Adam Ali)
----------------------------------------------------------------------
Message: 1
Date: Wed, 28 Oct 2015 10:00:32 +0200
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Pi & Logitech C920
To: [email protected], Motion discussion list
<[email protected]>
Message-ID:
<cachtdwq6fy_8vzvj4vseen_ivgr-621yjbw8giadoavp-0a...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
So has that resolved your issue?
On Wed, Oct 28, 2015 at 9:53 AM, Dave Howorth <[email protected]> wrote:
> On Wed, 2015-10-28 at 00:01 +0000, Dave Howorth wrote:
> > Looking at /dev/video0:
> >
> > $ ls -l /dev/video0
> > crw-rw---T 1 root video 81, 0 Jan 1 1970 /dev/video0
> >
> > and looking in /etc/group:
> >
> > $ grep motion /etc/group
> > video:x:44:pi,motion
> > motion:x:1002:
> >
> > so I'm not sure why it can't open the device.
>
> Ah, the joys of morning. I needed to restart motion's shell for it to
> notice it was in the video group.
>
> Cheers, Dave
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 28 Oct 2015 20:40:37 +0000
From: Dave Howorth <[email protected]>
Subject: Re: [Motion-user] Pi & Logitech C920
To: tosiara <[email protected]>
Cc: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Hello,
Yes it has thanks. It's now running and collecting files as appropriate.
My new Pi is able to collect all frames at 1 fps and some more but not
all frames at 2 fps, whereas the older one could only manage 1 fps at
best.
I'm interested in optimising it's performance. Are there any
configuration options that use less processing power than others, for
example? (choice of encoding, palette, threshold etc). google shows me
statements like "the Raspberry delivers great performence when
encoding/decoding H264. That's why the Raspberry can record 1080p videos
with 30fps." which are tantalising. Is there anything that explains the
performance impact of options and also possible avenues for future
optimization?
In the meantime, I'll try reducing resolution a bit and see what effect
that has.
Cheers, Dave
On Wed, 2015-10-28 at 10:00 +0200, tosiara wrote:
> So has that resolved your issue?
>
>
> On Wed, Oct 28, 2015 at 9:53 AM, Dave Howorth <[email protected]>
> wrote:
> On Wed, 2015-10-28 at 00:01 +0000, Dave Howorth wrote:
> > Looking at /dev/video0:
> >
> > $ ls -l /dev/video0
> > crw-rw---T 1 root video 81, 0 Jan 1 1970 /dev/video0
> >
> > and looking in /etc/group:
> >
> > $ grep motion /etc/group
> > video:x:44:pi,motion
> > motion:x:1002:
> >
> > so I'm not sure why it can't open the device.
>
> Ah, the joys of morning. I needed to restart motion's shell
> for it to
> notice it was in the video group.
>
> Cheers, Dave
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
>
------------------------------
Message: 3
Date: Thu, 29 Oct 2015 07:35:43 +0200
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Pi & Logitech C920
To: [email protected]
Cc: Motion discussion list <[email protected]>
Message-ID:
<cachtdwqg278gwa8jyrodcpzyewxhocsehv+kqxdxxooyctj...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Motion does not yet support decoding V4L2 H.264 pixel format. I have filed
feature request: https://github.com/Mr-Dave/motion/issues/86
And from your motion's log it seems you are using RAW pixel format, which
requires almost no processing (less cpu usage), but has hardware frame rate
limitations of the camera starting from 720p and up (due to usb bandwidth)
Sep 17 18:56:41 raspberrypi motion: [1] Using palette *YUYV (1280x720)*
On Wed, Oct 28, 2015 at 10:40 PM, Dave Howorth <[email protected]> wrote:
> Hello,
>
> Yes it has thanks. It's now running and collecting files as appropriate.
>
> My new Pi is able to collect all frames at 1 fps and some more but not
> all frames at 2 fps, whereas the older one could only manage 1 fps at
> best.
>
> I'm interested in optimising it's performance. Are there any
> configuration options that use less processing power than others, for
> example? (choice of encoding, palette, threshold etc). google shows me
> statements like "the Raspberry delivers great performence when
> encoding/decoding H264. That's why the Raspberry can record 1080p videos
> with 30fps." which are tantalising. Is there anything that explains the
> performance impact of options and also possible avenues for future
> optimization?
>
> In the meantime, I'll try reducing resolution a bit and see what effect
> that has.
>
> Cheers, Dave
>
> On Wed, 2015-10-28 at 10:00 +0200, tosiara wrote:
> > So has that resolved your issue?
> >
> >
> > On Wed, Oct 28, 2015 at 9:53 AM, Dave Howorth <[email protected]>
> > wrote:
> > On Wed, 2015-10-28 at 00:01 +0000, Dave Howorth wrote:
> > > Looking at /dev/video0:
> > >
> > > $ ls -l /dev/video0
> > > crw-rw---T 1 root video 81, 0 Jan 1 1970 /dev/video0
> > >
> > > and looking in /etc/group:
> > >
> > > $ grep motion /etc/group
> > > video:x:44:pi,motion
> > > motion:x:1002:
> > >
> > > so I'm not sure why it can't open the device.
> >
> > Ah, the joys of morning. I needed to restart motion's shell
> > for it to
> > notice it was in the video group.
> >
> > Cheers, Dave
> >
> >
> >
> >
>
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Motion-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Wed, 4 Nov 2015 01:57:06 +0700
From: Adam Ali <[email protected]>
Subject: Re: [Motion-user] [Explain like i am five] the Motion
detection algorithm / technology
To: Motion discussion list <[email protected]>
Message-ID:
<CAM5sJAtaymCUnzW7MU3v2SjnFvty+dXfdoxcKfJUtvM=js+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks for the answer sir
sorry
On Sun, Aug 16, 2015 at 2:27 PM, Colin Law <[email protected]> wrote:
> On 16 August 2015 at 01:23, Adam Ali <[email protected]> wrote:
> > Greetings,i am a newbie and learning linux(raspberry) user
> > i already got motion running in raspberry,i am planning to create simple
> > paper for my school project
> > but i dont get the explanation of Motion algorithm
> >
> > from http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionTechnology :
> > Motion detects motion by comparing the intensity of pixels in a fresh
> > grabbed image with a reference image. Color information is not utilized.
> If
> > there is no motion and no noise new_image-ref_image should be zero. If
> there
> > has been a change in the picture the result will be different. To prevent
> > noise being seen as motion the change has to exceed a threshold and there
> > have to be a certain number of changed pixels before a motion is
> declared.
> >
> > The reference frame itself is recursively updated with the new picture,
> so
> > after it has been updated with pictureN it will consist out of:
> 1/2*pictureN
> > + 1/4*pictureN-1 + 1/8*pictureN-2 and so on.
> >
> > can you explain in more detail? and what kind of paper or book you
> recommend
> > to study about it ?
> >
> > and about the formula,does
> > 1/2*pictureN mean :
> > a.half times pictureN
> > or
> > b. one divide ( 2 times pictureN )
>
> It means the reference image (which is compared with the current
> image) is a set of pixels making up the image where for each pixel its
> brightness is calculated from the brightness of the pixel at that
> point in the image over a number of previous samples using the formula
> 0.5 * pixel brightness from previous image + 0.25 * brightness from
> image before that + 0.125 * brightness from the one before that +
> etc. That sounds like a complex formula but actually is easy to
> calculate on the fly. The result of this is that if, for example, the
> brightness were to change from 0 to 1 suddenly then the brightness in
> the reference image over the next few samples would be 0.5, 0.75,
> 0.875 and so on, which is an exponential curve tending to 1.
>
> In the text you quoted when it says new_image-ref_image it means that
> a difference image is calculated where, for each pixel, the brightness
> is the brightness of the pixel in the new image minus that in the
> reference image.
>
> Does that help?
>
> Colin
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 114, Issue 1
*******************************************
