FF very rough

[mswlogo]

I'm using FLAC compressed to max level.

Wired SqueezeBox 3.

SlimServer running on Wired XP Laptop.

FF is very rough.

Sometimes it moves real slow, sometimes it moves so fast I'm on the next track.

I noticed if I tap FF it goes to Next Track (is that by design).

Why no Normal seperate button for FF and Next Track?

Anything I can do?

I'm running last nights 6.5.1 SlimServer Build.

[Ross L]

If you hold the FWD button for a few seconds it should begin to play at 2x, then 4x, then 8x, etc etc. If you tap the FWD button it will skip to the next song, yes this is by design.

This seems intuitive to me.

[mswlogo]

If you hold the FWD button for a few seconds it should begin to play at 2x, then 4x, then 8x, etc etc. If you tap the FWD button it will skip to the next song, yes this is by design.

This seems intuitive to me.

Thanks for the explaination.

Pretty awkward if you ask me. To over loaded a function on one key. Hard to use if your not watching the display especially if I have the Display on Large Font. I don't stand in front the SqueezeBox to use it.

Usually FF speeds up if you hold it (exactly how scrolling works)and a Tap would cancel it. In this case Holding it steps up 1 level (and holding any longer does nothing) and Tap goes to the next track.

[mswlogo]

I just realized another way, possibly better way of doing this, and may be possible now with a programmable remote.

Quick Taps of FF button should increase FF speed.
A seperate button should do next track.

[ceejay]

I've not tried this but... if there are a couple of buttons on the remote you are not using, you could very easily redefine them using the custom.map facility to correspond to skip forward and skip back, say...

If you want to use keys on a programmable remote that's fine, you'll just have to make sure you capture the IR and configure it into the slimserver .IR file.

Sorry I don't have the detail of how to do this, but there is a fair chance someone has trodden this path before. Of course, if you are the first I'm sure you'll post back here!

Ceejay

[MelonMonkey]

Using one button for Fast Forward and Next track is pretty common in an audio player. Nothing wrong with that. What complicates matters is that holding the button does not do a standard fast forward (one that forwards at a specific rate while holding and starts normal playback once released).

I understand trying to get the extra functionality in, but this is just a poor design. It's one of the only faults I can immediately point out with the standard remote configuration.

[Yannzola]

Are there any additional ways of modifying custom.map to tweak fwd_scan/rew_scan so that the ramping from x2,x4,x8 etc. is automatically done on continued hold (similar to how volume ramps ups)?