On Fri, 2007-04-27 at 09:15 +0200, Sebastian Dröge wrote: > Am Donnerstag, den 26.04.2007, 20:09 -0700 schrieb Joe Wreschnig: > I agree that the fix for this bug was not at all complete and this special > case should be handled too. Is "file://" the only URL that causes a problem > for > you or is quodlibet using "file://blabla/bla" in general? (note that there > are only > two slashes after the colon)
> "file://" is not a valid URI, it's only the protocol part of some URI. Then > according > to rfc1738 "file://blabla/bla" corresponds to the location "/bla" on the host > "blabla". Yes, I know; "http://"; is also not a valid URL, but it's what I was told in #gstreamer to use to check for generic HTTP support (whether via gnomevfs or neon), so I assumed that "file://" was similar. Quod Libet hands correctly formed URIs to the playbin to play actual files. > Then, if quodlibet wants to check for the element "filesrc" it should just > check if it > can create a "filesrc" element and not check if there is some random element > that might > support the "file://" protocol. Actually I don't care if there's a filesrc element, I just care if something supports file://. But the error message mentions filesrc because users have no idea what "Get an element that supports file://" means; they have a better idea what "Install filesrc" means, and this has helped people diagnose a lot of broken GStreamer installations in the past. > Apart from that, would you be fine if I just special case "file://" and allow > that as > a valid URI for filesrc as a workaround for this? Yes. -- Joe Wreschnig <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
