[Live-devel] Problem of new supportfor unicastRTSP/RTPstreaming from a single input source

[Mike Yan]

Hello Ross,

Thank you for your answer. I have added VOS header to my MPEG-4 ES. Now I
can stream and play it just fine. But I have problem when I try to use
"MPEG4ESVideoRTPSource" class to receive the stream on the client. It always
gives me the following error which the buffer is not enough.

"MultiFramedRTPSource::doGetNextFrame1(): The total received frame size
exceeds the client's buffer size (20000).  104 bytes of trailing data will
be dropped!"

I try to use "increaseReceiveBufferTo()" to increase socket's buffer, but it
does not work. I still get the same error. Could you educate me how to
correct this issue?

BTW, I test multiple unicast RTSP server for MPEG2 Transport Stream, still
getting same error "Missing sync byte!"

Mike

-----Original Message-----
From: live-devel-bounces at ns.live.com [mailto:live-devel-bounces at ns.live.com]
On Behalf Of Ross Finlayson
Sent: Friday, October 08, 2004 5:43 PM
To: LIVE.COM Streaming Media - development & use
Subject: Re: [Live-devel] Problem of new supportfor unicastRTSP/RTPstreaming
from a single input source


>>The problem with this file is that a "VisualObjectSequence" header - 
>>i.e., beginning with 0x000001B0 - does not appear anywhere.  Such a 
>>header *must* occur in the stream.  (When streaming from a file, it's OK 
>>for there to be only one such header, at the start of the file.
>>When streaming from stdin, such a header must appear throughout the 
>>stream (e.g., every 1 second or so).)
>
>Could you explain why you need the VOS header?

Short answer: Because the RTP payload format for MPEG-4 ES Video requires 
it.  (See RFC 3014, section 3).

Longer answer: Because this header is necessary in order for the RTSP 
server to determine the "config" string that gets included in the SDP 
description that gets passed to each client (in response to the RTSP 
"DESCRIBE" command).

So, if your input stream doesn't already include a VOS header, then you 
will need to add one periodically (once every second or so should be 
sufficient).

(Alternatively, if you know what the VOS header ("config" string) *would* 
be (if you sent it), I could conceivably update the LIVE.COM code to take 
that string as a parameter (instead of trying to extract it from the input 
stream).  Then, media player clients will still get the "config" 
information OK (in the SDP description), and then *might* be able to play 
the stream, even though it won't contain VOS headers.)


	Ross Finlayson
	LIVE.COM
	<http://www.live.com/>

_______________________________________________
live-devel mailing list
live-devel at lists.live.com
http://lists.live.com/mailman/listinfo/live-devel