Cut middle sections: pipeline 'cut' op with ranges, and Cut selection in the review player
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 42/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Read src/utils/pipelineStep.ts and src/utils/pipelineRun.ts to see how pipeline operations are defined and executed, then trace the keep-list path in src/utils/transcriptCut.ts and inspect the selection and export flow in assets/ui/player.js. Run the existing pipeline tests and add coverage for merging overlapping or unsorted ranges and for the new operation. Done means cuts retime sidecars and keep audio in sync, and the player can add, list, undo, and export multiple cut ranges.
由索引模型根据 Issue 内容生成。
描述
Summary
Neither the review player nor pipeline can remove a stretch from the middle of a recording. The player has a single IN/OUT pair, and the pipeline trim op keeps one segment. Removing "the 20 s where I typed my password" or "the wrong turn at 1:10" needs a multi-range cut.
Where
assets/ui/player.js:168-173, 368-369(oneinI/outIpair, exported as onetrim)src/utils/pipelineStep.ts:21-26(trim:start,end/durationonly)src/tools/cutByTranscript.ts:17(removecuts ranges, but only by quoting transcript text)src/tools/cutIdle.ts(cuts ranges, but only ones it detects itself)
Details
The cut machinery already exists inside cut_idle and cut_by_transcript (keep-list, concat, audio kept in sync, sidecars retimed), but there is no way to say "remove 12.0-31.5 and 70-74" directly.
Suggested fix
- Add a pipeline op
{ op: "cut", ranges: [{ start, end }, ...] }(andremoveontrimif that fits better) that reuses the cut_idle / transcript-cut keep-list path. Markers, event logs, and.edit.jsonretime the same way. - In the player, add Cut selection: select a range on the timeline and press it (or
X) to mark it removed. Removed ranges are shaded, listed, and can be undone. Export sends onecutstep afterredactand beforetrim.
Acceptance criteria
-
pipelineacceptscutwith overlapping and unsorted ranges, and merges them - Output duration = input − removed; audio stays in sync
- Player can mark, list, and remove several cut ranges, by keyboard as well as by pointer
- Tests for range merging and the pipeline op
Getting started
- Relevant files:
src/utils/pipelineStep.ts,src/utils/pipelineRun.ts,src/utils/transcriptCut.ts,assets/ui/player.js - Run
npm run docsafter changing the pipeline schema
Filed by repo-audit/feature-ideas at 1ac339f. Severity: high. Effort: M. audit-key: enhancement|src/utils/pipelineStep.ts|cut
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 4
- 平均合并
- 8 小时 17 分钟
- 30 天内合并 PR
- 46
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/screencast-mcp 的其他 Issue
-
effort: small good first issue priority: medium testing
难度 2/5 1-3 小时 新手友好度 84/100
TMHSDigital/screencast-mcp#351 · 2 条评论 ·
维护者通常 1 天内回复
-
effort: small enhancement good first issue priority: low
难度 3/5 1-2 天 新手友好度 72/100
TMHSDigital/screencast-mcp#380 ·
维护者通常 1 天内回复
-
effort: medium enhancement help wanted priority: medium
难度 4/5 3-5 天 新手友好度 56/100
TMHSDigital/screencast-mcp#379 ·
维护者通常 1 天内回复
-
effort: medium enhancement help wanted priority: medium
难度 4/5 3-5 天 新手友好度 57/100
TMHSDigital/screencast-mcp#378 ·
维护者通常 1 天内回复
-
Review player: limit a redaction box to a time window可能已有人在做 @lucky0559 于 2 天前认领。 未关闭effort: small enhancement good first issue priority: medium
难度 4/5 3-5 天 新手友好度 25/100
TMHSDigital/screencast-mcp#377 ·
维护者通常 1 天内回复
查看 TMHSDigital/screencast-mcp 的全部 Issue
相似的 Issue
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)未关闭
难度 2/5 1-3 小时 新手友好度 62/100
microsoft/playwright#44289 ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 半天 新手友好度 65/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
blamechris/chroxy#9272 ·
维护者通常 1 天内回复
-
no-repo-link tool-submission
难度 1/5 1 小时以内 新手友好度 66/100
BraveOPotato/NoSignups#2458 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
drmrd/vernacular#1061 ·
维护者通常 1 天内回复