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.

RTOS/TDA2EVM5777: About Display link in TIDL SemSeg Usecase

Part Number: TDA2EVM5777

Tool/software: TI-RTOS

Hi,

I have a question about Display link in TIDL Semantic Segmentation Usecase.

I saw the result of Alg_tidlpostproc in TIDL SemSeg usecase is YUV420_SP color map that is indicating each pixel of that map is contained some classes (None, Ped, Vehicle, ...).

After processed in Merge/Sync link, the result of Alg_tidlpostproc is in Metadata and original input video frame is in Video Buf.

So, the previous link (Alg_tidlpostproc_cpy) of Display link has the buffer that contains video frame and metadata(which is the result SemSeg Network).

I refered FVID2 document and it is saying the FVID2 frame has 2 fields like bellow image.

Then, in SemSeg usecase, the first field of FVID2 frame is for video frame and second field of FVID2 frame is for metadata?

Could you please confirm that i understood correctly?

  • Hi,

    yes your understanding is correct but not completely.

    For field 1 having video buf the representation is same as attached picture but not for metadata buffer.

    Regards,

    Anuj

  • Hi,

    Thanks for answering.

    I checked the sync link in TIDL SemSeg usecase adding the log.

    The all of log message was saying the input buffer is Video Frame data.

    I think the result of Alg_tidlpostproc link is video frame that is indicating each pixel is belonged to some class by using different color for different class.

    If this is correct, i'm curious that how the result of Alg_tidlpostproc is overlaped onto each original video frame.

    Regards,

    Yoo

  • Hi,

    Yes the output of tidl_postproc is video frame.

    In semseg usecase we use 2 postproc link 1 for creating clut and other for copying it onto original image.

    Please check below params from usecase

    pUcObj->Alg_tidlpostprocPrm.outDataFormat = SYSTEM_DF_YUV420SP_UV;
    pUcObj->Alg_tidlpostprocPrm.outWidth = SEMSEG_INPUT_WIDTH;
    pUcObj->Alg_tidlpostprocPrm.outHeight = SEMSEG_INPUT_HEIGHT;
    pUcObj->Alg_tidlpostprocPrm.colPalette565 = pObj->colPalette;
    pUcObj->Alg_tidlpostprocPrm.inPad = TIDL_MAX_PAD_SIZE;
    pUcObj->Alg_tidlpostprocPrm.numInputQueues = NUM_PIPELINES;
    pUcObj->Alg_tidlpostprocPrm.mode = TIDLPOSTPROC_MODE_CLUT;;

    /* Y and UV copy */
    pUcObj->Alg_tidlpostproc_cpyPrm.outDataFormat = SYSTEM_DF_YUV420SP_UV;
    pUcObj->Alg_tidlpostproc_cpyPrm.outWidth = SEMSEG_INPUT_WIDTH;
    pUcObj->Alg_tidlpostproc_cpyPrm.outHeight = SEMSEG_INPUT_HEIGHT;
    pUcObj->Alg_tidlpostproc_cpyPrm.numInputQueues = 1;
    pUcObj->Alg_tidlpostproc_cpyPrm.mode = TIDLPOSTPROC_MODE_COPY;

    Regards,

    Anuj

  • Hi,

    Its been long since any update on this thread.

    I hope the issue is resolved.

    If not then please reply below or create anew thread for different query.

    Regards,

    Anuj