<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
@Zahira<br>
<br>
you can try demuxing your TS with ffmpeg and then delivering two
separate streams for audio and video via RTP-over-RTSP. You will
need to reassemble them correctly on the receiving side however, or
face terrible lipsync issues.<br>
You can wrap both of these as a Transport Stream at the receiving
side; however asking further questions about it should better be
directed at the ffmpeg crew.<br>
<br>
Hope that helps.<br>
<div class="moz-signature">
<title>RT-RK default Signature</title>
<p><font style="font-family: Arial,sans-serif; font-size: 12px;"><strong>Aleksandar
Milenkovic</strong><br>
Software Engineer<br>
<br>
Phone: +381-(0)11-2695-244<br>
Fax: +381-(0)21-450-721<br>
Mobile: +381-(0)64-31-666-82<br>
E-mail: <a href="mailto:aleksandar.milenkovic@rt-rk.com">Aleksandar.Milenkovic@rt-rk.com</a><br>
<br>
RT-RK Computer Based Systems LLC<br>
Bulevar Milutina Milankovica 19a<br>
11000 Beograd, Serbia<br>
<a href="http://www.rt-rk.com">www.rt-rk.com</a></font>
</p>
</div>
<br>
On 9/20/2012 4:09 PM, <a class="moz-txt-link-abbreviated" href="mailto:live-devel-request@ns.live555.com">live-devel-request@ns.live555.com</a> wrote:
<blockquote
cite="mid:mailman.232.1348150148.859.live-devel@lists.live555.com"
type="cite">
<pre wrap="">Send live-devel mailing list submissions to
<a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
or, via email, send a message with subject or body 'help' to
<a class="moz-txt-link-abbreviated" href="mailto:live-devel-request@lists.live555.com">live-devel-request@lists.live555.com</a>
You can reach the person managing the list at
<a class="moz-txt-link-abbreviated" href="mailto:live-devel-owner@lists.live555.com">live-devel-owner@lists.live555.com</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of live-devel digest..."
Today's Topics:
1. Re: MPEG1or2DemuxedElementaryStream use (Ross Finlayson)
2. Re: Enumerate all 'clients' and memory leak (Ross Finlayson)
3. Re: Enumerate all 'clients' and memory leak (Ross Finlayson)
4. Re: Enumerate all 'clients' and memory leak (??????????????)
5. Re: MPEG1or2DemuxedElementaryStream use (Zahira Ammarguellat)
----------------------------------------------------------------------
Message: 1
Date: Thu, 20 Sep 2012 06:28:56 -0700
From: Ross Finlayson <a class="moz-txt-link-rfc2396E" href="mailto:finlayson@live555.com"><finlayson@live555.com></a>
To: LIVE555 Streaming Media - development & use
<a class="moz-txt-link-rfc2396E" href="mailto:live-devel@ns.live555.com"><live-devel@ns.live555.com></a>
Subject: Re: [Live-devel] MPEG1or2DemuxedElementaryStream use
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:4FE7CB02-4CF0-487E-AAAD-4FDBEB013121@live555.com"><4FE7CB02-4CF0-487E-AAAD-4FDBEB013121@live555.com></a>
Content-Type: text/plain; charset="us-ascii"
</pre>
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">
It's hard to answer this, because you haven't said anything about your system/environment.
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.
<a class="moz-txt-link-freetext" href="http://www.live555.com/">http://www.live555.com/</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="http://lists.live555.com/pipermail/live-devel/attachments/20120920/57f48a53/attachment-0001.html"><http://lists.live555.com/pipermail/live-devel/attachments/20120920/57f48a53/attachment-0001.html></a>
------------------------------
Message: 2
Date: Thu, 20 Sep 2012 06:37:23 -0700
From: Ross Finlayson <a class="moz-txt-link-rfc2396E" href="mailto:finlayson@live555.com"><finlayson@live555.com></a>
To: LIVE555 Streaming Media - development & use
<a class="moz-txt-link-rfc2396E" href="mailto:live-devel@ns.live555.com"><live-devel@ns.live555.com></a>
Subject: Re: [Live-devel] Enumerate all 'clients' and memory leak
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:3ECEC68E-8A0A-44D4-B73C-CECA1C8D0FB6@live555.com"><3ECEC68E-8A0A-44D4-B73C-CECA1C8D0FB6@live555.com></a>
Content-Type: text/plain; charset="us-ascii"
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">My ptable pointer allocated in MediaLookupTable::ourMedia but never deleted
No, that's incorrect - it *will* get deleted, if/when all "Medium" objects end
</pre>
</blockquote>
<pre wrap="">up getting deleted (so there's no memory leak here).
Both VLD (visual leak detector) and ms crt debug runtime reports leaks in that
code.
</pre>
</blockquote>
<pre wrap="">
Once again, this table will get deleted if (and only if) all "Medium" objects get deleted. (Recall that "Medium" objects are deleted by calling "Medium::close()".)
</pre>
<blockquote type="cite">
<pre wrap="">BTW, i also interested in removing UsageEnvironment object too. In the sample
code you are advised termination code looks like this:
pliveenvironment->reclaim();
delete m_plivetaskscheduller;
</pre>
</blockquote>
<pre wrap="">
That's correct. Note that the call to "UsageEnvironment::reclaim()" will reclaim all allocated memory, but *only if* all "Medium" objects have already been deleted.
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 their applications using multiple processes :-)
Ross Finlayson
Live Networks, Inc.
<a class="moz-txt-link-freetext" href="http://www.live555.com/">http://www.live555.com/</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="http://lists.live555.com/pipermail/live-devel/attachments/20120920/593cc357/attachment-0001.html"><http://lists.live555.com/pipermail/live-devel/attachments/20120920/593cc357/attachment-0001.html></a>
------------------------------
Message: 3
Date: Thu, 20 Sep 2012 06:44:46 -0700
From: Ross Finlayson <a class="moz-txt-link-rfc2396E" href="mailto:finlayson@live555.com"><finlayson@live555.com></a>
To: LIVE555 Streaming Media - development & use
<a class="moz-txt-link-rfc2396E" href="mailto:live-devel@ns.live555.com"><live-devel@ns.live555.com></a>
Subject: Re: [Live-devel] Enumerate all 'clients' and memory leak
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:87900AA7-0EA5-4FA8-985D-B7259E24DE3F@live555.com"><87900AA7-0EA5-4FA8-985D-B7259E24DE3F@live555.com></a>
Content-Type: text/plain; charset="us-ascii"
</pre>
<blockquote type="cite">
<pre wrap="">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 standard operator new (not overloaded, not a
`nothrow` version). But according the c++ standard operator new is never return
NULL, but throws bad_alloc on error. Why we need to check the return value?
</pre>
</blockquote>
<pre wrap="">
Yes, you're correct - in this case, the test for "rtspClient == NULL" is not needed, and could be removed.
Note, however, that not all "createNew()" functions are simply wrappers around operator new. "RTSPServer::createNew()", for example, is not.
Ross Finlayson
Live Networks, Inc.
<a class="moz-txt-link-freetext" href="http://www.live555.com/">http://www.live555.com/</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="http://lists.live555.com/pipermail/live-devel/attachments/20120920/5037da69/attachment-0001.html"><http://lists.live555.com/pipermail/live-devel/attachments/20120920/5037da69/attachment-0001.html></a>
------------------------------
Message: 4
Date: Thu, 20 Sep 2012 13:55:36 +0000 (UTC)
From: ?????????????? <a class="moz-txt-link-rfc2396E" href="mailto:zvyagintsev@atlantis.ru"><zvyagintsev@atlantis.ru></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:live-devel@ns.live555.com">live-devel@ns.live555.com</a>
Subject: Re: [Live-devel] Enumerate all 'clients' and memory leak
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:loom.20120920T154955-990@post.gmane.org"><loom.20120920T154955-990@post.gmane.org></a>
Content-Type: text/plain; charset=utf-8
Ross Finlayson <a class="moz-txt-link-rfc2396E" href="mailto:finlayson@..."><finlayson@...></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">
But the best/easiest way to reclaim all of the memory for all of the
</pre>
</blockquote>
<pre wrap="">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 their applications using
multiple processes
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
Nice irony, but my code (and live555 code also) live in a dynamic link library
which is directshow filter (COM object). I cant just 'exit(0)-and-have-fun' :)
------------------------------
Message: 5
Date: Thu, 20 Sep 2012 06:49:51 -0700
From: Zahira Ammarguellat <a class="moz-txt-link-rfc2396E" href="mailto:zammargu@marvell.com"><zammargu@marvell.com></a>
To: LIVE555 Streaming Media - development & use
<a class="moz-txt-link-rfc2396E" href="mailto:live-devel@ns.live555.com"><live-devel@ns.live555.com></a>
Subject: Re: [Live-devel] MPEG1or2DemuxedElementaryStream use
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:B2A7C617B3AB7F44B7B44C7D374B431E13A0FD6067@sc-vexch3.marvell.com"><B2A7C617B3AB7F44B7B44C7D374B431E13A0FD6067@sc-vexch3.marvell.com></a>
Content-Type: text/plain; charset="us-ascii"
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 creating an MPEG2-TS stream is not an ideal thing. Creating an RTP audio stream and a video stream are better suited for this work?
With this (small amount) information looking at testOnDemandRTSPServer still holds?
Thanks,
-Zahira
From: <a class="moz-txt-link-abbreviated" href="mailto:live-devel-bounces@ns.live555.com">live-devel-bounces@ns.live555.com</a> [<a class="moz-txt-link-freetext" href="mailto:live-devel-bounces@ns.live555.com">mailto:live-devel-bounces@ns.live555.com</a>] On Behalf Of Ross Finlayson
Sent: Thursday, September 20, 2012 9:29 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] MPEG1or2DemuxedElementaryStream use
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 use) a RTSP server? If so, then I suggest starting by reviewing the "testOnDemandRTSPServer", and reading the FAQ.
Ross Finlayson
Live Networks, Inc.
<a class="moz-txt-link-freetext" href="http://www.live555.com/">http://www.live555.com/</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="http://lists.live555.com/pipermail/live-devel/attachments/20120920/54bd8fb0/attachment.html"><http://lists.live555.com/pipermail/live-devel/attachments/20120920/54bd8fb0/attachment.html></a>
------------------------------
_______________________________________________
live-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
<a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
End of live-devel Digest, Vol 107, Issue 37
*******************************************
</pre>
</blockquote>
</body>
</html>