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: mpjpeg fails on wansview 1080p (Mike Wilson)
2. Re: mpjpeg fails on wansview 1080p (John Baker)
3. Re: Shoot HD images: 1080 is not a multiple of 16
(Kenneth Lavrsen)
----------------------------------------------------------------------
Message: 1
Date: Sat, 06 Aug 2016 18:38:33 +0000
From: Mike Wilson <[email protected]>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: Motion discussion list <[email protected]>
Message-ID:
<caaveucrymczclqjd287awssibkpdrpo4i7tvo+nqtjomd7f...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Are you turkey using the URL htp:// instead of http?
On Sat, Aug 6, 2016 at 4:48 AM tosiara <[email protected]> wrote:
> Run motion with param "-d 9" and provide full motion log
> It could be a known issue that requires a workaround, I rememeber
> something similar reported before. But could not quickly provide a solution
>
> On Sat, Aug 6, 2016 at 10:07 AM, John Baker <[email protected]> wrote:
>
>> Here's a new bug for you all. I've got a wansview 1080p camera (and I
>> have to say, the customer service has been excellent compared to my
>> Foscam experience!) and it largely works fine with motion & an rtsp URL.
>> The camera supports mpjpeg and I can verify it works in a browser. But
>> this is what I see in motion:
>>
>> [1] [ALR] [NET] [Aug 06 08:04:30] netcam_start: Network Camera thread
>> starting... for url (htp://aaaa:bb@xxx/mjpeg/stream.cgi?chn=0)
>> [1] [CRT] [NET] [Aug 06 08:04:30] netcam_start: libjpeg decompression
>> failure on first frame - giving up!
>>
>> Is there any additional debug we can obtain?
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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: Sat, 06 Aug 2016 19:55:13 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: [email protected]
Message-ID:
<1470509713.1000581.687870385.23842...@webmail.messagingengine.com>
Content-Type: text/plain
No, I appear to have copied/pasted/deleted a char. Debug level 9:
[1] [INF] [NET] [Aug 06 19:43:40] netcam_http_build_url: Netcam has
flags: HTTP/1.0: 1 HTTP/1.1: 0 Keep-Alive OFF.
[1] [INF] [NET] [Aug 06 19:43:40] netcam_http_build_url: Camera connect
string is ''GET /mjpeg/stream.cgi?chn=0 HTTP/1.0
Host: 192.168.0.102
User-Agent: Motion-netcam/Unofficial-Git-UNKNOWN
Connection: close
Authorization: Basic xxxxx
'' End of camera connect string.
[1] [INF] [NET] [Aug 06 19:43:40] netcam_http_request: about to try to
connect, time #0
[1] [INF] [NET] [Aug 06 19:43:40] netcam_connect: disconnecting netcam
since keep-alive not set.
[1] [INF] [NET] [Aug 06 19:43:40] netcam_connect: with no keepalive, new
socket created fd 7
[1] [INF] [NET] [Aug 06 19:43:40] netcam_connect: re-using socket 7
since keepalive is set.
[1] [INF] [NET] [Aug 06 19:43:40] netcam_read_first_header: Received
first header ('HTTP/1.0 401 Unauthorized')
[1] [INF] [NET] [Aug 06 19:43:40] netcam_read_first_header: HTTP Result
code 401
I've checked the real base64 string (xxxx) being sent as the
Authorisation header and it's correct, so the issue is the camera
returns 401 in this instance causing libjpeg to fail. But, motion should
be checking the HTTP status code returned and not assuming 200, ie it's
401 (for whatever reason) and this isn't reported to the log.
So there's an easy logging improvement for anyone hacking the C and I'll
figure out why the camera doesn't authenticate the client.
On Sat, Aug 6, 2016, at 07:38 PM, Mike Wilson wrote:
> Are you turkey using the URL htp:// instead of http?
------------------------------
Message: 3
Date: Sat, 6 Aug 2016 22:09:52 +0200
From: Kenneth Lavrsen <[email protected]>
Subject: Re: [Motion-user] Shoot HD images: 1080 is not a multiple of
16
To: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
The level of documentation that I want to maintain goes beyond the 2-3 lines of
text in the config files.
If you read the Motion Guide I have spent a lot of time explaining with images
and examples how the different things work.
I just tried to look through the current Git. The Motion Guide is for sure not
up to date and still points back to my site claiming it to be up to date. And
clearly it is not
And as I look at the configs there are things I do not understand how to use.
Example
# Level of log messages [1..9] (EMG, ALR, CRT, ERR, WRN, NTC, INF, DBG, ALL).
(default: 6 / NTC)
log_level 6
In the config this is fine. But in the guide would try to explain what the 3
letter accronyms mean. If you are not a programmer these accronyms mean
nothing. Surely you can Google then. But that you can say about everything. I'd
like to document things so noobs and other normal people can get started easily
Support of rtsp has been added to Motion. I am a bit behind. I do not know what
that is. So I am sure many newbies do not know either. I intend to find out and
spend 4 lines of text in the Netcam section explaining what it is.
Take a feature like the mask file. Note how I have documented this with
examples. It would be very hard to understand without the examples with images
etc
There are also things that do not need more documentation. The new video modes
that are supported are well documented by being listed. They just need to be
copied to the guide also. Easy piece of cake
Then there is SDL. I have tried to figure out what it is and how I use it. I
need one of you to explain to me what it is and how I use the feature. I can
find SDL on Google but I cannot link it to what is in Motion.
If I do not understand I am sure 1000s of other that downloaded Motion don't
either. Maybe 990 of them don't need to but the last 10 do. Can someone help
explaining what the SDL is and maybe an example how it is used? Then I can add
it to the documentation.
ext_pipe feature. I think I understand what is does.
In the Motion guide I would add some more explanation WHY you may want to use
this instead. One thing is that the feature syntax is defined. But what does it
do and why are there more ways to do the same thing. There are lots of good
reasons and it really helps the users to understand the background of the
feature.
There are not that many new features added.
It is mainly config options that changed name and a lot of the name changes
were done by Angel and me in an attempt to make Motion easier to understand.
Some of the options have terrible names in the old 3.x version.
I will start tomorrow with the cleanout of the wiki. It will take some days and
while I do it it will work like shit. Leave the cleanup to me.
Meanwhile you may want to consider which old wiki bug reports you want to move
over manually to the github
How you organize the github I will leave to Mr Dave. I will only focus on
reducing the wiki to only be the Motion Guide. Nothing else.
Kenneth
> On 06 Aug 2016, at 19:59, Joerg Weber <[email protected]> wrote:
>
> Hello Tosiara,
>
> I believe that Yoan was referring to the discussion here on the list about
> the outdated Wiki documentation on Kenneth's Motion site.
>
> I also believe that we should welcome Kenneth's offer to hand over the
> project and his initiative to keep the Wiki up to date in the future. I was
> also a bit frustrated about the silence, which we were facing in the past.
> But now he is here, willing to help.
>
>
> Brgds Joerg.
>
>
>
> 6. August 2016 17:10 Uhr, "tosiara" <[email protected]> schrieb:
> There is absolutely no lack of documentation. All changes have corresponding
> comments in readme and config file.
> For example, history of config file updates:
> https://github.com/Mr-Dave/motion/commits/master/motion-dist.conf.in
> Or complete diff since last SVN commit:
> git diff e9abd61a923be82276ebbbb11da2a4717be7aead
> 041797709d8186bfb2e99670fe597856cdb9bb2f motion-dist.conf.in
> On Sat, Aug 6, 2016 at 2:23 PM, Yoan Mollard <[email protected]> wrote:
> Ok cool thanks, I'm gonna test that one.
> Hope this fork will replace the old version soon in our distributions'
> repoitories, I see there are some discussions about the lack of
> documentation, is it a sign that there is a wish to merge the code?
> 2016-08-06 10:47 GMT+02:00 tosiara <[email protected]>:
> This is fixed in the latest "unofficial" version:
> https://github.com/Mr-Dave/motion
> On Fri, Aug 5, 2016 at 10:58 PM, Yoan Mollard <[email protected]> wrote:
> The last version, 3.2.12.
> Has this been corrected recently?
> 2016-08-05 14:33 GMT+02:00 tosiara <[email protected]>:
> What version are you using?
> On Fri, Aug 5, 2016 at 2:59 PM, Yoan Mollard <[email protected]> wrote:
> Hi all,
> I'd like to record a timelapse thanks to an HD webcam (1920x1080), but motion
> complains because 1080 is not a multiple of 16.
> Online some people suggest to change the code and recompile to fix the issue,
> ... but where does this constraint come from?
> I see very old messages in the mailing list about a possible bug because only
> 8 would make sense for 4/3 images (still, ... why?):
> https://sourceforge.net/p/motion/mailman/message/28581561/
>
> Anyway this is from 2011 and this "16" constraint is still there, is there a
> reason?
> If this is just a question of ratio, shouldn't it be only a WARNING instead
> of an ERROR?
> Because it does not shoot the images at all, thus the maximum HD resolution
> with can use with motion and HD cams is ... 720p :(
> Thanks
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> ------------------------------------------------------------------------------
> _______________________________________________
> 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 123, Issue 12
********************************************
