[XviD-devel] Changes ported to dev-api-4
Edouard Gomez
ed.gomez at free.fr
Tue Apr 8 18:51:18 CEST 2003
Radek Czyz (radoslaw at airnet.com.au) wrote:
> Other changes:
> - I didn't understand some of my _BITS code for INTRA ;) so I rewrote
> the part which I didn't understand. It performs better now, too ;).
Synced
> - Some b-frame decision stuff again... I invented a better way of
> detecting still scenes, it's not so sensitive for them (although the
> detection is very accurate) so the effect is very good :).
Synced
> - encoder.c - I disabled bframe_threshold (but just uncomment it if you
> need it), because our vfw was setting it to 255 (?). Anyway, it's
> dev-api-4 stuff, not dev-api-3.
Not synced, this change is not relevant.
So we have deva-pi-4 in sync with cvs_head since 2 weeks. As pete
mentioned in another email, dev-api-4 will be merged back soon to
cvs_head. It would be good that Windows devs start updating vfw (the one
in the xvidcore module, not the vfw module anymore).
I'd say dev-api-4 works fine on GNU/Linux (achieved 3 complete DVDs rips
using constant quant) but i have some questions before i start updating
the transcode frontend and help elcabesa maintaining his mencoder
module.
The problem is completly AVI related. In the hope to avoid A/V syncs
i've tried to use Packed bitstream, but all the AVIs i created using
this packed option, were completely unusable with WMP. The stream was
right, but basically the problem was that i was pushing data to the
muxer only when xvidcore returned me data. So i think classic parsers
(vfw, videolan client and mplayer <= 0.90rc3 iirc) were complaining "not
coded vops" every 2 frames.
How do you solved that with the new API in the VFW frontend ?
NB: this was not a problem in cvs_head because in those cases xvidcore
was returning NVOPS that we had just to push to the muxer.
--
Edouard Gomez-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://edu.bnhof.de/pipermail/xvid-devel/attachments/20030408/ccaebe67/attachment.bin
More information about the XviD-devel
mailing list