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. Re: mpjpeg fails on wansview 1080p (John Baker)
2. Re: mpjpeg fails on wansview 1080p (Kenneth Lavrsen)
3. Project Status (Mr Dave)
----------------------------------------------------------------------
Message: 1
Date: Sun, 07 Aug 2016 21:15:17 +0100
From: John Baker <jba...@dryfish.org.uk>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: motion-user@lists.sourceforge.net
Message-ID:
<1470600917.2140012.688520689.6d4fd...@webmail.messagingengine.com>
Content-Type: text/plain; charset="utf-8"
I completely got the point and fully agree. Modern web interfaces do not
sit within daemons. I was proposing motion does less than what it
currently does, ie offers a simple REST interface on a single port to
supply mp4/ogg streams of the cameras (as it currently does, but across
multiple ports), and an AngularJS UI does the rest.
An AngularJS UI is entirely separate from a daemon, but unless the
daemon supplies the useful information, it can't do very much.
On Sun, Aug 7, 2016, at 08:40 PM, Joerg Weber wrote:
> Hello John,
>
> I'm not 100% sure you really got what Kenneth was saying:
>
> Motion is supposed to be a daemon only. Its primary function is motion
> detecion - nothing more and nothing less. No bells and whistles. There
> are interfaces to do such jobs externally.
>
> We can discuss interfaces, but the core motion binary will not have a GUI
> nor will it integrate a fully featured web server. If you are looking for
> something more integrated and complete, then Motion is probably not the
> right tool for your needs.
>
>
> Brgds Joerg
>
>
> 7. August 2016 20:40 Uhr, "John Baker" <jba...@dryfish.org.uk> schrieb:
> > Apache takes almost zero CPU now-a-days, but what I'd like is a really
> > small webserver with a good REST interface, so a simple static website
> > can be built using AngularJS and served using Apache or a trivial Python
> > script. Or even by direct file access :)
> >
> > On Sun, Aug 7, 2016, at 07:28 PM, Kenneth Lavrsen wrote:
> >
> >> The libmicrohttpd seems like a good plan. Light. What I meant was like -
> >> do not assume Apache installed or require that the apache libs are used.
> >> That would kill Motion on a small box.
> >>
> >> I like your idea with libmicrohttpd
> >>
> >> Kenneth
> >>
> >> On 07-Aug-16 18:56, Mr Dave wrote:
> >>> The digest authentication has been issue for a while and I believe
> >>> does need to be addressed. Many of the current cameras will only
> >>> support digest or no authentication. In this situation, we are
> >>> forcing the user to leave the camera open to the world. I am planning
> >>> on investigating the use of that external microhttp lib for both the
> >>> streaming components as well as the non RTSP cameras. The RTSP
> >>> cameras use the ffmpeg libraries so addressing those would be a
> >>> different solution.
> >>>
> >>> Dave
> >>> On 8/7/2016 7:55 AM, tosiara wrote:
> >>>> Kenneth,
> >>>>
> >>>> the was suggestion to use libmicrohttpd which seems a good choice and
> >>>> is really not too heavy for motion:
> >>>> https://github.com/Mr-Dave/motion/pull/94#issuecomment-159535262
> >>>>
> >>>> On Sun, Aug 7, 2016 at 1:24 PM, Joseph Heenan <jos...@heenan.me.uk
> >>>> <mailto:jos...@heenan.me.uk>> wrote:
> >>>>
> >>>> 2 doesn?t seem a particularly high priority to me given that the
> >>>> camera works with motion using rtsp (which does support digest
> >>>> auth), but I may have missed something.
> >>>>
> >>>> Joseph
> >>>>
> >>>>
> >>>>> On 7 Aug 2016, at 08:08, tosiara <tosi...@gmail.com
> >>>>> <mailto:tosi...@gmail.com>> wrote:
> >>>>>
> >>>>> So here we have two issues:
> >>>>> 1. motion should better handle 401 or any non-200 http status
> >>>>> and show user friendly error
> >>>>> 2. digest auth support
> >>>>>
> >>>>> The first would probably be an easy code change
> >>>>> But the second would be a challenge. We can implement digest
> >>>>> auth. Or. There was a discussion already to replace all the
> >>>>> manual http code by some web library that provides better
> >>>>> support and better maintained. But that requires also quite a
> >>>>> lot of efforts to change the code
> >>>>>
> >>>>> On Sun, Aug 7, 2016 at 9:25 AM, John Baker
> >>>>> <jba...@dryfish.org.uk <mailto:jba...@dryfish.org.uk>> wrote:
> >>>>>
> >>>>> So being more awake this morning, I now spot the problem.
> >>>>> The camera
> >>>>> wishes to use HTTP digest authentication, which I guess
> >>>>> motion doesn't
> >>>>> support (another on the todo list Mr Dave / Joseph ?:).
> >>>>>
> >>>>> http://stackoverflow.com/questions/2384230/what-is-digest-authentication
> >>>>> <http://stackoverflow.com/questions/2384230/what-is-digest-authentication>
> >>>>>
> >>>>> Example:
> >>>>>
> >>>>>> HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
> >>>>>> Host: 192.168.0.102
> >>>>>> User-Agent: curl/7.49.1
> >>>>>> Accept: */*
> >>>>>>
> >>>>> < HTTP/1.1 401 Unauthorized
> >>>>> < WWW-Authenticate: Digest realm="IPCamera Login",
> >>>>> nonce="f35b3a998c0b964d21d99da3f8880f14", qop="auth"
> >>>>>
> >>>>>> HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
> >>>>>> Host: 192.168.0.102
> >>>>>> Authorization: Digest username="visitor", realm="IPCamera
> >>>>> Login", nonce="f35b3a998c0b964d21d99da3f8880f14",
> >>>>> uri="/mjpeg/stream.cgi?chn=0",
> >>>>> cnonce="MWY1N2M3NmUzMjNlODIxM2ZjMzAxYTcyNTIzMjA0MTY=",
> >>>>> nc=00000001, qop=auth,
> >>>>> response="3bb6cbc93342432432421104ebeed5c3a"
> >>>>>> User-Agent: curl/7.49.1
> >>>>>> Accept: */*
> >>>>>>
> >>>>> < HTTP/1.1 200 OK
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------------------------
> >>>>> _______________________________________________
> >>>>> Motion-user mailing list
> >>>>> Motion-user@lists.sourceforge.net
> >>>>> <mailto:Motion-user@lists.sourceforge.net>
> >>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
> >>>>> <https://lists.sourceforge.net/lists/listinfo/motion-user>
> >>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >>>>> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------------------------
> >>>>> _______________________________________________
> >>>>> Motion-user mailing list
> >>>>> Motion-user@lists.sourceforge.net
> >>>>> <mailto:Motion-user@lists.sourceforge.net>
> >>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
> >>>>> <https://lists.sourceforge.net/lists/listinfo/motion-user>
> >>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >>>>> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
> >>>>
> >>>>
> >>>> ------------------------------------------------------------------------------
> >>>>
> >>>> _______________________________________________
> >>>> Motion-user mailing list
> >>>> Motion-user@lists.sourceforge.net
> >>>> <mailto:Motion-user@lists.sourceforge.net>
> >>>> https://lists.sourceforge.net/lists/listinfo/motion-user
> >>>> <https://lists.sourceforge.net/lists/listinfo/motion-user>
> >>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >>>> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------------------------------------------------------
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Motion-user mailing list
> >>>> Motion-user@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/motion-user
> >>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >>>
> >>>
> >>>
> >>>
> >>> ------------------------------------------------------------------------------
> >>>
> >>>
> >>> _______________________________________________
> >>> Motion-user mailing list
> >>> Motion-user@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/motion-user
> >>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >>
> >> ------------------------------------------------------------------------------
> >> _______________________________________________
> >> Motion-user mailing list
> >> Motion-user@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/motion-user
> >> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > Motion-user mailing list
> > Motion-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
Message: 2
Date: Sun, 7 Aug 2016 22:48:11 +0200
From: Kenneth Lavrsen <kenn...@lavrsen.dk>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: motion-user@lists.sourceforge.net
Message-ID: <cc8f9b6a-b11b-3cc3-e3d7-f54199e5f...@lavrsen.dk>
Content-Type: text/plain; charset=utf-8; format=flowed
I always encouraged that people developed side projects that used and
integrated Motion
There are a few around on the wiki. Some are minor little things. Some
are my horrible PHP beginner website shitties.
Even if such projects are not always perfect they are excellent
frameworks for people to tailor things to their own needs.
I hope people come back and contribute. Make sure people can still
contribute these small side projects even without knowing anything about
git.
Kenneth
On 07-Aug-16 22:15, John Baker wrote:
> I completely got the point and fully agree. Modern web interfaces do not
> sit within daemons. I was proposing motion does less than what it
> currently does, ie offers a simple REST interface on a single port to
> supply mp4/ogg streams of the cameras (as it currently does, but across
> multiple ports), and an AngularJS UI does the rest.
>
> An AngularJS UI is entirely separate from a daemon, but unless the
> daemon supplies the useful information, it can't do very much.
>
>
>
> On Sun, Aug 7, 2016, at 08:40 PM, Joerg Weber wrote:
>> Hello John,
>>
>> I'm not 100% sure you really got what Kenneth was saying:
>>
>> Motion is supposed to be a daemon only. Its primary function is motion
>> detecion - nothing more and nothing less. No bells and whistles. There
>> are interfaces to do such jobs externally.
>>
>> We can discuss interfaces, but the core motion binary will not have a GUI
>> nor will it integrate a fully featured web server. If you are looking for
>> something more integrated and complete, then Motion is probably not the
>> right tool for your needs.
>>
>>
>> Brgds Joerg
>>
>>
>> 7. August 2016 20:40 Uhr, "John Baker" <jba...@dryfish.org.uk> schrieb:
>>> Apache takes almost zero CPU now-a-days, but what I'd like is a really
>>> small webserver with a good REST interface, so a simple static website
>>> can be built using AngularJS and served using Apache or a trivial Python
>>> script. Or even by direct file access :)
>>>
>>> On Sun, Aug 7, 2016, at 07:28 PM, Kenneth Lavrsen wrote:
>>>
>>>> The libmicrohttpd seems like a good plan. Light. What I meant was like -
>>>> do not assume Apache installed or require that the apache libs are used.
>>>> That would kill Motion on a small box.
>>>>
>>>> I like your idea with libmicrohttpd
>>>>
>>>> Kenneth
>>>>
>>>> On 07-Aug-16 18:56, Mr Dave wrote:
>>>>> The digest authentication has been issue for a while and I believe
>>>>> does need to be addressed. Many of the current cameras will only
>>>>> support digest or no authentication. In this situation, we are
>>>>> forcing the user to leave the camera open to the world. I am planning
>>>>> on investigating the use of that external microhttp lib for both the
>>>>> streaming components as well as the non RTSP cameras. The RTSP
>>>>> cameras use the ffmpeg libraries so addressing those would be a
>>>>> different solution.
>>>>>
>>>>> Dave
>>>>> On 8/7/2016 7:55 AM, tosiara wrote:
>>>>>> Kenneth,
>>>>>>
>>>>>> the was suggestion to use libmicrohttpd which seems a good choice and
>>>>>> is really not too heavy for motion:
>>>>>> https://github.com/Mr-Dave/motion/pull/94#issuecomment-159535262
>>>>>>
>>>>>> On Sun, Aug 7, 2016 at 1:24 PM, Joseph Heenan <jos...@heenan.me.uk
>>>>>> <mailto:jos...@heenan.me.uk>> wrote:
>>>>>>
>>>>>> 2 doesn?t seem a particularly high priority to me given that the
>>>>>> camera works with motion using rtsp (which does support digest
>>>>>> auth), but I may have missed something.
>>>>>>
>>>>>> Joseph
>>>>>>
>>>>>>
>>>>>>> On 7 Aug 2016, at 08:08, tosiara <tosi...@gmail.com
>>>>>>> <mailto:tosi...@gmail.com>> wrote:
>>>>>>>
>>>>>>> So here we have two issues:
>>>>>>> 1. motion should better handle 401 or any non-200 http status
>>>>>>> and show user friendly error
>>>>>>> 2. digest auth support
>>>>>>>
>>>>>>> The first would probably be an easy code change
>>>>>>> But the second would be a challenge. We can implement digest
>>>>>>> auth. Or. There was a discussion already to replace all the
>>>>>>> manual http code by some web library that provides better
>>>>>>> support and better maintained. But that requires also quite a
>>>>>>> lot of efforts to change the code
>>>>>>>
>>>>>>> On Sun, Aug 7, 2016 at 9:25 AM, John Baker
>>>>>>> <jba...@dryfish.org.uk <mailto:jba...@dryfish.org.uk>> wrote:
>>>>>>>
>>>>>>> So being more awake this morning, I now spot the problem.
>>>>>>> The camera
>>>>>>> wishes to use HTTP digest authentication, which I guess
>>>>>>> motion doesn't
>>>>>>> support (another on the todo list Mr Dave / Joseph ?:).
>>>>>>>
>>>>>>> http://stackoverflow.com/questions/2384230/what-is-digest-authentication
>>>>>>> <http://stackoverflow.com/questions/2384230/what-is-digest-authentication>
>>>>>>>
>>>>>>> Example:
>>>>>>>
>>>>>>>> HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
>>>>>>>> Host: 192.168.0.102
>>>>>>>> User-Agent: curl/7.49.1
>>>>>>>> Accept: */*
>>>>>>>>
>>>>>>> < HTTP/1.1 401 Unauthorized
>>>>>>> < WWW-Authenticate: Digest realm="IPCamera Login",
>>>>>>> nonce="f35b3a998c0b964d21d99da3f8880f14", qop="auth"
>>>>>>>
>>>>>>>> HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
>>>>>>>> Host: 192.168.0.102
>>>>>>>> Authorization: Digest username="visitor", realm="IPCamera
>>>>>>> Login", nonce="f35b3a998c0b964d21d99da3f8880f14",
>>>>>>> uri="/mjpeg/stream.cgi?chn=0",
>>>>>>> cnonce="MWY1N2M3NmUzMjNlODIxM2ZjMzAxYTcyNTIzMjA0MTY=",
>>>>>>> nc=00000001, qop=auth,
>>>>>>> response="3bb6cbc93342432432421104ebeed5c3a"
>>>>>>>> User-Agent: curl/7.49.1
>>>>>>>> Accept: */*
>>>>>>>>
>>>>>>> < HTTP/1.1 200 OK
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> _______________________________________________
>>>>>>> Motion-user mailing list
>>>>>>> Motion-user@lists.sourceforge.net
>>>>>>> <mailto:Motion-user@lists.sourceforge.net>
>>>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>>>> <https://lists.sourceforge.net/lists/listinfo/motion-user>
>>>>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>>>>> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> _______________________________________________
>>>>>>> Motion-user mailing list
>>>>>>> Motion-user@lists.sourceforge.net
>>>>>>> <mailto:Motion-user@lists.sourceforge.net>
>>>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>>>> <https://lists.sourceforge.net/lists/listinfo/motion-user>
>>>>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>>>>> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> Motion-user mailing list
>>>>>> Motion-user@lists.sourceforge.net
>>>>>> <mailto:Motion-user@lists.sourceforge.net>
>>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>>> <https://lists.sourceforge.net/lists/listinfo/motion-user>
>>>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>>>> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Motion-user mailing list
>>>>>> Motion-user@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Motion-user mailing list
>>>>> Motion-user@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Motion-user mailing list
>>>> Motion-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Motion-user mailing list
>>> Motion-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
Message: 3
Date: Sun, 7 Aug 2016 18:22:56 -0600
From: Mr Dave <motionmrd...@gmail.com>
Subject: [Motion-user] Project Status
To: motion-user@lists.sourceforge.net
Message-ID: <d19f80e8-6809-c36b-15da-bd6646424...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
I just wanted to send a note with the plan and status as of now.
The code repo has been moved over to the new location.
https://github.com/Motion-Project/motion If you linked to my old repo,
you'll now be redirected to here.
I know that there is a lot of pent up demand for fixes and features but
I'd ask that issues be opened on the repo so that we can track and
manage them accordingly. As demonstrated over these last few days,
keeping track of issues via the mailing list can be challenging.
We'll be working on the overall transition items as a first priority,
followed closely by doing the work necessary to get a updated release to
the distributors. We can then assess the issues reported to determine a
plan for addressing them. And to be clear, the documentation updates
fall within the transition process.
For anyone considering a pull, the current flow (which may evolve later)
is Pull request -> Unstable -> Master -> Release This roughly follows
the process used by Debian which helps facilitate getting error free
releases.
I will also be checking in on the IRC channel for discussion during the
US MT evening hours.
Dave
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 123, Issue 27
********************************************
