Remember the last-played track in the playlist view across invocations of cmus

[philc]

I restart cmus multiple times per day because it hangs, stops playing through my sound card, or because of normal reboots due to OSX system updates. I have a very long playlist of ambient background music I listen to at work and have to manually find where I left off and resume playing each time I restart cmus.

It would be nice if cmus remembered its cursor position in the playlist view.

cmus --version
cmus v2.7.1

[jareksprysz]

Try this: in cmus just write:

:set resume=true

[philc]

@jareksprysz The resume option resumes playback of the last-playing song. What I'm instead looking for is for the cursor position in the playlist to be saved. With resume=true, after cmus starts, once the resumed song finishes playing, the first song in the playlist is played rather than the song in the playlist which is after the currently playing song.

An artifact of this is that in the playlist view, the song that resumes playing after a cmus restart is not highlighted in yellow.

[forthrin]

@jareksprysz: I would also like this feature. I too have to restart cmus occasionally because it hangs (see #771) or because of occasional severe distortion when using eqMac2 (resolves when restarting cmus). Regardless it's a good idea to remember your position rather than always starting at first artist/album in the alphabet, which is rather arbitrary.

[maiermic]

It already works to resume playing the library (see resume_load). I suppose we need something like resume.pl_index that works kind of similar to resume.lib_filename for the playlist.

[aksh1618]

+1 for this feature request. I'd also like this feature, as I use a playlist for recently added tracks and would like it to be resumable.

[emilBeBri]

+1 here, would be awesome

[carlwarnick]

+1 also would like this

[ebpetway]

It appears that this functionality works now with :set resume=true.

[mathieu-lemay]

@ebpetway That option has been present for a long time. It doesn't fix this current issue. See #729 (comment)

[ebpetway]

@ebpetway That option has been present for a long time. It doesn't fix this current issue. See #729 (comment)

Ah, I misunderstood the thread. 👍