Closed sslneve closed 4 years ago
When you try the debug instructions for that feed with omxplayer, what happens?
On Tue, Jun 30, 2020, 6:48 PM sslneve notifications@github.com wrote:
The URL of the feed in the layout.conf.default is
"http://192.168.1.174/videostream.cgi?user=xxxx&pwd=xxxx"
This works in the browser but stays dark with displaycameras/omxplayer. For another camera model, exactly this URL (different IP of course) does work with displaycameras.
Console output (feed is named "Chicken"):
Starting omxplayer for Chicken Waiting for Chicken omxplayer startup 0 Waiting for Chicken omxplayer startup 1 Waiting for Chicken omxplayer startup 2 Waiting for Chicken omxplayer startup 3 Waiting for Chicken omxplayer startup 4 Waiting for Chicken omxplayer startup 5 Chicken failed playback Running a repair on failed feeds. Starting omxplayer for Chicken Waiting for Chicken omxplayer startup 0 Waiting for Chicken omxplayer startup 1 Waiting for Chicken omxplayer startup 2 Waiting for Chicken omxplayer startup 3 Waiting for Chicken omxplayer startup 4 Waiting for Chicken omxplayer startup 5 Chicken failed playback
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Anonymousdog/displaycameras/issues/57, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIYIKNZNOUUGQS65FL6T63RZJTURANCNFSM4OMZZTAA .
pi@openWB:~ $ sudo omxplayer --no-keys --no-osd --avdict rtsp_transport:tcp http://user:pwd@192.168.1.176/videostream.cgi --live -n -1 --timeout 30 Video codec omx-mjpeg width 640 height 480 profile 192 fps 25.000000 Subtitle count: 0, state: off, index: 1, delay: 0
.. but there should be another line after this like:
V:PortSettingsChanged: 640x480@25.00 interlace:0 deinterlace:0 anaglyph:0 par:1.00 display:0 layer:0 alpha:255 aspectMode:0
which just does not appear.
Try it without rearranging your URL from the first email.
On Fri, Jul 10, 2020, 11:38 AM sslneve notifications@github.com wrote:
pi@openWB:~ $ sudo omxplayer --no-keys --no-osd --avdict rtsp_transport:tcp http://user:pwd@192.168.1.176/videostream.cgi --live -n -1 --timeout 30 Video codec omx-mjpeg width 640 height 480 profile 192 fps 25.000000 Subtitle count: 0, state: off, index: 1, delay: 0
.. but there should be another line after this like:
V:PortSettingsChanged: 640x480@25.00 interlace:0 deinterlace:0 anaglyph:0 par:1.00 display:0 layer:0 alpha:255 aspectMode:0
which just does not appear.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Anonymousdog/displaycameras/issues/57#issuecomment-656740437, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIYIKPON46UFAFWIW3KBDDR24YXNANCNFSM4OMZZTAA .
Sorry, the IP has changed to .176
If I use the previous format, I get an unauthorized (only by adding the -i parameter):
pi@openWB:~ $ sudo omxplayer -i --no-keys --no-osd --avdict rtsp_transport:tcp http://192.168.1.176/videostream.cgi?user=xxx%26pwd=xxx --live -n -1 --timeout 30 [http @ 0x16aaa00] HTTP error 401 Unauthorized have a nice day ;)
I had to URL-encode the "&" as otherwise it doesn't work at all.
Not sure how to proceed from here. Omxplayer had to be able to play the feed for it to work within the displaycamerad package.
Andy
On Fri, Jul 10, 2020, 11:54 AM sslneve notifications@github.com wrote:
Sorry, the IP has changed to .176
If I use the previous format, I get an unauthorized (only by adding the -i parameter):
pi@openWB:~ $ sudo omxplayer -i --no-keys --no-osd --avdict rtsp_transport:tcp http://192.168.1.176/videostream.cgi?user=xxx%26pwd=xxx --live -n -1 --timeout 30 [http @ 0x16aaa00] HTTP error 401 Unauthorized have a nice day ;)
I had to URL-encode the "&" as otherwise it doesn't work at all.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Anonymousdog/displaycameras/issues/57#issuecomment-656748936, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIYIKLLQWQEUEPRBMITUHDR242UDANCNFSM4OMZZTAA .
Yeah ... probably some incompatibility between cheap China crap camera and omxplayer...
The URL of the feed in the layout.conf.default is
"http://192.168.1.174/videostream.cgi?user=xxxx&pwd=xxxx"
This works in the browser but stays dark with displaycameras/omxplayer. For another camera model, exactly this URL (different IP of course) does work with displaycameras.
Console output (feed is named "Chicken"):
Starting omxplayer for Chicken Waiting for Chicken omxplayer startup 0 Waiting for Chicken omxplayer startup 1 Waiting for Chicken omxplayer startup 2 Waiting for Chicken omxplayer startup 3 Waiting for Chicken omxplayer startup 4 Waiting for Chicken omxplayer startup 5 Chicken failed playback Running a repair on failed feeds. Starting omxplayer for Chicken Waiting for Chicken omxplayer startup 0 Waiting for Chicken omxplayer startup 1 Waiting for Chicken omxplayer startup 2 Waiting for Chicken omxplayer startup 3 Waiting for Chicken omxplayer startup 4 Waiting for Chicken omxplayer startup 5 Chicken failed playback