# Long offline renders: what's normal, and two things that bite

**URL:** <https://restem.discourse.group/t/long-offline-renders-whats-normal-and-two-things-that-bite/21>\
**Category:** Help & Support\
**Created:** [August 11, 2026, 3:36am UTC](https://restem.discourse.group/t/long-offline-renders-whats-normal-and-two-things-that-bite/21 "2026-08-11T03:36:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rim](https://yyz1.discourse-cdn.com/flex009/user_avatar/restem.discourse.group/rim/32/20_2.png) [@Rim](https://restem.discourse.group/u/Rim)\
**Post date:** [August 11, 2026, 3:36am UTC](https://restem.discourse.group/t/long-offline-renders-whats-normal-and-two-things-that-bite/21/1 "2026-08-11T03:36:50Z")

</div>

**What’s normal:** Best quality on a long song is heavy. With a supported GPU it’s usually minutes; on CPU-only machines a full song can take a long time — the progress bar and ETA keep moving the whole way.

**Two things that bite:**

1. **System sleep.** If your computer sleeps mid-render, the render stalls or looks impossibly slow afterwards. Set your machine not to sleep for long renders (ReStem keeps the machine awake during a render on current versions, but screensaver and lid-close policies vary).
2. **“It’s stuck at 99%.”** The last phase (MIDI trigger detection) on very long files can take a few minutes with the bar sitting near the top — give it time before force-quitting, and update to the latest version, which keeps the progress display moving through this phase.