This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

rdk software mosaic question

Hi,

I got an software mosaic question In the RDK 02.00.00.23.

The code define SYSTEM_SW_MS_MAX_WIN_PER_SC is only 18, can I increase it up to 24? is it the performance issue to turn lowing than previous version?

And the software mosaic instance SYSTEM_SW_MS_SC_INST_DEI_SC seems don't support up scaling, how do I break through this limitation?

Thanks,

Jacson

  • Jame,

    If you are increasing SYSTEM_SW_MS_MAX_WIN_PER_SC  to 24 what is the size of window? I don't think it can be D1 or greater.

    For SYSTEM_SW_MS_SC_INST_DEI_SC, default out size seems to be set to D1 so any lower resolution channel than D1 can be upscaled to D1 but that would be the max.

    Regards,

    Yogesh.

     

  • Hi Yogesh,

    Thanks for your response.

    The window size still according to mosaic layout id, max window is 1920x1080. As you said, if the window size only can be support <D1, that will not be usability. But I remember previous version don't have this limitation, why does this limitation appear at GA2.0?

    Thanks,

    Jacson

  • Hi Yogest,

    Do you have any comment on my first question response?

    Thanks,

    Jacson

  • Jacson,

    Sorry for confusion. Actually I should have said resolution of each channel instead of size of window. As I know the scalars have limitaion that each can do 16-18 D1 @ 30 fps. SYSTEM_SW_MS_MAX_WIN_PER_SC is signifying number of channels going through scalar so my point is if you increase this to 24 the channel resolution should be less than D1 to achieve same performance.

    Regards,

    Yogesh.

     

  • Hi Yogesh,

    So that is a performance issue. I understand. Thank you.

    Jacson

  • Hi Yogesh,

    I try to modify the define SYSTEM_SW_MS_MAX_WIN_PER_SC to be 24, but system will assert at swMsLink_drv.c function SwMsLink_drvCreateDeiDrv():

        pDrvObj->fvidHandle = FVID2_create(FVID2_VPS_M2M_DEI_DRV,
                                           pDrvObj->drvInstId,
                                           &pDrvObj->cfg.dei.deiCreateParams,
                                           &pDrvObj->cfg.dei.deiCreateStatus, &cbParams);
        UTILS_assert(pDrvObj->fvidHandle != NULL);

    I use three software mosaic and config like as:

        swMsPrm[0].numSwMsInst = 1;
        swMsPrm[1].numSwMsInst = 1;
        swMsPrm[2].numSwMsInst = 1;
        swMsPrm[0].swMsInstId[0] = SYSTEM_SW_MS_SC_INST_SC5;
        swMsPrm[1].swMsInstId[0] = SYSTEM_SW_MS_SC_INST_DEI_SC_NO_DEI;
        swMsPrm[2].swMsInstId[0] = SYSTEM_SW_MS_SC_INST_DEI_SC_NO_DEI; 

    I just want to use one swMs instance to do 24 windows split, I don't case performance issue, but the system seems can not flexibility modify the value, can you help me for that? Thanks.

    Jacson

     

  • Jacson,

    The error is coming from SWMS instance 1 or 2 as I look at the code. Can you confirm if it is instance 1 or 2? If this is instance 1 DEI SC driver itself would be restricting it to less than 24. numCh for dei sc is calculated as followed.

    pObj->DrvObj[i].endWin = pObj->DrvObj[i].startWin + SYSTEM_SW_MS_MAX_WIN_PER_SC - 1;

    ..........

    pDrvObj->cfg.dei.deiCreateParams.numCh = pDrvObj->endWin - pDrvObj->startWin + 1;

    As instance 1 and 2 are using same SC and you have set  SYSTEM_SW_MS_MAX_WIN_PER_SC to 24 effectively you are trying to pass 48 channels through same SC. Driver may have its own MAX channels because of which you are getting this assert. In this case, I need to look at DEI SC driver to see it is restricting numchannels. Let me check on that.

    Regards,

    Yogesh.

     

     

  • Hi Yogesh,

    This assertion happen at SWMS instance 1, not yet reach to instance 2. It seems only can be use 24 windows at SWMS instance 0. If this is a driver restrict, I think we should not use more than 16 windows at instance 1 or 2 on current rdk stage.

    Thank you with me discuss this issue.

    Jacson