> I've used the example "testH264VideoToTransportStream" as a basis for
> generating a H264-TS-over-RTP stream of packets.
> I have used Wireshark to view the stream of RTP packets, and they appear to
> be correctly filled with an integer number of 188 byte Transport-Stream
> packets.
>
> I am
I've used the example "testH264VideoToTransportStream" as a basis for
generating a H264-TS-over-RTP stream of packets.
I have used Wireshark to view the stream of RTP packets, and they appear to be
correctly filled with an integer number of 188 byte Transport-Stream packets.
I am trying to fur
> I am running the 12-2-2011 build of Live555. When I run
> RTSPClient::sendSetParameter(…) with a session that is running UDP to a
> live555 server implementation, the server parses and successfully runs the
> RTSPClientSession:: handleCmd_SET_PARAMETER (overridden in a subclass). If I
> run
Many apologies if this is a dupe, I don't think I properly signed up for the
list before sending this earlier so I'm not sure if the email was "lost" or not.
First I want to thank everyone involved in this project for such a high quality
library. This is surely open-source done right!
I am run
> No I don’t see this error message, however I am seeing continuous
> truncations, almost every frame is truncated. My own debug output looks like
> this, at a rate of around 4 frames per second:-
> deliverFrame(): newFrameSize:216054, fNumTruncatedBytes:66055
> deliverFrame(): newFrameSize:10899
Hi Ross,
>No, I meant the 'sink' object that those feed into. Is this a "RTPSink"
(subclass)? If so, then you should be seeing
>an error message like
> "MultiFramedRTPSink::afterGettingFrame1(): The input frame data was
too large for our buffer size"
>This error message will also tell you
