[bug] Disconnecting device while active causes stuck state

[Wheels35]

What happened?

One of the microphone devices I had connected was my AirPods Pro and upon disconnecting while a pipeline is active, the app correctly says 'device is no longer connected', but then changes the pielines visual state to 'Activate' while actually staying active.

Steps to reproduce

1. Activate pipeline with a microphone device
2. Disconnect device while pipeline is running
3. See error message and watch pipeline switch to 'Activate' from 'Deactivate', pipeline is still 'working'

Expected behavior

I expected either the pipeline to keep working with a disconnected device, or correctly deactivate the pipeline

App version

v1.1.0

Operating system

macOS

OS version

Tahoe 26.6.2

Additional context

On this, i would love an option to be able to set the device able to be 'disconnected' while a pipeline is active. This way i can switch beween devices (like airpods) without ever needing to reinitialize it. I can open an improvement request if needed.

[Horuse]

Thank you for taking the time to create this issue

I will implement this as you suggested (as I understand it): the pipeline will remain active if the device is disconnected, and will automatically resume streaming as soon as your device reconnects, without the need for manual activation.

The fix will be included in the next release.

[Wheels35]

Thank you for taking the time to create this issue

I will implement this as you suggested (as I understand it): the pipeline will remain active if the device is disconnected, and will automatically resume streaming as soon as your device reconnects, without the need for manual activation.

The fix will be included in the next release.

I'm assuming that means the plan is that in my setup, two input devices (A and B) in the pipeline, A goes off, the pipeline will still work for B. The if A reconnects, it will start feeding back into the pipeline?

[Horuse]

Exactly. Dropping device A won't affect device B, and reconnecting A will plug it straight back into the running pipeline. If all inputs disconnect, it will just idle with silence until one reconnects, avoiding manual restarts. Any thoughts on this approach are welcome

[Wheels35]

Thats perfect, maybe a checkbox on the card to 'Enable auto-reconnect on this' or something? That way those that might not want the feature, even though I don't know why you wouldn't if the pipeline is running, could toggle it.

I think this is great otherwise, that way i can have my pipeline just always working, and connect and disconnect the devices depending on what im doing where. I have other devices that this feature will enable useage without having to build separate pipelines depending on the device im using.