Right now with BigBlueButton, any network issues are largely invisible to the users. Combine high latency, dropped packets, and low bandwidth together, these network issues will cause poor audio for a user. But given network latency of 250 ms or 500 ms the users can hear the difference. A browser can load a web page in 250 ms or 500 ms and the users can't tell the difference. It's a common conclusion.Ĭonsistently sending and receiving media packets requires a stable network. If it doesn't, the problem must be with the software.
#Virtual audio cable 4.15 full crack software
But unfortunately, between all these tests among multiple users, the general agreement is that it's a bad experience in terms of its inconsistency.įrom a user's perspective, if the software loaded, it must therefore work.
Because I get no real feedback outside of "crackly audio" "green fuzziness video". Unfortunately, the problem is always going to come down the lack of experience with the user - they just want things to work, and when they don't, they're ready to trash it - which is annoying. No errors, ran from bbb-install.sh script.But unfortunately, we have users that require instant working connections 100% of the time. If I run your test at, that runs fine too.
We're running v2.2, and look, it runs fine when you test. I haven't seen any actual hardware performance come close to hitting those numbers. I can tell you the AWS instance have set up C5Large (10G throughput) was set up fine with bbb-install.sh - 4 cores, 8gb ram. The easiest common denominator was their version of Chrome, with an updated version some issues seemed to fix quickly. That's the thing, it's too intermittent (100 users), some in different countries, some at home, some in the office. If you are willing to provide more information, we're interested in figuring out why users are not having good audio.Īpologies for the brevity. There is a bit of investigation needed here. There experience with the above server - better/same/worse experience - will help isolate differences in (f) and (g). If you have users that are consistently having troubles, then have them try out
Does your server meet the minimum configuration required by BigBlueButton (Yes/No)?.What is the version of BigBlueButton you are using?.You haven't provided any details on your server, so the following would be helpful Can you share more details about your users? Usually (a) to (e) are good for the average user, but 'good' heavily depends on where they live. Some of these you can control - (f), (g), and (h) - but the rest are dependent on the users. The trick is to narrow down which step along the way is causing users to have poor bandwidth. The user's audio experience is dependent on (a) user's browser, (b) operating system, (c) computer, (d) connection to the internet (wired or wireless), (e) internet connection between their connection and your BigBlueButton server, (f) your BigBlueButton server's incoming bandwidth, (g) your server, and (h) the version of BigBlueButton running on the server. Are all the users in a session having troubles, or only some.Do you have users who are consistently having troubles, or occasionally having troubles?.You didn't offer any details on the users, but we're interested to try and help.