Tdesktop: Audio transmission is completely broken

Created on 16 Aug 2020  Β·  63Comments  Β·  Source: telegramdesktop/tdesktop

Steps to reproduce

  1. Receive or initiate a call
  2. Video is working normally
  3. Audio is silent for both sides

Expected behaviour

Both parties hear each other

Actual behaviour

No sound for both sides

Configuration

Operating system:
Tested on three PCs: Windows 10, two on 1909, one on 2004
Version of Telegram Desktop:
2.3
Used theme:
null (theme name)

Details

I called my PC (1) tofrom two different phones with TG Android 7.0.0 and from PC 3 with TD 2.3. In all the cases I had no sound for both sides. Complete silence.
I also tried calling from PC 3 with old TDesktop, I could hear it, but they couldn't.
PC2: tried with phones only, no sound both sides.
PC3: complete silence with PC1 (both 2.3). Unexpected: PC3 was working both sides with both phone 1 and 2.

bug
Source
picture 0xCA
👍4 😕1

Most helpful comment

I found out some interesting thing about non-working microphone. By default it's set to 2ch 24bit 192kHz by Windows. TDesktop can't work with it. The limit is 96kHz. Once I set it to 96kHz or lower (16 or 24 bits), it started working. Note for "Call Settings" screen: after any adjust in system settings, change your input device selection to something else and back to see if it's working.

picture 0xCA on 13 Sep 2020
👍4 🎉2

All 63 comments

I also Tested with Telegram (v7.0) in iPhone (SE v1) and Windows 7. Got exactly what you got, no sound from none of the sides

casa98 picture casa98 on 17 Aug 2020

This is happening on Linux too (v2.3) (on ArchLinux x86_64 on Kernel 5.7.12)

skoglar picture skoglar on 17 Aug 2020

Greetings!

I just downloaded the latest (2.3) version of the Telegram, but I can not make any calls because there is no in/out audio on the app since version ~1.9 .

I just got these lines when I try microphone test:

error: : cannot open
error: : cannot open
error: : cannot open
E/tgvoip: Error connecting to audio device ''
W/tgvoip: PulseAudio available but not working; trying ALSA
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM 
QTextCursor::setPosition: Position '-1' out of range

Audacity works fine with ALSA (I can record and play).
Teamspeak works fine with PulseAudio.

Linux IFAPC 4.19.0-0.bpo.6-amd64 #1 SMP Debian 4.19.67-2+deb10u2~bpo9+1 (2019-11-12) x86_64 GNU/Linux

iFA88 picture iFA88 on 17 Aug 2020

I just got these lines when I try microphone test

Microphone test is broken, don't trust it. #7296

ilya-fedin picture ilya-fedin on 17 Aug 2020

I just got these lines when I try microphone test

Microphone test is broken, don't trust it. #7296

Oh, I have tested again, a complete reinstall has solved my problem.

iFA88 picture iFA88 on 17 Aug 2020

Maybe you had set a non-existing device in settings Β―_(ツ)_/Β―

ilya-fedin picture ilya-fedin on 17 Aug 2020

i tried to call from android 10 (LOSQ) and telegram android 7 build 2064 to windows 10 (unknown version) and worked for me.

Aokromes picture Aokromes on 17 Aug 2020

i tried to call from android 10 (LOSQ) and telegram android 7 build 2064 to windows 10 (unknown version) and worked for me.

I tried to reinstall but it doesn't help (as I describe it here https://github.com/telegramdesktop/tdesktop/issues/8511)

2.2 version works well

metkram picture metkram on 27 Aug 2020

I also confirm that 2.3.0 and 2.3.1 breaks audio transmission on Windows 10 Version 1903 (OS Build 18362.1016) in both directions, be it either Android or iOS on the other side. Video transmission works though.

The only workaround is to revert back to 2.2.0. And forbid app to update automatically of course.

This is a major regression and critical defect.

If you need any logs, feel free to request it with corresponding instruction on how to gain them.

Deilan picture Deilan on 30 Aug 2020

Updating to Win10 2004 fixes this, anything with 1909 remains silent.

0xCA picture 0xCA on 1 Sep 2020

Using Windows 10 2004 version and Telegram Desktop 2.3.1 but when calling either from PC to Android or Android to PC both calls are complete silent... Reinstalling Telegram on PC didn't worked and tried different input/output devices in call settings.

semihsmg picture semihsmg on 2 Sep 2020

I have updated windows to 2004 and "silent issue" is still here

metkram picture metkram on 2 Sep 2020

I have the same problem and not sure how to solve it, waiting for update to solve it

zaid894 picture zaid894 on 6 Sep 2020

So far I "fixed" TD on 3 PCs by upgrading them to 2004.

0xCA picture 0xCA on 6 Sep 2020

I found out some interesting thing about non-working microphone. By default it's set to 2ch 24bit 192kHz by Windows. TDesktop can't work with it. The limit is 96kHz. Once I set it to 96kHz or lower (16 or 24 bits), it started working. Note for "Call Settings" screen: after any adjust in system settings, change your input device selection to something else and back to see if it's working.

0xCA picture 0xCA on 13 Sep 2020
👍4 🎉2

I found out some interesting thing about non-working microphone. By default it's set to 2ch 24bit 192kHz by Windows. TDesktop can't work with it. The limit is 96kHz. Once I set it to 96kHz or lower (16 or 24 bits), it started working. Note for "Call Settings" screen: after any adjust in system settings, change your input device selection to something else and back to see if it's working.

As I found out my mic can't reach above 16 bit, 48kHz but I changed speakers settings to 24bits, 96kHz. Then restarted TDesktop and now calls working as intended...
For me the issue is solved. Thank you 0xCA

semihsmg picture semihsmg on 13 Sep 2020

As I found out my mic can't reach above 16 bit, 48kHz but I changed speakers settings to 24bits, 96kHz. Then restarted TDesktop and now calls working as intended...
For me the issue is solved. Thank you 0xCA

You're absolutely right. I think we actually found it. Output is limited at 96 kHz as well. They both have to not exceed the limit.
Updating to 2004 made that thing: it reset everything to lowest possible bitrate and that was the true reason why it was "fixed".

0xCA picture 0xCA on 13 Sep 2020
👍1

Looks like the library just doesn't support frequency higher than 96KHz

ilya-fedin picture ilya-fedin on 13 Sep 2020

I found out some interesting thing about non-working microphone. By default it's set to 2ch 24bit 192kHz by Windows. TDesktop can't work with it. The limit is 96kHz. Once I set it to 96kHz or lower (16 or 24 bits), it started working. Note for "Call Settings" screen: after any adjust in system settings, change your input device selection to something else and back to see if it's working.

you're a man. Thanks, now it works

metkram picture metkram on 14 Sep 2020

to the ones still having problems, can you try the last post of:
https://www.tenforums.com/sound-audio/148115-how-do-i-reset-sound-settings-windows-10-a.html

Aokromes picture Aokromes on 14 Sep 2020

it's not supporting my microphone array, a single channel microphone works while the defaults microphone of my laptop isn't supported by the used library

zaid894 picture zaid894 on 14 Sep 2020

There is no sense to use microphone array since mono audio stream is used anyway

ilya-fedin picture ilya-fedin on 14 Sep 2020

it's pre-installed in my asus laptop already and I have to connect an external microphone to solve the problem

zaid894 picture zaid894 on 14 Sep 2020

it's pre-installed in my asus laptop already

Why there is no compatibility layer for applications that support only classic microphones then?

ilya-fedin picture ilya-fedin on 14 Sep 2020

The only app that doesn't work is telegram desktop, there must be something wrong in the library

zaid894 picture zaid894 on 14 Sep 2020

The only app that doesn't work is telegram desktop, there must be something wrong in the library

Are you talking about calls or voice messages? Calls are using google's webrtc library, chrome should have the same issues with web apps for calls. Voice messages are using openal and... I can't remember any other app that uses openal on Windows.

ilya-fedin picture ilya-fedin on 14 Sep 2020

The only app that doesn't work is telegram desktop, there must be something wrong in the library

Are you talking about calls or voice messages? Calls are using google's webrtc library, chrome should have the same issues with web apps for calls. Voice messages are using openal and... I can't remember any other app that uses openal on Windows.

I had no issues with google hangouts

metkram picture metkram on 14 Sep 2020

I had no issues with google hangouts

Oh, looks like they are using their own internal audio methods for webrtc (why am I not surprised πŸ™„)

ilya-fedin picture ilya-fedin on 15 Sep 2020

again, the ones still having problems, can you try the last post of:
tenforums.com/sound-audio/148115-how-do-i-reset-sound-settings-windows-10-a.html

Aokromes picture Aokromes on 15 Sep 2020

I am talking about the calls only , vioce messages works perfectly and I already tried resetting widows sounds

zaid894 picture zaid894 on 15 Sep 2020

same problem! I have an external USB audio interface and an external USB microphone. Voicemail works well both ways. But when I call, I do not hear my interlocutor, while he hears me normally.
Other applications do not have this problem.
Can I tell the program the output device for the call?

Mac OS 10.14.6
Telegram 7.0.1 (205092) Beta

x-tropic picture x-tropic on 22 Sep 2020

2.2.0 works fine for me. (without video calls)

x-tropic picture x-tropic on 22 Sep 2020

same problem! I have an external USB audio interface and an external USB microphone. Voicemail works well both ways. But when I call, I do not hear my interlocutor, while he hears me normally.
Other applications do not have this problem.
Can I tell the program the output device for the call?

Mac OS 10.14.6
Telegram 7.0.1 (205092) Beta

try this out https://github.com/telegramdesktop/tdesktop/issues/8443#issuecomment-691675354

in most cases it helps

metkram picture metkram on 22 Sep 2020

same problem! I have an external USB audio interface and an external USB microphone. Voicemail works well both ways. But when I call, I do not hear my interlocutor, while he hears me normally.
Other applications do not have this problem.
Can I tell the program the output device for the call?

Mac OS 10.14.6
Telegram 7.0.1 (205092) Beta

you don't use telegram desktop (telegram lite on macos) instead telegram for macos.

Aokromes picture Aokromes on 22 Sep 2020

you don't use telegram desktop (telegram lite on macos) instead telegram for macos.

I have already installed version 2.3.1.
will test.

x-tropic picture x-tropic on 22 Sep 2020

I guess what the problem is. In the system settings, audio-midi is 32-bit depth 44100. I cannot change this parameter, most likely telegram limits support to 24 bits?

x-tropic picture x-tropic on 24 Sep 2020

I guess what the problem is. In the system settings, audio-midi is 32-bit depth 44100. I cannot change this parameter, most likely telegram limits support to 24 bits?

it depends what external audio interface do you use
in my case (focusrite), I decreased it in the ASIO control panel

metkram picture metkram on 24 Sep 2020

I guess what the problem is. In the system settings, audio-midi is 32-bit depth 44100. I cannot change this parameter, most likely telegram limits support to 24 bits?

it depends what external audio interface do you use
in my case (focusrite), I decreased it in the ASIO control panel

I have a rme babyface. If I find an opportunity to change this setting to mac os, then I will write here about the result.

x-tropic picture x-tropic on 24 Sep 2020

I guess what the problem is. In the system settings, audio-midi is 32-bit depth 44100. I cannot change this parameter, most likely telegram limits support to 24 bits?

it depends what external audio interface do you use
in my case (focusrite), I decreased it in the ASIO control panel

I have a rme babyface. If I find an opportunity to change this setting to mac os, then I will write here about the result.

maybe it'll help https://www.rme-audio.de/downloads/bface_pro_e.pdf

metkram picture metkram on 24 Sep 2020

I found out some interesting thing about non-working microphone. By default it's set to 2ch 24bit 192kHz by Windows. TDesktop can't work with it. The limit is 96kHz. Once I set it to 96kHz or lower (16 or 24 bits), it started working. Note for "Call Settings" screen: after any adjust in system settings, change your input device selection to something else and back to see if it's working.

In my case both input (Playback) and output (Recording) are both limited by 16 bit, 48 kHz. But the issue is still present anyway.

Deilan picture Deilan on 25 Sep 2020

webrtc :+1: /s

ilya-fedin picture ilya-fedin on 25 Sep 2020

I guess what the problem is. In the system settings, audio-midi is 32-bit depth 44100. I cannot change this parameter, most likely telegram limits support to 24 bits?

Enable debug logs by entering debugmode in settings like a cheat code, make a call and check last_call_log.txt in DebugLogs folder of your tdesktop profile folder (%APPDATA\Telegram Desktop on Windows, ~/.local/share/Telegram Desktop on generic Linux installs (non-snap, non-flatpak), I don't know where it is on Mac)

ilya-fedin picture ilya-fedin on 25 Sep 2020

I guess what the problem is. In the system settings, audio-midi is 32-bit depth 44100. I cannot change this parameter, most likely telegram limits support to 24 bits?

Enable debug logs by entering debugmode in settings like a cheat code, make a call and check last_call_log.txt in DebugLogs folder of your tdesktop profile folder (%APPDATA\Telegram Desktop on Windows, ~/.local/share/Telegram Desktop on generic Linux installs (non-snap, non-flatpak), I don't know where it is on Mac)

last_call_log.txt.zip

x-tropic picture x-tropic on 25 Sep 2020

(audio_device_mac.cc:101): Error in AudioConverterFillComplexBuffer(): -1-1-1-50

x-tropic picture x-tropic on 25 Sep 2020

Seems to be a webrtc bug
https://webrtc.googlesource.com/src/+/refs/heads/master/modules/audio_device/mac/audio_device_mac.cc#2230
https://webrtc.googlesource.com/src/+/refs/heads/master/modules/audio_device/mac/audio_device_mac.cc#2470

I don't know where is their bugtracker though

ilya-fedin picture ilya-fedin on 25 Sep 2020
👍1

Looks like I found: http://bugs.webrtc.org/

ilya-fedin picture ilya-fedin on 25 Sep 2020
🎉1

Oh, i searched around their bugtracker and looks like their audio backends for demo purposes only and tdesktop should have its own audio backend for webrtc
https://bugs.chromium.org/p/webrtc/issues/detail?id=10622#c3
https://bugs.chromium.org/p/webrtc/issues/detail?id=10537#c2

ilya-fedin picture ilya-fedin on 25 Sep 2020

I'm having a similar issue https://github.com/telegramdesktop/tdesktop/issues/8648, and was told to move the discussion here.

All sounds work fine but it goes silent for both sides as soon as I make or get a call.

Default device set, telegram call setting set and tested πŸ‘‡ as you can see here

Zwmnxeu0pm

Logs:

[2020.09.28 12:56:14] Launched version: 2003001, install beta: [FALSE], alpha: 0, debug mode: [FALSE]
[2020.09.28 12:56:14] Executable dir: D:/Telegram/, name: Telegram.exe
[2020.09.28 12:56:14] Initial working dir: D:/Telegram/
[2020.09.28 12:56:14] Working dir: D:/Telegram/
[2020.09.28 12:56:14] Command line: D:\Telegram\Telegram.exe
[2020.09.28 12:56:14] Executable path before check: D:/Telegram/Telegram.exe
[2020.09.28 12:56:14] Logs started
[2020.09.28 12:56:14] Connecting local socket to Global\c2764e6f12b4016e432fe963325d797e-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2020.09.28 12:56:14] This is the only instance of Telegram, starting server and app...
[2020.09.28 12:56:14] Moved logging from 'D:/Telegram/log_start0.txt' to 'D:/Telegram/log.txt'!
[2020.09.28 12:56:14] Primary screen DPI: 96
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAOpenSansRegular.ttf' loaded 'DAOpenSansRegular'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAOpenSansRegularItalic.ttf' loaded 'DAOpenSansRegularItalic'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2020.09.28 12:56:14] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2020.09.28 12:56:15] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2020.09.28 12:56:15] App Info: reading settings...
[2020.09.28 12:56:15] App Info: reading encrypted settings...
[2020.09.28 12:56:15] Lang Info: Loaded cached, keys: 2723
[2020.09.28 12:56:15] OpenAL Logging Level: (not set)
[2020.09.28 12:56:15] Audio Playback Devices: OpenAL Soft on Speakers (2- Sound BlasterX G6);OpenAL Soft on VoiceMeeter Aux Input (VB-Audio VoiceMeeter AUX VAIO);OpenAL Soft on VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)
[2020.09.28 12:56:15] Audio Playback Default Device: OpenAL Soft on Speakers (2- Sound BlasterX G6)
[2020.09.28 12:56:15] Audio Capture Devices: OpenAL Soft on External Mic (2- Sound BlasterX G6)
[2020.09.28 12:56:15] Audio Capture Default Device: OpenAL Soft on External Mic (2- Sound BlasterX G6)
[2020.09.28 12:56:15] App Info: reading accounts info...
[2020.09.28 12:56:15] App Info: reading encrypted info...
[2020.09.28 12:56:15] App Info: reading map...
[2020.09.28 12:56:15] App Info: reading encrypted map...
[2020.09.28 12:56:15] App Info: reading encrypted user settings...
[2020.09.28 12:56:15] App Info: encrypted user settings read.
[2020.09.28 12:56:15] App Info: reading encrypted mtp data...
[2020.09.28 12:56:15] MTP Info: read keys, current: 4, to destroy: 0
[2020.09.28 12:56:15] Map read time: 0
[2020.09.28 12:56:15] App Info: reading encrypted mtp config...
[2020.09.28 12:56:15] Export Info: Destroy top bar by controller removal.
[2020.09.28 12:56:16] Message Info: bad message notification received (error_code 33) for msg_id = 6877475191079621176, seq_no = 36
[2020.09.28 12:56:16] Message Info: bad message notification received, msgId 6877475191079621176, error_code 33
[2020.09.28 12:56:36] Error: could not locate 'background.jpg' in a zip file.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡²πŸ‡« is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡²πŸ‡« is not supported, word: flag.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: diego garcia.
[2020.09.28 13:04:35] API Warning: emoji πŸ§‘β€πŸ€β€πŸ§‘ is not supported, word: bf.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: ta.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: ascension island.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: ac.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: flag_ac.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: tristan da cunha.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: british indian ocean territory.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: flag_ta.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡²πŸ‡« is not supported, word: st. martin.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: ceuta & melilla.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡²πŸ‡« is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡²πŸ‡« is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: ΨΉΩ„Ω….
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: Ψ£Ψ³ΩŠΩ†Ψ΄ΩŠΩ†.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ΉπŸ‡¦ is not supported, word: ΨͺريسΨͺΨ§Ω† Ψ―Ψ§ ΩƒΩˆΩ†Ψ§.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡©πŸ‡¬ is not supported, word: دييغو غارسيا.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: Ψ³Ψ¨ΨͺΨ© ΩˆΩ…Ω„ΩŠΩ„ΩŠΨ©.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡¦πŸ‡¨ is not supported, word: جزيرة Ψ£Ψ³ΩŠΩ†Ψ΄ΩŠΩ†.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: Ω…Ω„ΩŠΩ„ΩŠΨ©.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡ͺπŸ‡¦ is not supported, word: Ψ³Ψ¨ΨͺΨ©.
[2020.09.28 13:04:35] API Warning: emoji πŸ‡²πŸ‡« is not supported, word: Ψ³Ψ§Ω†Ψͺ Ω…Ψ§Ψ±ΨͺΩ†.
[2020.09.28 13:06:37] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:06:39] Audio Info: Closing audio playback device.
[2020.09.28 13:06:50] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:06:52] Message Info: bad message notification received (error_code 33) for msg_id = 6877477922251037772, seq_no = 136
[2020.09.28 13:06:52] Message Info: bad message notification received, msgId 6877477922251037772, error_code 33
[2020.09.28 13:06:52] Audio Info: Closing audio playback device.
[2020.09.28 13:06:52] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:06:56] Audio Info: Closing audio playback device.
[2020.09.28 13:07:17] Message Info: bad message notification received (error_code 33) for msg_id = 6877478029613228004, seq_no = 48
[2020.09.28 13:07:17] Message Info: bad message notification received, msgId 6877478029613228004, error_code 33
[2020.09.28 13:07:23] App Info: writing encrypted user settings...
[2020.09.28 13:07:23] Message Info: bad message notification received (error_code 33) for msg_id = 6877478055412725288, seq_no = 40
[2020.09.28 13:07:23] Message Info: bad message notification received, msgId 6877478055412725288, error_code 33
[2020.09.28 13:40:52] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:40:54] Audio Info: Closing audio playback device.
[2020.09.28 13:41:03] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:41:17] Call Info: Creating instance with version '2.7.7', allowP2P: [TRUE]
[2020.09.28 13:41:18] Call Error: Unexpected state in handleStateChange: 4
[2020.09.28 13:41:19] Audio Info: Closing audio playback device.
[2020.09.28 13:41:32] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:41:33] Audio Info: Closing audio playback device.
[2020.09.28 13:43:42] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:43:44] Audio Info: Closing audio playback device.
[2020.09.28 13:43:45] Audio Info: recreating audio device and reattaching the tracks
[2020.09.28 13:43:47] Audio Info: Closing audio playback device.
dtheb picture dtheb on 28 Sep 2020

Do the devs know that this issue exist? Have they stated something about it?

iocomxda picture iocomxda on 11 Oct 2020

The issue is still there I hope it's solved soon

zaid894 picture zaid894 on 25 Oct 2020

The issue is still there I hope it's solved soon

Yes, i currently switched to Discord because of this problem. Unbelievable.

iocomxda picture iocomxda on 26 Oct 2020

v2.4.7 on win 10 still not working

TEXHIK picture TEXHIK on 24 Nov 2020
👍1

How to fix this bug ?

Nawoth-Th picture Nawoth-Th on 30 Nov 2020

How to fix this bug ?

sadly it's not fixable yet

zaid894 picture zaid894 on 30 Nov 2020

I'm experiencing the same issue on 2.4.7 / w10.

amon picture amon on 7 Dec 2020
👍1

I'm experiencing the same issue on 2.4.7 / W10 20H2. The voice messages work well but the microphone doesn't work in the calls.

jeverduzco picture jeverduzco on 10 Dec 2020
👍1

Still not solved

zaid894 picture zaid894 on 11 Dec 2020
👍1

Same here

MarouaneMan picture MarouaneMan on 13 Dec 2020

is someone actually working on this ?

MarouaneMan picture MarouaneMan on 13 Dec 2020

is someone actually working on this ?

AFAIK, no

ilya-fedin picture ilya-fedin on 13 Dec 2020

Reverted back to 2.2.0, working as expected !

MarouaneMan picture MarouaneMan on 14 Dec 2020

Reverted back to 2.2.0, working as expected !

How did you solve? I tried to download 2.2.0 but it doesn't have the videocall option (as it's outdated).

iocomxda picture iocomxda on 14 Dec 2020

Reverted back to 2.2.0, working as expected !

How did you solve? I tried to download 2.2.0 but it doesn't have the videocall option (as it's outdated).

I had the problem with voice only calls, i'm not using video, reverting to 2.2.0 was suffisent to fix it.

MarouaneMan picture MarouaneMan on 14 Dec 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

abhyrz picture abhyrz  Β·  3Comments
ghost picture ghost  Β·  3Comments
TheAppService picture TheAppService  Β·  3Comments
qwitriy picture qwitriy  Β·  3Comments
FunctionalHacker picture FunctionalHacker  Β·  3Comments