I tested using the same client computer/browser against the
openmeetings demo server and had the same result.
I guess this is saying its my client software?
I did notice something new that I hadn't notice before..come to find
out it was also on my local server as well (just did not notice): in
th
A bit of follow up:
Concerned that chromium was the problem, I tried launching it with
these two arguments:
--use-file-for-fake-video-capture=blabla.y4m --use-fake-device-for-media-stream
found here
https://bugs.chromium.org/p/chromium/issues/detail?id=318797
While this does seem to solve the is
Hello David,
could you please provide the complete name of your recording on demo server?
I'll check raw data, conversion logs and resulting file
On Sat, Mar 3, 2018 at 8:16 AM, David Jentz wrote:
> A bit of follow up:
>
> Concerned that chromium was the problem, I tried launching it with
> thes
