Difference between revisions of "DBus-spec"

From VideoLAN Wiki
Jump to navigation Jump to search
Line 75: Line 75:
  
 
"Metadata" is data that the files carry within themselves as a means of self-identification (commonly known as "tags"), or data that has been retrieved about the files trough other means, e.g. an internet service that provides additional data about particular media files.
 
"Metadata" is data that the files carry within themselves as a means of self-identification (commonly known as "tags"), or data that has been retrieved about the files trough other means, e.g. an internet service that provides additional data about particular media files.
 +
"Metadata" is an array of dict entries, like ("Length", 1), ("Name", "Bolero"), ("vcodec", "DIVX"). The dict entry is in the form (string, variant) eg: {sv}.
  
 
Furthermore, "Metadata" can be split into two categories:
 
Furthermore, "Metadata" can be split into two categories:
  
1) Technical metadata: ( to be implemented with a struct )
+
1) Technical metadata:
* URI (string)
+
* "URI":"s"
* Length
+
* "length":"i" (length in seconds)
* video codec (fourcc, 4 characters)
+
* "vcodec":"s" (video codec as a fourcc)
* audio codec (fourcc, 4 characters)
+
* "acodec":"s" (audio codec as a fourcc)
* video bitrate
+
* "vb":"i" video bitrate
* audio bitrate
+
* "ab":"i" audio bitrate
* audio samplerate
+
* "as":"i" (audio samplerate)
  
2) Informational metadata ( to be implemented as an array of dict entries (string, string) )
+
2) Informational metadata
* "Name"
+
* "name":"s"
* "Artist"
+
* "artist":"s"
* "Album"
+
* "album":"s"
* "UID" : Unique Identifier as on http://musicbrainz.org
+
* "uid":"s" : Unique Identifier as on http://musicbrainz.org
* "Genre"
+
* "genre":"s"
* (This is extensible)
+
 
 +
 
 +
Required fields are:
 +
"URI", "length", "name"
  
 
= D-Bus =
 
= D-Bus =

Revision as of 14:36, 5 December 2006

Specification for a Common, Desktop neutral, Media Player D-Bus interface

THIS IS A DRAFT

VLC DOES NOT USE THAT AT THIS MOMENT ALTHOUGH IT IS PLANNED

What follows has been largely stolen from http://bmpx.beep-media-player.org/site/MPRIS_Interfacing_Specification

This is an attempt to create a specification for media players to use, for YOUR applications to be able to interact with ANY Media Player YOU want to use on ANY desktop YOU want to use.

This is in the spirit of http://www.freedesktop.org and uses code and ideas from this project, most notably D-Bus : http://dbus.freedesktop.org and uses ideas from http://www.musicbrainz.org

Other players

How other "Media Players" interact with D-Bus

bmpx

http://bmpx.beep-media-player.org/site/MPRIS_Interfacing_Specification

banshee

http://cvs.gnome.org/viewcvs/*checkout*/banshee/src/Banshee.Base/DBusPlayer.cs

rhythmbox

http://cvs.gnome.org/viewcvs/rhythmbox/remote/dbus/rb-client.c?view=markup

muine

http://cvs.gnome.org/viewcvs/muine/DBusLib/Player.cs?view=markup

amarok

http://amarok.kde.org/wiki/DCOP_Functions (D-Bus will replace dcop in kde4 ?)

Definitions

"Media Player"

An application, either with GUI or GUI-less (or which allows for both modes of operation) which is capable of playing back audio/video streams. The means by which it does accomplish that (e.g. which audio backend to use, and which output method) is out of the scope of this document.



The "Media Player" must:

  • Be able to play back at least local storage file streams.
  • Be able to play back at least one stream at a time.

The "Media Player" can, but does not need to:

  • Be capable of holding one or more "Tracklists" at a time.

"Client"

The Client is an unspecified application that will interact with the "Media Player" using D-Bus protocol. For example:

  • A softphone, that pauses, or step the volume down, when a call is being received.
  • An applet that nicely integrates in your desktop environment, to control your "Media Player".
  • An instant messaging client which informs your buddies of what you're listening to.
  • A monitor that stores in a database what you are listening to, for statistics purpose.
  • A video editing software that calls an external "Media Player" to preview your work.

"Tracklist"

A list of media files which resides within the "Media Player", and whose implementation is opaque to the remote interface.

The "Tracklist" must:

  • Hold an ordered list of locations of the media files as URIs (e.g. file:// or http://). The implementation of this can be opaque, which means, it does not neccesarily need to store URIs, but upon remote request, it must be able to return an URI for a given media file.
  • Keep the list in an ordered fashion. The order can be changed at any time trough e.g. sorting algorithms, in which case the "Media Player" must send information about the reordering trough it's remote interface

The "Tracklist" can, but does not need to:

  • Hold "Metadata" about media files

"Metadata"

"Metadata" is data that the files carry within themselves as a means of self-identification (commonly known as "tags"), or data that has been retrieved about the files trough other means, e.g. an internet service that provides additional data about particular media files. "Metadata" is an array of dict entries, like ("Length", 1), ("Name", "Bolero"), ("vcodec", "DIVX"). The dict entry is in the form (string, variant) eg: {sv}.

Furthermore, "Metadata" can be split into two categories:

1) Technical metadata:

  • "URI":"s"
  • "length":"i" (length in seconds)
  • "vcodec":"s" (video codec as a fourcc)
  • "acodec":"s" (audio codec as a fourcc)
  • "vb":"i" video bitrate
  • "ab":"i" audio bitrate
  • "as":"i" (audio samplerate)

2) Informational metadata


Required fields are: "URI", "length", "name"

D-Bus

The Service

org.freedesktop.MediaPlayer

The Object Hierarchy

  • / : Media Player identification
  • /Player : Playback control
  • /TrackList : TrackList management

The Methods

  • /

Identity : Identify the "Media Player" as in "VLC 0.9.0", "bmpx 0.34.9", "Totem 2.16.2" ...

  <method name="Identity">
    <arg type="s" direction="out"/>
  </method>
  • /TrackList

GetMetadata : Gives all meta data available for element at given position in the "TrackList"

 <method name="GetMetadata">
   <arg type="i" direction="in" />
   <arg type="a{sv}" direction="out" />
 </method>

GetCurrentTrack : Position of Current URI in the "TrackList"

  <method name="GetCurrentTrack">
    <arg type="i" direction="out" />
  </method>

GetLength : Number of elements in the "TrackList"

  <method name="GetLength">
    <arg type="i" direction="out" />
  </method>
  • /Player

Next : Goes to the next element (what if we're at the end?)

  <method name="Next">
  </method>

Prev : Goes to the previous element (what if we're at the beginning?)

  <method name="Prev">
  </method>

Pause : If playing : pause. If paused : unpause. If stopped : start playing

  <method name="Pause">
  </method>

Stop : Stop playing.

  <method name="Stop">
  </method>

Play : If playing : rewind to the beginning of current track, else : start playing.

  <method name="Play">
  </method>

GetStatus : Return the status of "Media Player": 0 = Playing, 1 = Paused, 2 = Stopped.

  <method name="GetStatus">
  <arg type="i" direction="out"/>
  </method>

VolumeSet : Sets the volume (argument must be in [0;100])

  <method name="VolumeSet">
  <arg type="i"/>
  </method>

VolumeGet : Returns the current volume (must be in [0;100])

  <method name="VolumeGet">
  <arg type="i" direction="out"/>
  </method>

PositionSet : Sets the playing position (argument must be in [0;100])

  <method name="PositionSet">
  <arg type="i"/>
  </method>

PositionGet : Returns the playing position (must be in [0;100])

  <method name="PositionGet">
  <arg type="i" direction="out"/>
  </method>

Quit : Makes the "Media Player" exit.

  <method name="Quit">
  </method>

The signals

TrackChange : Signal is emitted when the "Media Player" plays another "Track"

  <signal name="TrackChange">
  </signal>

StatusChange : Signal is emitted when status change. See GetStatus.

  <signal name="StatusChange">
   <arg type="i"/>
  </signal>