[PLUG] Using meet.jit.si [FIXED]

Rich Shepard rshepard at appl-ecosys.com
Thu Jun 4 20:52:44 UTC 2020


On Thu, 4 Jun 2020, Ben Koenig wrote:

> While running through steps 1 and 2, rebooting is a valuable tool to
> verify that everything is loaded to a known good state. There are race
> conditions involved with using pulseaudio. It has to load after the alsa
> drivers, and if it crashes it has a tendency to auto restart as a
> different process. By rebooting the host, you can be sure that everything
> is loaded and linked together in the correct order, with the correct
> permissions.

Ben, et al.:

Rebooting acted like an enema for the audio system. The webcam and
Audio-Technica mics show response when pavucontrol turns each on and the
other off. Haven't futzed with the headset; perhaps tomorrow.

Audacity also now responds when I click the mic on the top input bar and
start monitoring.

Fired up jitsi using chromium and it immediately recognized the microphone
as well as the webcam.

> Are we still on for this afternoon?

No need. I have found the need to reboot a desktop very infrequently so that
idea doesn't occur to me. And with 164 days, 19.5 hours of uptime a reboot
would be a Good Thing in any case. For jitsi it fixed whatever was ailing.

Thanks to all of you who offered suggestions and insights based on your
experiences.

Regards,

Rich



More information about the PLUG mailing list