>> But the best/easiest way to reclaim all of the memory for all of the
> LIVE555-allocated objects is simply to call "exit(0)" - i.e., by exiting the
> entire process. (But I forget - this is the 21st century. For some odd
> reason,
> software developers now have forgotten how to structure thei
In the 21s century people use things like smart pointers and the STL
and memory leaks rarely occur.
Matt S.
On Thursday, September 20, 2012 6:55:36 AM, ЗвягинцевАнтон wrote:
Ross Finlayson writes:
But the best/easiest way to reclaim all of the memory for all of the
LIVE555-allocated objec
nvironment.
Are you using (or planning to use) a RTSP server? If so, then I suggest starting by
reviewing the "testOnDemandRTSPServer", and reading the FAQ.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
-- next part --
An HTML attachment was s
One more thing Ross.
The Wifi display standard requires the use of MPEG2-TS. So we don't have much
choice about the way the multimedia input is transferred.
Thanks.
-zahira
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Thurs
Ross,
Ok here is more info that might help you help me :)
My server is a Linux system. My client is a QNX device. The idea is to use WIFI
display (using LIVE555 to build an MPEG2-TS stream) to stream an input
multi-media file to the QNX target.
It looks likes from your previous email that creati
Ross Finlayson writes:
>
> But the best/easiest way to reclaim all of the memory for all of the
LIVE555-allocated objects is simply to call "exit(0)" - i.e., by exiting the
entire process. (But I forget - this is the 21st century. For some odd reason,
software developers now have forgotten how
> And one more question, in the samples and the library itself many places in
> the
> code looks like this:
>
> RTSPClient* rtspClient = ourRTSPClient::createNew(env, rtspURL,
> RTSP_CLIENT_VERBOSITY_LEVEL, progName);
>
> if (rtspClient == NULL) {
>
> createNew() just a wrapper over the stand
>> My ptable pointer allocated in MediaLookupTable::ourMedia but never deleted
>> No, that's incorrect - it *will* get deleted, if/when all "Medium" objects
>> end
> up getting deleted (so there's no memory leak here).
>
> Both VLD (visual leak detector) and ms crt debug runtime reports leaks in
> You say:
> Instead, you should by transmitting audio and/or video as separate RTP
> streams, without any Transport Stream encapsulation.
>
>
> How do I do that please?
It's hard to answer this, because you haven't said anything about your
system/environment.
Are you using (or planning to u
Ross,
Thanks for your answer.
You say:
Instead, you should by transmitting audio and/or video as separate RTP streams,
without any Transport Stream encapsulation.
How do I do that please?
Thanks,
-Zahira
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Beha
Ross Finlayson writes:
> My ptable pointer allocated in MediaLookupTable::ourMedia but never deleted
> No, that's incorrect - it *will* get deleted, if/when all "Medium" objects end
up getting deleted (so there's no memory leak here).
Both VLD (visual leak detector) and ms crt debug runtime rep
> My ptable pointer allocated in MediaLookupTable::ourMedia but never deleted
No, that's incorrect - it *will* get deleted, if/when all "Medium" objects end
up getting deleted (so there's no memory leak here).
Out of curiosity, though: Why do you want to "enumerate all RTSPClients"?
Ross Finla
Hello.
As far as I understand live555 keep track the created 'objects' in internal
containers so my guess was it is possible to iterate over that containers.
What I need is to enumerate all rtspclients. According to this comment
// A data structure for looking up a Medium by its string name.
On 9/11/2012 2:54 PM, Mojtaba Nouri wrote:
We had the same problem, and we solved it by creating cbr ts files
stuffed with NULL packets.
The following thread shows the ffmpeg command parameters to create h.264
cbr files:
http://stackoverflow.com/questions/7125446/encoding-h-264-cbr-videos-with-ff
14 matches
Mail list logo
