[Bug 643625] g_warning from filesrc ! decodebin

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=643625
  GStreamer | gstreamer (core) | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|                            |OBSOLETE
   Target Milestone|HEAD                        |NONE

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2011-03-02 00:17:14 UTC ---
Fixed by this I believe:


commit 1f59906ec1a20645b1c299e835fa2d14c197b5eb
Author: Tim-Philipp Müller <tim.muller at collabora.co.uk>
Date:   Thu Feb 24 15:32:00 2011 +0000

    filesrc, filesink: fix URI creation regression for non-absolute locations

    Passing e.g. location=foo would lead to warnings because
g_filename_to_uri()
    wants an absolute file path and returns NULL otherwise. Use brand-new
    gst_filename_to_uri() instead, which will try harder to create a proper
    URI for us.

    Also add unit test.

commit 27027a2dd2c57d088e2a8b8d71c7526cf8083787
Author: Tim-Philipp Müller <tim.muller at collabora.co.uk>
Date:   Thu Feb 24 15:18:43 2011 +0000

    uri: add gst_filename_to_uri() that takes relative filenames

    Add function that (unlike the GLib equivalent) also accepts paths that
    aren't absolute and will clean up relative markers such as ./ and ../
    before forming a URI.

    Fixes warnings with e.g. filesrc location=foo ! typefind caused by the
    recent switch to g_filename_to_uri(), but also actually creates valid
    URIs for the first time.

    Windows code paths could need some more work, e.g. we don't clean up
    the relative markers there for now (because path could have \ and /
    as separators).

    API: gst_filename_to_uri()

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.