Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program

Bug #58537 reported by Jeremy LaCroix
10
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: amarok

Not a huge issue, but it is kind of annoying when trying to free your sound card for something else. When you are playing an MP3 in Amarok, and you want to stop, righclick the taskbar icon and choose "quite" the program exits but the sound is still playing for about 30 seconds after it exits.

Revision history for this message
John (john.e) wrote :

Aren't you using fade in / fade out ?

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote : Re: [Bug 58537] Re: Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program

No, I am not using crossfade.

On Saturday September 02 2006 1:47 pm, John wrote:
> Aren't you using fade in / fade out ?

Revision history for this message
thewbman (thewbman) wrote :

Same problem here. Running without any crossfade with xine-alsa. Using xinerama if that matters (unlikely).

Revision history for this message
Andrew Ash (ash211) wrote :

Is this still a problem on edgy?

Changed in amarok:
status: Unconfirmed → Needs Info
Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

Yes.

On November 11 2006 5:20 pm, Andrew Ash wrote:
> Is this still a problem on edgy?
>
> ** Changed in: amarok (Ubuntu)
> Status: Unconfirmed => Needs Info

Revision history for this message
Andrew Ash (ash211) wrote :

What database are you using under Configure -> Collection ?

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

It says "Sqlite" and both boxes are checked.

On November 11 2006 5:37 pm, Andrew Ash wrote:
> What database are you using under Configure -> Collection ?

Revision history for this message
Freddy Martinez (freddymartinez9) wrote :

Are you still having this problem? It seems like you are from your comments. Please let me know.

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

Yes, I'm still having this problem.

On Thursday December 21 2006 10:49 pm, Freddy Martinez wrote:
> Are you still having this problem? It seems like you are from your
> comments. Please let me know.

Revision history for this message
Andrew Ash (ash211) wrote :

I'm thinking it might have something to do with the underlying sound system, not necessarily Amarok itself. Does it take 30sec to stop playing a sound file with another music program?

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

With XMMS and music embedded in Konqueror it doesn't take any time at all.

On Thursday December 21 2006 11:12 pm, Andrew Ash wrote:
> I'm thinking it might have something to do with the underlying sound
> system, not necessarily Amarok itself. Does it take 30sec to stop
> playing a sound file with another music program?

Revision history for this message
Joseph Price (pricechild) wrote :

I'm on Feisty with latest amarok: 2:1.4.5-0ubuntu5

I can confirm this bug. It may not take 30 seconds to stop playing, but it takes atleast 10. Probably an exaggeration on the OP's part.

If I have amarok playing and decide to log out or shutdown, gnome will not log out before the sound has stopped playing, something which adds 10 seconds onto the shutdown.

Pricey

Changed in amarok:
status: Needs Info → Confirmed
Revision history for this message
kipeloff (s-boginskis) wrote :

I'm running KDE (Feisty), when I push 'quit on Amarok menu or system tray', Amarok plays song till the song end, then it stops playing.

Revision history for this message
Oliver Wilson (wool-in-silver) wrote :

Same here - vanilla Edgy install, all other sound apps behave normally, amarok keeps playing for 10sec+ after quitting.

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

This problem still happens. Any updates?

Changed in amarok:
importance: Undecided → Low
Revision history for this message
Shardsofmetal (shardsofmetal) wrote :

just to confirm, you have gone into options > playback and unchecked "fadeout on exit", right? that's not the same as crossfade

Revision history for this message
Michael Chang (thenewme91) wrote :

Are you outputting via either ARTS or PulseAudio? (This would likely be under the engine options.)

Both sound systems take about 30 seconds to free up the sound card after all connected applications stop playing sound, although that can be reconfigured.

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

I was just referring to however it is set up out of the box. At least
that's how I use it now. All the other music players I use stop the
sound immediately. Amarok just keeps playing for a while even after the
program was closed.

Michael Chang wrote:
> Are you outputting via either ARTS or PulseAudio? (This would likely be
> under the engine options.)
>
> Both sound systems take about 30 seconds to free up the sound card after
> all connected applications stop playing sound, although that can be
> reconfigured.
>
>

Revision history for this message
Michael Chang (thenewme91) wrote :

At risk of being too technical, Amarok itself doesn't play music. The current version actually calls another application (known as an "engine") to play the music -- and the music playing runs in another thread/process so that when the GUI lags, (which WILL happen due to stupidness in the way X is designed) your music doesn't skip. So, A) it takes time for the "quit" message to get from one application to another, and B) if there's a bug in the configuration of the engine, that would likely cause this behaviour. 30 seconds seems like a lot to me, but perhaps it's just me.

Does upgrading to the Amarok in Hardy or Intrepid fix the issue?

Of course, if the whole "using an engine" is the cause of the bug, then you may want to help with testing of Amarok 2, which uses some new-fangled KDE 4 library to play sound instead.

Oh... and for what it's worth, last I checked, XMMS is no longer being maintained, so if it breaks and there's a bug, there's nobody that can fix it. *shrugs*

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

In Intrepid I still had this problem. Unfortunately, yesterday I
upgraded all the computers to Amarok 2.0 Beta 3 so I no longer use the
original Amarok. I haven't had enough time to play with Amarok 2 to see
if the issue is fixed, unfortunately. But I should be able to soon.

Michael Chang wrote:
> At risk of being too technical, Amarok itself doesn't play music. The
> current version actually calls another application (known as an
> "engine") to play the music -- and the music playing runs in another
> thread/process so that when the GUI lags, (which WILL happen due to
> stupidness in the way X is designed) your music doesn't skip. So, A) it
> takes time for the "quit" message to get from one application to
> another, and B) if there's a bug in the configuration of the engine,
> that would likely cause this behaviour. 30 seconds seems like a lot to
> me, but perhaps it's just me.
>
> Does upgrading to the Amarok in Hardy or Intrepid fix the issue?
>
> Of course, if the whole "using an engine" is the cause of the bug, then
> you may want to help with testing of Amarok 2, which uses some new-
> fangled KDE 4 library to play sound instead.
>
> Oh... and for what it's worth, last I checked, XMMS is no longer being
> maintained, so if it breaks and there's a bug, there's nobody that can
> fix it. *shrugs*
>
>

Revision history for this message
Freddy Martinez (freddymartinez9) wrote :

Does anyone know it it is fixed in Amarok? I am using Amarok 2 in interepid and I do not see this issue anymore. I am not sure about other versions of Ubuntu. Is this fix committed?

Changed in amarok:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Assuming fixed in Amarok 2.

Changed in amarok (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.