Content-Type: text/plain; charset=iso-8859-15; format=flowed
From: Jerome Lenroue <jerome.lenroue at tamaris.tm.fr>
Date: Fri, 13 Dec 2002 09:19:24 +0100
Subject: [producersdk] Real Events


Hi Larry,

thank you for you help.  I think I will try the short-term workaround you 
told me (hoping it will not be to "resource demanding" since I also have to 
do other simultaneous processing during the encoding).
I will also watch closely the 9.1 release to see if this feature is 
implemented.


Thanks for everything and Merry Christmas ! :)

Jerome


On Thu, 12 Dec 2002 07:51:15 -0800, Larry Young <lyoung at real.com> wrote:

> Hi Jerome,
>
> Let me answer your question two ways -- what you would ideally have to 
> do, and what you have to do today given the limitations of the Producer 
> SDK.
>
> The intention of the mediaSinkInput is support the use case where the sdk 
> user already has uncompressed a/v samples (or events), and does not need 
> to use the file reading or capture plugins.  Ideally, for your use case, 
> you would instantiate and simultaneously use two different inputs -- the 
> capture plugin as well as the mediaSinkInput.  The encoding engine would 
> grab a/v samples from the capture plugin and your sdk app would pass 
> events to the mediaSinkInput
>
> Unfortunately, you may have noticed that there is no way to 
> simultaneously use two different inputs in the same job.  We hope to add 
> this feature to the 9.1 release (you can see the roadmap at: 
> http://helix- producer.helixcommunity.org/roadmap.htm), but there may or 
> may not be time to add that particular feature.  However, there is a sort 
> of oddball short-term workaround that you should be able to take 
> advantage of.  If you instantiate a capture input and run it in preview 
> mode (you don't have to associate the input with a job or anything like 
> that -- you can just enable preview mode), you can implement a preview 
> sink and use that to grab a/v samples and pass them to the mediaSinkInput 
> (which is the same mediaSinkInput that you're passing event samples to).
>
> BTW, if you respond to my email, could you please cc 
> discuss at producersdk.helixcommunity.org. We would like to use that mailing 
> list to discuss issues exactly like this.
>
> Thanks,
> Larry
>
> At 12:43 PM 12/12/2002 +0100, you wrote:
>> Hi Larry,
>>
>> Thank you very much for your help !
>>
>> Indeed I went through the "mediasinkencoder" sample app and I see how 
>> you manage to add event during a live session, using the event input pin 
>> and setting up an event stream for each audience selected. I am fine 
>> with that.
>>
>> But, to do so, it seems you have to configure a "mediaSinkInput" type 
>> input and when I choose another input type (i.e. "rn-capture-av") in 
>> order to get the audio/video from a capture device, I cannot add any 
>> event input pin.  To be a little more precise, in the SetupInput() 
>> function, this line return an error
>> 	
>> 	res = pInput->GetUnknown( kPropEventInputPin,&pUnk );
>>
>> I suppose it is because, when I set the input type to be a "rn-capture- 
>> av", no pins are available...(???)
>>
>> It also seems that when you are setting a "mediaSinkInput" (like in the sample 
>> app), there  is no way to define the source of the video/audio input 
>> pins.
>>
>> Thanks..... (again ;) )
>>
>> Jerome Lenroue
>>
>> On Wed, 11 Dec 2002 19:56:15 -0800, Larry Young <lyoung at real.com> wrote:
>>
>>> Hi Jerome,
>>>
>>> Sorry the documentation is lacking in this area.  If you want to add events 
>>> while an encode is going on, you'll want to use the Event Pin to pass 
>>> event samples to the encoding engine.  The "mediasinkencoder" sample 
>>> app demonstates how to do this (see the CMediaSinkEncoderApp::EncodeSamples 
>>> method).  If you want to add events to an already existing .rm file, 
>>> you'll want to use the Edit functionality within the SDK.  The 
>>> "rmevents" sample demonstrates how to do this (note that you must have 
>>> at least the 9.01 version of the Producer SDK -- the 9.0 version does 
>>> not have this sample app).
>>>
>>> Thanks,
>>> Larry
>
>



-- 
-------------------------------------------------------------------
Jérôme LENROUE - Skill Group ADI RENNES IT
Cap Gemini Ernst & Young - Géographie Ouest - Rennes
-------------------------------------------------------------------
--