Bug 95182 - plays every other song in playlist
Summary: plays every other song in playlist
Status: RESOLVED DUPLICATE of bug 91071
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-15 01:46 UTC by Jessica
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica 2004-12-15 01:46:13 UTC
Version:            (using KDE KDE 3.2.3)
Installed from:    Mandrake RPMs
OS:                Linux

When I create a playlist, amarok plays only every song in the list. For example, I start listening to song 1 and have the playlist open. As song 1 finishes, the playlist highlight briefly appears on song 2 but immediately moves to song 3, which begins playing. I can manually select song 2 by double-clicking it, but as song 2 finishes, the playlist highlight briefly appears on song 3 and then moves right along to song 4, which begins playing. I've even tried programming the songs in order by holding down the control button and right-clicking on the songs. The queue order appears -- correctly -- but still the "even" songs are skipped in the manner described above.

I've tried quitting and restarting the program. I have restarted the computer. I have loaded different playlists. I've tried docking and undocking the player window (xmms vs. iTunes). All to no avail!
Comment 1 Mark Kretschmann 2004-12-15 08:55:55 UTC
This problem is specific to aRts-engine. It has been reported before, so I'm marking this as DUPE. 

We have not yet been able to locate the cause of this bug, but there's also not much work going on in this direction. aRts-engine is basically unmaintained, and we strongly recommend using xine or GStreamer instead. (aRts is obsolete).

Also, please _always_ state the program version you are referring to, thanks.


*** This bug has been marked as a duplicate of 91071 ***