Bugzilla – Bug 2655
Add more advanced track positioning, e.g. random access
Last modified: 2011-01-24 00:06:03 UTC
The existing ffwd/fbwd mechanism is ok for tracks of just a few minutes in length, but when playing longer tracks or files with multiple segments, it's lacking. Random access both from the remote and SS GUI would be useful, such as moving to a user entered displacement within the file. Being able to skip forward or back a preset amount of time, e.g. 30 seconds or a minute, or to a point of silence, would be useful too. On the SS gui, similar controls for jumping forward or back in time would be useful.
there is a plugin for this (works only with native formats, as always)
Thanks Kevin, I saw your plugin and will definitely try it. Some control on the slimserver GUI would be great too though for when working at the PC and wanting control. On the SB, skip forward/back to silence, which I didn't see mentioned on the plugin overview, would also be particularly useful. Apologies if you've covered the slim GUI and the silence feature too as then you've definitely covered everything I could think of atm on that.
I believe ExBrowse3 skin is adding this fuctionality to the web interface as of 6.5. As far as skippign to next packet of silence, that would require a lot more processing than is curently going on at any level.
It would, although architecture permitting that's not necessarily a reason not to try it, even though it may not ultimately be successful. Although the user may have to wait a while for a brute force scan, it wouldn't be as long as normal speed, and would be less inconvenient than ffwd/fbwd where there's the chance of accidentally skipping forward or back a track by mistake. An option to cache observed silence points might also pay off for some users. Given caching support for silence points, another obvious feature would be an option to smart scan for the silence points in the background for files over a certain size, and/or that are not identified to be likely single tracks. Thinking forward from there, and having now identified file segments, being able to assign names to those segments could be another useful addition. Arguably the user might be better off using a 3rd party tool to simply split the large file into tracks, whether real or notional, and be done with it. However, they'd need to have such a tool, and for users that didn't want to be fiddling at the PC to manipulate their files, an integrated SB (& SS) interface to such a tool could be a nice solution. For users having complete albums in AlbumWrap format, native support for AW would be the preferred solution in that case.
Also present in the default SC 7 skin - for native formats.
Downgrading to P4 give that the song-scanner in SC7 is that much more functional.
The WebUI now has this functionality, as does the SB Touch. Other UIs are unlikely to get any further enhancements due to the complexity of the UI model that would be necessary.