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: Smooth Video Stream (tosiara)
2. Re: Motion Project (Kenneth Lavrsen)
3. Re: Motion Project (John Baker)
4. segfault (John Baker)
5. Re: [Motion-devel] Motion Project (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Mon, 25 Jul 2016 10:47:02 +0300
From: tosiara <tosi...@gmail.com>
Subject: Re: [Motion-user] Smooth Video Stream
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID:
<CACHTdwS9=BS-+zZ-axa_N_5Fc2POmczRdcd=o5e_rmlw01s...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Increase "stream_maxrate" in your config:
https://github.com/Mr-Dave/motion/blob/master/motion-dist.conf.in#L492
On Fri, Jul 15, 2016 at 6:39 AM, Lee Gold <leeg...@operamail.com> wrote:
> I guess I don't know enough at this point to make the right
> configuration - I assume change(s) in motion.conf.
>
> I can serve the output of my logitech 920 with motion, I see the image
> OK.
>
> I wanted to make it so it's like "video", right now it seems to sends a
> refreshed frame about once every few seconds so it's choppy. I haven't
> changed anything in the config file other than allowing it to serve to
> other then localhost and changed the device and it found the cam device
> just fine.
>
> I'm only serving on a local standard ethernet home network, using
> Xubuntu 16.04 Linux. So first question is how to get a reasonably smooth
> video served? Are there configs in the default conf file to do?
>
> it's motion Version 3.2.12+git20140228
>
> and I start it with $ sudo motion, then when done I just stop the
> process...
>
> Thanks
>
>
> --
> http://www.fastmail.com - Email service worth paying for. Try it for free
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Fri, 5 Aug 2016 04:49:30 +0200
From: Kenneth Lavrsen <kenn...@lavrsen.dk>
Subject: Re: [Motion-user] Motion Project
To: Mr Dave <motionmrd...@gmail.com>,
motion-user@lists.sourceforge.net
Cc: motion-de...@lists.sourceforge.net
Message-ID: <4a97eda1-c86f-4521-9adb-5481a7ea5...@lavrsen.dk>
Content-Type: text/plain; charset=us-ascii
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 <motionmrd...@gmail.com> 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
------------------------------
Message: 3
Date: Fri, 05 Aug 2016 07:01:05 +0100
From: John Baker <jba...@dryfish.org.uk>
Subject: Re: [Motion-user] Motion Project
To: motion-user@lists.sourceforge.net
Message-ID:
<1470376865.3193487.686654353.4c9bc...@webmail.messagingengine.com>
Content-Type: text/plain
Kenneth
Thank you for all your hard work. Given you've done a lot of work on
documentation, please can I raise one point for your consideration &
clarification? How exactly does ffmpeg_video_codecformat work? When do
I use flv over swf? The first part of the docs suggests it only has two
options, but then it talks about supported formats.
Thanks!
# Codec to used by ffmpeg for the video compression.
# Timelapse videos have two options.
# swf - Creates swf file with mpeg-2 encoding.
# If motion is shutdown and restarted, new pics will be appended
# to any previously created file with name indicated for timelapse.
# mpeg4 - Creates avi file with the default encoding.
# If motion is shutdown and restarted, new pics will create a
# new file with the name indicated for timelapse.
# Supported formats are:
# mpeg4 or msmpeg4 - gives you files with extension .avi
# msmpeg4 is recommended for use with Windows Media Player because
# it requires no installation of codec on the Windows client.
# swf - gives you a flash film with extension .swf
# flv - gives you a flash video with extension .flv
# ffv1 - FF video codec 1 for Lossless Encoding ( experimental )
# mov - QuickTime ( testing )
# ogg - Ogg/Theora ( testing )
# mp4 - MPEG-4 Part 14 H264 encoding
# mkv - Matroska H264 encoding
# hevc - H.265 / HEVC (High Efficiency Video Coding)
ffmpeg_video_codec mpeg4
------------------------------
Message: 4
Date: Fri, 05 Aug 2016 07:21:43 +0100
From: John Baker <jba...@dryfish.org.uk>
Subject: [Motion-user] segfault
To: motion-user@lists.sourceforge.net
Message-ID:
<1470378103.3196588.686664065.19616...@webmail.messagingengine.com>
Content-Type: text/plain
If anyone has some source in front of them and understands it, here's a
back trace from gdb:
Thread 1 (Thread 0x74086400 (LWP 1680)):
#0 0x00016424 in process_image_ring (cnt=cnt@entry=0x15f7c50,
max_images=max_images@entry=2) at motion.c:536
#1 0x00017d40 in motion_loop (arg=<optimized out>) at motion.c:1926
#2 0x76e46fbc in start_thread () from /usr/lib/libpthread.so.0
#3 0x758c5cf0 in ?? () from /usr/lib/libc.so.6
I had the ffmpeg_video_codec set to mpeg.
------------------------------
Message: 5
Date: Fri, 5 Aug 2016 10:48:21 +0300
From: tosiara <tosi...@gmail.com>
Subject: Re: [Motion-user] [Motion-devel] Motion Project
To: Motion SVN commit messages <motion-de...@lists.sourceforge.net>
Cc: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID:
<cachtdwryzln7efz+nmsvemxcamqfnbqghhy_+lwcnjes0q4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 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
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
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 <kenn...@lavrsen.dk> 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 <motionmrd...@gmail.com> 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
> motion-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
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 1
*******************************************
