Settings - Debug
- 30 Jan 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Settings - Debug
- Updated on 30 Jan 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This tab is usually only used for debugging of the application.
- Enable debug level logging - If activated, the application will log debug messages
- Enable debug features in GUI - Enable debug buttons in the GUI, under the “Performance” panel.
- Show debug properties - This will show debug properties in the Composer GUI when any debug properties are available. These are usually very technical and sometimes not described in the documentation.
- FFmpeg log level - Set the default log level of FFmpeg. The FFmpeg logs will posted to the Composer log.
Debug option in settings.xml
- "EnablePerformanceDebugLog": true - Composer will create a .csv file in the application folder (The file will have a name similar to: Performance-Debug-20240130 210123.csv). The CSV file will every frame log the following performance properties: DateTime, Frame, CongestionsLastSecond, NumCongestionsSinceStart, ProcessingTime, MaxProcessingTime, AverageProcessingTime, AverageProcessingTimeLong, ProcessingQueSize, NumAuthorizedApiCalls, NumErrors and NumWarnings.
Enabling this feature will continuously write metrics to the disk. Make sure to turn it off, as leaving it on may eventually cause the disk to run out of free space.
Was this article helpful?