[Live-devel] MPEG2TransportStreamIndexer Question

[Leary, Brent]

Ross,
The video data being received over the socket would need to be written
to a file as well as sent to the indexing object. It can't be written to
a file first & then indexed b/c the server may need to play the video
data immediately after its finished being received over the socket.
What interfaces does deriving from a FramedSource impose on a class? I'm
guessing by your response that something along the lines of a
ByteStreamSocketSource would need to be created from scratch? Is there
anything close to this already to start from?

Thanks,
-Brent

-----Original Message-----
From: live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Thursday, July 26, 2007 5:19 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] MPEG2TransportStreamIndexer Question

>Within the MPEG2TransportStreamIndexer's main, is there an existing
>class that could replace the ByteStreamFileSource that would receive
its
>video data off a UDP socket instead of reading from a file?

IMHO, it doesn't make any sense to apply the indexing algorithm to 
anything but a file, because
	1/ You want the input data to be exactly the same when you 
later *use* the index file, and
	2/ When you later use the index file, you will need to be 
able to seek within it.
-- 

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