Confusing UX in WhisperAX selectedTask picker

[elliottburris]

UX Feedback
When I first tried the WhisperAX example, the behavior of the .disabled state here was confusing.

Steps to Reproduce:

1. Select a multilingual model.
2. Set the selectedTask to Transcribe.
3. Switch to an .en model (English-only).

Observed Behavior:
The segmented control picker remained disabled and stuck on Translate, even though the .en model is English-only and doesn’t support that task. This created confusion because the picker’s disabled state wasn’t visually clear, and the selected option (Translate) didn’t reflect the actual selectedTask being used.

Expected Behavior:
When switching to an .en model:

• The picker should visually update to reflect the correct selectedTask (e.g., Transcribe).
• The disabled state should be clearer to the user, or the picker should update dynamically to prevent confusion.

Additional Notes:
I’m happy to submit a PR but would appreciate guidance on the intended UX pattern for handling these settings. Should the picker dynamically reflect the current selectedTask, or should the disabled state be improved to make it more intuitive?

[ZachNagengast]

This would be a good PR! You're right the picker should go back to how it should be for a non-multilingual model, not just disabled, especially if someone changed it while it was previously enabled.