- X3 REUNION CAUSINF WIN10 TO NOT LOAD DRIVER
- X3 REUNION CAUSINF WIN10 TO NOT LOAD SOFTWARE
- X3 REUNION CAUSINF WIN10 TO NOT LOAD CODE
I think at the end of the day this is still an Alsa problem, openal-soft
List of acceptable formats and Pulseaudio will figure out what is the Where instead of hardcoding a sample rate and format, you can give a I also tried using pa_stream_new_extended instead (see The problem appears as soon as OpenAL calls into pa_stream_new. I tried changing the hardcoded frequency and sample format to my nativeĪudio interface format, but the distorted audio still occurs. I looked into it but unfortunately it was a dead end again.
X3 REUNION CAUSINF WIN10 TO NOT LOAD SOFTWARE
What would be better, if I could set the sample rate that telegram requests from the system like in any decent audio software if I know what i'm doing (default to current sampling-rate by default add a tick "request sampling rate" on advanced menu). What ever the case may be, Telegram should respect the current sampling rate of the system and never ever try to change it on its own.
X3 REUNION CAUSINF WIN10 TO NOT LOAD DRIVER
Resetting the sample-rate back to what ever it was isn't that simple since it can't be done from my audio interfaces driver unless the audio device isn't being used at all (I have to shut down all applications using it first) It's even more infuriating since I have disabled sounds on telegram and thus the audio initialization routine is completely unnecessary. (48khz, 96khz or what ever I need or the project was made in) and every single time I start telegram it'll reset the sampling rate to 44.1khz and all the other programs are still expecting another sampling rate and audio is slowed down because of the mismatch. I use MOTU 828MKII audio interface for music production and I try to run my system on one single sampling rate no matter what. This is a huge issue on Windows 7 platform as well. If they can't support the frequency, just do nothing. And that is exactly what both methods shouldn't do.
X3 REUNION CAUSINF WIN10 TO NOT LOAD CODE
I am definitely sure the code that causes this problems is either media_audio_ffmpeg_loader#L201 or media_child_ffmpeg_loader#L72 as both have static comparisons of frequencies until they re-initialize the audio setup. Every single start of Telegram resets the device frequency, reproducible.
I cannot report or explain the bug in more detail, as this is exactly what happens. That is what Telegram is causing and no other App is causing. Any other application that plays back sound will be affected, even Chromium, Firefox, GNOME mplayer (and every other app you can imagine) because Telegram keeps resetting the goddamn frequency to 44.1kHz. So this is definitely a Telegram Bug, and nothing that is caused by the sound daemon. Yes, it is still the same issue on Debian Jessie, Ubuntu 16.10, ArchLinux and even on XFCE setups.
Yes everything is as up-to-date as possible as I'm using ArchLinux. Yes it is confirmed, the current version of Telegram is still causing the same problems. Eversince I reported this bug, this issue stays the same and is still causing troubles for devices that have no 44.1kHz frequency. Telegram keeps always resetting the frequency of the sound device, which it should not do. Every other application, even games, work perfectly without any issue. It is telegram, for absolutely nothing-else-breaks sure. I've been using the same identical setup for over 5 years now.
0 kommentar(er)
