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: [Motion-devel] Motion Project (Kenneth Lavrsen)
2. Re: [Motion-devel] Motion Project (Kenneth Lavrsen)
3. Re: Shoot HD images: 1080 is not a multiple of 16 (Mr Dave)
----------------------------------------------------------------------
Message: 1
Date: Sat, 6 Aug 2016 22:23:36 +0200
From: Kenneth Lavrsen <[email protected]>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: Motion SVN commit messages <[email protected]>,
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Note
I have started the redesign of the Motion Guide.
I assume you will like to have access to the historical records on the
wiki so I will not delete them but move them to a read only archive.
If you go to the wiki now you will see that I have put a visible message
on the top saying that the project is being transferred so the process
starts NOW
Kenneth
------------------------------
Message: 2
Date: Sun, 7 Aug 2016 00:49:48 +0200
From: Kenneth Lavrsen <[email protected]>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Going to bed now.
I have done these changes so far on the wiki.
I have changed the way the config option topics are both viewed and editied.
When you view them the form is hidden but you see the content that is
relevant inside the page at the top.
When you edit, you get the form fields. Next tab shows the extra text.
No more strange codes. Easy for anyone to edit now.
Pages that are not yet converted will look strange with the same
information duplicated so ignore the current state of the site.
I started at A and I am now at M. So half way. And a lot of new topics
created where the config option has changed names. The old one is then
marked obsolete.
These changes also mean that when you look at the Motion Guide pages
information is missing. It is because I have not yet adjusted the SEARCH
macros to the new way the information is stored. That I take care of later.
Let me see how far I get tomorrow Sunday.
Kenneth
On 06-Aug-16 22:23, Kenneth Lavrsen wrote:
> Note
>
> I have started the redesign of the Motion Guide.
>
> I assume you will like to have access to the historical records on the
> wiki so I will not delete them but move them to a read only archive.
>
> If you go to the wiki now you will see that I have put a visible message
> on the top saying that the project is being transferred so the process
> starts NOW
>
> Kenneth
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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: Sat, 6 Aug 2016 19:00:54 -0600
From: Mr Dave <[email protected]>
Subject: Re: [Motion-user] Shoot HD images: 1080 is not a multiple of
16
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Well, given that the guide was proposed as a patch rather than as a
completely different project I maintained the references back to your
website. It was however updated to reflect changes.
You are correct that I didn't document all the abbreviations on the log
levels and assumed that the regular users would be able to interpret the
abbreviations.
For your reference, the following is the crosswalk completed for
old/renamed and new configuration options.
http://www.lavrsen.dk/foswiki/pub/Motion/PatchworkForNewRelease/ConfigureOptionChanges.tar.gz
The following are snippets from the guide
(http://www.lavrsen.dk/foswiki/pub/Motion/PatchworkForNewRelease/motion_guide.tar.gz)
regarding the rtsp, SDL and extpipe options that you wanted more detail
on. Regarding the extpipe, I believe that the documentation of how to
exactly configure the encoder for accepting a pipe input should be out
of scope for the documentation of Motion. There are multiple encoders
that a user could use and how to configure them should be within the
scope of the encoder application.
RTSP references (from the basic setup section and the network cameras
section)
/Network cameras are set up via the netcam_url parameter. The latest
versions of Motion support rtsp format which many cameras now stream.
The URL connection string to enter is specific to the camera and is
usually provided by the manufacturer. The connection string is the same
as what would be used by other video playing software such as VLC. If
the camera does not stream via RTSP and instead uses a MJPEG, then
Motion can also view that format. See the option netcam_url for
additional options. //
/
/N//etwork Cameras//
//
// Motion can connect to a network camera through a normal TCP
socket. All you need to give it is the URL. The URL given must return
either one single jpeg picture or an mjpeg stream. For the time being
Motion cannot connect to a video stream such a mpeg, mpeg4, divx. The
URL must return one single jpeg image, a mjpeg stream a rtsp stream,
file or ftp. When getting a still image, make sure to validate that the
camera is serving up a actual raw JPG file and not a HTML page with an
embedded JPG which is the current standard. When the netcam_url is
defined the video4linux options above are ignored. If the connection to
a network camera is lost, Motion will reuse the last good image for
approx 30 seconds. After 30 seconds the image is replaced by a grey
image with a text telling that the signal is lost and when the
connection was lost. This text and its date format is not configurable.//
// netcam_url//
//
// Type: String//
// Range / Valid values: Max 4095 characters//
// Default: Not defined//
//
// URL to use if you are using a network camera, size will be
autodetected Available prefixes to the URL://
// http:////
// ftp:////
// mjpg:////
// rtsp:////
// mjpeg:////
// file://///
// The prefixes of mjpg and mjpeg are not actual protocols and allow
the user to specify different formats and methods to access the network
stream. They are internally translated into http. For options such as
rtsp, it is recommended that the connection string be validated with
other applications such as ffplay or VLC.//
//
// When the netcam_url is defined the video4linux options are ignored. //
/
This is the SDL explanation(I think this functionality needs further
consideration in later releases)
/sdl_threadnr//
//
// Type: String//
// Range / Valid values: Max 4095 characters//
// Default://
//
//The SDL option is optional and unusual. When SDL is included in the
building of Motion, there is the ability for Motion to create a SDL
preview window for the user. The author believes this option to be more
of a proof of concept on how to create a SDL window and show the image.
(This same functionality can be achieved via the stream options) To
activate the SDL window, include SDL support in the building of the
Motion application. Start Motion and note the thread number indicated.
Once that is noted, specify that thread number (or 1 more than that
number) for this option. When Motion is started again, it will then
create a SDL window to preview the image. To close the window, press X.
Author is not aware of any method to restart the SDL window after it has
been closed. //
/
And the extpipe options(This is in the pipes section and the discussion
of what is a pipe precedes it)
/use_extpipe//
//
// Type: String//
// Range / Valid values: Max 4095 characters//
// Default://
//
//This option specifies whether to send the output to a pipe for
external encoding into a movie.//
//
//Note that this option does not require the install or configure of the
videoloop back//
//
//extpipe//
//
// Type: String//
// Range / Valid values: Max 4095 characters//
// Default://
//
//This option specifies the program name and options for the program
that will receive and process the images during a movie event.//
//
//Note that this option does not require the install or configure of the
videoloop back//
//
//Sample://
//
//extpipe mencoder -demuxer rawvideo -rawvideo w=320:h=240:i420 -ovc
x264 -x264encopts
bframes=4:frameref=1:subq=1:scenecut=-1:nob_adapt:threads=1:keyint=1000:8x8dct:vbv_bufsize=4000:crf=24:partitions=i8x8,i4x4:vbv_maxrate=800:no-chroma-me
-vf denoise3d=16:12:48:4,pp=lb -of avi -o %f.avi - -fps %fps //
/
On 8/6/2016 2:09 PM, Kenneth Lavrsen wrote:
> 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]
> <mailto:[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]
>> <mailto:%22tosiara%22%20%[email protected]%3E>> 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
>> <http://motion-dist.conf.in>
>> On Sat, Aug 6, 2016 at 2:23 PM, Yoan Mollard <[email protected]
>> <mailto:[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]
>> <mailto:[email protected]>>:
>>
>> This is fixed in the latest "unofficial" version:
>> https://github.com/Mr-Dave/motion
>> <https://github.com/Mr-Dave/motion>
>> On Fri, Aug 5, 2016 at 10:58 PM, Yoan Mollard
>> <[email protected] <mailto:[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]
>> <mailto:[email protected]>>:
>>
>> What version are you using?
>> On Fri, Aug 5, 2016 at 2:59 PM, Yoan Mollard
>> <[email protected] <mailto:[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/
>>
>> <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]
>> <mailto:[email protected]>
>>
>> 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
>> [email protected]
>> <mailto:[email protected]>
>> 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
>> [email protected]
>> <mailto:[email protected]>
>> 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
>> [email protected]
>> <mailto:[email protected]>
>> 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
>> [email protected]
>> <mailto:[email protected]>
>> 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
>> [email protected]
>> <mailto:[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 13
********************************************
