: r624 - docs/nutissues.txt

Author: michael
Date: Wed Feb 13 15:17:09 2008
New Revision: 624

Log:
header elision update


Modified:
   docs/nutissues.txt

Modified: docs/nutissues.txt
============================================================
==================
--- docs/nutissues.txt	(original)
+++ docs/nutissues.txt	Wed Feb 13 15:17:09 2008
 -115,6
+115,8  we already know like the frame size.
 A. Store header bytes and length in the framecode table.
 B. Leave things as they are.
 
+Implemented
+
 
 Issue small-frames
 ------------------
 -135,6
+137,8  D. Use header compression, that is allow
    would allow us to store the size of a frame without any
redundancy.
    Thus effectivly avoiding the overhead small frames
cause.
 
+It seems the consensus is: A+D
+
 
 Issue pcm-frames
 ----------------
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel

On Wed, Feb 13, 2008 at 03:17:10PM +0100, michael wrote:
> Author: michael
> Date: Wed Feb 13 15:17:09 2008
> New Revision: 624
> 
> Log:
> header elision update
> 
> 
> Modified:
>    docs/nutissues.txt
> 
> Modified: docs/nutissues.txt
>
============================================================
==================
> --- docs/nutissues.txt	(original)
> +++ docs/nutissues.txt	Wed Feb 13 15:17:09 2008
>  -115,6 +115,8  we already know like the frame size.
>  A. Store header bytes and length in the framecode
table.
>  B. Leave things as they are.
>  
> +Implemented
> +
>  
>  Issue small-frames
>  ------------------
>  -135,6 +137,8  D. Use header compression, that is allow
>     would allow us to store the size of a frame without
any redundancy.
>     Thus effectivly avoiding the overhead small frames
cause.
>  
> +It seems the consensus is: A+D

With the specified bounds...

Rich
_______________________________________________
NUT-devel mailing list
NUT-develmplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/nut-devel