--- Begin Message ---
How can I fix it? I am new here. Any suggestions?
Much appreciate your pointing me in the right direction.
On Thursday, 26 June 2014, 4:44, Ross Finlayson wrote:
That's what I thought too. The "testOnDemandRTSPServer" prints "missing sync
byte" on the console when I tr
FYI, I've just installed a new version - 2014.06.27 - of the code that, I
believe, will fix the RTP/RTCP-over-HTTP server error that you saw.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live55
>> Try using "openRTSP" to receive your stream (and output it to a file).
>> Rename the output file to have a ".h264" filename suffix.
>>
>> Can VLC play this file (i.e., directly)?
>
> We did that,and it plays well.
OK, so now rename this file to have a ".264" (*not* ".h264") filename, and tr
Thanks!
Xxiao
On 06/27/2014 05:08 AM, Ross Finlayson wrote:
Below is the sdp captured,we noticed "m" has 0 for port
number,don'know if that's the problem.
BTW, that's not a problem. A port number of 0 in the SDP description
is normal when streaming a unicast stream using RTSP. (For unicast
Ross,
We did that,and it plays well.
Xxiao
2014年6月27日 上午5:04于 Ross Finlayson 写道：
>>
>> We have a live rtsp streaming that can be played by mplayer,can be saved as
>> file then replayed by vlc or mplayer. strangely,vlc can never play the live
>> rtsp directly
>
>
> Before using MPlayer or VLC (
Piers,
Thanks for the report. Using it, I was able to identify a bug in the RTSP
server code (when an incoming Base-64-encoded request is fragmented over
multiple reads, as in your case). A new version of the code - fixing this bug
- will be available shortly. (I'll send out another email wh
> Below is the sdp captured,we noticed "m" has 0 for port number,don'know if
> that's the problem.
BTW, that's not a problem. A port number of 0 in the SDP description is normal
when streaming a unicast stream using RTSP. (For unicast streams, the port
number(s) don't get assigned until later
> We have a live rtsp streaming that can be played by mplayer,can be saved as
> file then replayed by vlc or mplayer. strangely,vlc can never play the live
> rtsp directly
Before using MPlayer or VLC (which is not our software) to debug your server,
you should use "openRTSP":
http://www
We have a live rtsp streaming that can be played by mplayer,can be saved as
file then replayed by vlc or mplayer. strangely,vlc can never play the live
rtsp directly,we have been debugging this for two weeks.
Below is the sdp captured,we noticed "m" has 0 for port number,don'know if
that's the
> The idea is then to stream the file test.264 using live555. I tried different
> approaches; live555MediaServer, testONDemandRTSPServer,
> testH264VideoStreamer and a modified version of testONDemandRTSPServer where
> only test.264 is streamed. Regardless of the live555
> executable used, I am u
Hi Ross,
We have rebuilt with -g and without -o0 and get the same result (SIGABRT
in disassembled code, no stack trace).
We have tried the latest build of OpenRTSP with the -T flag. OpenRTSP
does not send GET_PARAMETER requests to the Live555 server, so it will
not call the code in base64Dec
> Is there any change in RTSP url when we stream RTSP over TLS ?
As I noted before, you can do this between an existing LIVE555 RTSP client and
an existing LIVE555 RTSP server - with no change to the existing LIVE555 code.
If you do things this way, then the answer is no - there's no change in
Is there any change in RTSP url when we stream RTSP over TLS ?
Regards,
Gaurav Badhan
>
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
13 matches
Mail list logo
