Rockbox General > Rockbox General Discussion

FF/Rewind across file boundaries

<< < (2/3) > >>

Llorean:
He wants to fast forward into the next track... notice the topic of the post.

Chronon:
Yes.  I did notice that.  I guess the more important operation is not FF to next track, but REW to previous anyway.  This does not work as desired for seeking across track boundaries (regardless of step size).  Skipping past the track boundary in reverse begins playback at the beginning of the previous track rather than near the end of the track even with a skip size of 5s.

Should we consider this as a feature idea?

Edit: I changed "Seeking past" to "Skipping past" as it's more accurate.

BruceHP:
>Should we consider this as a feature idea?

For people listening to audiobooks FF/Rewind to the Previous/next file can be a good feature, but it should be switchable.

Before Rockbox (bookmarking), I split my Books files (5 to 40 hours long) into 5 minute segments for better management.

Of course, this may be of no benefit to people not listening to serial  files.

Thanks!

MikeN:
> For people listening to audiobooks FF/Rewind to the Previous/next file
> can be a good feature, but it should be switchable.

Yes -- configurability is a major part of what makes Rockbox good.  As a comment though, it's hard to imagine a realistic case where it would be important to have FF/Rewind stop at the boundary.  You are more likely to achieve whatever you are trying to achieve by using boundary-crossing FF/RW and Next/Previous clicking.

> Before Rockbox (bookmarking), I split my Books files (5 to 40 hours long)
> into 5 minute segments for better management.

Yes.  I used a free tool called mp3DirectCut for that.  It was nice and small and fast.  You look for flat spots in the wave pattern that indicate that the reader is taking a decent pause between sentences, etc., then place cutpoints there.

Mike

Llorean:
Right now the default behaviour is for seeking to slow down as you approach the boundary. Our current method of accelerated seeking doesn't really mesh well with seeking across the boundaries, and a general assumption is that if you wanted to seek within something "as if it were one file" the simplest solution would be to have it actually be one file.

I'm not saying boundary-crossing seeking wouldn't be nice, but there are also some other pretty obvious solutions to the problem too.

Navigation

[0] Message Index

[#] Next page

[*] Previous page