When something needs explaining, the log is what explains it. This page says where to find it and what to send alongside.
Where it is
C:Program FilesUltimate Playoutengineconfigobs-studiologsOne file per run, named by date and time. The one you want is the run in which it went wrong — so send it before restarting the program a dozen times, or the right file is buried.
What is in it
Everything the program did, in order:
- Which modules were found and which are active.
- Which outputs were set up, on which device, and whether they started.
- Every GO: which cue, which type, which transition.
- Warnings about files, devices and encoders.
- If the window froze: where it was stuck.
That is usually enough to answer the question without anybody having to reproduce anything.
What to send with it
Four things, and they take a minute:
| Send | Where to find it |
|---|---|
| The log of the run it happened in | The folder above |
| The program version and the engine version | Settings → Info |
| What you saw, in your own words | — |
| When, to the minute if you can | — |
That last one matters more than it sounds: with a time, the relevant twenty lines can be found in a file of thousands.
What is not in it
Your rundown is not in the log, and neither is your media. If the question is about a specific list, send the .playout as well — it is a few kilobytes.
Passwords are not in it. Stream keys and the remote-control password are in the settings, not in the log.
File paths are, though. Those often contain the Windows user name — check before posting a log publicly.
The report after a crash
After the program closed unexpectedly, it asks at the next start whether to send a report to the developer — see it froze or closed unexpectedly. That report does not reach whoever supports your installation, so send them the log as well.
Before you send
If it is reproducible, do it once more and note the time. A log with a known moment in it is worth more than three logs of vaguely similar sessions.
If it is not reproducible, send what you have anyway. The line about which outputs started, and the GO lines around the moment, are often enough on their own.