I have built and tested the openrtsp command
line utility. It works fine for most of the most
commonly used payload formats. I also tried to
use the -t and -T options to use a RTP over RTSP
(or HTTP) tunnel and again it works very nice.
My question is as follows - I have a special
camera with
Hi all,
I have built and tested the openrtsp command line utility. It works fine for
most of the most commonly used payload formats. I also tried to use the -t and
-T options to use a RTP over RTSP (or HTTP) tunnel and again it works very
nice. My question is as follows - I have a special camera
On 26/11/09 00:28, Ross Finlayson wrote:
Yes, by modifying the code in "RTSPServer.cpp" :-)
Until we fix the problem (at least at the server end), that's the only
way I can see to overcome this issue - unless VLC is fixed to not use
"GET_PARAMETER" as a client liveness indicator. It doesn't r
Ross Finlayson wrote:
1) Is there a way to change the OPTIONS response?
Yes, by modifying the code in "RTSPServer.cpp" :-)
Until we fix the problem (at least at the server end), that's the only
way I can see to overcome this issue - unless VLC is fixed to not use
"GET_PARAMETER" as a client
Ottavio Campana ha scritto:
I tried following the stream with wireshark, and packets are sent
correctly every 40ms, one for H264 and one for data. The only thing that
surprises me is that the same sequence for the number of the packets is
used for the two streams. Thus, h264 packets have even s
Ross Finlayson ha scritto:
Now I would like to stream some custom data with the video stream, thus
I wrote a subclass of DeviceSource that feeds the custom data to a
subclass of OnDemandServerMediaSubsession .
When I try to play the stream with a "normal" player such as mplayer or
vlc I expect t
