[Live-devel] openRTSP Test Program Fails to Export a File
Layne Berge
Layne.Berge.1 at my.ndsu.edu
Sun Feb 5 12:03:24 PST 2012
>> I'm using the live555 library in order to save an RTSP stream from a PTZ camera. I used the openRTSP program in the "testProgs" directory in order to test whether it would work with the camera I was using. From the output, the program was able to connect to and talk to the camera and request frames from it. However, upon examining the output files from the program, the data was corrupt.
>
> Are you sure? You haven't said what RTP payload format the stream was using. Please post the RTSP protocol exchange (the debugging output from "openRTSP").
H:\live\testProgs>openRTSP -d 10 -V -Q rtsp://10.248.123.150/live2.sdp
Opened URL "rtsp://10.248.123.150/live2.sdp", returning a SDP description:
v=0
o=RTSP 1327875302 714 IN IP4 0.0.0.0
s=RTSP server
c=IN IP4 0.0.0.0
t=0 0
a=charset:Shift_JIS
a=range:npt=0-
a=control:*
a=etag:1234567890
m=video 0 RTP/AVP 96
b=AS:0
a=rtpmap:96 MP4V-ES/30000
a=control:trackID=2
a=fmtp:96 profile-level-id=3;config=000001B003000001B2464D5F5047204D6F6465000001
B509000001000000012000C48881F4514043C1463F;decode_buf=76800
m=audio 0 RTP/AVP 97
a=control:trackID=3
a=rtpmap:97 mpeg4-generic/44100/2
a=fmtp:97 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1210;SizeLengt
h=13; IndexLength=3; IndexDeltaLength=3; CTSDeltaLength=0; DTSDeltaLength=0;
Created receiver for "video/MP4V-ES" subsession (client ports 50818-50819)
Created receiver for "audio/MPEG4-GENERIC" subsession (client ports 50820-50821)
Setup "video/MP4V-ES" subsession (client ports 50818-50819)
Setup "audio/MPEG4-GENERIC" subsession (client ports 50820-50821)
Created output file: "video-MP4V-ES-1"
Created output file: "audio-MPEG4-GENERIC-2"
Started playing session
Receiving streamed data (for up to 10.000000 seconds)...
begin_QOS_statistics
subsession video/MP4V-ES
num_packets_received 360
num_packets_lost 3
elapsed_measurement_time 10.005074
kBytes_received_total 388.502000
measurement_sampling_interval_ms 1000
kbits_per_second_min 8.895464
kbits_per_second_ave 310.643979
kbits_per_second_max 726.239417
packet_loss_percentage_min 0.000000
packet_loss_percentage_ave 0.826446
packet_loss_percentage_max 8.333333
inter_packet_gap_ms_min 0.016000
inter_packet_gap_ms_ave 27.116086
inter_packet_gap_ms_max 1275.389000
subsession audio/MPEG4-GENERIC
num_packets_received 427
num_packets_lost 3
elapsed_measurement_time 10.005074
kBytes_received_total 158.056000
measurement_sampling_interval_ms 1000
kbits_per_second_min 4.746848
kbits_per_second_ave 126.380674
kbits_per_second_max 301.392489
packet_loss_percentage_min 0.000000
packet_loss_percentage_ave 0.697674
packet_loss_percentage_max 6.818182
inter_packet_gap_ms_min 0.013000
inter_packet_gap_ms_ave 22.985400
inter_packet_gap_ms_max 1051.451000
end_QOS_statistics
>
>
>> My next test was to try outputting a quicktime file. When I tried this, the program started printing Klingon to the screen and producing an annoying beeping.
>
> That's because the "-q" (and the "-i" and "-4" options) output to 'stdout'. If you want to write the output to a file, then you will need to redirect 'stdout' to it.
Is there a simple switch to do that or do I have to compile the test program in order to allow that? I did see the "-F" switch for specifying the output file prefix but I don't think that is what you are talking about, correct? Thank you for dealing with my software naivete.
More information about the live-devel
mailing list