The the ability to configure the fade in/fade out delays to the detail that
the PWM code has on the supported targets is not possible on every device
due to hardware implementation limitations. The Gigabeat F/X is an example
that without a large CPU time cost we cannot configure the delay to be
shorter while maintaining a smooth fade transistion. To increase the speed
beyond what it is at now (while maintaining a smooth step size) would
require an increase to the tick rate or multiple i2c writes in one tick.

Removing some of the configurabilty would be a benefit in terms of cross
device option consistency while keeping the penalty to performance low.

-Karl

On Mon, Jan 12, 2009 at 11:16 AM, Dominik Riebeling <
dominik.riebeling_at_gmail.com> wrote:

> On Mon, Jan 12, 2009 at 6:02 PM, Thomas Martitz
> <thomas.martitz_at_fhtw-berlin.de> wrote:
> > Personally, I cannot speak for the former one, but during the discussion
> it
> > was pointed out that the current defaults are sufficient and just fine,
> > providing a decent fading, and don't need further configurability.
>
> I completely disagree. I really like the configurability of the fading
> on my players and would hate to loose that flexibility. Usually I
> change the fade in / fade out delays to something that fits my taste
> better.
>
> Also, those settings have been there since years and I don't see a
> point in removing them at all.
>
>
> - Dominik
>
Received on 2009-01-12