> The Motion project is a bit dead from a developer perspective

It's sad to hear. Since kernel, V4L and ffmpeg are being actively developed - it could be that starting from some release of them motion will be finally broken and won't build on newer platforms?


On Mon, Sep 23, 2013 at 9:25 PM, Kenneth Lavrsen <kenneth@lavrsen.dk> wrote:
The Motion project is a bit dead from a developer perspective. I am not spending time on it any more. And I think Angel is also working on other stuff.

If some of you wish to get access to the SVN and take up the challenge, let me know.

I am happy to keep running the Motion wiki.

The fact that you cannot reach the site is a problem I have had the past 3 days where suddenly the web server looses the network. I am replacing the network card at the moment and I can see that Ubuntu is a bit crappy with respect to its network tools that keep on crashing.

Hopefully I get it working later tonight. Same server is also my mail server so I cannot live without it.

Kenneth


On 23/09/2013 17:15, Steve Goldsmith wrote:
Hey Mike, for the most part Motion is a dead project (the page didn't come up for me http://www.lavrsen.dk/foswiki/bin/view/Motion) and there's better solutions out there. I used motion for many years and finally just wrote my own with OpenCV and Python because of all the problems (unstable frame rate, blank frames, etc). Having said that there's forks of it out on GitHub, so you can start with that and knock yourself out.


On Mon, Sep 23, 2013 at 2:54 AM, Mike Wilson <knobby2346@gmail.com> wrote:
I have read that this wasn't supported, so I hacked it in to motion via ffmpeg. This is working for me now, but I'd like to make it correctly and submit a patch. I'm wondering if there are any objections or desires to reorganize the code a little.

With the addition of RTSP, the netcam file is getting pretty large. I was thinking about pushing each of the types out into their own file. I would create netcam_rtsp.c, netcam_http.c, netcam_ftp.c, etc. I would also probably need to create something like a netcam_util.c that had shared functions. The idea would be that anything new protocol would simply be a new file with functions for creating/destroying contexts, setup and a function to get a frame.

I'm a little worried that this is a large change and not in the direction desired for the project. I'm also worried that development may have stalled here.

Any suggestions or comments?

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
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




--
Steven P. Goldsmith


------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk


_______________________________________________
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


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
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