[Live-devel] Why H264 annexB bytestream transported incompletely?
Ishwar.Jasuja at jci.com
Ishwar.Jasuja at jci.com
Fri Mar 28 11:43:19 PDT 2008
Did you try increasing Socket send & receive buffer size & see if that
makes any difference?
Regards,
Ishwar
Andreas F?rber <faerber at pi4.informatik.uni-mannheim.de>
Sent by: live-devel-bounces at ns.live555.com
03/28/2008 02:17 AM
Please respond to
LIVE555 Streaming Media - development & use <live-devel at ns.live555.com>
To
LIVE555 Streaming Media - development & use <live-devel at ns.live555.com>
cc
Subject
Re: [Live-devel] Why H264 annexB bytestream transported incompletely?
Hello,
Am 28.03.2008 um 09:15 schrieb Felix:
I have been trying to stream H264 annexB bytestream with livemedia, and
have made little progress these days.
My own xH264VideoStreamFramer(subclass of H264VideoStreamFramer) and
H264VideoFileServerMediaSubsession have been done.
To check my classes, I modified live555MediaServer, and use it as the
server while openRTSP as client for test.
But when running, the bytestream cannot be transported completely. Only
the first few datas can be received. What puzzles me more is that the
amount of datas received is variational.
The size of H264 annexB bytestream file on the server is 70574 Bytes,
sometimes the receiver can only receive the first 48KB, or sometimes 68KB.
70574B can rarely been received completely.
I also compare the data received on client with the bytestream file on
the serever, and found that these data are just the first part of the
bytestream.
I have been working on a H.264 annex G video stream framer. For me, the
last access unit is not being transmitted, and I attribute this to my file
parsing code, which by nature of the live library does not recognize the
end of the file properly and therefore does not reach/mark the end of the
last access unit.
Regards,
Andreas
I checked the "fOctetCount" member of class "RTPSink", and found that
when "MultiFramedRTPSink" call its "onSourceClosure()" function,
live555MediaServer already sent 70574 Bytes to the client(openRTSP).
But on the client, the data received is incomplete and variational.
What might caused this problem?
Any help will be appreciated!
Best Regards
Felix
雅虎邮箱,您的终生邮箱!_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.live555.com/pipermail/live-devel/attachments/20080328/48e4a984/attachment.html
More information about the live-devel
mailing list