Support and General Use > User Interface and Voice

FF between files on Sansa Clip+

<< < (2/2)

seani:

--- Quote from: Llorean on December 31, 2010, 11:27:10 PM ---Well, if >> reached the end of the track and you kept holding it, I'd expect it to stop fast forwarding, then the track would end, then the next track would start, then Rockbox would say "hey, he's holding >>" and then start fast forwarding again.

So I wouldn't find it surprising that FF would take you "past the end" but it sounds like the WPS behaviour, at least, is buggy in relation to this.

Meanwhile in the same situation, if you rewound to << I would expect it'd stop, then just stay at 00:00 because you're still holding the button and it can't play.

This would then result in things that look like different behaviors for >> and <<, but really are the same behavior, "just keep doing it."

I'll agree though, it'd be nice to have the option between track boundaries stopping FF/RW or allowing it to continue past them (though this could create some awkwardness for acceleration / deceleration since it would decelerate more and more as you approached the end of the track).

--- End quote ---

I've been toying with an idea to change that behaviour (but done no code).

Rather than accelerating towards the end of the track, accelerate towards the midpoint between the current position and the end of the track, and then decelerate at the same rate when that midpoint is passed (but not coming to a stop, so not quite symmetrical).

A bit like a marble rolling into / out of a dip.

When a track boundary is "breached", reset the behaviour accel / decel based on the length of the newly entered track - no emergency stop and start.

Llorean:
Doesn't it already accelerate toward a midpoint, then decelerate past it?

[Saint]:
It seems to be some sort of fail with the acceleration?

I'm not sure...

Sometimes the whole "declerate when you're near the tracks end" thing works perfectly, and others it's possible for me to fast-forward off the end of track 1, hold for 2~3 seconds, then be in track 5-6-7ish.

I need to test it out more thoroughly when I have the time to, I tried it for 10 minutes or so whilst on my way home today and got *really* confused trying to find the "recipe".


[St.]

seani:

--- Quote from: Llorean on January 01, 2011, 07:09:37 PM ---Doesn't it already accelerate toward a midpoint, then decelerate past it?

--- End quote ---

I think it's been a long time since I even tried this - and it worked perfectly as you describe on my Clip+ for at least one podcast last night. I certainly should have checked before posting.

Navigation

[0] Message Index

[*] Previous page