[gst-devel] Could not close resource error when using gnomevfssrc with ftp
Tim-Philipp Müller
t.i.m at zen.co.uk
Tue Apr 20 11:54:10 CEST 2010
On Mon, 2010-04-19 at 22:35 -0300, Tiago Katcipis wrote:
> using a public ftp i run this:
> gst-launch -v gnomevfssrc
> location=ftp://194.44.214.3/pub/music/Collection/ArtofNoise.mp3 !
> queue ! decodebin ! fakesink
>
> and it works ok, the ftp is really slow...it takes a good time before
> it starts to download and decode....but works
>
> even if i try:
> gst-launch -v gnomevfssrc
> location=ftp://194.44.214.3/pub/music/Collection/ArtofNoise.mp3 !
> queue ! decodebin ! alsasink
>
> i can hear the music (it takes a while to go from paused to playing,
> something like 20-30 seconds....but if you wait it wil happen).
>
> 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
More information about the gstreamer-devel
mailing list