On Sun, Jul 19, 2020 at 11:33 PM Thomas Volkert <si...@gmx.net> wrote:
>
> Hi,
>
> On 19.07.2020 18:10, Gautam Ramakrishnan wrote:
> > On Thu, Jul 16, 2020 at 11:45 PM Carl Eugen Hoyos <ceffm...@gmail.com> 
> > wrote:
> >> Am Do., 16. Juli 2020 um 19:42 Uhr schrieb Gautam Ramakrishnan
> >> <gautamr...@gmail.com>:
> >>
> >>> How could I get access to some stream/file for testing this feature if
> >>> I implement this?
> >> GStreamer should allow you to test your implementation.
> >>
> >> Carl Eugen
> > So to clarify things, basically the enc version would take a compressed
> > codestream, and split it into RTP packets given in the RFC? Is there 
> > anything
> > more than that? Is there any documentation page I can refer to? I was not 
> > able
> > to find anything specific.
>
>
> Do you mean the RFC itself?
> -> https://tools.ietf.org/html/rfc5371
>
Yes
>
> Alternatively to GStreamer you can use Live555 to test your
> implementation. I would start with the receiver and then continue with
> the sender part.
> Live555 source code for handling this payload:
>
> ->
> https://github.com/ThomasVolkert/live555/blob/master/liveMedia/JPEG2000VideoRTPSink.cpp
>
> ->
> https://github.com/ThomasVolkert/live555/blob/master/liveMedia/JPEG2000VideoRTPSource.cpp
>
>
Thanks a lot for these, will be very helpful

Additionally, what I understand is that the packetisation is of 3 types,
main header, tile part header and codestream packets.
However, if I understand it correctly, the rtp encoder provides an encoded
j2k codestream. To get the codestream packets from this, the codestream will
have to be decoded. Any suggestions on how to solve this? It does not make sense
to decode a codestream for this purpose. Can the tile part packets be
dumped from the
encoder itself?



-- 
-------------
Gautam |
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to