[MPRIS] TrackChanged Signal

[Kevin Anthony]

That is true, but some players emit on more then just track change, Banshee
for example also emits PropertiesChanged->Metadata when someone edits the
track info, as it should. So if your just monitoring for when the track
changes, you would have to store the trackid and compare.  Although that
isn't the end of the world, i thought TrackChanged Signal would be useful.

On Wed, Aug 15, 2012 at 5:14 AM, Mirsal Ennaime <mirsal at videolan.org> wrote:

> Hi Kevin,
>
> On Tue, 2012-08-14 at 17:23 -0400, Kevin Anthony wrote:
> > I think it's useful for the player to emit a signal when the track is
> > changed. An example of this being useful is your querying the player's
> > metadata and displaying it on a LCD screen.  This prevents you from
> having
> > to query the metadata contently, you simply listen for the signal and
> when
> > you hear it, re-query the metadata.
>
> It is useful indeed, and it's already there[1] !
>
> Players must emit the org.freedesktop.DBus.Properties.PropertiesChanged
> signal
> when the Metadata property changes, so track changes can be detected using
> the mpris:trackid attribute.
>
> Whether the current way is too convoluted or not clear enough can still
> be discussed though :)
>
>
> [1]
> http://specifications.freedesktop.org/mpris-spec/2.2/Player_Node.html#Property:Metadata
>
>
> Best,
> --
> mirsal
>
> _______________________________________________
> MPRIS mailing list
> MPRIS at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mpris
>
>


-- 
Thanks
Kevin Anthony
www.NoSideRacing.com

Do you use Banshee?
Download the Community Extensions:
http://banshee.fm/download/extensions/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mpris/attachments/20120815/83dad5ff/attachment.html>