On 2008-10-10, David Schleef <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 10, 2008 at 06:21:22PM +0000, David Flynn wrote:
>> From: Jonathan Rosser <[EMAIL PROTECTED]>
>>
>> different encoder implementations may leave or prune excess bits at the
>> end of the arithmetic data.
>
>> @@ -2706,12 +2706,16 @@ schro_decoder_decode_subband (SchroPicture *picture,
>> if (ctx->arith->offset < ctx->subband_length) {
>> SCHRO_WARNING("arith decoding didn't consume buffer (%d < %d)",
>> ctx->arith->offset, ctx->subband_length);
>> +#ifdef DONT_DO_THIS
>> ctx->broken = TRUE;
>> +#endif
>
> Um, don't do this. :) I'd prefer to add real solutions rather than
> random ifdefs.
Indeed, however i don't know what the solution should be. The spec
offers no advice on such a situation; it is not possible to decide if
you have decoded incorrectly by looking at the number of databytes
consumed.
The only thing i can think of is to enable such detection if the
transport signals that there was a fault during reception of the packet.
Even then, it still suffers from the above problem.
I certainally don't an end user's decoding to fail due to use of a too
small epsilon.
thoughts welcome.
..david
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Schrodinger-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/schrodinger-devel
