-
Notifications
You must be signed in to change notification settings - Fork 30
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
Not listening to the recording device #55
Comments
Thanks. I'm not sure what goes wrong. |
Just a quick update since I still cannot repro on demand, but the recording device dropdown doesn't change. Still the same device selected and same devices available on the dropdown. Current version 2.4.13. |
Not sure if anything changed here, but I haven't had that happen with 2.4.15 knock on wood. Will close if I don't see it happen again. |
Nothing has changed in the capturing/recording for a while (latest change was in version 2.2)! |
OK, and as expected it's still happening. Still no repro. It's not the starting order of apps, nor it's sleep/wake. Since a restart of DAS always fixes it, how about a workaround to reset the audio capture at regular intervals? Maybe as a command-line option? My other alternative is to automatically restart DAS but that's got a couple of big downsides: since I can't use groups, one of the speakers will occasionally fail to initialize and I won't see that if unattended. And the connect sound from each speaker at every restart will get annoying for sure. |
With 2.4.5 (however not a new issue) intermittently the program may stop listening to the Recording Device. The dB meter will not show any signal even though the audio is playing through the recording device. Once this happens it won't recover, but a simple restart will always fix the issue. It's noticeable since I run 24/7.
I'll update if I can get a reliable repro.
The text was updated successfully, but these errors were encountered: