Skip to content

Troubleshooting

Most issues resolve with one step: right-click the tray icon → Restart all, then wait for green.

The tray icon is stuck on orange

Services are still starting. Give it 30–60 seconds. If it stays orange:

  1. Right-click the tray icon → Restart all.
  2. Wait for green before continuing.

If it turns red, a service has errored. Right-click → Open logs folder and check the log for the failing service.

The studio shows a service as not ready

The status dots in the studio (Runtime, TTS, Render) reflect whether the background engine is up. If one is not green:

  • Check the tray icon colour first — if it's not green, wait or restart.
  • If the tray is green but the studio still shows an issue, close and reopen the studio app.

Voice generation isn't working

  • Check you're in Edit Mode, not Render Mode — voice generation is paused during renders. Right-click the tray → Mode: Edit to switch back.
  • Check the TTS status dot in the studio is green.
  • If a render queue run just finished, allow 10–20 seconds for voice services to come back online.

A voice take came out wrong

This is normal — the voice model varies between attempts. Just regenerate. For long or complex lines, split the speech into shorter clips and regenerate only the piece that's off. See What to expect.

A render came out unsatisfactory

Add the take to the queue again — each attempt is independent. If you had a good render before and want to reproduce it exactly, use its seed.

A render is taking far too long

A full ten-second clip should render in about 15–20 minutes (shorter clips proportionally faster). If a render runs well past that, the graphics memory has likely saturated and the job is stagnating — this can happen after many renders in a row:

  1. Click Abort and confirm.
  2. Run the queue again. If it keeps happening, restart via the tray (Restart all) and let the team know.

Rendering is very slow or runs out of memory

  • Only one render runs at a time — this is by design.
  • Make sure nothing else is using the graphics card during a render (browsers, other apps, Topaz).
  • If you see out-of-memory errors, check that the system has fully switched to Render Mode before the queue runs (tray green, voice services stopped). The pre-render check normally handles this for you.

When reporting an issue

The more context, the faster the fix. Mention which project and which take you were working on and what you were doing when it happened — the team can then match it against the logs directly.

Where to find logs

Right-click the tray icon → Open logs folder. One log file per service. Logs are reset each time the launcher starts, so they cover the current session only.