From: David Bryant <dbryant_at_impulse.net>
Date: Sat, 11 Feb 2006 17:16:40 -0800

> I don't know if I'm alone in this desire, but I think it could be very
> valuable for Rockbox to handle correction files, if that's possible
> within the constraints of the platform. In this way it would be
> possible to carry around lossless versions of your tracks, but delete
> the correction files of the less used tracks when space becomes tight,
> giving a best of both worlds scenario.

I agree that handling the correction files would be great. Unfortunately, in
this case the problem is resources. Handling the correction files takes
about an additional 40% CPU cycles on the PC, and that doesn't take into
account the extra disk reading. In WavPack's "high" mode that would put us
at 100% boost ratio (without any dsp functions on), and even the default
mode would be pretty boosty.

It would be pretty easy to go ahead and try this for the fun of it, but like
Thom says, the whole codec structure has the Rockbox OS doing the disk
access, so there's no way to easily do it.

And I just thought of another headache! When WavPack on Rockbox currently
does a seek, it just estimates the position in the file where it wants to go
and just starts playing there (even if it's not exactly the right timecode).
When you're handling correction files, you have to seek both files
(obviously) and you would have to make sure you really had the exact same
timecode (and probably hunt around for it). On the PC this is instant; on
Rockbox it might be painful.
Received on 2006-02-12