At 04:17 PM 10/15/2008, you wrote:
Hello,
I am playing with the vobStreamer application, using MPlayer -rc2 to
view the stream.
The behavior I expect is that at the end of the stream, when
stopPlaying() is called on both sinks, live555 should send and RTCP
Bye packet, causing MPlayer to exit. B
The behavior I expect is that at the end of the stream, when
stopPlaying() is called on both sinks, live555 should send and RTCP
Bye packet, causing MPlayer to exit.
No, that's not what the code does. When the code reaches the end of
the input file, it reads/streams it again starting from th
Hello,
I am playing with the vobStreamer application, using MPlayer -rc2 to
view the stream.
The behavior I expect is that at the end of the stream, when
stopPlaying() is called on both sinks, live555 should send and RTCP
Bye packet, causing MPlayer to exit. But l have confirmed with
wireshark th
On Thu, Oct 16, 2008 at 12:29 AM, Ross Finlayson <[EMAIL PROTECTED]> wrote:
>
>> I am writing a streaming application with live555, both on the server
>> and client ends. I will be using live555 to mulitcast MPEG2 transport
>> streams over RTP to the clients. Periodically, the server will stop
>> m
I am writing a streaming application with live555, both on the server
and client ends. I will be using live555 to mulitcast MPEG2 transport
streams over RTP to the clients. Periodically, the server will stop
multicasting the current file and switch to a new one, sending it to
the same multicast
Hello,
I am writing a streaming application with live555, both on the server
and client ends. I will be using live555 to mulitcast MPEG2 transport
streams over RTP to the clients. Periodically, the server will stop
multicasting the current file and switch to a new one, sending it to
the same multi
