0003402: behavior of the 'seek' command in mpd protocol is inefficient and not intuitive

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0003402

MPD

Commands

public

2011-12-16 07:35

2012-01-12 15:38

Reporter

kazin

Assigned To

cirrus

Priority

low

Severity

feature

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

0.16.x

Target Version

Fixed in Version

git

Summary

0003402: behavior of the 'seek' command in mpd protocol is inefficient and not intuitive

Description

I'm working on a client, and I noticed a curiosity with the 'seek' command. In order to seek, one must provide the playlistID or libraryID of the current track - which requires first using the 'status' command to obtain this.

This is inefficient when I just want to seek in the currently playing song, rather than just sending 'seek +10' I first have to query status, parse it, then send the command with the song number.

I understand that when one already has the track number this is irrelevant, or when one wishes to skip to a different track and seek all at once, the current behavior is good. But in my case, it's wasteful, and as I'm writing a client for mobile applications, this waste is quite relevant.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0006988) cirrus (administrator) 2011-12-24 11:38	Command "seekcur" implemented in git master.

Issue History
Date Modified	Username	Field	Change
2011-12-16 07:35	kazin	New Issue
2011-12-16 07:35	kazin	Status	new => assigned
2011-12-16 07:35	kazin	Assigned To	=> cirrus
2011-12-24 11:38	cirrus	Note Added: 0006988
2011-12-24 11:38	cirrus	Status	assigned => resolved
2011-12-24 11:38	cirrus	Fixed in Version	=> git
2011-12-24 11:38	cirrus	Resolution	open => fixed
2012-01-12 15:38	Avuton Olrich	Status	resolved => closed