Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#2,357 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
react, rust, tauri, typescript
Bereich
audio-video-rtc, desktop

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
23.4k
Forks
2.1k
Ø Merge
1 T. 18 Std.
Gemergte PRs (30 T.)
252

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CapSoftware/Cap

Alle Issues in CapSoftware/Cap

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.