I am sorry if Iitwasn't clear enough. Your suggestion is exactly what I
want to do: implement my own LIVE555 transcoding filter (based on
libAV). My confusion is about the registering of urls and where to put
the libAV play command. Do I need to register two urls: the "normal
camerastream" and the "transcoded camerastream", or should it be enough
to just use the "transcoded camerastream"? What happens if a player
tries to play the "transcoded camerastream"? This will result in sending
a RTSP play command to the camera, but does the libAV play command do
the same? I have not totally clear what will happen and therefore need
some suggestions in the right direction.
best regards,
Frank van Eijkelenburg
On 01-09-15 21:41, Ross Finlayson wrote:
Sorry, but I don’t see how your question has anything to do with our
software.
From what I can tell, you are using VLC to transcode a RTSP/RTP
stream. Although VLC uses our “RTSPClient” code to access the
‘back-end’ RTSP/RTP stream, it doesn’t use any of our code at all
(including our ‘proxy server’ code) to do the transcoding, nor to
implement the RTSP server for the ‘front-end’ stream. (When VLC acts
as a RTSP server, it uses its own RTSP server implementation - not ours.)
You *could*, if you wish, implement your own LIVE555 transcoding
filter (e.g., using FFMPEG/libAV) and plug that into our
“ProxyServerMediaSession” - to implement a transcoding LIVE555 Proxy
RTSP server. But that’s not what VLC is doing; it uses its own
software to do this (except for accessing the ‘back-end’ RTSP/RTP stream).
So, you should be asking your question on a VLC mailing list.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
