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. Issues with RTSP cameras (Willy Gardiol)
2. Re: Issues with RTSP cameras (folkert)
3. Re: Issues with RTSP cameras (Willy Gardiol)
4. Re: Issues with RTSP cameras (folkert)
----------------------------------------------------------------------
Message: 1
Date: Thu, 31 Jan 2019 15:42:10 +0100
From: Willy Gardiol <wi...@gardiol.org>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Issues with RTSP cameras
Message-ID: <7576f1ba-601b-1454-84bc-2d91e9ffb...@gardiol.org>
Content-Type: text/plain; charset=utf-8
Hi!
i have a few RTSP cameras, they are crappy Chinese v380 ones, and quite
slow in responding, but nontheless, they work.
I have intermittent images from the cameras, and i get a lot of messages
like this:
[11:ml11] [ERR] [VID] vid_start: Netcam RTSP failed to open
[11:ml11] [WRN] [ALL] motion_init: Could not fetch initial image from
camera
[11:ml11] [WRN] [ALL] motion_init: Motion continues using width and
height from config file(s)
[11:ml11] [WRN] [ALL] mlp_retry: Retrying until successful connection
with camera
[11:ml11] [ERR] [NET] netcam_rtsp_open_context: Normal resolution:
Unable to open camera((null)): Connection refused
[11:ml11] [ERR] [VID] vid_start: Netcam RTSP failed to open
After a while the image resume correctly. The RTSP camera output x264
compressed stream and i can _always_ get a frame using ffpmeg directly,
albeit it's quite slow (can take from 1 to 2 or 3 secs to get an image
manually).
Somebody has ideas on how to debug or improve this?
------------------------------
Message: 2
Date: Thu, 31 Jan 2019 20:40:55 +0100
From: folkert <folk...@vanheusden.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Issues with RTSP cameras
Message-ID:
<20190131194055.ehvodbbjwl54f...@belle.intranet.vanheusden.com>
Content-Type: text/plain; charset=us-ascii
> i have a few RTSP cameras, they are crappy Chinese v380 ones, and quite
> slow in responding, but nontheless, they work.
...
> compressed stream and i can _always_ get a frame using ffpmeg directly,
> albeit it's quite slow (can take from 1 to 2 or 3 secs to get an image
> manually).
What works for me with my software (https://github.com/flok99/constatus
) is setting the i-frame interval to 1. Thus every frame transmitted by
the camera is in i-frame.
I realised that for me also the first frame is always correct, and the
first frame is always an i-frame. So there you are.
Folkert van Heusden
--
------------------------------
Message: 3
Date: Fri, 01 Feb 2019 06:30:22 +0100
From: Willy Gardiol <wi...@gardiol.org>
To: folkert <folk...@vanheusden.com>, Motion discussion list
<motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Issues with RTSP cameras
Message-ID: <275fe083-99a0-4c5d-bfdd-bd182a156...@gardiol.org>
Content-Type: text/plain; charset="utf-8"
Is this something you do on the camera or on motion?
Il 31 gennaio 2019 20:40:55 CET, folkert <folk...@vanheusden.com> ha scritto:
>> i have a few RTSP cameras, they are crappy Chinese v380 ones, and
>quite
>> slow in responding, but nontheless, they work.
>...
>> compressed stream and i can _always_ get a frame using ffpmeg
>directly,
>> albeit it's quite slow (can take from 1 to 2 or 3 secs to get an
>image
>> manually).
>
>What works for me with my software (https://github.com/flok99/constatus
>) is setting the i-frame interval to 1. Thus every frame transmitted by
>the camera is in i-frame.
>
>I realised that for me also the first frame is always correct, and the
>first frame is always an i-frame. So there you are.
>
>
>Folkert van Heusden
>
>--
--
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevit?.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Fri, 1 Feb 2019 08:55:36 +0100
From: folkert <folk...@vanheusden.com>
To: Willy Gardiol <wi...@gardiol.org>
Cc: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Issues with RTSP cameras
Message-ID:
<20190201075536.pay5ya6h7yc73...@belle.intranet.vanheusden.com>
Content-Type: text/plain; charset=iso-8859-1
on the camera (I don't use motion)
On Fri, Feb 01, 2019 at 06:30:22AM +0100, Willy Gardiol wrote:
>
> Is this something you do on the camera or on motion?
>
>
>
> Il 31 gennaio 2019 20:40:55 CET, folkert <folk...@vanheusden.com> ha scritto:
> >> i have a few RTSP cameras, they are crappy Chinese v380 ones, and
> >quite
> >> slow in responding, but nontheless, they work.
> >...
> >> compressed stream and i can _always_ get a frame using ffpmeg
> >directly,
> >> albeit it's quite slow (can take from 1 to 2 or 3 secs to get an
> >image
> >> manually).
> >
> >What works for me with my software (https://github.com/flok99/constatus
> >) is setting the i-frame interval to 1. Thus every frame transmitted by
> >the camera is in i-frame.
> >
> >I realised that for me also the first frame is always correct, and the
> >first frame is always an i-frame. So there you are.
> >
> >
> >Folkert van Heusden
> >
> >--
>
> --
> Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevit?.
Folkert van Heusden
--
Curious about the inner workings of your car? Then check O2OO: it'll
tell you all that there is to know about your car's engine!
http://www.vanheusden.com/O2OO/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
------------------------------
------------------------------
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 152, Issue 1
*******************************************
