When it's running in stand-alone dtdriver, it just has a mini-context
with MediaEngine, there is no client engine. Most file formats don't
need a client engine, the dtdriver just loads the file format plugin and
remderer/decode plugins (if decoding), but RTSP needs the client engine
to do the actual streaming.

Actually rtspff is quite a generic translation layer to the file format
interface, I don't think there is anything specific to RTSP other than
the URL schemes it claims!

-Jamie

On 2/1/2011 1:04 PM, Sheldon Fu wrote:
> Looks good.
>
> Out of curiosity and not related to this CR, why does rtspfformat need
> to create a client engine for itself? This looks like a very interesting
> use case.
>
> fxd
>
> Jamie Gordon wrote:
>> Synopsis
>> ========
>> Updates to match the interrupt settings in the MiniContext scheduler
>> and the ClientEngine.
>>
>> Branches: PRODUCER_14_0_RN, HEAD
>> Suggested Reviewer: anyone
>>
>>
>> Description
>> ===========
>> Removes my earlier change to force MiniContext scheduler to enable
>> interrupt on platforms where the ClientEngine defaults to enabled -
>> change back to disable interrupt.
>>
>> Updates the rtspfformat to check its scheduler interrupt settings when
>> creating a new ClientEngine and set the ClientEngine to match.
>>
>> Added IHXScheduler3 and IHXSchedulerInterruptSupport to the
>> MediaPlatform's scheduler wrapper, CHXMediaPlatformScheduler
>> (so that the rtspfformat can actually get the aforementioned
>> scheduler interrupt settings).
>>
>> Files Affected
>> ==============
>> datatype/tools/minicntx/minicntx.cpp
>> datatype/rtsp/fileformat/rtspfformat.cpp
>> client/medpltfm/chxmedpltfmsched.cpp
>> client/medpltfm/pub/chxmedpltfmsched.h
>>
>>
>> Testing Performed
>> =================
>> RTSP input to producer via dtdriver
>>
>> Platforms Tested: win32-i386-vc9
>> Build verified: win32-i386-vc9
>>
>>
>> QA Hints
>> ===============
>>
>> n/a
>>
>>
>>
>>
>>
>>
>>
>