Skip to content

ship cutting a stretch out of a recording, plus cleanup and preset renames - #19

Merged
noxend merged 24 commits into
mainfrom
simplify-config
Aug 15, 2026
Merged

ship cutting a stretch out of a recording, plus cleanup and preset renames#19
noxend merged 24 commits into
mainfrom
simplify-config

Conversation

@noxend

@noxend noxend commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Closes #1.

Cuts a stretch out of a recording via a .cuts sidecar next to the video, one range per line. mark-cuts Quick Action opens it for editing. 0-0:20 cuts the first 20s, 2:30-end cuts from 2:30 to the end.

Found and fixed three bugs going back over it: an out-of-bounds range said "cut applied" but did nothing, a locked source could leave its .cuts sidecar archived without the video, and the near-miss warning could flag an unrelated file with a similar name.

Rest is cleanup from the same stretch of work: output_dir gone, output/ is a symlink, filenames come from the preset name now, chat renamed to tiny, new sharp preset for higher quality.

noxend added 18 commits August 13, 2026 12:45
a name that says what it does to the file, not where it is going;
'chat' left the reader to infer 'small' with no clue in the menu itself
closes the gap chat/tiny left: nothing pushed crf the other way, and a
reviewer reading a diff or dense UI needs that more than a small file
a plain word beats an abbreviation in a menu with no room for a tooltip
noxend added 6 commits August 13, 2026 13:05
the setting itself was already dropped when output naming switched to the
preset name; this example line in the shipped config was missed at the time
ffmpeg's trim= just clamps an out-of-bounds range to the real length, so it
was accepted, logged as 'cut applied', and shipped the source untouched;
found reviewing PR #19 before merge, since this is exactly the redaction
use case the feature exists for
the two mv calls were independent statements, so a locked or
permission-denied source left its sidecar archived alone while the video
stayed stuck in input/; found reviewing PR #19 before merge
a bare prefix glob also matched an unrelated recording sharing the first
few characters of its name, e.g. clip.mov / clip 2.mov, and warned about a
sidecar that was never meant for the file being processed; found
reviewing PR #19 before merge
0-0:20 already worked (0 is unambiguous), so only the end side needed
anything new. A bare trailing dash (2:30-) would have worked too, but a
leading one (-0:20) reads exactly like a negative number to anyone who
has not read this file's own rules -- end is a real word instead
@noxend
noxend merged commit 4ed2c4c into main Aug 15, 2026
2 checks passed
noxend added a commit that referenced this pull request Aug 15, 2026
ffmpeg's trim= just clamps an out-of-bounds range to the real length, so it
was accepted, logged as 'cut applied', and shipped the source untouched;
found reviewing PR #19 before merge, since this is exactly the redaction
use case the feature exists for
noxend added a commit that referenced this pull request Aug 15, 2026
the two mv calls were independent statements, so a locked or
permission-denied source left its sidecar archived alone while the video
stayed stuck in input/; found reviewing PR #19 before merge
noxend added a commit that referenced this pull request Aug 15, 2026
a bare prefix glob also matched an unrelated recording sharing the first
few characters of its name, e.g. clip.mov / clip 2.mov, and warned about a
sidecar that was never meant for the file being processed; found
reviewing PR #19 before merge
@noxend
noxend deleted the simplify-config branch August 15, 2026 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cut arbitrary ranges out of a video, via a .cuts sidecar file

1 participant