Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
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
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. some comments on motion detection (Graham Toal)
2. Re: ?????? ?????? (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Thu, 6 Jun 2019 00:51:33 -0500
From: Graham Toal <gt...@gtoal.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] some comments on motion detection
Message-ID:
<CABwQhLmzvnaigWb7Tw-yp442cE_KV5rNCFX+OPdaqOA=i_m...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi - I've been using motion on raspberry pies for a few years now.
I have some thoughts I'ld like to pass on. Motion's detection has too many
false positives for my liking, and the offered solutions haven't ever
really fixed it for me. So...
1) perhaps a tweak to the algorithm, so that changed pixels which also
change hue are weighted more strongly than changes in intensity, so that
increases or decreases in light level don't register as strongly as an
object moving over the display (which with colour cameras usually causes a
change in pixel colour as well as intensity - not so true at night or in IR
mode, but then the current algorithm would work as a fallback)
(I know the downside of this is that someone could walk over a green lawn
in green camo, but I'm not suggesting using hue changes *only* - just
giving them a heavier weighting)
2) after detecting motion, the video could then be run through an external
program supplied by the user which implements a user-written algorithm that
returns motion/no-motion and allows the system to cancel that detection and
do nothing further with the video. (This can be done to some extent with
the existing script hooks but maybe not as cleanly)
3) Could there be a mechanism to add some external trigger to supplement
the motion detection, eg a PIR sensor or radar sensor - and have motion
handle the video only if it detects motion in the video *and* the external
trigger also has detected motion? (and some users might want the option of
"OR" rather than "AND" depending on their tolerance of false positives)
just passing thoughts to consider some day...
regards
Graham
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Thu, 6 Jun 2019 09:33:42 +0300
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] ?????? ??????
Message-ID:
<CACHTdwSfQX5NKf2BReqD3mncn=p7qyae8z0ewgpfpojszp4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Please install ffplay on your server and run:
ffplay -rtsp_transport tcp rtsp://your-camera/stream
Play for 5 minutes. Does it play fine? Is picture good? Send the command's
output
On Thu, Jun 6, 2019, 01:28 QQQ www <s...@cord.ws> wrote:
> Hi!
> Thank you very much for replying to my letter!
>
> In attach log
>
>
>
> 05.06.2019, 08:32, "tosiara" <tosi...@gmail.com>:
> > Can you show full motion log with "-d 7"?
> >
> > On Wed, Jun 5, 2019 at 12:59 AM QQQ www <s...@cord.ws> wrote:
> >> ?????? ????
> >> ?????????????? ????? ??????.
> >> "?????????????" ???? ??? ????????? ? ?????? ?????? ? motion. ??? ????,
> ???? ???????? ????? ??????????????? ? ??????, ????????? ???.
> >>
> >> ????? ????:
> >> [6:nc6] [INF] [ENC] [Jun 04 02:53:57] ffmpeg_avcodec_log: RTP: missed
> 67 packets
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:57] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:57] ffmpeg_avcodec_log: RTP: missed
> 1 packets
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:57] ffmpeg_avcodec_log: error while
> decoding MB 97 60, bytestream -5
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:58] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:58] ffmpeg_avcodec_log: RTP: missed
> 148 packets
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:58] ffmpeg_avcodec_log: cabac decode
> of qscale diff failed at 108 4
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:58] ffmpeg_avcodec_log: error while
> decoding MB 108 4, bytestream -5
> >> [6:nc6] [INF] [ENC] [Jun 04 02:53:59] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [6:nc6] [INF] [ENC] [Jun 04 02:53:59] ffmpeg_avcodec_log: RTP: missed
> 67 packets
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:59] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:59] ffmpeg_avcodec_log: RTP: missed
> 3 packets
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:59] ffmpeg_avcodec_log: cabac decode
> of qscale diff failed at 26 49
> >> [7:nc7] [INF] [ENC] [Jun 04 02:53:59] ffmpeg_avcodec_log: error while
> decoding MB 26 49, bytestream -3
> >> [7:nc7] [INF] [ENC] [Jun 04 02:54:00] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [7:nc7] [INF] [ENC] [Jun 04 02:54:00] ffmpeg_avcodec_log: RTP: missed
> 14 packets
> >> [7:nc7] [INF] [ENC] [Jun 04 02:54:00] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >>
> >> ???? ????? ?? ????? _______________________________________________
> >> Motion-user mailing list
> >> Motion-user@lists.sourceforge.net
> >> 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
> > Motion-user@lists.sourceforge.net
> > 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
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 156, Issue 12
********************************************
