RE: Video codecs

-] I can't comment on looping, since we haven't attempted anything more
-] complex than the "play this movie" interface, but
-] implementing the IStream interface to feed DirectShow off 
-] your packfiles
-] is trivial - it takes less than 100 lines of code code for us.
-] 
-] When I said Microsoft MPEG-4 v2, I was not talking about WMV files, 
-] but of plain old AVIs containing MPEG-4 encoded content. WMV provided
-] better quality, but failed to use hardware stretching when 
-] playing back
-] on some videocards, resulting in choppy playback. (Maybe it's better
-] to switch to 640x480 when playing movies anyway.) 

I used the INSSBuffer, IStream, IWMReaderCallback, and
IWMReaderCallbackAdvanced interfaces to accomplish everything required.  If
you encode all of your movies at 512x512 and then wrap then derive from
INSSBuffer so that you use a DirectX texture as the buffer it renders into,
then you will always have hardware stretching.  Plus it speeds up playback
because the decoded frame gets put directly into the video memory update DMA
chain without an extra intermediate buffer and an extra copy involved.

Dave Huseby
[email protected]


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Gamedevlists-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gamedevlists-general
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=557