Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request] Editor media library + audio processing (speed & pitch for audio segments)

Aperta
  • Qualcosa non va?
#2,357 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

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
Stack tecnologico
react, rust, tauri, typescript
Ambito
audio-video-rtc, desktop

Direzione di ricerca

Start by tracing the editor's existing media pickers, timeline asset handling, and video-clip speed controls; the issue does not name specific files or tests. Review related issue #2328 and PR #2308 for existing timeline and waveform work. Done means the scope is agreed or split, with library persistence, compatible drag-and-drop reuse, and standalone audio speed and pitch behavior covered.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Description

Two editor workflow gaps in Cap 0.6.1 (Windows). Video clips already have speed
control with "Keep pitch" audio handling — this request is about bringing similar
processing to standalone audio segments, plus a central media library.

1. Media library panel in the editor

Right now, importing media happens through one-off pickers (audio picker, image
import), and imported items land directly on the timeline. There is no persistent
library panel inside the editor where assets live while editing.

Expected: a "Media" / "Library" panel (sidebar or dockable) where users can:

  • Import files via button or drag-and-drop from Explorer/Finder (video, audio, images)
  • See imported assets persisted across editing sessions in the project
  • Drag assets from the library onto any compatible timeline track (video → clip/
    video track, audio → audio track, image → image track), reusing the same asset
    on multiple tracks without re-importing

2. Audio processing for standalone audio segments

Audio segments (background music, imported audio) currently only support volume
and fade in/out. Meanwhile video clips already offer speed with three audio modes
(mute / keep pitch / match speed) — none of that applies to audio segments.

Expected:

  • Audio speed: time-stretch an audio segment (e.g. 0.25x–4x), with a
    pitch-preservation option, consistent with the existing clip speed UX
  • Pitch shift: adjust pitch in semitones (e.g. -12 to +12) for creative
    effects or key-matching music to a voiceover, independent of speed
  • Ideally exposed in the same right-click / settings panel as clip speed
Reproduction
  1. Open the editor for any Studio recording.
  2. Add an audio file to an audio track and right-click it: only volume/fade/
    split actions are available — no speed or pitch controls.
  3. Look for a media library panel to collect and re-drag imported files: none
    exists; assets must be re-imported through pickers each time.
Additional Context
  • Cap version: 0.6.1
  • Operating system, version: Windows 11 (x64)
  • Related: #2328 (timeline/audio feature requests), PR #2308 (imported media
    tracks & waveforms) — a library panel would complement that work nicely.

Happy to split into separate issues if maintainers prefer.

Lingua principale
Rust
Stelle
22.8k
Fork
2k
Merge medio
8h 10m
PR unite (30g)
83

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CapSoftware/Cap

Tutte le issue di CapSoftware/Cap

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.