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: VSDK - Issue with playing HD (1920*1080) videos in 1920* 720 display resolution

Other Parts Discussed in Thread: DRA744

Tool/software: TI-RTOS

Hi all,

We are using DRA746-Jacinto processor and 12.3 inch display (1920 * 720).
We are using vsdk3dot1 version.
We are running below usecase in IPU1 core. With the below usecase (weston_dualcamera_dsswb),we are not able to play HD videos.
We are using ipu2  for video decoding.

UseCase: weston_dualcamera_dsswb

Capture_0 -> Display_Video0
Capture_1 -> Display_Video1
DefLink_dispDist (A15) -> Display_Gfx
DefLink_dispDist_1 (A15) -> Display_vid1
Capture_dsswb -> Alg_SwCrc


Also we tried another (weston_dualcamera_screen)usecase, in that HD (1920*1080) videos playing for few seconds & then crashes. We also observe flickers while playing HD videos.

"UseCase: weston_dualcamera_screen"

Capture_0 -> Display_Video0
Capture_1 -> Display_Video1
DefLink_dispDist (A15) -> Display_Gfx
Capture_dsswb -> Alg_SwCrc

adv_high_mediaone_logs.txt


But We also have a similar usecase as below, running in dra744 Jacinto which has 7 inch display (800 *480).We don't find issues in this case.

DRA744 Jacinto & 7 inch display

Capture_0 -> Display_Video0
DefLink_dispDist (A15) -> Display_Gfx
DefLink_dispDist_1 (A15) -> Display_vid1
Capture_dsswb -> Alg_SwCrc

Can you please support on this issue ?

Regards,
Gokul

  • Hello Ram,

    I have verified the two pipelines, but no flickering observed.
    But when I run these pipelines getting these logs fro both pipelines:

    WARNING: from element /GstPipeline:pipeline0/GstWaylandSink:waylandsink0: A lot of buffers are being dropped.
    Additional debug info:
    /home/buildserver/work/jenkins/var/lib/jenkins/workspace/MMT2020_DB_Advanced_applinux/project/elina-distro/build-cpm-mmt-2020/tmp/work/cortexa15hf-vfp-neon-elina-linux-gnueabi/gstreamer1.0/1.6.3-r0/gstreamer-1.6.3/libs/gst/base/gstbasesink.c(2846): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstWaylandSink:waylandsink0:
    There may be a timestamping problem, or this computer is too slow.
    WARNING: from element /GstPipeline:pipeline0/GstWaylandSink:waylandsink0: A lot of buffers are being dropped.
    Additional debug info:
    /home/buildserver/work/jenkins/var/lib/jenkins/workspace/MMT2020_DB_Advanced_applinux/project/elina-distro/build-cpm-mmt-2020/tmp/work/cortexa15hf-vfp-neon-elina-linux-gnueabi/gstreamer1.0/1.6.3-r0/gstreamer-1.6.3/libs/gst/base/gstbasesink.c(2846): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstWaylandSink:waylandsink0:
    There may be a timestamping problem, or this computer is too slow.
    WARNING: from element /GstPipeline:pipeline0/GstWaylandSink:waylandsink0: A lot of buffers are being dropped.

    Regards,
    Ikshwaku
  • Hi Shravan,

    As you mentioned ,We added the hear beat -print message in IPU1 core . The Prints are comings from IPU1 core.(IPU1 is alive)

    But the display is in blank state.

    V_3_4_60FPS_LOGS.txt

    Regards,

    Gokul

  • Gokul, Ikshwaku,

    I believe that we are going back and forth on multiple issues on this ONE thread, and also adding more issues / questions on this one.

    Can we stick to only one problem per thread?

    The original problem stated in THIS thread was:
    (brief summary) application derived from 3.01 vision SDK fails to play fullHD videos on a a920x720 screen. The screen goes blank.

    Is the original problem resolved?
    If yes, lets close this thread.

    Also, please create more threads (one distinct problem per thread) for other issues that we are discussing here.

    Regards,
    Subhajit
  • Hi Subhajit,

    The issue (Flickers & Display Blank) is reproducible in 3.04 version also. We have shown this issue during the workshop (30 Jan 2019).

    Regards,
    Gokul
  • Yes, I am aware of that.
    However, lets close this thread for now as we are not actively pursuing this (3.01)

    We will reopen this if the issue is fixed in 3.04 and backporting those patches do not resolve the issue in 3.01.

    - Subhajit