Bugzilla – Bug 1911
More ffwd/rew enhancement ideas
Last modified: 2009-09-08 09:14:17 UTC
In addition to automatically displaying the "now playing" screen w/ remaining time and progress bar (or something similar) on pressing FF of REW, I think another helpful and intuitive feature would be for the x4,x8,x12 speeds to ramp up automatically similarly to how the volume , or title scrolling currently works "on button hold". Most MP3 and CD players work this way... On button release, the player could either automatically start playing (like a CD Player) or it could continue as it does now, until Play, Pause, or the opposite scanning direction button is pressed (like some MP3 players and most video players). Perhaps this could be user configurable? Or perhaps the two functions could be rolled into one... where tapping the FF button "skips" 20 secs forward, and REW skips 5 sec back and resumes play automatically (like Tivo/MCE 2004). Holding down the same FF/REW for longer than x seconds (user selectable?) would begin the automatic ramping described above. Another additional tweak might be to add to or replace the existing x2,x4, etc. display with larger, easier to read at a distance >,>>,>>>,etc. directional icons in addition to the elapsed time bar. Even more: Pressing REW while paused could go to the start of the track (still paused), as Dean suggested... in addition pressing FFWD while paused could bring bring the user 20secs (user confugurable?) away from the end of the track. A handy feature for those wanting to listen to the last few seconds of a song to see how it blends with the next track when putting together playlists.
In addition to the items above.... I would also add the recommndations made in: Bugzilla Bug 39: reduce volume during ffwd/rew.
Another alternative. To please those who like the way scanning works now...keep the existing behaviour for key taps, but ramp up on key hold.
tapping is used for skip fwd and skip back.
Kdf, to clarify: I'm refering to tapping the ff/rew buttons, not the previous/next track buttons. The current behaviour for tapping the key in scanning mode ups the speed in increments. I'm suggesting auto ramping of speed increments on key hold.
look at the slim devices remote. they are the same buttons.
Duh. Yes, tapping skips tracks. On hold initiates scanning, at which point further held "taps" are neccessary to ramp speed up. (My remote is at home... and obviously my memory sucks)
Moving to untargetted for review post 6.5
*** This bug has been marked as a duplicate of 1592 ***
I dont see how this is a duplicate of 1592?
Sorry for the confusion. We're going to fix this ui problem by making press and hold start fast forwarding and releasing the button ending the fast-forward. We'll also have the fast-forwarding ramp up over time. Bug 1592 is the original bug report for this problem. *** This bug has been marked as a duplicate of 1592 ***