<div dir="auto">Maybe next meeting should be online with topic how to fix my jitsi session. If someone has problems we can all work together to fix it.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 14, 2020, 9:37 AM Jim Kinney via Ale <<a href="mailto:ale@ale.org">ale@ale.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Good test results and write-up. We've discussed ale meetings being published in the past but never moved beyond idea phase. This sounds like a very workable process. If we add the recording feature and a vps reflector, we have the makings of a pretty awesome meeting process. <br><br>Maybe people can wear go pro cameras for the post meeting beer :-)<br><br><div class="gmail_quote">On March 14, 2020 9:22:54 AM EDT, DJ-Pfulio via Ale <<a href="mailto:ale@ale.org" target="_blank" rel="noreferrer">ale@ale.org</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<pre>Sound problems are usually local pulseaudio stuff. Each person needs to<br>figure that out themselves. Usually killing pulseaudio is my 1st step,<br>then using pavucontrol to get the correct HW connected to the right output.<br><br>Viewing works w/ Firefox, but presenting wants Chromium-based browsers.<br><br>BTW, both FF and Chromium were run constrained via --private firejail<br>sandboxes during my testing. 10+ other people running a mix of OSes<br>didn't have issues besides poor bandwidth on their side.<br><br>During testing, i shared a presentation, a terminal window and everyone<br>said both were quite clear. Audio basically always worked, even when<br>someone's video dropped due to local (their side) issues. Turned out<br>the USB hub used was breaking the video.<br><br>There are many flaws w/ any webRTC solution, that is certain.<br><br>On 3/14/20 1:56 AM, Steve Litt wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #729fcf;padding-left:1ex">On Thu, 12 Mar 2020 18:13:09 -0400<br>DJ-Pfulio via Ale <<a href="mailto:ale@ale.org" target="_blank" rel="noreferrer">ale@ale.org</a>> wrote:<br><br><blockquote class="gmail_quote" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #ad7fa8;padding-left:1ex">On 3/12/20 11:32 AM, Jim Kinney via Ale wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #8ae234;padding-left:1ex"><br> Now might be a good time to experiment with Apache Meeting. <br></blockquote><br> Or jisti-meet. At ALE-NW, a new member setup the teleconf on a VPS in<br> about 10 minutes. The presenter doesn't need any local software<br> installed to share her screen. Any WebRTC capable browser worked.<br></blockquote><br>I beg to differ. Our GoLUG meetings use Jitsi. Only works with<br>Chromium: No firefox, no Midori, nothing. I tried jitsi-meet: Even<br>worse. No sound. <br></blockquote><hr>Ale mailing list<br><a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br><a href="https://mail.ale.org/mailman/listinfo/ale" target="_blank" rel="noreferrer">https://mail.ale.org/mailman/listinfo/ale</a><br>See JOBS, ANNOUNCE and SCHOOLS lists at<br><a href="http://mail.ale.org/mailman/listinfo" target="_blank" rel="noreferrer">http://mail.ale.org/mailman/listinfo</a><br></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.</div>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
<a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>