No correct Audacious 3 support

[M4he]

I tried both Audacious 3.2.4 and 3.3-beta2 with CoverGloobus 1.7 Rev 370. "MPRIS 2 Server" plugin within Audacious is activated.

When I choose "Audacious2" within the CoverGloobus settings it displays the current song's name, time, cover and progress correctly. However when another song is played, the name, time and cover always stay the same (from the first song played when CoverGloobus was started). Only the progress bar is updated.

[Alexandr Grigorcea (cahr-gr)]

Hi,

I've just checked with Audacious 3.2.4, the problem is that it is not
sending all required signals, so it is probably an Audacious bug.
I've added into the trunk another plugin, called Audacious3 (you can have
it by installing from bazaar), it uses MPRIS2 interface. With that plugin
song info update works well, but no time updates, because Audacious is not
exposing 'Position' and 'mpris:length' properties via
org.freedesktop.DBus.Properties interface, so it looks like another poor
implementation of MPRIS interface. You can try to report a bug to audacious
devs.

Cheers,
Alexandr

On Wed, Jul 25, 2012 at 11:12 AM, M4he <email address hidden> wrote:

> Public bug reported:
>
> I tried both Audacious 3.2.4 and 3.3-beta2 with CoverGloobus 1.7 Rev
> 370. "MPRIS 2 Server" plugin within Audacious is activated.
>
> When I choose "Audacious2" within the CoverGloobus settings it displays
> the current song's name, time, cover and progress correctly. However
> when another song is played, the name, time and cover always stay the
> same (from the first song played when CoverGloobus was started). Only
> the progress bar is updated.
>
> ** Affects: covergloobus
> Importance: Undecided
> Status: New
>
>
> ** Tags: audacious mpris
>
> ** Summary changed:
>
> - No correct Audacious 3
> + No correct Audacious 3 support
>
> --
> You received this bug notification because you are a member of Gloobus
> Developers, which is the registrant for CoverGloobus.
> https://bugs.launchpad.net/bugs/1028815
>
> Title:
> No correct Audacious 3 support
>
> Status in CoverGloobus:
> New
>
> Bug description:
> I tried both Audacious 3.2.4 and 3.3-beta2 with CoverGloobus 1.7 Rev
> 370. "MPRIS 2 Server" plugin within Audacious is activated.
>
> When I choose "Audacious2" within the CoverGloobus settings it
> displays the current song's name, time, cover and progress correctly.
> However when another song is played, the name, time and cover always
> stay the same (from the first song played when CoverGloobus was
> started). Only the progress bar is updated.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/covergloobus/+bug/1028815/+subscriptions
>

[M4he (mahe)]

Thanks for implementing the Audacious3 plugin!

It works flawlessly now with Audacious 3.3 which correctly implements the MPRIS2 interface now.

[M4he (mahe)]

Sorry to reopen this but I still seem to have issues with Audacious 3.3:

When I set CoverGloobus to hide when player is closed and quit Audacious while playing music, it doesn't reappear when I start Audacious again and all settings of CoverGloobus are reset. Here are the --debug outputs:

before quitting Audacious: http://pastebin.com/v4fDxgeC
after relaunching Audacious: http://pastebin.com/9bUFQa4Q

If the option to hide when player is closed is disabled, the settings don't reset but the time progress bar never updates after relaunching Audacious and the debug output is the same.

Unfortunately I have no clue about this dbus and MPRIS stuff and can't judge whether this is an Audacious or CoverGloobus problem but I'm reporting it here since the Audacious devs claim to have the MPRIS2 implementation fixed with version 3.3

Thanks for your support!

[Alexandr Grigorcea (cahr-gr)]

indeed their implementation looks like being ok now, the problem was that
there was a time gap between audacious start and mpris interface
registration, so CG was reading data when mpris interface was not ready,
fixed that with a timeout, should be ok now (unless some other problems
appear :D ), give it a try

On Sun, Jul 29, 2012 at 1:03 PM, M4he <email address hidden> wrote:

> Sorry to reopen this but I still seem to have issues with Audacious 3.3:
>
> When I set CoverGloobus to hide when player is closed and quit Audacious
> while playing music, it doesn't reappear when I start Audacious again
> and all settings of CoverGloobus are reset. Here are the --debug
> outputs:
>
> before quitting Audacious: http://pastebin.com/v4fDxgeC
> after relaunching Audacious: http://pastebin.com/9bUFQa4Q
>
> If the option to hide when player is closed is disabled, the settings
> don't reset but the time progress bar never updates after relaunching
> Audacious and the debug output is the same.
>
> Unfortunately I have no clue about this dbus and MPRIS stuff and can't
> judge whether this is an Audacious or CoverGloobus problem but I'm
> reporting it here since the Audacious devs claim to have the MPRIS2
> implementation fixed with version 3.3
>
> Thanks for your support!
>
> ** Changed in: covergloobus
> Status: Fix Committed => New
>
> --
> You received this bug notification because you are a member of Gloobus
> Developers, which is the registrant for CoverGloobus.
> https://bugs.launchpad.net/bugs/1028815
>
> Title:
> No correct Audacious 3 support
>
> Status in CoverGloobus:
> New
>
> Bug description:
> I tried both Audacious 3.2.4 and 3.3-beta2 with CoverGloobus 1.7 Rev
> 370. "MPRIS 2 Server" plugin within Audacious is activated.
>
> When I choose "Audacious2" within the CoverGloobus settings it
> displays the current song's name, time, cover and progress correctly.
> However when another song is played, the name, time and cover always
> stay the same (from the first song played when CoverGloobus was
> started). Only the progress bar is updated.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/covergloobus/+bug/1028815/+subscriptions
>

[M4he (mahe)]

Thanks for the update! This seems to fix the reappear problem.

Unfortunately, there are still issues:

1. upon reappearing, the "always on top" option is ignored. It acts more like "stick to desktop" and stays below all other windows until "always on top" is unticked and ticked again.

2. Clicking on the seekbar leads to crash: http://pastebin.com/yezb4jz5

Thanks for your support. Keep up the good work!

[Mancuso (mancuso-lobo)]

Hi, actually I too did the same problem. but I have no idea how to run the above solution (bazaar?), if I could say a place to download the plugin, I would appreciate it greatly!