After reviewing RFC 4175 (and your code), I've decided not to implement this
RTP payload format in the released "LIVE555 Streaming Media" source code (at
least, not right now). There are a number of issues:
1/ For the "RTPSource" subclass (for receiving RTP packets using this payload
format):
Hi,
>> I am currently trying to implement uncompressed video streaming according to
>> RFC4175.
> Because this is likely to be something of general use (e.g., someone else was
> asking about this just yesterday), I suggest posting the code that you have
> so far (i.e., for your subclass of "Mu
> I am currently trying to implement uncompressed video streaming according to
> RFC4175.
Because this is likely to be something of general use (e.g., someone else was
asking about this just yesterday), I suggest posting the code that you have so
far (i.e., for your subclass of "MultiFramedRTPS
Hello,
I am currently trying to implement uncompressed video streaming according to
RFC4175. An issue that I struggle with, is that the payload header is variable
in length (see [1]). The header length depends on packet size, image line
length and current fragmentation offset. (I use some simpl
