> I did not see a way to send a REGISTER command to the Proxy Server.
We have code that allows a RTSP server to register one of its *own* streams
with a proxy server (or with a client application). We don't have code that
allows some 3rd-party application to send a "REGISTER_REMOTE" (not "REGIS
That all sounds clear now, thank you!
--
Joshua Kordani
LSA Autonomy
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
>> Nonetheless, small NAL units are still a good idea, because they reduce the
>> effect of network packet loss. It's always a good idea, for example, to
>> break large 'I-frame' NAL units into multiple slices; they just don't need
>> to be as small as a standard MTU (1500 bytes), because our s
Ross,
Thank you for your detailed response! I have responded inline.
On 10/8/13 3:11 PM, Ross Finlayson wrote:
You don't have to do that. The LIVE555 code automatically takes care
of fragmenting large NAL units into appropriate-sized RTP packets.
Nonetheless, small NAL units are still a goo
Many thanks for the on-going dialog!
My evaluation of the Proxy Server / Live Media is probably going to lead to
total dependence :-) openRTSP and the entire live555 library is very much
on our radar screen. I'm still becoming familiar with the various pieces
and parts. I did spend some time looki
On Oct 8, 2013, at 10:48 AM, Bob Bischan
wrote:
> Attached is the diagnostic output.
>
> Looks like the client is sending a TEARDOWN...
Yes, your client (VLC) is sending a TEARDOWN. I don't know why; did you click
the 'stop' button? Or perhaps it sent a TEARDOWN because it didn't receive a
> I wish to use live555 to deliver in memory nals created with x264. In my
> application, I spawn off the live555 event loop into a separate thread from
> the one responsible for doing the encoding. I am configuring my encoder to
> output nals that will fit inside the standard mtu.
You don't
Attached is the diagnostic output.
Looks like the client is sending a TEARDOWN...
Thanks,
Bob
On Tue, Oct 8, 2013 at 10:30 AM, Ross Finlayson wrote:
> When I connect to the registered stream using VLC
>
>
> FYI, it's better (and easier) to use "openRTSP" (or "testRTSPClient") as
> your clien
Greetings all,
I wish to use live555 to deliver in memory nals created with x264. In my
application, I spawn off the live555 event loop into a separate thread
from the one responsible for doing the encoding. I am configuring my
encoder to output nals that will fit inside the standard mtu.
I
> When I connect to the registered stream using VLC
FYI, it's better (and easier) to use "openRTSP" (or "testRTSPClient") as your
client when testing a server, because you'll also get to see the RTSP protocol
exchange at the client end.
> I see "ProxyServerMediaSubsession["H264"]::createNewStre
openSVC share some SVC streams
http://sourceforge.net/projects/opensvcdecoder/files/?source=navbar
From: finlay...@live555.com
Date: Mon, 7 Oct 2013 06:39:44 -0700
To: live-de...@ns.live555.com
Subject: Re: [Live-devel] Streaming H.264/SVC
i want to know if the Live555 Streaming Media libraries
Ross,
Thanks for your time and consideration with making the modifications. I
have tested the new code and have a few observations to pass along:
I see "Play this stream using the URL:
rtsp://:8554/registeredProxyStream-1" when I send the
REGISTER_REMOTE command.
Proxy Server connects to the str
12 matches
Mail list logo
