Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding the 'Listening' device of the 'Recording' input device #1527

Open
SomunsMo opened this issue Jun 20, 2024 · 0 comments
Open

Regarding the 'Listening' device of the 'Recording' input device #1527

SomunsMo opened this issue Jun 20, 2024 · 0 comments
Labels
Enhancement Issue which are a enhancement

Comments

@SomunsMo
Copy link

What workfow do you want to improve?

After my mandatory triggering rule takes effect, the 'Listen' device I set for 'Recording' will become 'Default Playback Device' (I don't want this to happen). I have tried not running 'SoundSwitch', and at this time, the 'Listening' device of my 'Recording' is the 'ASUS CU4K30' I want

How to make it better?

I have two ideas, hoping to achieve one

  1. I want to change the 'Recording' device without changing the 'Listen' device I previously set.
  2. I would like to set the 'Listen' device for the 'Recording' device, regardless of whether the set 'Listen' device is currently in the 'Not plugged in' state.

Any alternative?

I have tried not to use 'SoundSwitch', and although the issue has been resolved, every time my computer starts up, there is another issue: the 'Playback' and 'Recording' devices are set to 'ASUS CU4K30' (this is a feature of the new firmware version of ASUS devices. I have tried to provide feedback to the manufacturer, but they have not provided a useful solution).

Additional context

After replying to ASUS, I implemented the plan they provided, but it was not ideal. So I gave them a solution (there is currently no other solution), which is to use 'SoundSwitch' to force the desired input and output devices.

If you feel it's not necessary to do this feature, then I'm sorry for causing you unnecessary trouble.
Anyway, I am grateful for being able to read my issue.

@SomunsMo SomunsMo added the Enhancement Issue which are a enhancement label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Issue which are a enhancement
Projects
None yet
Development

No branches or pull requests

1 participant