Connect UI and Processor

[OpenSauce]

[Copilot]

Pull Request Overview

This PR connects the GUI layer to the audio processor by wiring up ProcessorManager into the application start-up and update flow.

• Implements Debug for ProcessorManager to expose key internal state
• Changes start to accept a ProcessorManager instance and removes the old “Start” message
• Adds a flag-driven update that calls ProcessorManager::set_amp_chain after any stage change

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/io/manager.rs	Added a Debug impl for ProcessorManager showing sample_rate and recorder presence
src/gui/amp.rs	Changed start signature to take ProcessorManager, removed Start button and message, added should_update_chain logic and update_processor_chain method

Comments suppressed due to low confidence (4)

src/io/manager.rs:96

• [nitpick] The Debug field is named recorder but prints a boolean. Consider renaming the field to has_recorder or include the actual recorder state for clarity.

.field("recorder", &self.recorder.is_some())

src/gui/amp.rs:402

• [nitpick] Remove the commented-out Start button code to clean up dead code.

-            button("Start").on_press(Message::Start),

src/gui/amp.rs:365

• Add tests to verify that update_processor_chain correctly invokes set_amp_chain on ProcessorManager, ensuring UI updates propagate to the processor layer.

fn update_processor_chain(&self) {

src/gui/amp.rs:18

• Changing the start function signature to require a ProcessorManager is a breaking API change; update any external callers and documentation accordingly.

pub fn start(processor_manager: ProcessorManager) -> iced::Result {

[Copilot]

[nitpick] Consider consolidating the repeated should_update_chain = true; assignments in each message arm—perhaps by returning an indication from each variant or using a helper method—to reduce duplication and improve readability.