[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ale] ALE meeting location

Sound problems are usually local pulseaudio stuff.  Each person needs to
figure that out themselves. Usually killing pulseaudio is my 1st step,
then using pavucontrol to get the correct HW connected to the right output.

Viewing works w/ Firefox, but presenting wants Chromium-based browsers.

BTW, both FF and Chromium were run constrained via --private firejail
sandboxes during my testing.  10+ other people running a mix of OSes
didn't have issues besides poor bandwidth on their side.

During testing, i shared a presentation, a terminal window and everyone
said both were quite clear.  Audio basically always worked, even when
someone's video dropped due to local (their side) issues.  Turned out
the USB hub used was breaking the video.

There are many flaws w/ any webRTC solution, that is certain.

On 3/14/20 1:56 AM, Steve Litt wrote:
> On Thu, 12 Mar 2020 18:13:09 -0400
> DJ-Pfulio via Ale <ale at ale.org> wrote:
>> On 3/12/20 11:32 AM, Jim Kinney via Ale wrote:
>>> Now might be a good time to experiment with Apache Meeting.  
>> Or jisti-meet.  At ALE-NW, a new member setup the teleconf on a VPS in
>> about 10 minutes.  The presenter doesn't need any local software
>> installed to share her screen.  Any WebRTC capable browser worked.
> I beg to differ. Our GoLUG meetings use Jitsi. Only works with
> Chromium: No firefox, no Midori, nothing. I tried jitsi-meet: Even
> worse. No sound.