Hi Everyone!
I'm writing Xvideo streamer. I've written my own Video source file derived
from FramedSource and I'm using MPEG4VideoStreamDiscreteFramer and
MPEG4ESVideoRTPSink. I'm using VLC player to receive stream. The problem is
that receiver shows only first frame correctly and gradually this f
When i stream file2 (rename this file's extension as m4e) using
LiveMediaServer demo application, The following message is printed
continously on the screen:
MPEG4VideoStreamParser::parseVideoObjectPlane(): Saw unexpected code 01F5
MPEG4VideoStreamParser::parseVideoObjectPlane(): marker bit
rtsp://202.43.34.236/TPBS_arch/15-04-2009T20.asf <-- but this server
implement speed header.
Speed header, is not fast-forward, but it is to increase bandwidth.
However, to implement it in rtsp client, is very simple.
Is there any disadvantage to have it?
On 6/25/09, Ross Finlayson wrote:
> We d
When i stream file2 (rename this file's extension as m4e) using
LiveMediaServer demo application, The following message is printed
continously on the screen:
MPEG4VideoStreamParser::parseVideoObjectPlane(): Saw unexpected code 01F5
MPEG4VideoStreamParser::parseVideoObjectPlane(): marker bit
I am trying to connect multiple clients to a live H264 stream from a file
source. I have set the resuseFirstSource flag to be true to enable all the
clients to render the same data. I could always connect the first client,
but the subsequent clients on VLC always give a warning message called
"Wai
Hi All,
I am trying to connect multiple clients to a live H264 stream from a file
source. I have set the resuseFirstSource flag to be true to enable all the
clients to render the same data. I could always connect the first client,
but the subsequent clients on VLC always give a warning message cal
I'm using the Live555 in order to make a unicast transmission of an MPEG2T.
my sender and receiver are both Live555 .
I used the DEBUG mode on RTCP.CPP to check the messages .
I noticed that the receiver sends the RTCP packets only to itself
(they are being received on 127.0.0.1 and on the same p
Hi,
I'm using the Live555 in order to make a unicast transmission of an MPEG2T.
my sender and receiver are both Live555 .
I used the DEBUG mode on RTCP.CPP to check the messages .
I noticed that the receiver sends the RTCP packets only to itself
(they are being received on 127.0.0.1 and on the s
We don't support the "Speed:" header in our RTSP client, because few
- if any - servers implement it. It's just not very useful in
practice.
(Note that if you want "fast-forward", then you do that using the
"Scale:" header - which we *do* support - not the "Speed:" header.)
--
Ross Finlayso
Hi,
rtspclient should support "Speed: " header.
It is easy to implement.
The attached file is the patch for this.
Thank you,
Anon.
diff -urN liblivemedia-2008.07.25.orig/liveMedia/MediaSession.cpp
liblivemedia-2008.07.25.develop/liveMedia/MediaSession.cpp
--- liblivemedia-2008.07.25.orig/liveMed
I am trying to stream out an audio and a video stream in a single
SDP sessions and would like add these as two separate media
sub-sessions. Based on my understanding, I plan to try the following:
sms = ServerMediaSession::createNew()
sms->addSubsession(AudioMediaSubsession::createNew(...))
Dear Experts,
I am trying to stream out an audio and a video stream in a single SDP sessions
and would like add these as two separate media sub-sessions. Based on my
understanding, I plan to try the following:
sms = ServerMediaSession::createNew()
sms->addSubsession(AudioMediaSubsession::c
Thanks Ganesh it solved my problem. I have one more problem. i have tested two
files for streamer. when file1 is streamed by streamer, the received file is
not playable if i dont add initial stream information. While when file2 is
streamed by the streamer, the received file is directly playable
13 matches
Mail list logo
