GNOME Bugzilla – Bug 336190
[gnomevfssink] should accept non-URI filenames as "location"
Last modified: 2006-03-27 16:18:58 UTC
Please describe the problem: Using the attached transcoding script I get the following error: [cschalle@localhost ~]$ ./transcode2oggt diva001_2.avi diva001_2.ogg Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /pipeline0/gnomevfssink0: Could not open vfs file "file:diva001_2.ogg" for writing: Invalid URI. Additional debug info: gstgnomevfssink.c(383): gst_gnome_vfs_sink_open_file (): /pipeline0/gnomevfssink0: system error: Success Setting pipeline to NULL ... FREEING pipeline ... Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 62123 [details] transcode2oggt script
This works fine if I use 'filesink' in the attached script.
Well, those aren't proper URIs and gnomevfs{src|sink} only really accept URIs. However, given that gnomevfssrc actually seems to accept non-URI filepaths as well (like filesrc/filesink) it seems a good idea to make gnomevfssink do the same just for the sake of consistency: 2006-03-27 Tim-Philipp Müller <tim at centricular dot net> * ext/gnomevfs/gstgnomevfs.c: (gst_gnome_vfs_location_to_uri_string): * ext/gnomevfs/gstgnomevfs.h: * ext/gnomevfs/gstgnomevfssink.c: (gst_gnome_vfs_sink_set_property): * ext/gnomevfs/gstgnomevfssrc.c: (gst_gnome_vfs_src_set_property): Make gnomevfssink accept filenames as well as URIs for the "location" property, just like gnomevfssrc does (and filesrc/filesink do) (#336190).