[WIN] Debug Mode in the Measure app

The Measure app in Reference 4 features a Debug Mode, making it easier to investigate and fix particularly complex speaker measurement issues. The debug data will be essential for our support and development teams to figure out what exactly is causing the problem.

 

IMPORTANT! The Measure app requires very specific configuration aspects in terms of its interaction with your hardware/software and other third-party components. Settings that don't seem obviously related can turn out to be crucial for the Measure app to work. Most issues can easily be self-diagnosed and avoided using the Measure app troubleshooting guide instead.

 

_MSR__Win_-_Debug_Mode.png

 

The Debug Mode is found in the Measure app settings and can be used on its own. However, for a complete picture of the issue, the debugging process will need an additional step to it: escalating the logging environment of your PC. 

 

Follow these steps to collect the debug data:


1.
Download the two script files attached at the bottom of this article: 'Debug_logger_Measure.bat' and 'Disable_logger.bat'.

2. Right-click on the 'Debug_logger_Measure.bat' script file and choose 'Run as administrator'. A Microsoft Defender warning dialog will now pop up - click on More info > Run anyway. This will escalate the logging environment, clean up the logging history, and relaunch the Systemwide app. It will also open the debug log directory, making it easier to collect the files afterward:

_LOG__Win_-_Run__Debug_Logger_Measure_.bat.png_CMD__Script_-_More_info_-_Run_anyway.png

 

3. Measure app should now be re-launched in the escalated logging environment. Now click on Settings and enable the Debug Mode checkbox. Then click on Save and Close.

_MSR__WIN_-_Settings.png

_MSR__Win_-_Debug_Mode_2.png

 

4. Save and proceed with the speaker measurements up to the point where you're getting stuck. During this stage, feel free to take screenshots, video/audio captures of any errors or other problematic behavior, third-party component configuration aspects, or anything else you consider useful.

 

5. Exit Measure completely and collect the logs from the location opened previously. If the log directory has closed for any reason, relaunch Measure and click on Settings > Open debug folder. Collect the entire Logs folder content including the Dumps subfolder. You can also navigate to this directory manually:

C:\Users\your_username\AppData\Local\Sonarworks\Reference 4\Measure\Logs

_MSR__WIN_-_Debug_Logs___Dumps.png


6.
Collect the additional escalated environment log files form this location:

C:\Users\your_username\AppData\Local\Sonarworks\Logs

_MSR__WIN_-_Escalated_Logs.png


7.
 Run the 'Disable_logger.bat' file (attached at the bottom of this article) to de-escalate the logging environment.


8.
 Compress all collected data into a ZIP file (if you don't have any arriving solution available, use 7-Zip or other free archiving software). Submit a support ticket below and attach the logs to it. When submitting the ticket, be thorough with the information you provide in regards to the hardware, operating system, software, and any third-party components you're using (model names, version numbers, etc.).

 

Allow showing hidden files

N.B. The AppData folder on Windows is hidden by default - if you cannot access it, you'll need to enable the 'Show hidden items' setting in Windows Explorer:

  1. Click on View in Windows Explorer
  2. Check the Hidden Items checkbox
  3. Uncheck the 'Hidden items' checkbox to hide hidden items again!

_WIN__Show_Hidden_Files__2_.png

Attachments

  • Debug_logger_Measure.bat
    800 Bytes Download
  • Disable_logger.bat
    191 Bytes Download

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request

0 comments

Please sign in to leave a comment.