![jitsi voice jitsi voice](https://i0.wp.com/karada-house.de/wp-content/uploads/2020/03/meditation.jpg)
But that is difficult to say since Musicians also definitely do want lowest possible latencies… That could even eliminate loudness differences when Speakers are moving around (and thus, change their audio level which is of course massively influenced by the distance to the Microphone)įor Musician Purposes, some kind of Compander Logic to reduce needed Bandwidth could be a good Idea, too. To get really improvements for speaker Conferences, using some sophisticated massive Dynamics (Multiband Noise Gate, Compressor. Of course, it would be even better if he could switch “on the fly” since even in a Clarinet Lesson there may be some talking time and som play time. He will know if he is doing some Insurance Sales Meeting or a Clarinet Lesson and can decide. It would be a good Idea to allow the Moderator of a conference to set defaults for most of these switches. For example, if someone plays a decrescendo with activated AGC - the decrescendo can be completely eliminated. Or, more precise: mainly, these improve speech quality in a sense of “understanding language”.įor Musician purposes, most of those settings are counter-productive. Yes, they are for a standard conference with speakers. The settings you disable with a “true” here are all meant to improve sound quality Please remember that I’m very new to Jitsi and everything I say could be very wrong
![jitsi voice jitsi voice](https://playcrack.com/wp-content/uploads/2020/09/maker-min.png)
I’ve since re-enabled AEC (via writing “false” after the colon) without noticing a loss of quality. They seem to correspond to features available in webkit/chrome/chromium, so here is my best guess at what they do: disableAP: true, // disable ?ĭisableAEC: true, // disable echo suppression and cancellationĭisableNS: true, // disable noise suppressionĭisableAGC: true, // disable automatic gain controlĭisableHPF: true, // disable high pass filter? (no lower-than-speech sounds) Nonetheless, I think I noticed an improvement, maybe just because of better client performance. The settings you disable with a “true” here are all meant to improve sound quality, so it is counter intuitive to disable them with a “true”. So if you just uncomment them and change them to true, the changes should be applied to all people reloading their browsers. Within this file, the options I wrote above are listed right at the end (without explanation). This is the client-side configuration that will be downloaded by the web client AND by all the apps. If you are running Jitsi Meet on one of your own servers with docker-jitsi-meet from, you will have a directory under ~/.jitsi-meet-cfg/web/ with a file called config.js. As far as I know none of the settings require that specific commit (because they are all client-side settings) and I just added the information so people with more knowledge than I have can make an informed decision if what I wrote can be true. Ebfa142d384466fefc7cd224cdca50df9cfe40c7 is the git commit my server is running with.