Feature requests: audio waveforms, multi-select bulk actions, blank/gap segments, optional auto-retrim on speed change, manual keyboard markers
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Ambito
- desktop
Direzione di ricerca
No files, tests, or entry points are named. Start by splitting the five timeline requests into separately scoped issues and locating the existing waveform, selection, gap, retiming, and zoom-point behavior. Done means each chosen capability has the expected timeline interaction and behavior described in the issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
I've been using Cap for editing and ran into several editor limitations. Filing them together since they're all related to timeline/track workflow. Happy to split into separate issues if maintainers prefer.
1. Show waveform for audio/music clips, not just video clips
Video clips on the timeline render a waveform, but standalone audio clips (music track / imported audio) either don't show a waveform or it's inconsistent. This makes it hard to align cuts to beats or spoken words without scrubbing back and forth.
Expected: Every audio-bearing clip (video's audio channel, music tracks, imported audio) should render the same kind of waveform as video clips do.
2. Multi-select clips, audio segments, or entire tracks for bulk delete/move
Currently each clip, audio segment, or track item requires individual selection and individual actions. There's no way to shift-click or drag-select multiple clips (or a whole track) and then delete or move them together.
Expected: Support marquee/shift-click multi-select across clips, audio pieces, and tracks, with bulk delete and bulk drag-to-move (keeping relative offsets between selected items).
3. Support empty/blank timeline segments (gaps) not tied to a clip, like DaVinci Resolve
Right now the overall timeline length seems to be driven entirely by the last clip's end — there's no way to insert a blank/black gap after the last clip. For example, I want the video to end but keep an audio track playing for several extra seconds over a black screen, without needing a filler video clip.
Expected: Allow inserting an empty gap segment (like DaVinci Resolve's blank/gap clips) that extends the timeline duration without requiring a video clip to fill it — rendering as black/silence where no video track covers it.
4. Make auto-trimming of other tracks on speed change (clip retiming) optional
When I change a clip's speed, other tracks (audio, overlays) on the timeline get automatically shortened/trimmed to match the new duration, which cuts and distorts prepared audio/other elements I didn't want touched.
Expected: Add a toggle (per-project or per-action) to disable automatic retiming/trimming of other tracks when a clip's speed changes, so unrelated tracks keep their original length and timing.
5. Allow manually adding a "Keyboard" marker/segment the same way Zoom points are added
Cap already supports zoom points added directly on the timeline, and there's keystroke overlay functionality, but adding a keyboard-indicator point manually (independent of an auto-captured keystroke) doesn't work the same way zoom points do.
Expected: Let users add a "Keyboard" marker/segment directly on the timeline the same way Zoom points are added — same interaction pattern (click to add, drag to position/resize).
I'd be happy to work on one (or more) of these myself. If a maintainer could point me to which of these are most wanted / not already being worked on, I'll pick one up and submit a PR. Happy to start with whichever is lowest priority for the core team to tackle themselves.
- Lingua principale
- Rust
- Stelle
- 22.5k
- Fork
- 1.9k
- Merge medio
- 7h 43m
- PR unite (30g)
- 80
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di CapSoftware/Cap
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
CapSoftware/Cap#2305 · 2 commenti ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
CapSoftware/Cap#1714 · 3 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
CapSoftware/Cap#2340 · 1 commento ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
CapSoftware/Cap#2339 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
CapSoftware/Cap#2329 · 2 commenti ·
Tutte le issue di CapSoftware/Cap
Issue simili
-
bug github_actions
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
registrystack/registry-stack#1393 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
longbridge/gpui-kit#3223 ·
-
bug engine
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
rocky-data/rocky#2181 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
oasisprotocol/oasis-sdk#2523 ·
-
[indexer] [QA] Add a focused test for the new NonRetryableError / assertSocketAlive() behavior. Apertabot:ai-assisted component:indexer QA-roadmap status:untriaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
midnightntwrk/midnight-indexer#1557 ·