[Live-devel] live-devel Digest, Vol 128, Issue 13

Mon Jun 23 00:43:27 PDT 2014

Thanks Ross for the links. As I said I inherited this code so wouldn't have known that it is using obsolete libraries.
Are there any samples of c#/VB.net wrappers which can be a starting point.

Thanks

-----Original Message-----
From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of live-devel-request at ns.live555.com
Sent: Friday, June 20, 2014 5:44 PM
To: live-devel at ns.live555.com
Subject: live-devel Digest, Vol 128, Issue 13

Send live-devel mailing list submissions to
	live-devel at lists.live555.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.live555.com/mailman/listinfo/live-devel
or, via email, send a message with subject or body 'help' to
	live-devel-request at lists.live555.com

You can reach the person managing the list at
	live-devel-owner at lists.live555.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of live-devel digest..."

Today's Topics:

   1. Re: Starting Frames are corrupted (Vikram Singh)
   2. API's unavailable after version update (Manish Agarwal)
   3. Re: API's unavailable after version update (Ross Finlayson)

----------------------------------------------------------------------

Message: 1
Date: Fri, 20 Jun 2014 19:57:40 +0530
From: "Vikram Singh" <vikram at vizexperts.com>
To: "'LIVE555 Streaming Media - development & use'"
	<live-devel at ns.live555.com>
Subject: Re: [Live-devel] Starting Frames are corrupted
Message-ID: <001401cf8c93$cc0981d0$641c8570$@vizexperts.com>
Content-Type: text/plain; charset="us-ascii"

Hi ross,

Please ignore my previous mail. I was sent accidently.

Just for testing purpose, I have reduced my streaming video size to 100*100 px size.

By reducing the size I want to avoid the scenario where on the client side there is truncation of data, due to buffer overflow in the starting.

This buffer overflow was assumed because the client had no idea about server frame size and initialized a default size to the buffer that receives data.

Even then I have the problem of corrupt frames in the starting.

Can there be any other case because of which this initial corruption of frames is happening.

An another observation is when I had incorrect OutPacketBuffer::maxSize initialized to it, the frame rendered were like this

https://drive.google.com/file/d/0B9yXmUZbfI7_OWJiblZta1hXYWM/edit?usp=sharin
g

i.e the frame would bleed to the bottom and that symbolizes the truncation of frame.

Instead the corruption was something like this

https://docs.google.com/file/d/0B9yXmUZbfI7_YUxEb1ltZ2pwa3M/edit

and after some time it would clear up like this

https://docs.google.com/file/d/0B9yXmUZbfI7_VW9uU2NWU041SkE/edit

So can there be any other issue that is causing this problem.

-vikram

From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Wednesday, June 18, 2014 11:13 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Starting Frames are corrupted

I am having --  unsigned OutPacketBuffer::maxSize = 900000;  in mediaSink.cpp

If I decrease the maxSize then the frames I get are truncated.

OK, there are two separate buffer sizes that you need to concern yourself with.

"OutPacketBuffer::maxSize" is the buffer size that is used - by your server
- when *transmitting* NAL units.  You must set it to be at least as large as your largest NAL unit.  Otherwise you will see (in 'stderr') error messages about needing to increase "OutPacketBuffer::maxSize".

The receiving application - in your case VLC - must also have sufficient buffer space to be able to reassemble the incoming RTP packets into a complete NAL unit.  That is what I referred to in my previous email message.

In any case, 900000 bytes is an *insanely large* NAL unit (I-frame) size!!
A NAL unit this large will get fragmented into *60* RTP packets, and *all* of these RTP packets must be received by the receiving application, otherwise the entire frame will be unrenderable.  This is why it's much better to reconfigure your encoder so that it breaks up large I-frames into smaller 'slice' NAL units.

 Can you please specify how to decrease the nal unit size without decreasing the value of maxSize.

You mean "how to decrease the nal unit size without *increasing* the value of maxSize"?  Once again, you need to reconfigure your encoder to break up large I-frames into smaller 'slice' NAL units.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20140620/7413f29f/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 20 Jun 2014 16:06:36 +0100
From: Manish Agarwal <ma at Remsdaq.com>
To: "live-devel at lists.live555.com" <live-devel at ns.live555.com>
Subject: [Live-devel] API's unavailable after version update
Message-ID:
	<74CE1D9764EDBF4989C259DC7E8FF2624BFD2C6E71 at exch-svr.Remsdaq.co.uk>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20140620/004252e1/attachment-0001.html>

------------------------------

Message: 3
Date: Fri, 20 Jun 2014 09:43:53 -0700
From: Ross Finlayson <finlayson at live555.com>
To: LIVE555 Streaming Media - development & use
	<live-devel at ns.live555.com>
Subject: Re: [Live-devel] API's unavailable after version update
Message-ID: <909366BA-4147-453A-B17E-13FABCCD0F3B at live555.com>
Content-Type: text/plain; charset="windows-1252"

> I have inherited legacy code and have been tasked with fixing the bugs after the Live555 version update to May 2014 release. I downloaded the source code and compiled it to work with the existing code. Expectedly our code is breaking where it is calling the methods on Live555. For example one of the error is ?'playMediaSession' : is not a member of 'RTSPClient'?.

It seems that your application code is using the old 'synchronous' RTSP client interface, which has been obsolete for more than 4 years (and completely unavailable for more than 1 year).  This change was announced numerous times on this mailing list, so it's unfortunate that it has taken you this long to join this mailing list.

> Is there any documentation available which can help me in firstly understanding what a particular method is doing and secondly with which new method the older one is replaced with.

The Doxygen web page for the "RTSPClient" interface is
	http://www.live555.com/liveMedia/doxygen/html/classRTSPClient.html
Note also the "RTSPClient.hh" file itself - especially the comments in the file:
	http://www.live555.com/liveMedia/doxygen/html/RTSPClient_8hh-source.html

I suggest also that you look at the code for the "testRTSPClient" demo application (in the "testProgs" directory).

>  Also, since I am not a C++ guy and the existing application creates a 
> C++ wrapper so that the assembly is available for .net, are there any 
> samples anywhere which can help me with creating/understanding the 
> .net wrapper

Sorry, but that's not our code.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20140620/b4984704/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

------------------------------

End of live-devel Digest, Vol 128, Issue 13
*******************************************

Design : Develop : Manufacture | Delivering World-Class Technology Solutions | SCADA : Security : Mobilising

Forthcoming Events: 

Rail Live 18-19 June 2014, Warwickshire  UK- visit Remsdaq's Security Business Unit

Smart Grids 2-3 December 2014, Thailand - visit Remsdaq's SCADA Business Unit

News: Essex Fire and Rescue Service and Bedfordshire Fire and Rescue Service have chosen Remsdaq's Resque 4i for their new control room mobilising system.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20140623/66f0d710/attachment-0001.html>