How to enable the "trace" module

[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.

[U1X6WK]

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.

[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!

[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

[U1X6WK]

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

6. 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

7. You will find trace log at /root/lttng-traces/