[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OpenDivX digest, Vol 1 #53 - 2 msgs
Send OpenDivX mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.projectmayo.com/mailman/listinfo/opendivx
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenDivX digest..."
Today's Topics:
1. New Decoder API (Andrea Graziani)
2. IRC channel? ([email protected])
--__--__--
Message: 1
Reply-To: "Andrea Graziani" <[email protected]>
From: "Andrea Graziani" <[email protected]>
To: "opendivx list" <[email protected]>
Date: Thu, 12 Apr 2001 11:23:52 -0700
Organization: MySelf
Subject: [OpenDivX] New Decoder API
This is a multi-part message in MIME format.
------=_NextPart_000_0011_01C0C343.0D608B70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
A new version of the decoder API is on the CVS repository since some =
day. Probably this is generating some confusion so I try to explain the =
motivations for this change.=20
The main reason of the change is an excellent idea coming from the =
experience of Jonathan, that worked to port OpenDivX on the MIP: since =
there are a lot of consideration to take in care in the memory usage, =
it's better to leave to the application the freedom to allocate the VLD =
tables, the buffers, ... of the decoder.
The new API has a preprocessor definition, _DEC_MEM_REQS_, that is used =
by the application to ask the decoder how much memory it needs for the =
differents structures. The application then has the control on how and =
where allocate the memory. After the memory allocation, the application =
calls again the decoder through the API to initialize the decoder.
The code of the Windows Multimedia Driver and the of the DirectShow =
filter have alredy been upgraded to use the new API. In addiciton, you =
can find in decore.c a main(...) that shows how the API is supposed to =
be used. The main(...) itself can be compiled (#undef _DECORE) to run =
the decoder as a console application.
Andrea
------=_NextPart_000_0011_01C0C343.0D608B70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>A new version of the decoder API is on =
the CVS=20
repository since some day. P</FONT><FONT face=3DArial size=3D2>robably =
this is=20
generating some confusion so I try to explain the motivations for this =
change.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The main reason of the change is an =
excellent idea=20
coming from the experience of Jonathan, that worked to port =
OpenDivX on the=20
MIP: since there are a lot of consideration to take in care in the =
memory usage,=20
it's better to leave to the application the freedom to allocate the VLD =
tables,=20
the buffers, ... of the decoder.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The new API has a preprocessor =
definition,=20
_DEC_MEM_REQS_, that is used by the application to ask the decoder how =
much=20
memory it needs for the differents structures. The application =
then=20
has the control on how and where allocate the memory. After the memory=20
allocation, the application calls again the decoder through the API to=20
initialize the decoder.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The code of the Windows Multimedia =
Driver and the=20
of the DirectShow filter have alredy been upgraded to use the new API. =
In=20
addiciton, you can find in decore.c a main(...) that shows how the API =
is=20
supposed to be used. The main(...) itself can be compiled (#undef =
_DECORE) to=20
run the decoder as a console application.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Andrea</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_0011_01C0C343.0D608B70--
--__--__--
Message: 2
Date: Thu, 12 Apr 2001 15:48:41 -0400
From: [email protected]
To: [email protected]
Subject: [OpenDivX] IRC channel?
Does this project curently have a IRC channel for developers?
If not, I would recomend we start one...
irc.openprojects.net is a great place to be for projects, keeps the signal to noise ratio down quite a bit over being on Dalnet or such.
I'll be in #opendivx on irc.openprojects.net if anyone wants to join me.. Perhaps we could use that channel, or go somewhere else if anyone prefers.
Steve Pinkham
--
--__--__--
_______________________________________________
OpenDivX mailing list
[email protected]
http://lists.projectmayo.com/mailman/listinfo/opendivx
End of OpenDivX Digest
Reply To Poster
Local References / HOW-TO / FAQs