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 445764 - Can't fast forward through some tracks
Can't fast forward through some tracks
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: playback
0.10.0
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-09 14:12 UTC by Cory Doctorow
Modified: 2017-07-29 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cory Doctorow 2007-06-09 14:12:36 UTC
Please describe the problem:
I have a smart playlist composed of "tracks with a 4 or 5 star rating that I haven't played in the last 30 days." The best way to remove a track from this playlist is to start playing it, then fast-forward all the way through by moving the cursor to the middle/end of the progress bar and holding the mouse down, so that the track is marked as played. 

Sometimes, after fast-forwarding in this fashion, the pointer that shows how far into the song Rhythmbox is jumps back to near the beginning of the track and Rhythmbox just hangs there until I manually click the next-track button (which doesn't update the last-played time for that track). If I then restart the "stubborn" track and fast-forward through it, the same thing reoccurs. 

If I skip through or fast forward ALL the remaining tracks in the playlist, and THEN restart the stubborn track, I can skip all the way to the end and it will update the last played time.

A track that is stubborn today won't necessarily be stubborn tomorrow. Some are long tracks. Some are short.

Steps to reproduce:
1. Make a smart playlist of tracks above 3-star rating whose last-played time is more than 30 days ago 
2. Start playing the playlist. Skip most songs (by clicking the skip track button). 
3. For some tracks, try fast-forwarding through them (by holding your mouse down in the progress-bar, to the right of the progress-cursor, until the progress-cursor is all the way to the right of the screen)
4. Repeat until you find a "stubborn" track

Actual results:
Some of the tracks will be "stubborn" and not have their last-played fields updated. The play-cursor will jump most of the way to the left. The track will not play. Clicking "skip track" will jump to the next track.

Expected results:
All tracks should have their last-played fields updated and disappear from the playlist.

Does this happen every time?
No.

Other information:
Comment 1 Jonathan Matthew 2007-06-12 13:19:41 UTC
Does this only happen with a particular type of file?  If there's a particular file it's happened with a few times, can you try playing it several times in a row and see how many times this happens?  Can you also try playing any such files in totem to see if seeking works properly there?
Comment 2 Cory Doctorow 2007-06-12 17:47:26 UTC
> Does this only happen with a particular type of file? 

All I have in my library are MP3s, and so all the files it happens with are MP3s.

> If there's a particular
file it's happened with a few times, can you try playing it several times in a
row and see how many times this happens?  Can you also try playing any such
files in totem to see if seeking works properly there?

It's never recurred for any file (that I've noticed). The next time it happens, I'll try playing the file with Totem.

Comment 3 André Klapper 2014-12-02 01:36:32 UTC
Hi Cory. 
Sorry that noone has taken a look at this report yet. 
if you have time, could you please check again whether this issue still happens in Rhythmbox 3.1 or 3.0 and update this report by adding a comment and changing the "Version" field and provide information about your distribution? Thanks a lot.
Comment 4 André Klapper 2017-07-29 15:06:44 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!