Plugin API: third-party DSP and playback events #21

Closed
opened 2026-10-06 21:16:50 +02:00 by SBDeveloper · 1 comment
Owner

Part of #13

What to build

A third-party Plugin can process audio and react to playback events, on the same API the bundled Plugins use. UI views from Plugins are covered by #45 (declarative plugin UI and slots), not here.

Acceptance criteria

  • DSP Plugin alters the audio path
  • Playback events delivered to consented Plugins
  • Core integration tests with fixture Plugins

Blocked by

Part of #13 ## What to build A third-party Plugin can process audio and react to playback events, on the same API the bundled Plugins use. UI views from Plugins are covered by #45 (declarative plugin UI and slots), not here. ## Acceptance criteria - [ ] DSP Plugin alters the audio path - [ ] Playback events delivered to consented Plugins - [ ] Core integration tests with fixture Plugins ## Blocked by - #19
SBDeveloper changed title from Plugin API: third-party UI views and DSP to Plugin API: third-party DSP and playback events 2026-10-07 19:53:24 +02:00
Author
Owner

Implemented in 3bb36c9: extension plugin kind with audio_processing (process export in the decode path) and playback_events (on_event) capabilities, consent-gated, with fixture plugin tests in crates/core/tests/extensions.rs. UI views are left to #45.

Implemented in 3bb36c9: extension plugin kind with audio_processing (process export in the decode path) and playback_events (on_event) capabilities, consent-gated, with fixture plugin tests in crates/core/tests/extensions.rs. UI views are left to #45.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
SBDeveloper/medley#21
No description provided.