When a VVAS GStreamer plugin is loaded, VVAS core log messages are forwarded to the GStreamer debug system. Use GST_DEBUG to select VVAS core categories and the standard GStreamer variables to control log output.
Example:
export GST_DEBUG="2,vvas_xinfer:5,vvas_core_*:5"
export GST_DEBUG_FILE=/tmp/run.log
export GST_DEBUG_NO_COLOR=1
gst-launch-1.0 <pipeline>
The vvas_core_* pattern enables messages from all VVAS core modules. You can also select individual modules:
Category |
VVAS core source |
|---|---|
|
Common and VVAS context modules |
|
VVAS parser module |
|
VVAS video decoder module |
|
VVAS image processing module |
|
VVAS core inference module |
|
VVAS core postprocess module |
|
VVAS MetaConvert module |
|
VVAS overlay module |
|
VVAS MetaAffixer module |
|
VVAS tracker module |
|
All VVAS core modules |
If VVAS_CORE_DEBUG is unset when the VVAS plugin loads, the logging bridge sets it to 5. This allows the GST_DEBUG category thresholds to control the VVAS core messages. If VVAS_CORE_DEBUG is set explicitly, the VVAS core library filter is applied first. Messages filtered by the library are not forwarded to GStreamer.
Use GST_DEBUG_FILE to write the bridged logs to a file. If it is not set, the logs are printed to the console. Set GST_DEBUG_NO_COLOR=1 when the output is intended for machine processing.
Logs without a module basename use the fallback vvas_core category.
Note
VVAS_CORE_LOG_FILE_PATH controls file, console, or syslog output for
standalone VVAS core applications. It does not select the output
destination for VVAS core messages forwarded by the GStreamer logging
bridge. For GStreamer pipelines, use GST_DEBUG_FILE.