[Live-devel] TS over UDP (or RTP)

[Pannaman, Jonathan]

Hi

I have been working on this, I have a DeviceSource with doGetNextFrame and deliverFrame methods. I want to check if my process is correct.

The DirectShow filter calls a method on my DeviceSource and offloads a large block of TS packets. The deliverFrame method when called gets the next 7xTS packet Frame each time it is called. The data is copied into fTo rather than fTo being changed per the framework instructions.

The doGetNextFrame method I assume is called from the framework, it calls deliverFrame. These are all interlocked to make sure data doesn't overwrite and nothing is blocking.

Any comments?

the examples I have just call taskScheduler.doEventLoop() though the DeviceSource framework implies I could call turnOnBackGroundReadHandler, I couldn't find an example of that. I currently have the live portion of my software running in its own thread so the doEventLoop can run and not block the DS code.

Do you have a recommendation if this is not an appropriate approach.

Thanks

Jon

________________________________
From: live-devel-bounces at ns.live555.com
To: LIVE555 Streaming Media - development & use
Sent: Thu Oct 01 21:13:56 2009
Subject: Re: [Live-devel] TS over UDP (or RTP)

My question then is do I have to create a FramedSource derived class

Yes.
and which methods do I have to implement/override?

doGetNextFrame()
 If you can point me at a example of this it would be great.

There are several in the code.  However, for a template of how to do this, see "DeviceSource.cpp".

Also, for an example of code that reads from a capture devlce, converts it into a Transport Stream, collects Transport Stream packets into groups of 7, and then streams it via RTP, see the "wis-streamer" code - http://www.live555.com/wis-streamer/ - in particular, "WISMPEG2TransportStreamServerMediaSubsession.cpp"

--


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

________________________________
Please consider the environment before printing this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20091010/662125ce/attachment.html>