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 (John Baker)
2. Re: Motion Project (TN Patriot)
3. Motion input from File? (Thomas Drebert)
4. Re: Motion input from File? (tosiara)
5. Re: Motion Project (John Baker)
----------------------------------------------------------------------
Message: 1
Date: Sun, 07 Aug 2016 15:14:31 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: [email protected]
Message-ID:
<1470579271.1170381.688345297.41388...@webmail.messagingengine.com>
Content-Type: text/plain
Kenneth,
> A little advice
Totally agree that motion should not be complicated. All I want is a
process that does basic motion detection & timelapse video recording in
a reliable fashion. A modern web interface, so I can monitor it via my
phone, would be welcome. I don't use Zoneminder as it's too complicated
/ requires a database etc. But motion has its issues, for example, I
have two cameras on RTSP and I run separate motion processes fr them,
because if I try one motion process, it segfaults (due to some issue I
never quite figured out (connection related).
I'd like to see a lot of the home brew code ejected, ie the HTTP code,
the webserver, video4linux, the config file loading stuff (which could
be replaced by something to read a YAML file into a generic structure -
as I can do with one line of code in Python), and the focus of motion
being the processing of images / motion detection.
John
------------------------------
Message: 2
Date: Sun, 7 Aug 2016 09:21:11 -0500
From: TN Patriot <[email protected]>
Subject: Re: [Motion-user] Motion Project
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 5 Aug 2016 04:49:30 +0200
Kenneth Lavrsen <[email protected]> wrote:
> > On 05 Aug 2016, at 02:29, Mr Dave <[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
> >
>
> 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
>
It's a little sad to see you not be able to keep working on your baby (I know
it's not 'yours' per se, but you've held it the longest, heh). I've been
watching (and trying to use) Motion for many years.
It's always been fairly difficult for me to setup, so I've never really kept
with using it due to frustration. I do keep up with it by watching the mailing
list all the time to see changes and such, and I even remember way back when
Dave was first trying to get people to try out his GUI version.
As it is now though, it's not so much the documentation that keeps me from
trying it again, it's as you say it's just plain difficult to figure out how
to even use it since everything's so 'new' and different from several years
ago. I also can't even figure out how or from where to even download it
anymore.
Anyway, I'll keep watching the list and hopefully I'll catch something
somewhere that someone posts the finally cleaned up site, downloads and
documentation for Motion, as it's pretty much the defacto app for Linux users.
Again, sorry to see you go, and hope you'll still be around for us to say Hi
or Thanks to once in a while, heh.
JB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlenQ+AACgkQVKoUne6H+sQ2SQCgrTQfE6403t5BbvffRpeT0/b7
66QAoINedlfqH6Muuyk0VMizmomctmnl
=zDpq
-----END PGP SIGNATURE-----
------------------------------
Message: 3
Date: Sun, 7 Aug 2016 16:59:08 +0200
From: Thomas Drebert <[email protected]>
Subject: [Motion-user] Motion input from File?
To: Motion discussion list <[email protected]>
Message-ID:
<CANn+32gaiEJ=+majmtsegpo-mohqdpb2g6j4whnqxf5nqy2...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Helio,
i have a Timelapse mpg Video capture with Motion.
I would like use this file as input for Motion,
but it does not work.
I tried it with VLC as streamer, with transcode or without.
As mpeg1, m-jpeg with http or rstp.
And direct as file.
This is the Error:
[1] [ALR] [NET] [Aug 07 15:41:50] netcam_start: Network Camera thread
starting... for url (rstp://192.168.0.128:8554/stream.sdp)
[1] [CRT] [NET] [Aug 07 15:41:50] netcam_start: Invalid netcam_url (rstp://
192.168.0.128:8554/stream.sdp)
if i use a other VLC with this URL, i can see the Video.
What can i do?
regards
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Sun, 7 Aug 2016 18:30:20 +0300
From: tosiara <[email protected]>
Subject: Re: [Motion-user] Motion input from File?
To: Motion discussion list <[email protected]>
Message-ID:
<cachtdwszlqlzd+quky3uklp-kctqfov6_bjjvzweknk9jwf...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
You have a typo - not RSTP, it should RTSP
On Sun, Aug 7, 2016 at 5:59 PM, Thomas Drebert <[email protected]> wrote:
> Helio,
>
> i have a Timelapse mpg Video capture with Motion.
> I would like use this file as input for Motion,
> but it does not work.
>
>
> I tried it with VLC as streamer, with transcode or without.
> As mpeg1, m-jpeg with http or rstp.
> And direct as file.
>
> This is the Error:
> [1] [ALR] [NET] [Aug 07 15:41:50] netcam_start: Network Camera thread
> starting... for url (rstp://192.168.0.128:8554/stream.sdp)
> [1] [CRT] [NET] [Aug 07 15:41:50] netcam_start: Invalid netcam_url (rstp://
> 192.168.0.128:8554/stream.sdp)
>
> if i use a other VLC with this URL, i can see the Video.
>
> What can i do?
>
> regards
> Thomas
>
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> 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: 5
Date: Sun, 07 Aug 2016 17:32:27 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] Motion Project
To: [email protected]
Message-ID:
<1470587547.1190231.688412465.60453...@webmail.messagingengine.com>
Content-Type: text/plain
Is anyone able to help with the enquiry below?
On Fri, Aug 5, 2016, at 07:01 AM, John Baker wrote:
> 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
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 123, Issue 20
********************************************
