[gstreamer-bugs] [Bug 321532] New: Support device setting in cdda:// URI

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=321532
 GStreamer | gst-plugins-good | Ver: 0.9.x

           Summary: Support device setting in cdda:// URI
           Product: GStreamer
           Version: 0.9.x
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: abockover at novell.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: all-bugs at bugzilla.gnome.org


In GStreamer 0.8, if an application uses the playbin element and wishes to play
an audio CD from the non-default drive, the application must handle the
notify::source event to set the device on the underlying cddasrc/cdparanoia element.

For 0.9, it would be nice for playbin or the underlying source element to handle
this by way of the cdda:// URI. 

In Banshee, I am using the cdda://<track_num>#<device_node> scheme only because
it is possible to pass this entire URI to the source, and it will ignore the #
and anything after, which means the original URI does not need to be truncated.
I then just extract <device_node> and set the device.

However, for the sake of being new and clean, I think the following URI scheme
makes most sense, if you think audio tracks as files or directories on the CD:

cdda://<device_node>/<track_number> 

RhythmBox currently uses cdda://<device_node>:<track_number>. 

So, possible schemes:

[1] cdda://8#/dev/hdc
[2] cdda:///dev/hdc:8
[3] cdda:///dev/hdc/8

Ultimately, the scheme doesn't matter *too* much, so long as this support is in
some level of GStreamer, and not the consuming application, but there's no
reason not to make it clean and semantic, which I think goes to [3].

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.