Skip to content
This repository was archived by the owner on Jul 22, 2025. It is now read-only.
This repository was archived by the owner on Jul 22, 2025. It is now read-only.

How to enable the "trace" module #77

Open

Description

@kuroneko306

I have sccessfully run the OMAF-Sample and stream 4K tiled immersive video through network.

However, I have trouble trying to activate the "trace" module and output trace data.
The "USE_TRACE" option set to "OFF" by default in "/Immersive-Video-Sample-master/src/CMakeLists.txt" has been modified to be "ON" before make, but there is still trouble output trace log files.
There is still no any trace log file exist in the docker container after video streaming.

Any help on telling what may resolve the problem will be appreciated.

Activity

  1. U1X6WK commented on May 5, 2022

    @U1X6WK
    Contributor

    Can you provide the output of ldd /usr/local/lib/libVROmafPacking.so | grep trace to make sure library linking is correct?

    Also you can try to add -DUSE_TRACE=ON in this line.

  2. htliu6 commented on Jun 10, 2022

    @htliu6

    @kuroneko306 Hi, I have already acquired the trace log about E2E delay. Is there anything I can help you?

    BTW, @U1X6WK, have you successfully ran the shell script generate_client_bandwidth_summary.sh? I have some trouble when executing babeltrace2 ust/ > downloaded_trace.txt, i.e.,

    No trace was found based on input ust/.

    Do you know how to fix it? Thanks!

  3. congnguyen commented on Jun 27, 2022

    @congnguyen

    Dear @U1X6WK I have same problem. Please make short guide to run trace module with script generate_client_bandwidth_summary.sh. Thank you so much

  4. U1X6WK commented on Jun 29, 2022

    @U1X6WK
    Contributor
    1. Change this line to ON).
    2. Change this line to cmake -DCMAKE_BUILD_TYPE=Release -DTARGET=server -DDE_FLAG=true -DUSE_SAFE_MEM_LIB=OFF -DENABLE_MSDK=OFF -DUSE_TRACE=ON ../...
    3. Change this line to cmake -DCMAKE_BUILD_TYPE=Release -DTARGET=client -DUSE_TRACE=ON ../../.
    4. Build server and client.
    5. Execute following commands on server side:
    lttng-sessiond --daemonize
    lttng create packing_trace
    lttng enable-event --userspace bandwidth_tp_provider:initial_viewport_info
    lttng enable-event --userspace bandwidth_tp_provider:tiles_selection_redundancy
    lttng enable-event --userspace bandwidth_tp_provider:encoded_frame_size
    lttng enable-event --userspace bandwidth_tp_provider:packed_segment_size
    lttng enable-event --userspace bandwidth_tp_provider:segmentation_info
    lttng start
    # Your server command
    lttng destroy
    1. Execute following commands on client side:
    lttng-sessiond --daemonize
    lttng create downloaded_trace
    lttng enable-event --userspace bandwidth_tp_provider:initial_viewport_info
    lttng enable-event --userspace bandwidth_tp_provider:tiles_selection_redundancy
    lttng enable-event --userspace bandwidth_tp_provider:encoded_frame_size
    lttng enable-event --userspace bandwidth_tp_provider:packed_segment_size
    lttng enable-event --userspace bandwidth_tp_provider:segmentation_info
    lttng enable-event --userspace bandwidth_tp_provider:extractor_track_dependent_info
    lttng enable-event --userspace bandwidth_tp_provider:download_info
    lttng start
    # Your client command
    lttng destroy
    1. You will find trace log at /root/lttng-traces/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions