<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] JPEG2000</title></head><body>
<blockquote type="cite" cite><tt>I already a message on this list and
nobody answered. So i send it again...</tt></blockquote>
<div><br></div>
<div>Because of this, all future postings from you will be moderated.
If you do this again (sending the exact same message to the mailing
list), you will be permanently banned!</div>
<div><br></div>
<div>Not every question that gets posted to this mailing list ends up
getting answered. (Note, however, that in general, questions
posted by people with professional email addresses - i.e., *not*
"@gmail", "@yahoo", "@hotmail" etc. -
are more likely to get answered.)</div>
<div><br></div>
<div>But in short, there are no current plans to implement the RTP
payload format for JPEG 2000 (as currently defined in the Internet
Draft
<http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-1<span
></span>8.txt>). If you want to do this yourself, you would
need to implement new subclasses of "MultiFramedRTPSink"
(for transmission) and "MultiFramedRTPSource" (for
reception), similar to the existing "JPEGVideoRTPSink" and
"JPEGVideoRTPSource" classes.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>