[gst-devel] Could not close resource error when using gnomevfssrc with ftp

[Kulecz, Walter (JSC-SK)[WYLE INTEG. SCI. & ENG.]]

What is the proper source to use for a "netcam" that produces an MJPEG stream?

http://x.y.z.n/video.cgi delivers a MJPEG image stream.

This works in Firefox with NoScript blocking x.y.z.n by default, so its not 
using any client side code in the browser.


I've tried the following:

gst-launch giosrc location=http://192.168.1.100/video.cgi ! xvimagesink

Which gives:

(gst-launch-0.10:3359): GLib-WARNING **: g_set_prgname() called multiple times
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 227460 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...


AND:
gst-launch playbin2 uri=http://192.168.1.100/video.cgi ! queue ! jpegdec ! xvimagesink

Which gives:

(gst-launch-0.10:3375): GLib-WARNING **: g_set_prgname() called multiple times
WARNING: erroneous pipeline: could not link playbin20 to queue0
Ubuntu910:~/gst-learn$ gst-launch playbin2 uri=http://192.168.1.100/video.cgi ! xvimagesink
(gst-launch-0.10:3395): GLib-WARNING **: g_set_prgname() called multiple times
WARNING: erroneous pipeline: could not link playbin20 to xvimagesink0



Ubuntu 9.10 uses gstreamer-0.10.25.
This is a low priority for me, but if I knew it worked it could be useful for me as
a video source to experiment with gstreamer on Windows XP.

________________________________________
From: Tim-Philipp Müller [t.i.m at zen.co.uk]
Sent: Tuesday, April 20, 2010 4:54 AM
To: gstreamer-devel at lists.sourceforge.net
Subject: Re: [gst-devel] Could not close resource error when using gnomevfssrc with ftp
----------------- stuff deleted ------------------------------------------

> But if i take the queue element out:
> gst-launch -v gnomevfssrc
> location=ftp://194.44.214.3/pub/music/Collection/ArtofNoise.mp3 !
> decodebin ! fakesink
>
> the pipe stays blocked for ever (on both cases)... is this behavior
> expected? have anyone faced something like that? is a good policy to
> always put a queue after a gnomevfssrc?

If there's no queue between the source and the decoder/parser, then
gnomevfssrc may be activated in pull mode if gnomevfssrc thinks it can
seek in the resource it opened. I don't think this ever worked
particularly well. "ftp" should probably be in the blacklist of
protocols that shouldn't operate in pull mode, like http is already.

But in any case, you should really use giosrc instead. gnomevfs and
hence gnomevfssrc are deprecated.

Cheers
 -Tim