[Red5] HELP NEEDED!
bowljoman at hotmail.com
Sat Jun 20 19:20:02 PDT 2009
If you can set the buffer-size of the subscriber with client code such as,
netStream.bufferTime=1.0, AND each buffer time for each client can be set to
a unique value, What make you think that the publisher needs to send that
What ever the reason is, and we'll probably learn soon why you cannot play
the content until publishment is done, Trying to trigger
netStream.Buffer.full from your rtmp client, is NOT the answer.
----- Original Message -----
From: "Jase" <jason at hybd.net>
To: <red5 at osflash.org>
Sent: Saturday, June 20, 2009 7:12 PM
Subject: [Red5] HELP NEEDED!
> I've spent most of the day going round in circles and I'm sure someone
> here has as idea what I need to do. I know I've posted several times
> here, but surely someone must know, as I'm making little ground by my
> self and I'm starting to loose my sanity quickly. This is a major hurdle
> (and hopefully the last hurdle) that is stopping me from using Red5 at
> the moment.
> As stated in previous posts, I'm stuck getting a live stream to play
> when publishing via a RTMPClient based Java app using the red5 API. My
> live stream only plays when the publishing process stops...
> I think I need to make a NetStream.Buffer.Full event trigger (as it does
> if I publish using Flash). I assume this is set in Flash via NetStream's
> I've scoured what I can in the API and what little docs there are and
> assume that this translates in RTMP terms to using a Ping to set the
> buffer size and the Ping.CLIENT_BUFFER option.
> I have no idea how to get my RTMPClient based app to do this, and would
> like some sort of assistance. Given a number of people here know the
> RTMP specs and Red5 API better than me given I have few days experience
> in the FLV format/RTMP/Red5 API.
> I'm getting increasingly frustrated, as there is practically nothing out
> there in the way of docs etc for newbies.
> My testing RTMPClient code is here: http://pastie.org/517808 and my
> previous post outlining more/exactly what my issues are is here:
> Can someone please confirm if I the need to send a buffer size 'Ping'
> signal is what I really need to do (or am I barking up the wrong tree),
> and possibly illustrate roughly how this translates in the Red5 API.
> Red5 mailing list
> Red5 at osflash.org
More information about the Red5