Bugzilla – Bug 286
add support for jumping to a specific position within a track
Last modified: 2009-09-08 09:27:50 UTC
Customer requested feature. It was recommended that we just display a progress bar of the song's duration, and allow the user to adjust specifically where in the song's duration to skip to.
*** Bug 50 has been marked as a duplicate of this bug. ***
I thought I'd add a few points that maybe need considering. 1. tracks, especially classical ones can often be 20 minutes or more, so an option that just allowed up/down by a set unit might get very tedious from the remote control unit. 2. To minimise key pressing on the remote I would be happy with an option to enter a simple numerical value, to be entered as two digits, and interpreted as a percentage of the time. Or if it was a VBR file without embedded timing info then perhaps even a percentage of file length. To make this useful you'd also need to display current position in the relevant units when this function was selected.
there is a new INPUT.Bar mode that I'm working on, and its basically done and ready for any go-ahead to add to the server. Perhaps with this now in place, it would be feasable to use the slider control to create an arbitrary jump to any point in a given song. The slider would represent 1-100% of the song duration. The trick is how to trigger this feature. A plugin might be an annoying amount of navigation, but I dont know what buttons it could be tied to otherwise.
I've created a basic plugin (Song Scanner) to handle this. I still have to work out the best way to exit the function, but for now is simply displays a progress bar, scrolling up and down increases and decreases the position in the track. exiting left jumps to that position. currently, there is no way to exit without causing a jump to that position :) http://www.deane-freeman.com/slimserver/
a plugin is available to accomplish this, so basically it is fixed. the plugin could at some point be included, but that's another thing entirely
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.