GNOME Bugzilla – Bug 711486
Not able to play rtsp stream with 1.2.0 under windows
Last modified: 2013-11-05 13:57:23 UTC
Switching from 1.0.10 to 1.2.0 the following command does not longer work: D:\gstreamer\1.0\x86\bin>gst-launch-1.0.exe -m playbin uri=rtsp://127.0.0.1:8554 Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Got message #0 from element "streamsynchronizer0" (state-changed): GstMessageSta teChanged, old-state=(GstState)GST_STATE_NULL, new-state=(GstState)GST_STATE_REA DY, pending-state=(GstState)GST_STATE_VOID_PENDING; Got message #1 from element "playsink" (state-changed): GstMessageStateChanged, old-state=(GstState)GST_STATE_NULL, new-state=(GstState)GST_STATE_READY, pending -state=(GstState)GST_STATE_VOID_PENDING; Got message #2 from element "playbin0" (state-changed): GstMessageStateChanged, old-state=(GstState)GST_STATE_NULL, new-state=(GstState)GST_STATE_READY, pending -state=(GstState)GST_STATE_PAUSED; Got message #3 from element "uridecodebin0" (state-changed): GstMessageStateChan ged, old-state=(GstState)GST_STATE_NULL, new-state=(GstState)GST_STATE_READY, pe nding-state=(GstState)GST_STATE_VOID_PENDING; Got message #6 from element "streamsynchronizer0" (state-changed): GstMessageSta teChanged, old-state=(GstState)GST_STATE_READY, new-state=(GstState)GST_STATE_PA USED, pending-state=(GstState)GST_STATE_VOID_PENDING; Got message #7 from element "source" (state-changed): GstMessageStateChanged, ol d-state=(GstState)GST_STATE_NULL, new-state=(GstState)GST_STATE_READY, pending-s tate=(GstState)GST_STATE_PAUSED; Got message #8 from element "source" (progress): GstMessageProgress, type=(GstPr ogressType)GST_PROGRESS_TYPE_START, code=(string)open, text=(string)"Opening\ St ream", percent=(int)0, timeout=(int)-1; Progress: (open) Opening Stream Got message #9 from element "source" (state-changed): GstMessageStateChanged, ol d-state=(GstState)GST_STATE_READY, new-state=(GstState)GST_STATE_PAUSED, pending -state=(GstState)GST_STATE_VOID_PENDING; Got message #10 from element "uridecodebin0" (state-changed): GstMessageStateCha nged, old-state=(GstState)GST_STATE_READY, new-state=(GstState)GST_STATE_PAUSED, pending-state=(GstState)GST_STATE_VOID_PENDING; Got message #11 from element "playbin0" (state-changed): GstMessageStateChanged, old-state=(GstState)GST_STATE_READY, new-state=(GstState)GST_STATE_PAUSED, pend ing-state=(GstState)GST_STATE_VOID_PENDING; Got message #12 from element "source" (progress): GstMessageProgress, type=(GstP rogressType)GST_PROGRESS_TYPE_CONTINUE, code=(string)connect, text=(string)"Conn ecting\ to\ rtsp://127.0.0.1:8554", percent=(int)0, timeout=(int)-1; Progress: (connect) Connecting to rtsp://127.0.0.1:8554 Got message #13 from element "source" (progress): GstMessageProgress, type=(GstP rogressType)GST_PROGRESS_TYPE_CONTINUE, code=(string)open, text=(string)"Retriev ing\ server\ options", percent=(int)0, timeout=(int)-1; Progress: (open) Retrieving server options Got message #14 from element "source" (progress): GstMessageProgress, type=(GstP rogressType)GST_PROGRESS_TYPE_CONTINUE, code=(string)open, text=(string)"Retriev ing\ media\ info", percent=(int)0, timeout=(int)-1; Progress: (open) Retrieving media info Got message #15 from element "source" (error): GstMessageError, gerror=(GError)N ULL, debug=(string)"gstrtspsrc.c\(5065\):\ gst_rtspsrc_send\ \(\):\ /GstPlayBin: playbin0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source:\012Not\ found"; ERROR: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstRTSPSr c:source: Resource not found. Additional debug info: gstrtspsrc.c(5065): gst_rtspsrc_send (): /GstPlayBin:playbin0/GstURIDecodeBin:ur idecodebin0/GstRTSPSrc:source: Not found ERROR: pipeline doesn't want to preroll. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ... With 1.0.10 it is working fine
What's the server you're using? Does it work if you use rtsp://127.0.0.1:8554/ (note the extra / at the end)? I remember a change around that
It is working by using rtsp://127.0.0.1:8554/ Thanks
This was the commit in question that changed this behaviour: commit 9a78542ded27461b70c5b2eb835ef2ed16da32f8 Author: Thomas Scheuermann <Thomas.Scheuermann@barco.com> Date: Mon Apr 8 09:09:33 2013 +0200 rtsp: Don't use / as path if no path was provided RTSP does not mandate that a non-zero-length path is used and some devices (e.g. IQinVision IQeye 1080p) requires that a zero-length path is used.