[XviD-devel] todo/action list

[peter ross]

>I hope everyone knows the debugview output the VFW generates.
>
>Why not putting exactly that stuff into a file? Would be easy to do, and 
>it's easily parsable.

some comments:

* we should not store the field name on each line of the file.
  it wastes space, and makes it harder to parse (right gruel?)

* what values do we need?
  - frame_size   (bytes)
  - header_bits  (VOL/VOP)
  - texture_bits
  - quant_type
  - quant
  - kblocks
  - mblocks
  - ublocks

motion/macroblock info bits can be derived from:
frame_size*8 - header_bits - texture_bits.

* i also reckon we should not abandon .stats immediately.

---
xvid 1st/2nd-pass logs
---
1st-pass: size:22780 total-kbytes:22 intra quant:2 H.263 kblocks:697 
mblocks:0

2nd-pass: quant:2 H.263 intra stats1:22780 scaled:22780 actual:22780 
overflow:0 movie


----
divx5 logs:
---
##version 3
quality 5
bidirect 0
bidir_mult 2.000000
Frame 0: intra 1, quant 4, texture 43844, motion 0, total 44184, complexity 
548050
Frame 1: intra 0, quant 4, texture 23634, motion 3864, total 55864, 
complexity 295425
Frame 2: intra 0, quant 4, texture 36318, motion 5542, total 58128, 
complexity 453975
---

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com