Please DO NOT ask the same question on the mailing list multiple times. (This
is explained in the FAQ!) I already answered your question two days ago.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@l
how do i modify live555ProxyServer so let it work like live555MediaServer,
when i want to get a stream source that live555ProxyServer hadn't create a link
of this source when it started up, live555ProxyServer can link this new source
and brocasts it so i can get it by another program like "ope
> What should I do for other types, i.e. RTP Payload Format for H.264 Video
> (format code: 96)?
I can't answer this unless you tell me specifically what kind of stream this is
- i.e., how it is delivered.
Is this stream served with a RTSP server of its own? I.e., does it have its
own "rtsp:/
On Apr 4, 2013, at 5:44 AM, Shrishty Deorari
wrote:
> what i did exacty in my main file is : ..
>
>
> RTPSink* audioSink;
>
Hi,
The testOnDemandRTSPServer works great receiving RTP MPEG Transport Stream
Packets (format code 33), but is there a strong resctriction for other
payload
types?
What should I do for other types, i.e. RTP Payload Format for H.264
Video (format code: 96)?
Thanks
__
Hi,
I tried to create the testAACAudiostreamer.cpp for streaming the .aac
audio file
in that i used MPEG4GenericRTPSink class for creating the audioSink (as i
have read in previous live-devel answers that RTPSink" subclass that you
would use for streaming AAC audio is a "MPEG4GenericRTPSink" and a
> Unfortunately it appears to happen on all branded cameras I have to test:
> ACTi, Sony, Axis, D-Link, Vivotek and Lilin.
I find this very difficult to believe - especially considering that nobody else
has reported this problem.
Nonetheless, because you provided definitive evidence of at least
Thanks for your fast reply.
Unfortunately it appears to happen on all branded cameras I have to test:
ACTi, Sony, Axis, D-Link, Vivotek and Lilin. I updated the firmware on this
specific Sony camera to the latest last week.
It appears to be a very typical response to kill the connection when
rece
> Hi, sorry, it's a dynamic IP and there was a power cut:
>
> rtsp://86.146.238.165/media/video1
OK, I've tested this now.
You're correct that your camera server appears to crash (closing down the TCP
connection) and reboot whenever it receives the proxy's "GET_PARAMETER"
command. I.e., the
Hi, sorry, it's a dynamic IP and there was a power cut:
rtsp://86.146.238.165/media/video1
On 4 April 2013 03:56, Ross Finlayson wrote:
> The stream will freeze after a few minutes. When the stream is opened
> directly, it does not freeze:
>
> ./testProgs/testRTSPClient rtsp://86.146.236.49/me
10 matches
Mail list logo
