Playing with internal sound device it will blank the screen but playing to USB external DAC it wouldn't blank the screen.
Ah. So it is probably the USB or DAC driver that is stopping the screen from blanking.
Try this:
1. Open a Command Prompt using "Run as Administrator". i.e. Search for "cmd" in the Windows Taskbar search, right-click on the Command Prompt Desktop App result and select "Run as Administrator".
If that doesn't open a Command Prompt, which it may not depending on your Windows setup, right-click on the Command Prompt Desktop App result, select "Open file location", right-click on the "Command Prompt" shortcut and select "Open file location", then right-click on "cmd.exe" and select "Run as Administrator". That always seems to work. You may need to enter Administrator credentials at some stage.
2.
With MC closed, in the Command Prompt windows, run the command "powercfg /energy /trace". This will create a very detailed power management event log, energy-trace.etl, by default in the C:\Windows\System32 directory. It will run for one minute.
3. During the minute that the trace is running,
start MC and start playback of an audio file in Standard View, as you usually do.
4. When the trace finishes, stop playback in MC, then start the Windows Event Viewer. Use the "Open saved log" link on the right, search for "energy-trace.etl" on the C:\ drive, and select the file to open it. Windows will ask if you want to create a new converted event log copy. Just say Yes, and it will create a file called "energy-trace.evtx", Click OK on the "Open Saved Log" dialogue.
5. Click the "Filter Current Log" link on the right side, enter Event ID "62" in the appropriate box, and click OK. Event Viewer should show you all events where something has overridden the Power Management settings. It should give you some information about what made the change, either an application, process, or driver. I think you will find one event from MC, when it prevents the PC (tablet) from sleeping, but there should be one more, where something disables the screensaver. See if you can work out what the cause of the screen saver being disabled is from that.
I ran the above process but instead of playing audio I played a video in MC, as I know that will disable the screensaver and prevent the PC from going to sleep. Playing back audio will also cause MC to prevent the PC from going to sleep, so you should find an Event 62 for MC, plus one for whatever is stopping the screensaver from activating. At least I think it will, as I hope launching MC causes your USB external DAC driver to activation and set that power condition. But it may not show up in the trace, as the driver may already have set that power management state.
I can't find any way to check what actually disables the screensaver. Only how to detect a power management change.
See how you go with the above. I found out all the above just by some Googling, so if the above doesn't work, perhaps search for how to check what actually disables the screensaver.