Bug 320504 - Amarok stops playback when a track is not playable (but Amarok doesn't know it and doesn't gray it out) with phonon-gstreamer
Summary: Amarok stops playback when a track is not playable (but Amarok doesn't know i...
Status: RESOLVED WORKSFORME
Alias: None
Product: phonon-backend-gstreamer
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.6.3
Platform: Other Linux
: NOR minor
Target Milestone: 4.7
Assignee: Rohan Garg
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-05-30 22:43 UTC by Edward
Modified: 2018-10-27 02:48 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backend config (70.86 KB, image/png)
2013-05-31 20:34 UTC, Edward
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Edward 2013-05-30 22:43:21 UTC
The GUI allows a choice between random playback and repeat playback.  These options should not be mutually exclusive; i.e. I should be able to shuffle songs and repeat (random order and repeat when I get to the end of the playlist).

Reproducible: Always
Comment 1 Matěj Laitl 2013-05-30 22:47:33 UTC
(In reply to comment #0)
> I should be able to shuffle songs and repeat (random order and repeat when I get to
> the end of the playlist).

Actually, this is the current behaviour AFAICS, the playback never stops in Random Tracks/Albums mode here. Or did you mean something different?
Comment 2 Edward 2013-05-30 22:50:24 UTC
That's odd... it plays randomly then stops when it has played all the songs for me.  I use the "Random Tracks" mode.
Comment 3 Matěj Laitl 2013-05-30 23:00:29 UTC
I use current git version, perhaps the behaviour changed since then? I don't recall any commit mentioning it. Would you be able to use development version? Howto is at http://blogs.fsfe.org/myriam/2009/09/compiling-amarok-from-git-locally-full-summary/
Comment 4 Edward 2013-05-30 23:04:48 UTC
I was just doing some more testing and I don't think the problem is what I described.. it stops playing for no apparent reason.  I thought it was because it reached the end of the playlist, but it looks like something else.  Is there any way (a log?) to see why it stopped playing?  If I press the Play button, it still won't play until I double click on a song in the playlist.
Comment 5 Matěj Laitl 2013-05-30 23:08:39 UTC
Known problem, workaround is to switch to phonon-vlc, see bug 296100. Thanks for being a very attentive reporter.

*** This bug has been marked as a duplicate of bug 296100 ***
Comment 6 Edward 2013-05-30 23:14:00 UTC
I'm not sure this is the same problem.  More testing has revealed the problem is when it encounters an item in the playlist where the underlying file no longer exists (e.g. if I moved the file to another folder or deleted it.

Would better behaviour be to skip invalid items (i.e. missing files) and continue to the next item in the playlist?
Comment 7 Matěj Laitl 2013-05-30 23:20:11 UTC
(In reply to comment #6)
> Would better behaviour be to skip invalid items (i.e. missing files) and
> continue to the next item in the playlist?

Yes, Amarok should behave like that and does not, this is a bug, I can reproduce with v2.7.0-348-g480ca9f. Thanks again for being attentive.
Comment 8 Matěj Laitl 2013-05-30 23:26:31 UTC
Okay, I've tested it, it happens only with phonon-gstreamer, not with phonon-vlc, which correctly skis to next track. It also is not specific to random play mode. Reassigning to pgst.
Comment 9 Edward 2013-05-31 20:34:11 UTC
(In reply to comment #8)
> Okay, I've tested it, it happens only with phonon-gstreamer, not with
> phonon-vlc, which correctly skis to next track. It also is not specific to
> random play mode. Reassigning to pgst.

I switched to phonon-vlc, but it still just stops when it encounters the invalid track. 
Attaching configuration screenshot.
Comment 10 Edward 2013-05-31 20:34:51 UTC
Created attachment 80223 [details]
Backend config
Comment 11 Myriam Schweingruber 2014-08-10 10:38:30 UTC
Is this still valid with phonon-backend-gstreamer version 4.7.2 or later?
Comment 12 Andrew Crouthamel 2018-09-25 03:55:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Andrew Crouthamel 2018-10-27 02:48:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!