de-interlacer dynamic resolution change

Yes DEI doesnt support runtime resolution change but we have since added this feature and it will be available in the next RDK release 3.5.

Regarding your usecase, can u explain why a select link is required. I remember we had some discussion on this but the reason is not clear.

VIP0 always outputs HD (Progressive)

VIP1 always captures 4D1 (Interlaced)

If the above is true why does the usecase require a select link.Cant capture output queues be directly connected to different DEI links ?

Hi Badri,

1. Vip will be single channel, but in any resolution and scan type , not only HD, progressive.

2. The user can select for each channel the required encoding scan type, and changing channel X encoding scan type, must not cause stop and start of other channel (stop/start usecase is not allowed in our system)

if I can change capture output queue connection to different dei/nsf than it might be also OK, but it must be done dynamically, without interfering other channels. I don't think it is possible in framework, is it ?

Thank you very much for your comment about the usecase,

Ran

Ok for this usecase you will require select link. Also implementing it without DEI supporting dynamic resolution would require some hacks.It would be better to migrate to RDK 3.5 release where DEI supports runtime resolution change.If this is not possible for some reason we can provide a patch on top of RDK 3.0.1 with this feature included.

Ok, thank you. Is 3.5 version already published ?

Ran

DVR RDK3.5 will be available mid december 2012.

Hi Badri,

Thank you very much for all answers. I would like to ask about the dynamic input resolution capability change in next 3.5 version: does it refer to width, height or also to scan-type, and frame-rate (each standard input enum contains these parameters). If it refers also to scan-type and frame-rate are the dynamic change of these parameters is also supoprted for all the Links in the chain (dei, noise filter, scalers, encoder links).

Thank you !!

Ran

The new feature added in RDK 3.5 is width and hieght can change dynamically for DEI input.ALso application can dynamically change the width and height output by capture link.

Scan type is not expected to change dynamically and links dont support dynamic change in scan type.As you are probably aware at DEI driver level we have to specifiy at create time whether it has to be created with DEI in bypass mode or DEI enabled mode. This means it is not possible to dynamically switch between DEI enable and DEI disable based on input scan type for a driver instance. You need to create two DEI link instance one with DEI enabled and another with DEI disabled and route frames to the correct link using a select link.

I didnt understand your comment about frame rate.Frame rate info is not associated with frames and info is not sent from one link to another.

Shiju has added feature to dynamically delete and create a encoder instance since our call.This feature will not be part of RDK 3.5 release but we can provide it to you separately as a patch.This makes the encoder channels independent and application can change format/profile/scna type of a particular encoder channel by deleting and creating code runtime.Note that encoder still has to be created with max resolution as we already discussed.

HI Badri,

Thank you and also for Shiju for the added feature, this is most valuable !!!

About the frame-rate, I might not have been clear enough. What I meant is that when changing input standard, it is in form of the following enum
SYSTEM_STD_720P_60, /**< 1280x720 60FPS progressive HD standard. */ ....
In which each  "standard" has 4 value: resolution (width&height), frame-rate (fps) and scan type. Therefore, when standard changes from one type to another each of this parameter: width&height, frame-rate ,scan type can be different. For example, in our project scan type can change dynamicall, and so frame-rate,  for example: when we changed input from camera #1 which is SYSTEM_STD_720P_60 to camera #2 which is SYSTEM_STD_480I.

Best Regards,

Ran

Will you be connecting and disconnecting a different camera dynamically to the same VIP port . i.e Will you be runtime changing camera from 480i to 720p ? If so it requires significant changes as you will have to delete and recreate the capture FVID2 driver. My understanding was you will always have 4D1 480i connected to one VIP port and 720p connected to another VIP port.It would help if you could share your latest data flow including dynamic configuration change requirement in your application so that we can discuss this internally and identify gaps if any.