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: RTSP - how does it work? (John Baker)
2. Re: RTSP - how does it work? (Stealth Sztelf)
3. Re: RTSP - how does it work? (John Baker)
4. Re: RTSP - how does it work? (Mike Wilson)
----------------------------------------------------------------------
Message: 1
Date: Fri, 04 Mar 2016 20:34:02 +0000
From: John Baker <[email protected]>
Subject: Re: [Motion-user] RTSP - how does it work?
To: [email protected]
Message-ID:
<1457123642.3098683.539952290.2a0e5...@webmail.messagingengine.com>
Content-Type: text/plain
This is what mplayer -v -v -v outputs:
[rtsp @ 0x7f4e9109afa0]ret=0 c=00 [LAVF_header: avformat_open_input()
failed
Opening as detected format "libavformat" failed.
DEMUXER: freeing libavformat demuxer at 0x13b4e10
Failed to recognize file format.
On Fri, Mar 4, 2016, at 08:25 PM, Mike Wilson wrote:
> I just used ffmpeg to do it. Motion calls avformat_open_input with an
> option to enable tcp if requested. It doesn't seem to be anything
> special.
> Maybe something is different between the ffmeg versions being used?
>
> On Fri, Mar 4, 2016 at 11:46 AM John Baker <[email protected]> wrote:
>
> > How is motion performing RTSP? It appears that motion is the only tool
> > on the planet that can read the RTSP stream from a Foscam C1 (see
> > http://foscam.us/forum/foscam-c1-broken-rtsp-t18352.html) and I think
> > others would benefit from knowing how motion is doing it. Perhaps it's
> > using ffmpeg and invoking some options?
> >
> >
> > ------------------------------------------------------------------------------
> > Site24x7 APM Insight: Get Deep Visibility into Application Performance
> > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> > Monitor end-to-end web transactions and take corrective actions now
> > Troubleshoot faster and improve end-user experience. Signup Now!
> > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> > _______________________________________________
> > Motion-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> >
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
Message: 2
Date: Fri, 4 Mar 2016 21:41:58 +0100
From: Stealth Sztelf <[email protected]>
Subject: Re: [Motion-user] RTSP - how does it work?
To: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
try http://www.live555.com/ <http://www.live555.com/>
> Wiadomo?? napisana przez John Baker <[email protected]> w dniu
> 04.03.2016, o godz. 21:34:
>
> This is what mplayer -v -v -v outputs:
>
> [rtsp @ 0x7f4e9109afa0]ret=0 c=00 [LAVF_header: avformat_open_input()
> failed
> Opening as detected format "libavformat" failed.
> DEMUXER: freeing libavformat demuxer at 0x13b4e10
> Failed to recognize file format.
>
>
> On Fri, Mar 4, 2016, at 08:25 PM, Mike Wilson wrote:
>> I just used ffmpeg to do it. Motion calls avformat_open_input with an
>> option to enable tcp if requested. It doesn't seem to be anything
>> special.
>> Maybe something is different between the ffmeg versions being used?
>>
>> On Fri, Mar 4, 2016 at 11:46 AM John Baker <[email protected]> wrote:
>>
>>> How is motion performing RTSP? It appears that motion is the only tool
>>> on the planet that can read the RTSP stream from a Foscam C1 (see
>>> http://foscam.us/forum/foscam-c1-broken-rtsp-t18352.html) and I think
>>> others would benefit from knowing how motion is doing it. Perhaps it's
>>> using ffmpeg and invoking some options?
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>>> _______________________________________________
>>> Motion-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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: 3
Date: Fri, 04 Mar 2016 20:53:47 +0000
From: John Baker <[email protected]>
Subject: Re: [Motion-user] RTSP - how does it work?
To: [email protected]
Message-ID:
<1457124827.3104046.539968546.0ea66...@webmail.messagingengine.com>
Content-Type: text/plain
Err, suddenly ffmpeg has started working:
ffmpeg -i rtsp://user:[email protected]:554/videoMain -r 30 -an -t 900
out.mp4
But I see a lot of:
Invalid UE golomb code
These Foscam C1 cameras are a bit weird..
I don't think they use TCP/UDP:
[libx264 @ 0x55c85c10] using cpu capabilities: none!
[libx264 @ 0x55c85c10] profile High, level 3.1
[libx264 @ 0x55c85c10] 264 - core 148 r2579 73ae2d1 - H.264/MPEG-4 AVC
codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html -
options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7
psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6
lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf
mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40
aq=1:1.00
Output #0, mp4, to out.mp4
Metadata:
title : videoMain
encoder : Lavf56.40.101
Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021),
yuv420p, 1280x720, q=-1--1, 30 fps, 15360 tbn, 30 tbc
Metadata:
encoder : Lavc56.60.100 libx264
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
Press [q] to stop, [?] for help
------------------------------
Message: 4
Date: Fri, 04 Mar 2016 22:41:58 +0000
From: Mike Wilson <[email protected]>
Subject: Re: [Motion-user] RTSP - how does it work?
To: Motion discussion list <[email protected]>
Message-ID:
<CAAVeUCrZQ_0oEE3a6TYLRbaEqXcJvbqU=coxvd4jpqekcsm...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
You can see the current fork here:
https://github.com/Mr-Dave/motion/blob/master/netcam_rtsp.c#L441-L461
It shows how the options are set and things. This has changed a good deal
since the initial implementation, but it's still basically doing the same
thing. I'm happy to see that this project hasn't stagnated.
On Fri, Mar 4, 2016 at 3:55 PM John Baker <[email protected]> wrote:
> Err, suddenly ffmpeg has started working:
>
> ffmpeg -i rtsp://user:[email protected]:554/videoMain -r 30 -an -t 900
> out.mp4
>
> But I see a lot of:
>
> Invalid UE golomb code
>
> These Foscam C1 cameras are a bit weird..
>
> I don't think they use TCP/UDP:
>
> [libx264 @ 0x55c85c10] using cpu capabilities: none!
> [libx264 @ 0x55c85c10] profile High, level 3.1
> [libx264 @ 0x55c85c10] 264 - core 148 r2579 73ae2d1 - H.264/MPEG-4 AVC
> codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html -
> options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7
> psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
> 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6
> lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
> bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
> b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250
> keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf
> mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40
> aq=1:1.00
> Output #0, mp4, to out.mp4
> Metadata:
> title : videoMain
> encoder : Lavf56.40.101
> Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021),
> yuv420p, 1280x720, q=-1--1, 30 fps, 15360 tbn, 30 tbc
> Metadata:
> encoder : Lavc56.60.100 libx264
> Stream mapping:
> Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
> Press [q] to stop, [?] for help
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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...
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 118, Issue 2
*******************************************
