A good bug report lets the problem be reproduced and fixed on the first try, without a long back-and-forth. This page shows what to collect and where to send it; most reports take five minutes.
Check first
Collect the details
Detail | Where to find it |
Orfeo version | Bottom of Setup, for example |
Build | Installer or portable. The portable file is named |
Windows version | Press |
Sound engine |
|
MIDI keyboard | Its make and model, if the bug involves one |
Write the steps to reproduce
Describe the shortest path from opening Orfeo to seeing the bug, one action per line:
Say whether it happens every time or only sometimes, and whether it happens with other songs too.
Attach what helps
Copy errors from the developer console
Orfeo logs technical errors to a hidden console. Copying them into your report often points straight at the cause.
IMAGE · support-devtools-console.png · 1400 × 800 px · Orfeo with the developer tools open on the right, the Console tab selected and one red error line highlighted.
Tip
The console is read-only for this purpose. Don’t type or paste anything into it; just copy what is already there.
Send the report
If you | Send it to |
Have a GitHub account | GitHub Issues: click New issue and paste your report |
Don’t have one | The contact form, or email [email protected] with your files attached |