Refocused 1.0.10: retry for failed chapters, segmentation on Windows, and bug fixes

Refocused 1.0.10 is out now for all platforms. This update is primarily bug fixes, but we also updated some functionality with regards to chapters.

Retry failed chapters

Chapters mode splits a long video at scene cuts, runs each chapter as its own job, and stitches the results back together. Until now, when one chapter failed, the run stopped with an error. The finished chapters and the per-chapter pieces stayed on disk, and the only way to finish was to re-run that chapter by hand and stitch the result yourself.

In 1.0.10 the other chapters keep going when one fails, and the status line under the settings says which chapter failed. Once they are done, the status line shows the error and a Retry failed chapters button. Retry re-runs only the chapters that did not finish, and starts each one from the stage that failed: if Refocus finished but Regenerate-Q failed, Regenerate-Q and the stages after it run again, and Refocus does not. It then stitches every stage and deletes the pieces as usual. The run is kept when you leave the Enhance page or restart the app, and finished chapters are remembered even if the engine restarts. To get back to a run, open the same source in Enhance.

Retry works for chapters runs started in 1.0.10 or later.

Bug fixes

Segmentation Issues on Windows

In 1.0.8 and 1.0.9, Refine's segmentation masks (the Objects mask tool) never started on Windows, with either NVIDIA or AMD GPUs. The segmentation engine ships with the Windows app, but the app only started it on macOS and Linux. On AMD, the Model Library also listed Segmentation as Not installed, and its Install button did nothing, because the app did not recognize how the AMD segmentation model is packaged.

1.0.10 starts segmentation on Windows and recognizes the AMD model, including the copy already on your disk, so there is nothing to reinstall. The mask tool also falls back to an installed model size when the size picked in Refine is not installed. On Windows and Linux, Essentials installs the Small model, while the default size was Tiny. On Linux, that meant the first mask failed until you switched the model size to Small.

Additional Fixes

• Windows with an NVIDIA GPU: constant background load with no job running. The Activity screen and the engine read GPU statistics by starting nvidia-smi through a command shell, several times a second. Together they started about 450 short-lived processes a minute (nvidia-smi.exe, cmd.exe and conhost.exe), and Microsoft Defender scanned each one. That showed up in Task Manager as CPU and disk activity from Refocused and Defender while nothing was running. The app now keeps a single nvidia-smi running while the Activity screen is open, and the engine calls it directly without a shell, once per sample. That brings it to about 56 process starts a minute on our test machine. The app also stops collecting these statistics while its window is minimized or closed to the tray.
• The app could stop responding when the video player stalled. Every call to the video player waited for the player to answer, so a player that stopped responding froze the whole app. One report came from Windows: Compare opened to a black view, and the app stopped responding. The app now sends commands to the player without waiting and reads the playback position from a cache. If a player stops answering for about 10 seconds, that view switches to the app's built-in player. We could not reproduce the original report, so if you see it again, please send us the app log described below.
• macOS 27: the Neural Engine gauge always read 0%. On the Activity screen, the Neural Engine gauge showed 0% for every job on macOS 27, including Regenerate-Q jobs that run their encoder and decoder on the Neural Engine. macOS 27 no longer updates the power reading the gauge was based on, so it now uses the Neural Engine's activity, which macOS still reports. When no reading is available, the gauge shows "—" instead of 0%. macOS 26 and earlier keep the power reading.
• Refine: no quality choice for ProRes. The encoder settings in Refine's Reprocess and Mix hid the quality row for the ProRes encoders. They now offer the same six profiles as the Output card in Enhance, from 422 Proxy to 4444 XQ, and picking a profile sets the matching pixel format.
• Compare: moving the wipe while zoomed in. Above 100% zoom, a Pan/Wipe toggle decided what dragging did, and it was set to Pan by default. Now dragging always moves the wipe, and right-drag or middle-drag pans. On a trackpad, Option-drag (Alt-drag on Windows) pans. The toggle is gone, and the zoom control shows Drag: wipe · Right-drag: pan.
• Grain & noise: the Restore grain amount was reset. Switching the Grain & noise card from Restore grain to Denoise and back reset the Restore grain amount to the default (50%). The card now keeps the amount you set.
• A log file for the app itself. The app now writes its own log, refocused_app_main.log, next to the engine log. It is in %APPDATA%\RefocusedApp\output on Windows, ~/Library/Application Support/RefocusedApp/output on macOS and ~/.config/RefocusedApp/output on Linux. It also records video player problems. When you report an issue, please include both logs.

Thank you

Thanks for the bug reports and feedback this cycle, and we appreciatee your support as a customer! We are excited and working hard on the V2 model suite, but will be prioritizing existing issues, so if you run into any problems, don't hesitate to reach out!

To update, download the latest build from the install page, or use the in-app updater in Settings → Application.