-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
bug: input device from call settings should also be used for voice message recording #26489
Comments
A possible solution is to use
tdesktop/Telegram/SourceFiles/media/audio/media_audio_capture.cpp Lines 245 to 246 in 8bd9293
#include "settings/settings_calls.h"
// ...
using Settings::CurrentAudioInputName;
d->device = alcCaptureOpenDevice(CurrentAudioInputName().toLatin1().data(), kCaptureFrequency, AL_FORMAT_MONO16, kCaptureFrequency / 5); It builds, but I cannot test whether it works, because it does not link on my system for the following reason (perhaps, a protobuf 23.4 related issue Cockatrice/Cockatrice#4825):
UPD: fixed by changing
|
No, it shouldn't as it's clearly specified as call settings. |
tdesktop's and tg_owt's CMAKE_BUILD_TYPE must match. |
Well, then maybe a "voice message input device" setting should be introduced? 😄 |
There's already a feature request for that |
I can't seem to find it, could you please reference the issue or PR? |
Steps to reproduce
Expected behaviour
Telegram should respect it's own settings :)
Actual behaviour
The application fallbacks to system's default input source avoiding any streams from the configuration.
While changing the settings:
When recording a vocie message:
system settings:
Operating system
EndeavourOS Linux 6.4.1-arch2-1
Version of Telegram Desktop
4.8.4-2
Installation source
Other (unofficial) source
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: