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. Can't connect to rtsp feed (Robert Brown)
2. Re: Can't connect to rtsp feed (MrDave)
3. Re: Can't connect to rtsp feed (Robert Brown)
4. Fwd: Re: Can't connect to rtsp feed (Robert Brown)
----------------------------------------------------------------------
Message: 1
Date: Mon, 13 Mar 2017 13:06:41 +1100
From: Robert Brown <rebr...@exemail.com.au>
Subject: [Motion-user] Can't connect to rtsp feed
To: motion-user@lists.sourceforge.net
Message-ID: <1607fe2e-f81c-47f6-8cff-fb71b021b...@exemail.com.au>
Content-Type: text/plain; charset=utf-8; format=flowed
Running 3.4.1 on Ubuntu 16.04 after trying the 3.2.12 default version.
VLC command works:
rtsp://user:pwd@192.168.1.111/onvif2
Log looks like:
[0] [NTC] [ALL] [Mar 13 12:35:51] motion_startup: Using log type (ALL)
log level (NTC)
[0] [NTC] [ENC] [Mar 13 12:35:51] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD
3670272 LIBAVFORMAT_BUILD 3670272
[0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is from
/etc/motion/motion.conf
[0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is device:
rtsp://admin:20160404@192.168.1.111:554/onvif2 input -1
[0] [NTC] [ALL] [Mar 13 12:35:51] main: Stream port 554
[0] [NTC] [ALL] [Mar 13 12:35:51] main: Waiting for threads to finish,
pid: 18218
[1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Thread 1 started , motion
detection Enabled
[1] [ALR] [NET] [Mar 13 12:35:51] netcam_start: Network Camera thread
starting... for url (rtsp://admin:20160404@192.168.1.111:554/onvif2)
[1] [NTC] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: Using tcp
transport
[1] [ERR] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: unable to
open input(rtsp://admin:20160404@192.168.1.111:554/onvif2): Invalid data
found
when processing input
[1] [WRN] [ALL] [Mar 13 12:35:51] motion_init: Could not fetch initial
image from camera Motion continues using width and height from config
file(s)
[1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
pre_capture buffer to 1 items
[1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream testing :
IPV4 addr: 0.0.0.0 port: 554
[1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream Bound :
IPV4 addr: 0.0.0.0 port: 554
[1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Started motion-stream
server in port 554 auth Disabled
[1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
pre_capture buffer to 3 items
[1] [WRN] [ALL] [Mar 13 12:36:00] motion_loop: Retrying until successful
connection with camera
[1] [ALR] [NET] [Mar 13 12:36:00] netcam_start: Network Camera thread
starting... for url (rtsp://admin:20160404@192.168.1.111:554/onvif2)
[1] [NTC] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: Using tcp
transport
[1] [ERR] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: unable to
open input(rtsp://admin:20160404@192.168.1.111:554/onvif2): Invalid data
found when processing input
I notice it reports input -1 even though conf file says input 1.
Also tried on raspbian Jessie with same result.
------------------------------
Message: 2
Date: Sun, 12 Mar 2017 23:18:38 -0600
From: MrDave <motionmrd...@gmail.com>
Subject: Re: [Motion-user] Can't connect to rtsp feed
To: motion-user@lists.sourceforge.net
Message-ID: <c8cbef77-edfe-7c30-2fdf-0393024b1...@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Does "ffplay rtsp://user:pwd@192.168.1.111:554/onvif2" work?
What kind of camera is it?
On 3/12/2017 8:06 PM, Robert Brown wrote:
> Running 3.4.1 on Ubuntu 16.04 after trying the 3.2.12 default version.
> VLC command works:
> rtsp://user:pwd@192.168.1.111/onvif2
> Log looks like:
> [0] [NTC] [ALL] [Mar 13 12:35:51] motion_startup: Using log type (ALL)
> log level (NTC)
> [0] [NTC] [ENC] [Mar 13 12:35:51] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD
> 3670272 LIBAVFORMAT_BUILD 3670272
> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is from
> /etc/motion/motion.conf
> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is device:
> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Stream port 554
> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Waiting for threads to finish,
> pid: 18218
> [1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Thread 1 started , motion
> detection Enabled
> [1] [ALR] [NET] [Mar 13 12:35:51] netcam_start: Network Camera thread
> starting... for url (rtsp://user:pwd@192.168.1.111:554/onvif2)
> [1] [NTC] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: Using tcp
> transport
> [1] [ERR] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: unable to
> open input(rtsp://user:pwd@192.168.1.111:554/onvif2): Invalid data
> found
> when processing input
> [1] [WRN] [ALL] [Mar 13 12:35:51] motion_init: Could not fetch initial
> image from camera Motion continues using width and height from config
> file(s)
> [1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
> pre_capture buffer to 1 items
> [1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream testing :
> IPV4 addr: 0.0.0.0 port: 554
> [1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream Bound :
> IPV4 addr: 0.0.0.0 port: 554
> [1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Started motion-stream
> server in port 554 auth Disabled
> [1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
> pre_capture buffer to 3 items
> [1] [WRN] [ALL] [Mar 13 12:36:00] motion_loop: Retrying until successful
> connection with camera
> [1] [ALR] [NET] [Mar 13 12:36:00] netcam_start: Network Camera thread
> starting... for url (rtsp://user:pwd@192.168.1.111:554/onvif2)
> [1] [NTC] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: Using tcp
> transport
> [1] [ERR] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: unable to
> open input(rtsp://user:pwd@192.168.1.111:554/onvif2): Invalid data
> found when processing input
>
> I notice it reports input -1 even though conf file says input 1.
> Also tried on raspbian Jessie with same result.
>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> 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
>
------------------------------
Message: 3
Date: Mon, 13 Mar 2017 16:28:54 +1100
From: Robert Brown <rebr...@exemail.com.au>
Subject: Re: [Motion-user] Can't connect to rtsp feed
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID: <718606a3-92d9-d42b-17cf-795401ea0...@exemail.com.au>
Content-Type: text/plain; charset=windows-1252; format=flowed
Yes the ffplay command and vlc both work fine.
The camera is Digoo M1Q:
http://www.mydigoo.com/Digoo-DG-M1Q-960P-2_8mm-Wireless-Mini-WIFI-Night-Vision-Smart-Home-Security-IP-Camera-Onvif-Monitor-p-38.html
Thanks
On 13/03/17 16:18, MrDave wrote:
> Does "ffplay rtsp://user:pwd@192.168.1.111:554/onvif2" work?
>
> What kind of camera is it?
>
>
> On 3/12/2017 8:06 PM, Robert Brown wrote:
>> Running 3.4.1 on Ubuntu 16.04 after trying the 3.2.12 default version.
>> VLC command works:
>> rtsp://user:pwd@192.168.1.111/onvif2
>> Log looks like:
>> [0] [NTC] [ALL] [Mar 13 12:35:51] motion_startup: Using log type (ALL)
>> log level (NTC)
>> [0] [NTC] [ENC] [Mar 13 12:35:51] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD
>> 3670272 LIBAVFORMAT_BUILD 3670272
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is from
>> /etc/motion/motion.conf
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is device:
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Stream port 554
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Waiting for threads to finish,
>> pid: 18218
>> [1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Thread 1 started , motion
>> detection Enabled
>> [1] [ALR] [NET] [Mar 13 12:35:51] netcam_start: Network Camera thread
>> starting... for url (rtsp://user:pwd@192.168.1.111:554/onvif2)
>> [1] [NTC] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: Using tcp
>> transport
>> [1] [ERR] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: unable to
>> open input(rtsp://user:pwd@192.168.1.111:554/onvif2): Invalid data
>> found
>> when processing input
>> [1] [WRN] [ALL] [Mar 13 12:35:51] motion_init: Could not fetch initial
>> image from camera Motion continues using width and height from config
>> file(s)
>> [1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
>> pre_capture buffer to 1 items
>> [1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream testing :
>> IPV4 addr: 0.0.0.0 port: 554
>> [1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream Bound :
>> IPV4 addr: 0.0.0.0 port: 554
>> [1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Started motion-stream
>> server in port 554 auth Disabled
>> [1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
>> pre_capture buffer to 3 items
>> [1] [WRN] [ALL] [Mar 13 12:36:00] motion_loop: Retrying until successful
>> connection with camera
>> [1] [ALR] [NET] [Mar 13 12:36:00] netcam_start: Network Camera thread
>> starting... for url (rtsp://user:pwd@192.168.1.111:554/onvif2)
>> [1] [NTC] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: Using tcp
>> transport
>> [1] [ERR] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: unable to
>> open input(rtsp://user:pwd@192.168.1.111:554/onvif2): Invalid data
>> found when processing input
>>
>> I notice it reports input -1 even though conf file says input 1.
>> Also tried on raspbian Jessie with same result.
>>
>>
>> ------------------------------------------------------------------------------
>> Announcing the Oxford Dictionaries API! The API offers world-renowned
>> dictionary content that is easy and intuitive to access. Sign up for an
>> account today to start using our lexical data to power your apps and
>> projects. Get started today and enter our developer competition.
>> http://sdm.link/oxford
>> _______________________________________________
>> 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
>>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> 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
>
------------------------------
Message: 4
Date: Mon, 13 Mar 2017 17:15:52 +1100
From: Robert Brown <rebr...@exemail.com.au>
Subject: [Motion-user] Fwd: Re: Can't connect to rtsp feed
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID: <6f9a4d63-a03c-2da6-4fd5-f3b2f2a1d...@exemail.com.au>
Content-Type: text/plain; charset="windows-1252"
In case it is helpful nmap shows that port 80 is not open:
Nmap scan report for 192.168.1.111
Host is up (0.021s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
23/tcp open telnet
554/tcp open rtsp
5000/tcp open upnp
MAC Address: E0:B9:4D:91:8D:81 (Unknown)
and ffplay tells us:
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc 53. 3.100 / 53. 3.100
[h264 @ 0x7ff4b8000d20] RTP: missed 67 packets0KB sq= 0B f=0/0
Input #0, rtsp, from 'rtsp://usr:pwd@192.168.1.111:554/onvif2':
Metadata:
title : H.264 Video, RtspServer_0.0.0.2
Duration: N/A, start: 1.649333, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuv420p, 320x240, 15 fps, 15.15
tbr, 90k tbn, 30 tbc
32.35 M-V: 0.009 fd= 5 aq= 0KB vq= 28KB sq= 0B f=1/1
-------- Forwarded Message --------
Subject: Re: [Motion-user] Can't connect to rtsp feed
Date: Mon, 13 Mar 2017 16:28:54 +1100
From: Robert Brown <rebr...@exemail.com.au>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Yes the ffplay command and vlc both work fine.
The camera is Digoo M1Q:
http://www.mydigoo.com/Digoo-DG-M1Q-960P-2_8mm-Wireless-Mini-WIFI-Night-Vision-Smart-Home-Security-IP-Camera-Onvif-Monitor-p-38.html
Thanks
On 13/03/17 16:18, MrDave wrote:
> Does "ffplay rtsp://user:pwd@192.168.1.111:554/onvif2" work?
>
> What kind of camera is it?
>
>
> On 3/12/2017 8:06 PM, Robert Brown wrote:
>> Running 3.4.1 on Ubuntu 16.04 after trying the 3.2.12 default version.
>> VLC command works:
>> rtsp://user:pwd@192.168.1.111/onvif2
>> Log looks like:
>> [0] [NTC] [ALL] [Mar 13 12:35:51] motion_startup: Using log type (ALL)
>> log level (NTC)
>> [0] [NTC] [ENC] [Mar 13 12:35:51] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD
>> 3670272 LIBAVFORMAT_BUILD 3670272
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is from
>> /etc/motion/motion.conf
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Thread 1 is device:
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Stream port 554
>> [0] [NTC] [ALL] [Mar 13 12:35:51] main: Waiting for threads to finish,
>> pid: 18218
>> [1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Thread 1 started , motion
>> detection Enabled
>> [1] [ALR] [NET] [Mar 13 12:35:51] netcam_start: Network Camera thread
>> starting... for url (rtsp://user:pwd@192.168.1.111:554/onvif2)
>> [1] [NTC] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: Using tcp
>> transport
>> [1] [ERR] [NET] [Mar 13 12:35:51] netcam_rtsp_open_context: unable to
>> open input(rtsp://user:pwd@192.168.1.111:554/onvif2): Invalid data
>> found
>> when processing input
>> [1] [WRN] [ALL] [Mar 13 12:35:51] motion_init: Could not fetch initial
>> image from camera Motion continues using width and height from config
>> file(s)
>> [1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
>> pre_capture buffer to 1 items
>> [1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream testing :
>> IPV4 addr: 0.0.0.0 port: 554
>> [1] [NTC] [STR] [Mar 13 12:35:51] http_bindsock: motion-stream Bound :
>> IPV4 addr: 0.0.0.0 port: 554
>> [1] [NTC] [ALL] [Mar 13 12:35:51] motion_init: Started motion-stream
>> server in port 554 auth Disabled
>> [1] [NTC] [ALL] [Mar 13 12:35:51] image_ring_resize: Resizing
>> pre_capture buffer to 3 items
>> [1] [WRN] [ALL] [Mar 13 12:36:00] motion_loop: Retrying until successful
>> connection with camera
>> [1] [ALR] [NET] [Mar 13 12:36:00] netcam_start: Network Camera thread
>> starting... for url (rtsp://user:pwd@192.168.1.111:554/onvif2)
>> [1] [NTC] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: Using tcp
>> transport
>> [1] [ERR] [NET] [Mar 13 12:36:00] netcam_rtsp_open_context: unable to
>> open input(rtsp://user:pwd@192.168.1.111:554/onvif2): Invalid data
>> found when processing input
>>
>> I notice it reports input -1 even though conf file says input 1.
>> Also tried on raspbian Jessie with same result.
>>
>>
>> ------------------------------------------------------------------------------
>> Announcing the Oxford Dictionaries API! The API offers world-renowned
>> dictionary content that is easy and intuitive to access. Sign up for an
>> account today to start using our lexical data to power your apps and
>> projects. Get started today and enter our developer competition.
>> http://sdm.link/oxford
>> _______________________________________________
>> 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
>>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> 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...
------------------------------
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
------------------------------
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 130, Issue 9
*******************************************
