Set alsa_device_name according to the capture and playback device when configuring streams so error messages reference the correct device
Ensure the device name is assigned before opening each stream to accurately report any ALSA errors
When “Use same device” is enabled, changing that setting now ensures the input device also supports playback, switching to the first bidirectional device if necessary
The input device dropdown hides devices lacking playback capability whenever the same-device option is active
The device change handlers now call “applyAlsaDevices” with the latest settings to recalculate latency and validation, ensuring UI state matches valid ALSA configurations
“applyAlsaDevices” accepts an optional same-device flag so callers can specify when input and output devices should be treated as identica
Updated the input and output device change handlers so new settings are validated through applyAlsaDevices, ensuring latency and OK status are refreshed
Added a new “useSameDevice” flag in the Jack server settings dialog state to track whether input and output devices are locked together
Initialized the flag based on whether the current configuration uses the same input and output device
Updated device handlers to mirror the input device into the output device when the toggle is enabled
Inserted a checkbox labeled “Use same device for input/output” into the dialog UI and hid the output selector when this option is active
Added new fields to track ALSA device capabilities, letting the application know whether a device supports capture or playback
Updated serialization to include the new flags in the JSON data exchanged with the UI
Modified the dummy driver so test devices always indicate capture and playback support
Adjusted the TypeScript model and dialog to filter device choices based on the new flags, ensuring only valid options appear in selectors
Summary
Added imports for the new refresh button in the JACK settings dialog, enabling quick reloading of ALSA devices without closing the dialog
Inserted an IconButton next to the audio device selectors so users can refresh the list on demand
The dialog now disables the device selectors and shows a “Loading…” placeholder until ALSA devices are available, preventing runtime errors during the initial render
Added helper functions to combine and intersect ALSA device capabilities, ensuring validation works across separate input and output devices
Updated buffer handling logic to use both selected devices and compute min/max sizes appropriately
Revised validation to check both ALSA input and output devices when enabling the OK button
Simplified rendering logic to intersect sample rates and buffer options for the chosen devices
AlsaDriver single device err calls fixed.
Added guidance on using USB audio interfaces or Raspberry Pi audio HATs and choosing separate ALSA input and output devices during setup
Clarified that the Audio Device Settings dialog allows independent configuration of input and output devices, with updated instructions for selecting audio channels
Summary
Ensured that checking for a query key now returns true when the key is found, allowing accurate existence checks
Added “&” separators when reconstructing query strings so that URIs are properly formatted with multiple parameters
Extremesecrecy