[Live-devel] openRTSP writing all zeros
Wiser, Tyson
TWiser at logostech.net
Fri Dec 17 06:18:05 PST 2010
Hi Ross,
Thanks for the reply.
Yes, if I omit the "-m" option the single large file looks the same. I've tried using a debugger to trace it back. I'm not at my work computer right now, so this is all from memory and may not be entirely correct. As I recall, however, the FileSink had a SimpleRTPSource as its source. The SimpleRTPSource received it's data from a Groupsock. Both when copying the data from the SimpleRTPSource to the FileSink and from the Groupsock to the SimpleRTPSource the buffers that the memory was being copied from contained all zeros (with very few exceptions). They were always of the correct size, but just didn't seem to contain the correct data.
Thanks,
Tyson
-----Original Message-----
From: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Friday, December 17, 2010 8:31 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] openRTSP writing all zeros
>However, now the entire file, with the exception of a very few bytes
>at the beginning and scattered seemingly randomly throughout,
>contains all zeros. Using wireshark I can verify that the actual
>non-zero data is being sent. The QoS statistics also show that no
>packets were dropped.
That's very strange. I can't explain this.
Do you also get a strange-looking file if you omit the "-m" option
(so that you write just a single output file)?
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
More information about the live-devel
mailing list