The window stopped responding, or the program disappeared. Both leave a trace behind; this page is about not losing it.
When the window stops responding
From version 1.1.6 the program keeps watch on its own interface. When it has stopped responding for 5 seconds — about when Windows turns the window white — the log records where it is stuck. It records that again at 30 seconds, then a line every minute, and one more line when the window comes free, with how long it stood still.
The second record is the useful one: it shows whether the program was stuck in one place, or still moving but far too slowly.
A shutdown that hangs is watched too: after 15 seconds of closing, the log records where it is stuck.
When it closed unexpectedly
At the next start, before anything else, a window titled Ultimate Playout stopped unexpectedly says Ultimate Playout did not shut down cleanly last time. — or A module stopped unexpectedly last time. — and asks whether to send a report to the developer.
The report contains the error details, the log of that session, the version numbers, the country and a fingerprint of this computer. No name and no IP address — but the log can contain file paths, and those often include the Windows user name. That is why it asks every time: nothing is sent without Yes, and with No everything keeps working as usual.
A window you forced closed counts too: to the program, that session did not end cleanly.
What to do
- Wait up to 30 seconds before force-closing a frozen window. It often comes free by itself; if it does not, the log by then says where it hung and whether it was still moving.
- At the next start, answer Yes to the report if you can.
- Send the log of that session, with the time it happened — see sending logs. The report goes to the developer; whoever supports your installation needs the log.