[Live-devel] Multiple Files sequentially streamed

[Jeff Oliver]

Ross,

Thanks for your help, everything works great!   I will definitely come 
back here if I have any more questions.

Keep up the good work!

Jeff Oliver


Ross Finlayson wrote:

> Jeff,
>
> FYI, there is now a new version (2004.01.22) of the software that adds 
> "preferredFrameSize" and "playTimePerFrame" as (optional) parameters 
> to "ByteStreamMultiFileSource::createNew()".
>
>>  The added feature I need is a way to set the RTP Marker bit every 
>> time the file changes.  Is there a way to connect the RTPSink and the 
>> ByteStreamMultiFileSource together in order to share the file change 
>> information?  Or at least any ideas on how I might do this?
>
>
> FYI, I've also added a new member function
>         Boolean haveStartedNewFile()
> to "ByteStreamMultiFileSource()".  This tells a reader (in your case, 
> the RTPSink) whether or not the most recently-delivered frame was the 
> first from a newly-opened file.
>
> To use this, I suggest that you write your own subclass of 
> "SimpleRTPSink" that redefines "doSpecialFrameHandling()" (and nothing 
> else).  Your redefined "doSpecialFrameHandling()" would
>         1/ cast "fSource" to a "ByteStreamMultiFileSource*"
>         2/ call "haveStartedNewFile()" on it
>         3/ call "setMarkerBit()" if "haveStartedNewFile()" returned True.
>         4/ call "MultiFramedRTPSink::doSpecialFrameHandling()" (to set 
> the packet's timestamp properly).
>
>
>     Ross Finlayson
>     LIVE.COM
>     <http://www.live.com/>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live.com
> http://lists.live.com/mailman/listinfo/live-devel
>
>


Disclaimer: The information contained in this transmission, including any 
attachments, may contain confidential information of Matsushita Avionics 
Systems Corporation.  This transmission is intended only for the use of the 
addressee(s) listed above.  Unauthorized review, dissemination or other use 
of the information contained in this transmission is strictly prohibited. 
If you have received this transmission in error or have reason to believe 
you are not authorized to receive it, please notify the sender by return 
email and promptly delete the transmission