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 (John Baker)
2. Re: Shoot HD images: 1080 is not a multiple of 16 (Yoan Mollard)
3. How the documentation on the Motion wiki is working
(Kenneth Lavrsen)
----------------------------------------------------------------------
Message: 1
Date: Fri, 05 Aug 2016 20:51:59 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: [email protected]
Message-ID:
<1470426719.3372992.687275633.2270d...@webmail.messagingengine.com>
Content-Type: text/plain; charset="utf-8"
Here are some changes I'd like to see:
1. Give each camera a unique ID, perhaps moving away from a single
configuration file to the 'common' file and separate files per camera,
and perhaps use the camera's configuration file name as the ID.
2. A single HTTP interface which the following operations:
(a) /stream/[format]/[id] where [format] is mp4 or ogg and [id] is the
camera.
(b) /configuration/camera, returns a JSON encoded list of camera IDs,
ie ['blah', 'bee'].
(c) /configuration/camera/[id], returns a JSON encoded configuration
of the camera.
I could then build a simple video viewing interface using AngularJS,
which could be run using any webserver or a Python simple HTTP server
given Python is everywhere now-a-days.
I'm wondering if all the video capture stuff should go, given people use
IP cameras now-a-days. That'll remove a bunch of code that you don't
have to maintain.
On Fri, Aug 5, 2016, at 08:39 PM, Joseph Heenan wrote:
> Hi Kenneth,
>
> I?m also offering to help where I can, though I have nowhere near the
> experience with motion that the other members you mention have. I do have
> close to 20 years experience of working on/leading very large C projects
> though.
>
> I do not yet understand how the documentation process works. Particularly
> I don?t see where a new man page is generated from the wiki.
>
> Is there some documentation somewhere on the general process of updating
> the documentation that you can point us at? Or can you give the list a
> quick primer please?
>
> Thanks
>
> Joseph
>
>
> > On 5 Aug 2016, at 19:52, Kenneth Lavrsen <[email protected]> wrote:
> >
> > Tosiara
> >
> > I do not understand your sharp tone.
> >
> > I have agreed to pass over the project.
> >
> > And I wrote below I am OK that bug reports etc are moving to Github.
> >
> > But you also have to be honest here
> >
> > You guys have added several new options and new values to existing options.
> > And none of you could be bothered to update the documentation. I just read
> > 2-3 questions on this mailing list that relates to options that are not
> > documented.
> >
> > It takes days to code a new feature and test it. It takes 10 minutes to
> > document it. I can for the world not understand why programmers in general
> > do not understand the importance of documenting how it works.
> >
> > Bugs report, feature requests will be removed from the wiki. Patches work
> > so much better with pull requests on git. I will remove all this also.
> >
> > It is the Motion Guide that I will like see online and up to date. I will
> > be happy to bring it up to date provided that you tell me how the new
> > things work.
> >
> > Last time I tried to build Motion I found several features that I do not
> > know how to use!!!
> >
> > Tell me how it works and I will update the docus. And I also commit to
> > remove all the abandonned features on the wiki. I do not have time to code
> > and develop Motion but As I said I am OK to keep the wiki running and the
> > Motion Guide working. But I need you guys to commit (gentlemens agreement)
> > that you will keep the documentation up to date (with my help with the
> > practical stuff) and also make sure the man pages and the html version of
> > the Motion guide up to date. As I said it is easy. When the wiki docu is up
> > to date it will autogenerate the html and manpage.
> >
> > You guys focus on the code and supporting the users. I keep the wiki alive
> > and update the docu which is probably 20-30 minutes work per year. I use
> > the wiki for other things so keeping it alive is not an issue. And if you
> > guys feed me when you add new features or edit the existing pages when you
> > change the existing options then it is not a problem for me. And when I
> > hand over the project I also hand over all decisions on what is changed. I
> > just become the project secretary and wiki admin.
> >
> > So MrDave, Joerg Weber, Tosiara. Are you game to become the official new
> > Motion team with MrDave as the new formal owner?
> >
> > And anyone else wanting to commit to help along?
> >
> > Kenneth
> >
> > On 05 Aug 2016, at 09:48, tosiara <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >> Kenneth,
> >>
> >> Let's be honest, SVN version is dead. Poor RTSP support, configure and
> >> build issues, deprecated ffmpeg functions and lots of bugs (including
> >> security issues with buffer overflow which can allow remote code
> >> execution). A lot of people already switched to MrDave's fork and all of
> >> them seem to be happy with existing documentation.
> >>
> >> Fowsiki contains a lot of info, right. But it is still quite outdated and
> >> nobody maintains it. For example, how many support requests have been
> >> resolved recently? Check it out:
> >> http://www.lavrsen.dk/foswiki/bin/view/Motion/SupportRequests
> >> <http://www.lavrsen.dk/foswiki/bin/view/Motion/SupportRequests> I tried to
> >> do my best to provide users support through Foswiki, but the nature of
> >> wiki engine is so, that users never get notifications about answers and
> >> don't provide further details. No bug tracking at all. Patch submission is
> >> so hard, that nobody uses that. How many patches have been received and
> >> merged for the past few years? Zero.
> >>
> >> Just take a look how the life goes on at github:
> >> https://github.com/Mr-Dave/motion/issues?q=is%3Aissue+is%3Aclosed
> >> <https://github.com/Mr-Dave/motion/issues?q=is%3Aissue+is%3Aclosed>
> >> People submit patches and their changes get merged into master branch. Not
> >> as fast as it could be (as only MrDave maintains the repo), but at least
> >> they exist. You can see on the fork map how many people are keeping coding
> >> and even updating README: https://github.com/Mr-Dave/motion/network
> >> <https://github.com/Mr-Dave/motion/network>
> >>
> >> This motion version is alive and is evolving.
> >> All we need is to give it the official status so all the distros pulls
> >> this new version, because it is de facto "real" motion. Everyone will
> >> benefit
> >>
> >> On Fri, Aug 5, 2016 at 5:49 AM, Kenneth Lavrsen <[email protected]
> >> <mailto:[email protected]>> wrote:
> >> Resent to the right mailing list
> >>
> >> Mr Dave
> >>
> >> I am happy to to see the project handed over to someone that will give it
> >> tender love and care. I had hoped to get time for it again but I have to
> >> recognize that I do not even have time to read this mailing list
> >>
> >> I can see from this thread that there is a team willing to take over and
> >> that is good.
> >>
> >> The only concern I have is documentation.
> >>
> >> When I joined the Motion project, it was wonderful code with no
> >> documentation at all. And very few users because noone had a clue how to
> >> use the code.
> >>
> >> I changed that and wrote the Motion Guide. It changed the project
> >> completely. A year later the project was given to another coder while I
> >> maintained the documentation. And finally I took over the project but I
> >> was never the main coder.
> >>
> >> I created this mailing list. I moved the project on to Twiki and later to
> >> Foswiki which I participated in very actively.
> >>
> >> To pass on the project is easy. To find people willing to do the work is
> >> the difficult part.
> >>
> >> The team that takes over need to do more than just code. You need to keep
> >> a project like Motion fully documented. A config file based program does
> >> not explain itself the way a GUI program does. The config file itself is
> >> not enough.
> >>
> >> I would like some commitment that you guys will not just code and code and
> >> code but also ensure that Motion is still a well documented project.
> >>
> >> Moving the code to Git. Moving the bug reporting away from the current
> >> wiki. Fine! Feature requests etc etc. No worries.
> >>
> >> I will be happy to continue running the server and the Foswiki. The Motion
> >> Guide part of the wiki is actually very smart and it requires very little
> >> work to maintain the documentation if you invest an hour learning how it
> >> works. The documentation builds itself. It will even build the manpage for
> >> you. All it requires is maintaining one simple "database" record on the
> >> wiki per config parameter. And it is a good idea that it is not the coders
> >> that maintain this as long as they pass on the information.
> >>
> >> It is hard to run a project on your own. It needs a leader that can take
> >> the final decisions and formally owns it. I am no longer the right person
> >> for that, because of lack of time. I am OK to pass on the ownership. But
> >> it would be nice if I knew that there are 3-4 of you willing to help. And
> >> I am deeply concerned about the project falling back to undocumented geek
> >> mode where only C programmers that can read the code can use the software.
> >> That would be very sad.
> >>
> >> I will make an effort on reading the mailing list the next days
> >>
> >> Kenneth
> >>
> >> > On 05 Aug 2016, at 02:29, Mr Dave <[email protected]
> >> > <mailto:[email protected]>> wrote:
> >> >
> >> > Kenneth,
> >> >
> >> > I believe it is a best practice to formally ask you to take over the
> >> > Motion project before I officially move to create a new project. Please
> >> > let me know either way of your decision. If you are uncomfortable
> >> > passing it to me, would you consider putting it up for adoption to
> >> > someone else that would be able to maintain it.
> >> >
> >> > MrDave
> >>
> >> ------------------------------------------------------------------------------
> >> _______________________________________________
> >> Motion-devel mailing list
> >> [email protected]
> >> <mailto:[email protected]>
> >> https://lists.sourceforge.net/lists/listinfo/motion-devel
> >> <https://lists.sourceforge.net/lists/listinfo/motion-devel>
> >>
> >> ------------------------------------------------------------------------------
> >> _______________________________________________
> >> 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-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/motion-devel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
Message: 2
Date: Fri, 5 Aug 2016 21:58:37 +0200
From: Yoan Mollard <[email protected]>
Subject: Re: [Motion-user] Shoot HD images: 1080 is not a multiple of
16
To: Motion discussion list <[email protected]>
Message-ID:
<CAAJ=dj1g9jw3f7gobh_0eahmdfu8rd9fnymdg-owy9upnib...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Fri, 5 Aug 2016 23:07:34 +0200
From: Kenneth Lavrsen <[email protected]>
Subject: [Motion-user] How the documentation on the Motion wiki is
working
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi all
Let me introduce what is under the hood of the project documentation of
Motion
Ignore all the bug report, feature request, patch features. They are
awful and could be implemented much better but there is no point that I
try to do that because Github offers the same out of the box in a
familiar and superiour way.
But on the documentation side the Foswiki features are pretty cool and
not at all supported by Github or Sourceforge
You probably all know the Motion guide.
You go to http://www.lavrsen.dk/foswiki/bin/view/Motion/WebHome. You
click in the Motion Guide and you land on
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionGuide
From there you have several choices.
The first is the Installation. And if you ever try to edit that page it
has a short text and then followed by
%TOC%
%INCLUDE{"MotionOverview"}%
%INCLUDE{"KnownProblems"}%
%INCLUDE{"InstallOverview"}%
%INCLUDE{"PrepareInstall"}%
%INCLUDE{"ConfigureScript"}%
%INCLUDE{"MakeInstall"}%
%INCLUDE{"UpgradingFromOlderVersion"}%
%INCLUDE{"ErrorLogging"}%
All the %SOMETHING% are macros. %TOC% is a table of content. And
%INCLUDE.... simply includes pages. So all it is is a modular approach
so you do not have to sit and edit an evil long page. So to edit the
documentation you go to the sub page and start typing.
The markup language is simple.
---+ Headline level 1
---++ Headline level 2
---+++ Headline level 3
Some *bold* text.
WikiWords like WoW, HitMeGood etc automatically link to a page with that
name. WikiWord starts with upper case followed by lower case followed by
uppercase and you have a WikiWord.
WikiWord
Notawikiword (not capitals in the middle)
notAwikiWord (does not start with a capital)
Wiki2Word is a wikiword because number count as lower case.
ALSoaWikiWord2Go - Also a wiki word. The minute the parser saw ALSoaW it
because a wiki word.
If the page exists it links to it. If the page does not exist it suggest
that you create it.
!IDoNotWantThisAsWikiWord is not a wikiword. The ! cancels the
wikiword-ness but the ! is invisible.
There are two edit modes. Normal Edit is a WYSIWYG editor which is OK.
Edit Wikitext is for us geeks that want to control what we do. If you
edit existing text you quickly see how it works
Tables use the syntax
| *Heading text* | *Second Heading* |
| text here | more cell text here |
| hello | here I am |
Very simple.
Back to the documentation
*Getting It Running* is also a bunch of includes. Some are pretty smart
and intelligent.
Like the table of options. Noone had written that table.
The table gets generated in the included page ConfigFileOptions (
http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigFileOptions )
It has code that looks like this
%TABLE{valign="top" headeralign="left" columnwidths="170,240"}%
| *Option* | *Range/Values<br />Default* | *Description* |
%SEARCH{ "Group != 'Obsolete'" topic="ConfigOption*" casesensitive="on"
type="query" nosearch="on" nototal="on" order="formfield(Option)"
excludetopic="ConfigOptionTemplate, ConfigOptionForm" format="|
[[$topic][$formfield(Option)]]| Values: $formfield(Range)<br />Default:
$formfield(Default) | $formfield(Description) |"}%
What is going on?
First line is a Macro %TABLE... which defines how the table looks like.
Mostly allignment of text and columnwidths
Then | *Option* | *Range/Values<br />Default* | *Description* |
Which is he header of the table. Notice how you can use HTML in the markup.
And then the smart feature - the formatted SEARCH.
The SEARCH looks up all pages that start with ConfigOption. Note the
topic="ConfigOption*" where * is a wild card.
And it exclude the topics where Group != 'Obsolete'
What is this? Is it a database? Well almost. I will get back to that.
There are some more options for the SEARCH that controls how it presents
data. In this case it basically means "shut up with all your noise" and
finally there is the format parameter which defines how the pages
(topics) are presented.
Each found topic becomes a table row.
format="| [[$topic][$formfield(Option)]]| Values: $formfield(Range)<br
/>Default: $formfield(Default) | $formfield(Description) |"}%
So the format is a row where
First column is a link to the page that defines the parameter.
Second column is a combination of the field values for Range and Default
values.
Third column is the description
So each motion.conf option has its own wikipage. The naming convention
is ConfigOptionOptionName where OptionName is a WikiWord version of the
option. Simple. It does not have to be but that is how I defined it and
it makes it easy to find the right page
Now to the config option pages.
Let us take an example. The option "height" from motion conf is defined
on http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigOptionHeight. So
the topic (Pages are called topics in Foswiki - horrible I know) is
ConfigOptionHeight.
When you look at it you see a plain descriptive text
And below a table which is a Form. The structure of this form is defined
in ConfigOptionForm which looks like
Form Topic for motion.conf options
Name:
<http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigOptionForm?sortcol=0;table=1;up=0#sorted_table>
Type:
<http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigOptionForm?sortcol=1;table=1;up=0#sorted_table>
Size:
<http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigOptionForm?sortcol=2;table=1;up=0#sorted_table>
Values:
<http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigOptionForm?sortcol=3;table=1;up=0#sorted_table>
Tooltip message:
<http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigOptionForm?sortcol=4;table=1;up=0#sorted_table>
Option text 50 Option Name - always lower case and with
underscore
between words
Type select 1 Boolean, Integer, String, Discrete Strings Date
type
of option
Range text 70 min: x, max: y Range for integers, or list of allowed
strings/values
Default text 50 Default value when option is commented
out
Description textarea 80x4 Short Description
Group select 1 Runtime Options, Capture Device, Round Robin, Motion
Detection Settings, Image File Output, Movie File Output, Snapshots,
Text Display, Target Directories and Filenames, Live Webcam Server, HTML
Based Control, Tracking, External Commands, Common Options For Database,
Database Options For MySQL, Database Options For PostgreSQL, Video
Loopback Device, Debugging for Programmers, Thread, Obsolete Option
group from motion.conf
So in reality it is like a primitive database where each option is a
record in a database and the database fields are
Option: The name of the option
Type: One of the values Boolean, Integer, String, Discrete Strings
Range: is a plain text field where you define the range of valid values
if there is a range
Default: is the default value
Group: Is one of the values - Runtime Options, Capture Device, Round
Robin, Motion Detection Settings, Image File Output, Movie File Output,
Snapshots, Text Display, Target Directories and Filenames, Live Webcam
Server, HTML Based Control, Tracking, External Commands, Common Options
For Database, Database Options For MySQL, Database Options For
PostgreSQL, Video Loopback Device, Debugging for Programmers, Thread,
Obsolete
The group is used to be able to autogenerate the documentation and
present the different options grouped together. If you need a new group
you edit the ConfigOptionForm topic and the new value will be in the
pick list
To create a new ConfigOptionXXXXX topic you create it first and then add
the ConfigOptionForm to the topic and it then gets the nice structured
database like fields to it. Very simple once you get the idea.
Once you have the the config options defined as one topic for each
option only fantasy limits the ways you can present the data using the
SEARCH macro.
And this is what I do in the Motion Guide. In
http://www.lavrsen.dk/foswiki/bin/view/Motion/ConfigFileOptions it
creates the table of all config options.
Back to the Motion Guide. Now that you know what is going on let us look
at http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionGuideBasicFeatures.
Again just a bunch of INCLUDEs.
And inside each included topic I have a plain text introduction. And
then followed by a SEARCH that presents the the options based on a
section criteria based on Group value. I can see I need to simplify the
SEARCHes a little because there is a newer query syntax available now in
Foswiki that works a bit like SQL. I will update all those.
But the principle is the same all over. The documention is a mix of
plaintext and reuse of the ConfigOptionXXXX topics.
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionGuideAlphabeticalOptionReferenceManual
simply lists ALL the config options in one big document.
It is a bit hidden. It is under
http://www.lavrsen.dk/foswiki/bin/view/Motion/MiscellaneousInformation
and there you find
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionOptionsAlphabeticalManpage
And what is under the hood of that?
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionOptionsAlphabeticalManpage?raw=on
First some plain text Main page intro. Nothing fancy and all within
<pre> and </pre> tags that makes Foswiki show the text as raw code but
still interprets macros.
%STARTATTACH...% and %ENDATTACH...% enclose the text we want saved in a
man page file.
Each time you edit and save the page a new man page is created and
attached to the topic. Yes you can also attach files to the wikipages.
In this case a plugin does it automatically each time you save.
Inside the pre tags you find a SEARCH macro.
%SEARCH{ "Group != 'Obsolete'" type="query" topic="ConfigOption*"
casesensitive="on" nosearch="on" nototal="on" order="formfield(Option)"
excludetopic="ConfigOptionTemplate, ConfigOptionForm,
ConfigOptionFfmpegFilename, ConfigOptionMinimumGap" format=".TP$n().B
$formfield(Option)
$percntCALC{\"$LOWER($formfield(Type))\"}$percnt$n()Values:
$formfield(Range) / Default:
$formfield(Default)$n().br$n()$formfield(Description)"}%
It again find all the options and present them neatly in a format that
makes sense in a man page.
In this case it presents all options except the ones that are in marked
as Obsolete in the Group field. So now you know how to hide the options
that are removed in the new versions. Change the group field to Obsolete
and it is hidden from all views but can be presented on a list of
obsolete options.
The Macros in Foswiki are parsed top to down, left to right, inside out.
So when you want to put macros inside the format string of the SEARCH
you have to hide the macros (inside out) until the search is run. The
$percnt or $percent is the way you delay the macro expansion inside SEARCH.
So first the SEARCH finds all the option topics, then creates the table
rows, replaceing all the $percnt with "%" and when the SEARCH is
complete the the now visible macros get parsed. In this case the CALC
macro which is a swiss army knife of small functions. Here is changes
text to lower case.
I do not expect you guys to understand all this. But you can easily edit
the pages that are already there.
With a little help you can create new config option topics and they then
automatically appear in the Motion guide in the right chapter based on
the Group field.
And if you remove an option you change it to the obsolete group.
When you want to generate a new man page - just look up
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionOptionsAlphabeticalManpage.
Edit the page and save it. And then download the updated "motion.1"
attachment. Easy, right?
You edit one config option file one place. And all the many versions of
the options tables, the reference manual, the detailed manual, the man
pages - everything is up to date. THAT is WHY the Motion guide is on
Foswiki. It takes a little effort to get the head around it but then it
is easy to maintain
And I will gladly do that. I am using Foswiki at work every day. I just
need you guys to ping me when you need to update something that is not
just a simple edit of an existing page
The motion guide which is included when you build Motion (at least from
the old SVN version) simply downloads the HTML from
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionGuideOneLargeDocument
And it does it in a mode where all the menus and shit is removed and you
just get a plain HTML file. You can see some grumpy users that added a
note that the file is out of date and that people have to read the code
to find out how it works. That is so wrong and not easy if you do not
read C code.
Long email. But the few of you that are interested should not understand
how it works. I will update the SEARCH syntax used to query search
instead of the old regex searches used which are a bit dodgy to read.
Kenneth
-------------- 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 6
*******************************************
