Skip to main content
Use the bug-reporting portal linked from the StageMic website to report unexpected behaviour. A useful report explains what happened, what you expected and how to reproduce it.

​
During a performance

Prioritise the running show. Use manual scene selection or an established fallback where appropriate. Avoid restarting, updating or changing network settings during a performance solely to investigate a bug. Record the details when practical and submit the report afterwards.

​
Before reporting

Check the relevant troubleshooting page and the release notes. If you can reproduce the issue safely, note the shortest sequence of steps that causes it. Do not risk your only show copy while testing. Save a separate .mic backup before making experimental changes.

​
What to include

Provide:
  • StageMic version.
  • Operating system and version.
  • What you were trying to do.
  • Steps to reproduce the issue.
  • What you expected.
  • What actually happened.
  • Any exact error message.
  • Whether it happens consistently or intermittently.
For display problems, also include the device, browser and connection method. For OSC problems, include the controller, destination settings and message sent.

​
Suggested report format

Summary
A short description of the problem. Environment
StageMic version, operating system and any relevant display or controller details. Steps to reproduce
A numbered sequence someone else can follow. Expected result
What should have happened. Actual result
What happened instead. Attachments
Relevant screenshots, recordings or a minimal example show.

​
Attachments

Screenshots and short recordings can make interface problems easier to understand. For plotting issues, a small .mic file that reproduces the problem is often more useful than a large production file. If possible, replace real cast names with fictional names before sharing. Do not attach licence keys, Crew passwords, browser authentication cookies or the entire StageMic application-data folder. Check whether the portal entry and attachments will be public before submitting them.

​
Follow-up information

Support may ask for a smaller example, another screenshot or a test on a later version. Keep a copy of the affected show so that the issue can be investigated without altering your working production file.