Can't seek with seekbar in Listen & Quod Libet

Bug #657399 reported by ktp on 2010-10-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Panflute
Low
Unassigned

Bug Description

I'm using Panflute 0.6.2 from the PPA in combination with Listen (0.6.5.99) and Quod Libet (2.2.1).
Panflute displays the time progress in the seekbar correctly but I'm not able to skip forward or backwards by dragging the knob of the seekbar.

Paul Kuliniewicz (kuliniew) wrote :

Neither Listen nor Quod Libet provide an interface for seeking within the current song. Panflute 0.7.0 will show the seek bar as disabled when using a player that doesn't support seeking, to provide a visual cue that it won't work.

Changed in panflute:
status: New → Won't Fix
ktp (kari-petersen) wrote :

Quod Libet has an interface for seeking within the current song.
You just have to invoke another instance from the commandline to try that:

quodlibet --seek=[+|-][HH:]MM:SS

Listen music player can also be controlled via commandline:

listen --[rewind|forward]

Although you can't specify the time, it would be nice if a click in the seekbar before or behind the actual position would result in listen skipping forward or backwards.

I tried that with both players and was able to seek/skip within the playing song.
When the song is paused when skipping panflute does not update the position.
When playing the position is updated after a second.

description: updated
Paul Kuliniewicz (kuliniew) wrote :

Oh, ick. That is probably doable then, even though there's a bit of hackery if you don't want to assume the player is in the PATH.

Changed in panflute:
status: Won't Fix → Confirmed
importance: Undecided → Low
ktp (kari-petersen) wrote :

I think they are in the PATH by default. I didn't add them to the path variable and can call them from my home dir. Maybe you could add an option for entering the path in the UI besides an automatic search for the executable. You could also just try to execute and if not found pop up a dialog. Just some guesses ;-)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers