After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 440628 - Banshee should emit a signal on DBus whenever the song changes
Banshee should emit a signal on DBus whenever the song changes
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: 2.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-23 05:13 UTC by Will Farrington
Modified: 2010-09-15 20:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Will Farrington 2007-05-23 05:13:24 UTC
Currently, whenever a track changes, libnotify pops up and that's the end of that.

What I'm requesting is for a DBus Signal to be emitted too (like Rhythmbox).

The logic behind this is that it enables, for example, Xchat scripts to automatically broadcast the songs playing in Banshee, or would allow someone to write a plugin for Gaim to broadcast Banshee's music in the Status Message.
Comment 1 Josiah Ritchie - flickerfly 2007-08-23 03:27:40 UTC
Please specify the latest version of banshee you have been able to test this against or let us know that this is no longer a problem. Thank you for helping us keep track of your bug.
Comment 2 Andrew Conkling 2008-02-16 04:23:37 UTC
I think this happens now?
Comment 3 herd 2008-04-20 15:08:21 UTC
I can confirm that Banshee 0.13.1 does not emit any signals on the dbus.
Required would be:
void TrackChange();
void StateChange();
clients would no longer need to poll the interface,
resulting in better energy savings with paused playback and during play.
Comment 4 Bertrand Lorentz 2010-09-15 20:46:38 UTC
This should not be provided by the new MPRIS extension, which implements the new MPRIS v2 specification :
http://www.mpris.org/2.0/spec/

It uses the standard PropertiesChanged signal, which is fired when the current track changes, amongst others cases. You can then determine that the Metadata property has changed, and what the new value is.