> - OPAL plugins and dynamic video codecs
> If I understand correctly, the plugin interface to
audio codecs
> differ from the interface to video codecs in one way:
> Audio codecs only pass the PAYLOAD field in the RTP
frame to OPAL
> - Video codecs however do pass the ENTIRE RTP frame to
OPAL (i.e.
> including Marker, timecode, payload type,...)
IMHO, both methods should be supported by the plugin
infrastructure, as it is
in the MediaStream class.
And the latter method is actually preferred (if the plugin
was implemented to
support it) because it gives valuable information, e.g. for
packet loss
detection, or the RTP payload type (useful in some cases for
decoding as well).
Granted all such info could be passed by option fields to
the codecs too.
____________________________________________________________
________________________
Low, Low, Low Rates! Check out Yahoo! Messenger's cheap
PC-to-Phone call rates
(http://voice.yahoo.com)
------------------------------------------------------------
------------
Check the FAQ before asking! - http://www.
openh323.org/~openh323/fom.cgi
The OpenH323 Project mailing list, using Mailman. To
unsubscribe or
change your subscription options, goto
htt
p://www.openh323.org/mailman/listinfo/openh323
Maintained by Quicknet Technologies, Inc - http://www.quicknet.net
------------------------------------------------------------
------------
|