Dear all,
I used a non-RTSP protocol(defined by someone) to get MPEG4 video frames from
IP cameras and then save them to a memory buffer. I want to do live streaming
from IP cameras to my PC.
I try to modified testMPEG4VideoStreamer and find the FramedSource is
file-base. It does not fit my n
>Cha Gascon wrote:
>>I can connect and play the stream but after a while, it will stop
>>streaming. When it actually stops is random, sometimes a few
>>frames, sometimes after getting a lot of frames.
>The axis camera sends a "BYE" after some time. I do not know whether
>it is a bug or a feature
Cha Gascon wrote:
I can connect and play the stream but after a while, it will stop
streaming. When it actually stops is random, sometimes a few frames,
sometimes after getting a lot of frames.
The axis camera sends a "BYE" after some time. I do not know whether it
is a bug or a feature... but
My situation is similar with this one.
Using Axis 214 network camera and openRTSP as client. Used -t option for
rtsp over tcp.
I can connect and play the stream but after a while, it will stop streaming.
When it actually stops is random, sometimes a few frames, sometimes after
getting a lot of fr
> >On the client, I just added one sentence in MediaSession.cpp's
>> MediaSession::lookupPayloadFormat():
>>
>> case 96: {temp = "H264"; freq = 9; nCh = 1; break;}
This is completely wrong. 96 is a dynamic RTP payload format code;
it does *not* have a static definition.
The
Hi,
Am 29.03.2008 um 14:13 schrieb Felix:
>On the server, I just added my own
> H264VideoFileServerMediaSession and xH264VideoStreamFramer.
>On the client, I just added one sentence in MediaSession.cpp's
> MediaSession::lookupPayloadFormat():
>
> case 96: {temp = "H264"; freq
