Skip to main content
A StageMic show is the allocation plan for a production: its scenes, characters, actors and mics, together with who wears each mic in each scene. StageMic saves shows using the .mic extension.

​
What a show file contains

A .mic file includes:
  • The production name.
  • Scenes and their order.
  • Characters and their order.
  • Actors and their character links.
  • Numbered mics.
  • Scene-by-scene allocations.
  • Explicit Mic table assignments.
  • Intentional multiple-mic approvals.
  • The incomplete-handover alert setting.
Scenes also have internal identifiers. These keep scene-specific OSC addresses attached to the correct scene when you rename or reorder it.

​
What is stored separately

The following belong to the controlling computer and are not included in a .mic file:
  • Licence activation.
  • Display and OSC network settings.
  • The Crew password and remembered Crew access.
  • Handover completion records.
Sending someone a show file does not send your licence or Crew password. It also does not transfer the completion ticks from a performance.

​
Opening a show

Use Load to open a .mic file. Where the operating system associates .mic files with StageMic, you can also double-click a file to open it. StageMic asks whether you want to save the current show before replacing it. Cancelling leaves the current show open.

​
Moving and sharing shows

A .mic file can be copied, emailed or moved between computers. The receiving computer needs its own valid StageMic activation to open the editor. Configure its network settings separately and check the backstage displays before use. Show files can contain cast names and production information. Check that you are happy to share those details before sending a file.

​
File format

A .mic file contains JSON data internally. The custom extension identifies it as a StageMic show. You do not need to edit this data manually. Use StageMic to make changes so that allocations, scene identifiers and related information remain consistent.

​
Backups

Autosave protects your current work, but it is not a history of previous versions. Use Save to keep separate backups, particularly before major plotting changes or an application update. Descriptive filenames make versions easier to identify, for example: Example Production — Before Technical Rehearsal.mic See Saving, Autosaving, and Loading.