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: keep alive missing (MrDave)
   2. Re: keep alive missing (Richard Bown)


----------------------------------------------------------------------

Message: 1
Date: Wed, 14 Dec 2022 06:49:48 -0700
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] keep alive missing
Message-ID: <b59499b3-0770-17b2-c7c9-76e3d3108...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

FFmpeg is now used as the default for processing network cameras since 
it is more flexible and has greater support for all of the possible 
cameras and protocols in the world.? Users can specify any FFmpeg 
parameters via the netcam_params

Some relevant ffmpeg options for this situation could be:

reconnect_on_network_error = 1
reconnect_at_eof=1
reconnect=1
multiple_requests=1
reconnect_streamed=1

Specify them like

netcam_params 
reconnect_on_network_error=1,reconnect_at_eof=1,reconnect=1,multiple_requests=1,reconnect_streamed=1

I'd note that these options became the default for http cameras in 
version 4.5.0.? So if any of them are not desired in that version the 
user must turn them off by specifying 0 instead of 1. Version 4.5.0 also 
suppresses some of the excess messages that may be produced from 
reconnecting using the options.

These and other camera options are included in the FFmpeg protocols 
documentation page.

 ?To avoid using FFmpeg and instead use the legacy tcp methods, specify 
the camera url prefix as mjpeg instead of http.

On 12/14/2022 3:39 AM, tosiara wrote:
> How does your netcam_url look like?
> Try different protocols, like http://, mjpeg://, mjpg:// - does any of 
> them work?
>
> On Wed, Dec 14, 2022 at 12:30 PM Richard Bown <rich...@g8jvm.com> wrote:
>
>     Hi, I have a Tenvis 391W ip cam , had it for ages, and with earlier
>     versions it was working,? however, with 4.4 motion disables the cam as
>     its says in the logs no keep alive signal from the cam.
>     Is there a config setting that will cause motion to ignore this
>     please,
>     I can send a section of the log if need be. I know the camera is
>     functional as I can monitor it on its direct ip-address, but after
>     about 20 mins motion just greys it out.
>     Thanks
>     -- 
>     -- 
>     ?Best wishes /73
>     ?Richard Bown
>
>     ?Email : rich...@g8jvm.com
>
>     ?HTTP??: https://www.g8jvm.com
>
>     ?######################################################################
>
>     ########
>
>     ?Ham Call: G8JVM . QRV: HF + 50-432 MHz + Microwave
>     ?Maidenhead QRA: IO82SP38, LAT. 52.6620 N LONG. 2.4696 W
>     ?VHF: 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W,
>     ?Microwave: 1296MHz 110W, 2320MHz 100W, 3400MHz 15W, 5760MHz 10W &
>     10368MHz 5W
>     ?OS: Linux Mint 20.3, on a Dell Inspiron 3580 laptop
>     ?######################################################################
>
>     ########
>
>
>     _______________________________________________
>     Motion-user mailing list
>     Motion-user@lists.sourceforge.net
>     https://lists.sourceforge.net/lists/listinfo/motion-user
>     https://motion-project.github.io/
>
>     Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe:https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Wed, 14 Dec 2022 13:56:12 +0000
From: Richard Bown <rich...@g8jvm.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] keep alive missing
Message-ID: <3d33b42843e7793f89153a4586714783e689532f.ca...@g8jvm.com>
Content-Type: text/plain; charset="utf-8"

On Wed, 2022-12-14 at 06:49 -0700, MrDave wrote:


Thanks for the info, I've ordered a TP-link tapo cam to use in its
place , which will be happier I hope

> FFmpeg is now used as the default for processing network cameras
> since it is more flexible and has greater support for all of the
> possible cameras and protocols in the world.? Users can specify any
> FFmpeg parameters via the netcam_params
> Some relevant ffmpeg options for this situation could be:
> reconnect_on_network_error = 1
> reconnect_at_eof=1
> reconnect=1
> multiple_requests=1
> reconnect_streamed=1
> Specify them like 
> netcam_params
> reconnect_on_network_error=1,reconnect_at_eof=1,reconnect=1,multiple_
> requests=1,reconnect_streamed=1
> I'd note that these options became the default for http cameras in
> version 4.5.0.? So if any of them are not desired in that version the
> user must turn them off by specifying 0 instead of 1.? Version 4.5.0
> also suppresses some of the excess messages that may be produced from
> reconnecting using the options. 
> These and other camera options are included in the FFmpeg protocols
> documentation page.
> ?To avoid using FFmpeg and instead use the legacy tcp methods,
> specify the camera url prefix as mjpeg instead of http.?? 
> On 12/14/2022 3:39 AM, tosiara wrote:
>  
> > 
> > How does your netcam_url look like?
> > Try different protocols, like http://, mjpeg://, mjpg:// - does any
> > of them work?
> >  
> > On Wed, Dec 14, 2022 at 12:30 PM Richard Bown <rich...@g8jvm.com>
> > wrote:
> >  
> > > Hi, I have a Tenvis 391W ip cam , had it for ages, and with
> > > earlier
> > > versions it was working,? however, with 4.4 motion disables the
> > > cam as
> > > its says in the logs no keep alive signal from the cam.
> > > Is there a config setting that will cause motion to ignore this
> > > please,
> > > I can send a section of the log if need be. I know the camera is
> > > functional as I can monitor it on its direct ip-address, but
> > > after
> > > about 20 mins motion just greys it out.
> > > Thanks
> > > -- 
> > > --?
> > > ?Best wishes /73?
> > > ?Richard Bown
> > > ?
> > > ?Email : rich...@g8jvm.com
> > > 
> > > ?HTTP??:??https://www.g8jvm.com
> > > ?
> > > ?################################################################
> > > ######
> > > 
> > > ########
> > > 
> > > ?Ham Call: G8JVM . QRV: HF + 50-432 MHz + Microwave?
> > > ?Maidenhead QRA: IO82SP38, LAT. 52.6620 N LONG. 2.4696 W
> > > ?VHF: 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W,?
> > > ?Microwave: 1296MHz 110W, 2320MHz 100W, 3400MHz 15W, 5760MHz 10W
> > > &
> > > 10368MHz 5W
> > > ?OS: Linux Mint 20.3, on a Dell Inspiron 3580 laptop
> > > ?################################################################
> > > ######
> > > 
> > > ########
> > > 
> > > 
> > > _______________________________________________
> > > Motion-user mailing list
> > > Motion-user@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > https://motion-project.github.io/
> > > 
> > > Unsubscribe:
> > > https://lists.sourceforge.net/lists/options/motion-user
> > > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Motion-user mailing list
> > Motion-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > https://motion-project.github.io/
> > 
> > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
> 
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 196, Issue 14
********************************************

Reply via email to