CutBench 1.0.9: one fight, one clip, and YouTube uploads that resume

Plus what arrived without notes since 1.0.2: a new interface, written captions on 6 GB cards, achievements.

Fights are no longer cut in two at their peak, a YouTube upload picks up where it stopped after a dropped connection, and a 6-8 GB card on a light desktop stops waiting in the middle of a job. These are also the first patch notes since 1.0.2, so the second half covers what arrived quietly in between. Runs locally, no subscription.

One fight, one clip

• A fight is no longer cut in two at its peak: it comes back as one clip, from the first kill to how it ends.
• With the 30-second ceiling gone, a clip ends where its story ends.
• After a death, a clip ends on the screen that follows it instead of running on past it.
• A recording of 90 seconds or less, such as a saved replay, becomes one clip: the whole file.
• The hook text stays inside the frame, on the video and on its thumbnail.

Subtitles and captions

• The language of a recording is worked out from speech across the whole recording instead of only its first 30 seconds of speech, so a few English words at the start of a Russian stream no longer decide its language.
• Each hashtag appears once in the description instead of repeating the caption's own tags, and the clips and planned posts already in the app are cleaned up once, on the first launch.
• Raid wording and the #raid and #base tag suggestions, left over from the survival games CutBench was first tested on, are gone.

YouTube

• An upload that loses its connection picks up where it stopped instead of failing at the first drop.
• If it still fails, the message says the connection was cut, not that YouTube rejected the video.
• Uploads follow the Windows proxy setting, the way TikTok already did. If that proxy can't be reached, the upload goes direct, as before.
• When YouTube's daily upload limit is reached, the post moves to the nearest free slot on a day with room, instead of every held-back post going out at 9:00 the next morning.

6-8 GB cards

With a light desktop, a job on a 6-8 GB card no longer stops for up to 20 minutes partway through, waiting for graphics memory, and carries straight on. START ANYWAY in the graphics memory dialog now skips that wait, and when memory really is short, the wait ends after five minutes in which nothing gets freed.

Since 1.0.2

Changes in versions 1.0.3 to 1.0.7, which went out without notes:

• The new interface opens each job as a grid of clips with a panel for the selected one, and publishing asks for one set of choices per batch.
• 6-8 GB cards get written titles and descriptions too, so the 10 GB line in the 1.0.2 notes no longer applies.
• Subtitles catch much more of what is said, and a clip never starts or ends in the middle of a word.
• Before a job starts, the app checks the graphics memory and names the programs holding it.
• 14 Steam achievements, with past activity counting on the first launch after the update.
• A GET STARTED strip walks through six steps, from connecting YouTube to a week of scheduled posts.
• English captions: far fewer repeated stock lines, no title cut mid-word, no caption ending on a dangling word.
• Emoji now show in the caption fields.
• Closing the app no longer crashes it.

Thanks to the beta tester whose report prompted several of these fixes. If a clip comes out wrong, post it in the Discussions with the recording's length and your graphics card.

Originally posted on Steam on 26 October 2026: read it there