• [OT] Video conferencing

    From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Thu Apr 15 08:19:33 2021
    From Newsgroup: alt.os.linux.ubuntu

    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    I asked last summer, and some folks here said that they were running
    one or more of these just fine under Ubuntu. Some advice I got at
    the time seemed to take care of it, but that turned out to be
    coincidence.

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    Any suggestions, even on how to do my own research on this would
    be appreciated.

    --
    Michael F. Stemper
    Exodus 22:21
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Jonathan N. Little@lws4art@gmail.com to alt.os.linux.ubuntu on Thu Apr 15 09:48:55 2021
    From Newsgroup: alt.os.linux.ubuntu

    Michael F. Stemper wrote:

    I have been having problems running Zoom,

    No problem running Zoom on my 8-year-old Lenovo L530 i5-3230M with 8GB
    RAM running 20.04. Thankfully we have switched to Google Meet which I
    prefer and hove dumped Zoom

    WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    Never used WebEx or Discord. Library director uses Discord on a Lenovo ThinkCentre M710s i3-7100 8GB RAM without issue.

    --
    Take care,

    Jonathan
    -------------------
    LITTLE WORKS STUDIO
    http://www.LittleWorksStudio.com
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Bit Twister@BitTwister@mouse-potato.com to alt.os.linux.ubuntu on Thu Apr 15 09:33:32 2021
    From Newsgroup: alt.os.linux.ubuntu

    On Thu, 15 Apr 2021 08:19:33 -0500, Michael F. Stemper wrote:
    I have been having problems running Zoom,

    Any suggestions, even on how to do my own research on this would
    be appreciated.

    Would not have hurt to post your your hardware specs and OS and version.

    I do recommend downloading the latest Zoom. There were a flurry of updates
    last month, about one a week. Latest release I have is zoom-5.6.13632.0328-1.x86_64.rpm
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From anton@anton@mips.complang.tuwien.ac.at (Anton Ertl) to alt.os.linux.ubuntu on Thu Apr 15 15:51:14 2021
    From Newsgroup: alt.os.linux.ubuntu

    "Michael F. Stemper" <mstemper@gmail.com> writes:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)
    ...
    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    I very much doubt GPUs play much of a role.

    I use a laptop with a Core i3-3227U (2 cores, 1.9GHz) and its on-chip
    GPU, and Zoom works fine there (as well as BigBlueButton, Jitsi, and GotoMeeting). That's with Ubuntu 18.04 for now.

    - anton
    --
    M. Anton Ertl Some things have to be seen to be believed anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen http://www.complang.tuwien.ac.at/anton/home.html
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Bobbie Sellers@bliss@mouse-potato.com to alt.os.linux.ubuntu on Thu Apr 15 09:35:26 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    I asked last summer, and some folks here said that they were running
    one or more of these just fine under Ubuntu. Some advice I got at
    the time seemed to take care of it, but that turned out to be
    coincidence.

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    Any suggestions, even on how to do my own research on this would
    be appreciated.


    As BT says tell us about your hardware. What other softwares are you using while meeting on video.

    bliss -“Nearly any fool can use a GNU/Linux computer. Many do.” After
    all here I am...

    --
    bliss dash SF 4 ever at dslextreme dot com
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Thu Apr 15 11:39:18 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 15/04/2021 09.33, Bit Twister wrote:
    On Thu, 15 Apr 2021 08:19:33 -0500, Michael F. Stemper wrote:
    I have been having problems running Zoom,

    Any suggestions, even on how to do my own research on this would
    be appreciated.

    Would not have hurt to post your your hardware specs and OS and version.

    Here is inxi output from my fastest box:

    CPU~Dual core Intel Core i5 M 540 (-HT-MCP-) speed/max~1199/2534 MHz Kernel~4.4.0-206-generic x86_64 Up~21 days Mem~1864.1/3813.1MB HDD~1008.0GB(6.2% used) Procs~263 Client~Shell inxi~2.2.35

    16.04 LTS.

    I do recommend downloading the latest Zoom. There were a flurry of updates last month, about one a week. Latest release I have is zoom-5.6.13632.0328-1.x86_64.rpm

    Actually, I listed those in a bad order. My primary use case is
    Discord (weekly chat with my son). After that is twice-monthly
    meetings on WebEx. I gave a Zoom talk a couple weeks back, but
    haven't made any other use of that platform.


    --
    Michael F. Stemper
    Always remember that you are unique. Just like everyone else.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Bobbie Sellers@bliss@mouse-potato.com to alt.os.linux.ubuntu on Thu Apr 15 09:59:33 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 4/15/21 9:39 AM, Michael F. Stemper wrote:
    On 15/04/2021 09.33, Bit Twister wrote:
    On Thu, 15 Apr 2021 08:19:33 -0500, Michael F. Stemper wrote:
    I have been having problems running Zoom,

    Any suggestions, even on how to do my own research on this would
    be appreciated.

    Would not have hurt to post your your hardware specs and OS and version.

    Here is inxi output from my fastest box:

    CPU~Dual core Intel Core i5 M 540 (-HT-MCP-) speed/max~1199/2534 MHz Kernel~4.4.0-206-generic x86_64 Up~21 days Mem~1864.1/3813.1MB HDD~1008.0GB(6.2% used) Procs~263 Client~Shell inxi~2.2.35

    16.04 LTS.

    I do recommend downloading the latest Zoom. There were a flurry of
    updates
    last month, about one a week. Latest release I have is
    zoom-5.6.13632.0328-1.x86_64.rpm

    Actually, I listed those in a bad order. My primary use case is
    Discord (weekly chat with my son). After that is twice-monthly
    meetings on WebEx. I gave a Zoom talk a couple weeks back, but
    haven't made any other use of that platform.


    I foolishly think that your should update your OS. But I
    do not know if that will fix the problem. Is your memory maxed out?
    If not maxxed out you might want to increase that. You might look
    for CPUpower which is a tool to permit you to control the speed
    of your CPU to the highest in this use case.

    bliss -“Nearly any fool can use a GNU/Linux computer. Many do.” After
    all here I am...

    --
    bliss dash SF 4 ever at dslextreme dot com
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Thu Apr 15 12:58:31 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 15/04/2021 11.59, Bobbie Sellers wrote:
    On 4/15/21 9:39 AM, Michael F. Stemper wrote:
    On 15/04/2021 09.33, Bit Twister wrote:
    On Thu, 15 Apr 2021 08:19:33 -0500, Michael F. Stemper wrote:
    I have been having problems running Zoom, (and other stuff)

    Here is inxi output from my fastest box:

    CPU~Dual core Intel Core i5 M 540 (-HT-MCP-) speed/max~1199/2534 MHz
    Kernel~4.4.0-206-generic x86_64 Up~21 days Mem~1864.1/3813.1MB
    HDD~1008.0GB(6.2% used) Procs~263 Client~Shell inxi~2.2.35

    16.04 LTS.

    I do recommend downloading the latest Zoom. There were a flurry of
    updates
    last month, about one a week. Latest release I have is
    zoom-5.6.13632.0328-1.x86_64.rpm

    Actually, I listed those in a bad order. My primary use case is
    Discord (weekly chat with my son). After that is twice-monthly
    meetings on WebEx. I gave a Zoom talk a couple weeks back, but
    haven't made any other use of that platform.

    I foolishly think that your should update your OS.

    16.04 is probably going EOL soon, yeah. I had updated one box to
    18.04 LTS, which I extremely disliked. When the disk died, I ended
    up reinstalling from the 16.04 flash drive that was sitting on my
    dresser.

    I foolishly think that your should update your OS. But I
    do not know if that will fix the problem.  Is your memory maxed out?

    Absolutely not. It runs about 10%-15% during a WebEx or Discord,
    according to top.

    If not maxxed out you might want to increase that.  You might look
    for CPUpower which is a tool to permit you to control the speed
    of your CPU to the highest in this use case.

    I don't follow this. Are you saying that it'll make my CPU run faster?
    That seems improbable, but I can't find any other interpretation.

    Any ideas what to look for in a new laptop?

    --
    Michael F. Stemper
    Always remember that you are unique. Just like everyone else.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Thu Apr 15 13:03:14 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 15/04/2021 11.35, Bobbie Sellers wrote:
    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

        As BT says tell us about your hardware.  What other softwares are you using while meeting on video.

    Well, you've already seen (and responded to) the post with my inxi
    output. I'll have a dozen or so xterms open, waiting for me to get back
    to them, and a few static pages in tabs in Firefox. Sometimes, I'll
    look something up in Duck^2Go and close the tab.

    But, to be clear, the 250% to 300% is not total CPU utilization; it's
    CPU utilization for WebEx or Discord.


    --
    Michael F. Stemper
    Always remember that you are unique. Just like everyone else.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Dirk T. Verbeek@dverbeek@xs4all.nl to alt.os.linux.ubuntu on Thu Apr 15 20:32:02 2021
    From Newsgroup: alt.os.linux.ubuntu

    Op 15-04-2021 om 15:19 schreef Michael F. Stemper:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    I asked last summer, and some folks here said that they were running
    one or more of these just fine under Ubuntu. Some advice I got at
    the time seemed to take care of it, but that turned out to be
    coincidence.

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    Any suggestions, even on how to do my own research on this would
    be appreciated.

    I use Zoom, Signal and Skype on a 10 y/o Thinkpad w520, i7/8Gb with
    Kubuntu, no problems with either the Intel or nVidia video card.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Paul@nospam@needed.invalid to alt.os.linux.ubuntu on Thu Apr 15 16:14:37 2021
    From Newsgroup: alt.os.linux.ubuntu

    Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    I asked last summer, and some folks here said that they were running
    one or more of these just fine under Ubuntu. Some advice I got at
    the time seemed to take care of it, but that turned out to be
    coincidence.

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    Any suggestions, even on how to do my own research on this would
    be appreciated.


    https://bloggeek.me/when-will-zoom-use-webrtc/

    Then you look at the potential for hardware acceleration
    on desktop platforms.

    (Table at bottom)

    https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video

    (Encoding doesn't have good VP8/VP9 representation, Decode has some)

    https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

    (AMD VCN support... crickets... have to use wiki)

    https://www.phoronix.com/scan.php?page=news_item&px=Radeon-VCN-Encode-Lands
    ( https://en.wikipedia.org/wiki/AMD_Accelerated_Processing_Unit )

    Android is likely to have some hardware acceleration.

    The WebRTCSDK has some samples showing hardware acceleration
    is available.

    Summary:

    "Nobody ever went wrong buying a CPU"

    What this means is, you might never be able to verify
    with any certainty, on any particular day, that
    a suitable video encoder in hardware will be present.
    If you buy a strong CPU, you can laugh at these
    issues. If your CPU can turbo to 4.3GHz on one core,
    no matter how poorly written the software is, you'll
    be able to conference at 640x480 resolution.

    How is that for a "weak endorsement" of computers ???

    Really, 1.5GHz of processing should be enough for
    any reasonable video encoder. My 4.3GHz number is
    sheer fantasy on my part. But we must "buy for the future",
    and with containerization of softwares being the new thing,
    we have to plan for "tremendous software wastage"
    in future.

    Where do the rules come from ?

    "Your CPU must be as fast as the CPU on
    the developers desk"

    Nothing less is sufficient.

    Paul
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Paul@nospam@needed.invalid to alt.os.linux.ubuntu on Thu Apr 15 18:12:29 2021
    From Newsgroup: alt.os.linux.ubuntu

    Michael F. Stemper wrote:
    On 15/04/2021 11.35, Bobbie Sellers wrote:
    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    As BT says tell us about your hardware. What other softwares are
    you using while meeting on video.

    Well, you've already seen (and responded to) the post with my inxi
    output. I'll have a dozen or so xterms open, waiting for me to get back
    to them, and a few static pages in tabs in Firefox. Sometimes, I'll
    look something up in Duck^2Go and close the tab.

    But, to be clear, the 250% to 300% is not total CPU utilization; it's
    CPU utilization for WebEx or Discord.

    CPU~Dual core Intel Core i5 M 540 <=== Intel i5-540M (3M Cache, 2.53 GHz) ???

    speed/max~1199/2534 MHz EIST 12x minimum multiplier, 100MHz BCLK

    Kernel~4.4.0-206-generic x86_64

    Mem~1864.1/3813.1MB

    HDD~1008.0GB(6.2% used)

    16.04 LTS.

    *******

    2C 4T 2.53Ghz 3MB cache Arrandale
    Intel HD Graphics
    32 nm
    Spring 2010 release
    35W TDP

    That's 2C 4T and at 300% is fully fully loaded.
    That's too much for it. 200% leaves some margin.

    "Its direct predecessor, the GMA X4500, featured
    10 EUs at 800 MHz, but it lacked some capabilities.[14]

    Model number Tier Execution Units Shading Units Base Clk Boost Clk GFLOPS (FP32)
    HD Graphics ? 12 24 500 900 24.0 - 43.2
    "

    Likely to be 1 year before the first QuickSync
    processor came along (video encoder on the GPU
    next to the CPU). Intel is so far along now...
    they dropped VP8 and just support VP9 now,
    even though normal silicon, you'd keep both.

    *******

    Next time, you could try "inxi -F", but it's
    not likely to be any more expressive in this case.

    Paul
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Bobbie Sellers@bliss@mouse-potato.com to alt.os.linux.ubuntu on Thu Apr 15 18:30:35 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 4/15/21 1:14 PM, Paul wrote:
    Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    I asked last summer, and some folks here said that they were running
    one or more of these just fine under Ubuntu. Some advice I got at
    the time seemed to take care of it, but that turned out to be
    coincidence.

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    Any suggestions, even on how to do my own research on this would
    be appreciated.


    https://bloggeek.me/when-will-zoom-use-webrtc/

    Then you look at the potential for hardware acceleration
    on desktop platforms.

      (Table at bottom)

      https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video

      (Encoding doesn't have good VP8/VP9 representation, Decode has some)


    https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

      (AMD VCN support... crickets... have to use wiki)


    https://www.phoronix.com/scan.php?page=news_item&px=Radeon-VCN-Encode-Lands
      ( https://en.wikipedia.org/wiki/AMD_Accelerated_Processing_Unit )

    Android is likely to have some hardware acceleration.

    The WebRTCSDK has some samples showing hardware acceleration
    is available.

    Summary:

      "Nobody ever went wrong buying a CPU"

    What this means is, you might never be able to verify
    with any certainty, on any particular day, that
    a suitable video encoder in hardware will be present.
    If you buy a strong CPU, you can laugh at these
    issues. If your CPU can turbo to 4.3GHz on one core,
    no matter how poorly written the software is, you'll
    be able to conference at 640x480 resolution.

    How is that for a "weak endorsement" of computers ???

    Really, 1.5GHz of processing should be enough for
    any reasonable video encoder. My 4.3GHz number is
    sheer fantasy on my part. But we must "buy for the future",
    and with containerization of softwares being the new thing,
    we have to plan for "tremendous software wastage"
    in future.

    Where do the rules come from ?

      "Your CPU must be as fast as the CPU on
       the developers desk"

    Nothing less is sufficient.

      Paul

    Actually the developer's Ryzen 7 tower broke down.
    Possibly a video card problem and this year double the
    price of last year's same card. Meantime Real Life problems
    come to dominate one's time and thinking.

    bliss

    --
    bliss dash SF 4 ever at dslextreme dot com
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Bobbie Sellers@bliss@mouse-potato.com to alt.os.linux.ubuntu on Thu Apr 15 18:44:15 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 4/15/21 11:03 AM, Michael F. Stemper wrote:
    On 15/04/2021 11.35, Bobbie Sellers wrote:
    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

         As BT says tell us about your hardware.  What other softwares are
    you using while meeting on video.

    Well, you've already seen (and responded to) the post with my inxi
    output. I'll have a dozen or so xterms open, waiting for me to get back
    to them, and a few static pages in tabs in Firefox. Sometimes, I'll
    look something up in Duck^2Go and close the tab.

    But, to be clear, the 250% to 300% is not total CPU utilization; it's
    CPU utilization for WebEx or Discord.



    To be quite honest I do not know what you may need besides
    my suggestion of an OS upgrade. I do perfectly well on my 2nd hand
    Dell Latitude E7450 with an i7 dual core and an SSD 500 GB hard drive.
    On a DSL line but I only use jit.si meets and the jit.si server has
    the hard work.

    I probably will do as well with my older second(?) hand Dell
    E6540 i7 with 4 cores and I bet the 2nd hand E6520 i5 dual core will work.

    CPU Power tool lets you speed up the CPU to its maximum speed.
    Note that in the inxi output you report "speed/max~1199/2534 MHz"
    Well this tool might take it to the max without the OS software deciding
    you do not need that much speed and just pushing the slower speed
    to take more and more cycles.

    When I (simpleton) asked about maximum memory I was talking
    about whether or not your motherboard had filled all its slots.

    bliss -“Nearly any fool can use a GNU/Linux computer. Many do.” After
    all here I am...

    --
    bliss dash SF 4 ever at dslextreme dot com
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Henry Crun@mike@rechtman.com to alt.os.linux.ubuntu on Fri Apr 16 14:54:25 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 15/04/2021 19:39, Michael F. Stemper wrote:
    On 15/04/2021 09.33, Bit Twister wrote:
    On Thu, 15 Apr 2021 08:19:33 -0500, Michael F. Stemper wrote:
    I have been having problems running Zoom,

    Any suggestions, even on how to do my own research on this would
    be appreciated.

    Would not have hurt to post your your hardware specs and OS and version.

    Here is inxi output from my fastest box:

    CPU~Dual core Intel Core i5 M 540 (-HT-MCP-) speed/max~1199/2534 MHz Kernel~4.4.0-206-generic x86_64 Up~21 days
    Mem~1864.1/3813.1MB HDD~1008.0GB(6.2% used) Procs~263 Client~Shell inxi~2.2.35

    16.04 LTS.

    I do recommend downloading the latest Zoom. There were a flurry of updates >> last month, about one a week. Latest release I have is
    zoom-5.6.13632.0328-1.x86_64.rpm

    Actually, I listed those in a bad order. My primary use case is
    Discord (weekly chat with my son). After that is twice-monthly
    meetings on WebEx. I gave a Zoom talk a couple weeks back, but
    haven't made any other use of that platform.


    16.04 is a good few years old, which could be significant.
    Have you checked swap activity? disk thrashing? and possibly adjusted swappiness?

    --
    Mike R.
    Home: http://alpha.mike-r.com/
    QOTD: http://alpha.mike-r.com/qotd.php
    No Micro$oft products were used in the URLs above, or in preparing this message.
    Recommended reading: http://www.catb.org/~esr/faqs/smart-questions.html#before
    and: http://alpha.mike-r.com/jargon/T/top-post.html
    Missile address: N31.7624/E34.9691
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Fri Apr 16 07:54:34 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 16/04/2021 06.54, Henry Crun wrote:
    On 15/04/2021 19:39, Michael F. Stemper wrote:
    On 15/04/2021 09.33, Bit Twister wrote:

    CPU~Dual core Intel Core i5 M 540 (-HT-MCP-) speed/max~1199/2534 MHz
    Kernel~4.4.0-206-generic x86_64 Up~21 days Mem~1864.1/3813.1MB
    HDD~1008.0GB(6.2% used) Procs~263 Client~Shell inxi~2.2.35

    16.04 LTS.

    I do recommend downloading the latest Zoom. There were a flurry of
    updates
    last month, about one a week. Latest release I have is
    zoom-5.6.13632.0328-1.x86_64.rpm

    Actually, I listed those in a bad order. My primary use case is
    Discord (weekly chat with my son). After that is twice-monthly
    meetings on WebEx. I gave a Zoom talk a couple weeks back, but
    haven't made any other use of that platform.


    16.04 is a good few years old, which could be significant.

    I had been running 18.04 until a disk failure in August, and was having
    the issues before that.

    Have you checked swap activity? disk thrashing? and possibly adjusted swappiness?

    Would the checking be watching these lines from top?

    KiB Mem : 3904580 total, 349520 free, 1800984 used, 1754076 buff/cache
    KiB Swap: 4051964 total, 3693352 free, 358612 used. 1412520 avail Mem

    If not, what would I look at? (Please note that this wasn't taken during
    a video conference, since I only have one or two a week.)


    --
    Michael F. Stemper
    Nostalgia just ain't what it used to be.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Big Bad Bob@BigBadBob-at-mrp3-dot-com@testing.local to alt.os.linux.ubuntu on Fri Apr 16 12:04:37 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 2021-04-15 11:03, Michael F. Stemper wrote:
    On 15/04/2021 11.35, Bobbie Sellers wrote:
    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

         As BT says tell us about your hardware.  What other softwares are
    you using while meeting on video.

    Well, you've already seen (and responded to) the post with my inxi
    output. I'll have a dozen or so xterms open, waiting for me to get back
    to them, and a few static pages in tabs in Firefox. Sometimes, I'll
    look something up in Duck^2Go and close the tab.

    But, to be clear, the 250% to 300% is not total CPU utilization; it's
    CPU utilization for WebEx or Discord.



    That's interesting but doesn't say what your camera or audio hardware is.

    How about a 'lsusb' output?



    --
    (aka 'Bombastic Bob' in case you wondered)

    'Feeling with my fingers, and thinking with my brain' - me

    'your story is so touching, but it sounds just like a lie'
    "Straighten up and fly right"
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Fri Apr 16 14:38:46 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 16/04/2021 14.04, Big Bad Bob wrote:
    On 2021-04-15 11:03, Michael F. Stemper wrote:
    On 15/04/2021 11.35, Bobbie Sellers wrote:
    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

         As BT says tell us about your hardware.  What other softwares >>> are you using while meeting on video.

    Well, you've already seen (and responded to) the post with my inxi
    output. I'll have a dozen or so xterms open, waiting for me to get back
    to them, and a few static pages in tabs in Firefox. Sometimes, I'll
    look something up in Duck^2Go and close the tab.

    But, to be clear, the 250% to 300% is not total CPU utilization; it's
    CPU utilization for WebEx or Discord.

    That's interesting but doesn't say what your camera or audio hardware is.

    How about a 'lsusb' output?


    Here's my camera, based on lsusb -v:



    Bus 002 Device 038: ID 05a3:9331 ARC International
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize0 64
    idVendor 0x05a3 ARC International
    idProduct 0x9331
    bcdDevice 1.04
    iManufacturer 1
    iProduct 2
    iSerial 3
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 850
    bNumInterfaces 4
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 500mA
    Interface Association:
    bLength 8
    bDescriptorType 11
    bFirstInterface 0
    bInterfaceCount 2
    bFunctionClass 14 Video
    bFunctionSubClass 3 Video Interface Collection
    bFunctionProtocol 0
    iFunction 4
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 14 Video
    bInterfaceSubClass 1 Video Control
    bInterfaceProtocol 0
    iInterface 4
    VideoControl Interface Descriptor:
    bLength 13
    bDescriptorType 36
    bDescriptorSubtype 1 (HEADER)
    bcdUVC 1.00
    wTotalLength 51
    dwClockFrequency 48.000000MHz
    bInCollection 1
    baInterfaceNr( 0) 1
    VideoControl Interface Descriptor:
    bLength 18
    bDescriptorType 36
    bDescriptorSubtype 2 (INPUT_TERMINAL)
    bTerminalID 1
    wTerminalType 0x0201 Camera Sensor
    bAssocTerminal 0
    iTerminal 0
    wObjectiveFocalLengthMin 0
    wObjectiveFocalLengthMax 0
    wOcularFocalLength 0
    bControlSize 3
    bmControls 0x00000002
    Auto-Exposure Mode
    VideoControl Interface Descriptor:
    bLength 11
    bDescriptorType 36
    bDescriptorSubtype 5 (PROCESSING_UNIT)
    Warning: Descriptor too short
    bUnitID 2
    bSourceID 1
    wMaxMultiplier 16384
    bControlSize 2
    bmControls 0x0000177f
    Brightness
    Contrast
    Hue
    Saturation
    Sharpness
    Gamma
    White Balance Temperature
    Backlight Compensation
    Gain
    Power Line Frequency
    White Balance Temperature, Auto
    iProcessing 0
    bmVideoStandards 0x 9
    None
    SECAM - 625/50
    VideoControl Interface Descriptor:
    bLength 9
    bDescriptorType 36
    bDescriptorSubtype 3 (OUTPUT_TERMINAL)
    bTerminalID 3
    wTerminalType 0x0101 USB Streaming
    bAssocTerminal 0
    bSourceID 2
    iTerminal 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0010 1x 16 bytes
    bInterval 8
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 0
    bNumEndpoints 0
    bInterfaceClass 14 Video
    bInterfaceSubClass 2 Video Streaming
    bInterfaceProtocol 0
    iInterface 0
    VideoStreaming Interface Descriptor:
    bLength 16
    bDescriptorType 36
    bDescriptorSubtype 1 (INPUT_HEADER)
    bNumFormats 3
    wTotalLength 628
    bEndPointAddress 130
    bmInfo 0
    bTerminalLink 3
    bStillCaptureMethod 0
    bTriggerSupport 0
    bTriggerUsage 0
    bControlSize 1
    bmaControls( 0) 11
    bmaControls( 1) 11
    bmaControls( 2) 11
    VideoStreaming Interface Descriptor:
    bLength 11
    bDescriptorType 36
    bDescriptorSubtype 6 (FORMAT_MJPEG)
    bFormatIndex 1
    bNumFrameDescriptors 6
    bFlags 0
    Fixed-size samples: No
    bDefaultFrameIndex 1
    bAspectRatioX 0
    bAspectRatioY 0
    bmInterlaceFlags 0x00
    Interlaced stream or variable: No
    Fields per frame: 1 fields
    Field 1 first: No
    Field pattern: Field 1 only
    bCopyProtect 0
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 7 (FRAME_MJPEG)
    bFrameIndex 1
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1920
    wHeight 1080
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwMaxVideoFrameBufferSize 460800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 7 (FRAME_MJPEG)
    bFrameIndex 2
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1280
    wHeight 960
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwMaxVideoFrameBufferSize 460800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 7 (FRAME_MJPEG)
    bFrameIndex 3
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1280
    wHeight 720
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwMaxVideoFrameBufferSize 460800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 7 (FRAME_MJPEG)
    bFrameIndex 4
    bmCapabilities 0x00
    Still image unsupported
    wWidth 800
    wHeight 600
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwMaxVideoFrameBufferSize 460800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 7 (FRAME_MJPEG)
    bFrameIndex 5
    bmCapabilities 0x00
    Still image unsupported
    wWidth 640
    wHeight 480
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwMaxVideoFrameBufferSize 460800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 7 (FRAME_MJPEG)
    bFrameIndex 6
    bmCapabilities 0x00
    Still image unsupported
    wWidth 640
    wHeight 360
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwMaxVideoFrameBufferSize 460800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 27
    bDescriptorType 36
    bDescriptorSubtype 4 (FORMAT_UNCOMPRESSED)
    bFormatIndex 2
    bNumFrameDescriptors 6
    guidFormat
    {59555932-0000-1000-8000-00aa00389b71}
    bBitsPerPixel 16
    bDefaultFrameIndex 1
    bAspectRatioX 0
    bAspectRatioY 0
    bmInterlaceFlags 0x00
    Interlaced stream or variable: No
    Fields per frame: 2 fields
    Field 1 first: No
    Field pattern: Field 1 only
    bCopyProtect 0
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
    bFrameIndex 1
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1920
    wHeight 1080
    dwMinBitRate 29491200
    dwMaxBitRate 29491200
    dwMaxVideoFrameBufferSize 1843200
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 1999998
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
    bFrameIndex 2
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1280
    wHeight 960
    dwMinBitRate 29491200
    dwMaxBitRate 29491200
    dwMaxVideoFrameBufferSize 1843200
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 1999998
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
    bFrameIndex 3
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1280
    wHeight 720
    dwMinBitRate 29491200
    dwMaxBitRate 29491200
    dwMaxVideoFrameBufferSize 1843200
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 1999998
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
    bFrameIndex 4
    bmCapabilities 0x00
    Still image unsupported
    wWidth 800
    wHeight 600
    dwMinBitRate 29491200
    dwMaxBitRate 29491200
    dwMaxVideoFrameBufferSize 1843200
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 999999
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
    bFrameIndex 5
    bmCapabilities 0x00
    Still image unsupported
    wWidth 640
    wHeight 480
    dwMinBitRate 29491200
    dwMaxBitRate 29491200
    dwMaxVideoFrameBufferSize 1843200
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
    bFrameIndex 6
    bmCapabilities 0x00
    Still image unsupported
    wWidth 640
    wHeight 360
    dwMinBitRate 29491200
    dwMaxBitRate 29491200
    dwMaxVideoFrameBufferSize 1843200
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 28
    bDescriptorType 36
    bDescriptorSubtype 16 (FORMAT_FRAME_BASED)
    bFormatIndex 3
    bNumFrameDescriptors 6
    guidFormat
    {48323634-0000-1000-8000-00aa00389b71}
    bBitsPerPixel 16
    bDefaultFrameIndex 1
    bAspectRatioX 0
    bAspectRatioY 0
    bmInterlaceFlags 0x00
    Interlaced stream or variable: No
    Fields per frame: 2 fields
    Field 1 first: No
    Field pattern: Field 1 only
    bCopyProtect 0
    bVariableSize 1
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 17 (FRAME_FRAME_BASED)
    bFrameIndex 1
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1920
    wHeight 1080
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwBytesPerLine 0
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 17 (FRAME_FRAME_BASED)
    bFrameIndex 2
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1280
    wHeight 960
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwBytesPerLine 0
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 17 (FRAME_FRAME_BASED)
    bFrameIndex 3
    bmCapabilities 0x00
    Still image unsupported
    wWidth 1280
    wHeight 720
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwBytesPerLine 0
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 17 (FRAME_FRAME_BASED)
    bFrameIndex 4
    bmCapabilities 0x00
    Still image unsupported
    wWidth 800
    wHeight 600
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwBytesPerLine 0
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 17 (FRAME_FRAME_BASED)
    bFrameIndex 5
    bmCapabilities 0x00
    Still image unsupported
    wWidth 640
    wHeight 480
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwBytesPerLine 0
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 30
    bDescriptorType 36
    bDescriptorSubtype 17 (FRAME_FRAME_BASED)
    bFrameIndex 6
    bmCapabilities 0x00
    Still image unsupported
    wWidth 640
    wHeight 360
    dwMinBitRate 7372800
    dwMaxBitRate 7372800
    dwDefaultFrameInterval 333333
    bFrameIntervalType 1
    dwBytesPerLine 0
    dwFrameInterval( 0) 333333
    VideoStreaming Interface Descriptor:
    bLength 6
    bDescriptorType 36
    bDescriptorSubtype 13 (COLORFORMAT)
    bColorPrimaries 1 (BT.709,sRGB)
    bTransferCharacteristics 1 (BT.709)
    bMatrixCoefficients 4 (SMPTE 170M (BT.601))
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 1
    bNumEndpoints 1
    bInterfaceClass 14 Video
    bInterfaceSubClass 2 Video Streaming
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x82 EP 2 IN
    bmAttributes 5
    Transfer Type Isochronous
    Synch Type Asynchronous
    Usage Type Data
    wMaxPacketSize 0x0400 1x 1024 bytes
    bInterval 1
    Interface Association:
    bLength 8
    bDescriptorType 11
    bFirstInterface 2
    bInterfaceCount 2
    bFunctionClass 1 Audio
    bFunctionSubClass 0
    bFunctionProtocol 0
    iFunction 5
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 2
    bAlternateSetting 0
    bNumEndpoints 0
    bInterfaceClass 1 Audio
    bInterfaceSubClass 1 Control Device
    bInterfaceProtocol 0
    iInterface 5
    AudioControl Interface Descriptor:
    bLength 9
    bDescriptorType 36
    bDescriptorSubtype 1 (HEADER)
    bcdADC 1.00
    wTotalLength 39
    bInCollection 1
    baInterfaceNr( 0) 3
    AudioControl Interface Descriptor:
    bLength 12
    bDescriptorType 36
    bDescriptorSubtype 2 (INPUT_TERMINAL)
    bTerminalID 2
    wTerminalType 0x0201 Microphone
    bAssocTerminal 0
    bNrChannels 1
    wChannelConfig 0x0003
    Left Front (L)
    Right Front (R)
    iChannelNames 0
    iTerminal 0
    AudioControl Interface Descriptor:
    bLength 9
    bDescriptorType 36
    bDescriptorSubtype 3 (OUTPUT_TERMINAL)
    bTerminalID 4
    wTerminalType 0x0101 USB Streaming
    bAssocTerminal 0
    bSourceID 6
    iTerminal 0
    AudioControl Interface Descriptor:
    bLength 9
    bDescriptorType 36
    bDescriptorSubtype 6 (FEATURE_UNIT)
    bUnitID 6
    bSourceID 2
    bControlSize 2
    bmaControls( 0) 0x03
    bmaControls( 0) 0x00
    Mute Control
    Volume Control
    iFeature 0
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 3
    bAlternateSetting 0
    bNumEndpoints 0
    bInterfaceClass 1 Audio
    bInterfaceSubClass 2 Streaming
    bInterfaceProtocol 0
    iInterface 0
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 3
    bAlternateSetting 1
    bNumEndpoints 1
    bInterfaceClass 1 Audio
    bInterfaceSubClass 2 Streaming
    bInterfaceProtocol 0
    iInterface 0
    AudioStreaming Interface Descriptor:
    bLength 7
    bDescriptorType 36
    bDescriptorSubtype 1 (AS_GENERAL)
    bTerminalLink 4
    bDelay 1 frames
    wFormatTag 1 PCM
    AudioStreaming Interface Descriptor:
    bLength 11
    bDescriptorType 36
    bDescriptorSubtype 2 (FORMAT_TYPE)
    bFormatType 1 (FORMAT_TYPE_I)
    bNrChannels 1
    bSubframeSize 2
    bBitResolution 16
    bSamFreqType 1 Discrete
    tSamFreq[ 0] 16000
    Endpoint Descriptor:
    bLength 9
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 13
    Transfer Type Isochronous
    Synch Type Synchronous
    Usage Type Data
    wMaxPacketSize 0x0180 1x 384 bytes
    bInterval 4
    bRefresh 0
    bSynchAddress 0
    AudioControl Endpoint Descriptor:
    bLength 7
    bDescriptorType 37
    bDescriptorSubtype 1 (EP_GENERAL)
    bmAttributes 0x01
    Sampling Frequency
    bLockDelayUnits 1 Milliseconds
    wLockDelay 1 Milliseconds

    Lotta grist for your mill.

    Please note that I'm using an internal mic and my headphones plug
    into an audio jack, so they don't show up.

    Although this webcam has a built-in mic, I'm not using it, so
    that pulling the (USB) plug on it doesn't interrupt the audio.


    --
    Michael F. Stemper
    The FAQ for rec.arts.sf.written is at <http://leepers.us/evelyn/faqs/sf-written.htm>
    Please read it before posting.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Paul@nospam@needed.invalid to alt.os.linux.ubuntu on Sat Apr 17 00:29:52 2021
    From Newsgroup: alt.os.linux.ubuntu

    Michael F. Stemper wrote:
    On 16/04/2021 14.04, Big Bad Bob wrote:
    On 2021-04-15 11:03, Michael F. Stemper wrote:
    On 15/04/2021 11.35, Bobbie Sellers wrote:
    On 4/15/21 6:19 AM, Michael F. Stemper wrote:
    I have been having problems running Zoom, WebEx, and Discord. CPU
    utilization will rise to 250% or 300%, and the call/meeting will
    completely freeze. (Memory doesn't seem to be an issue, as top
    shows it at about 15%.)

    What kind of hardware do I need to run these? Do I need to get
    a box with a super-charged CPU? Do I need to focus on GPUs, since
    it's video?

    As BT says tell us about your hardware. What other softwares
    are you using while meeting on video.

    Well, you've already seen (and responded to) the post with my inxi
    output. I'll have a dozen or so xterms open, waiting for me to get back
    to them, and a few static pages in tabs in Firefox. Sometimes, I'll
    look something up in Duck^2Go and close the tab.

    But, to be clear, the 250% to 300% is not total CPU utilization; it's
    CPU utilization for WebEx or Discord.

    That's interesting but doesn't say what your camera or audio hardware is.

    How about a 'lsusb' output?


    Here's my camera, based on lsusb -v:

    Bus 002 Device 038: ID 05a3:9331 ARC International
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize0 64
    idVendor 0x05a3 ARC International
    idProduct 0x9331
    <snip>

    Lotta grist for your mill.

    Please note that I'm using an internal mic and my headphones plug
    into an audio jack, so they don't show up.

    Although this webcam has a built-in mic, I'm not using it, so
    that pulling the (USB) plug on it doesn't interrupt the audio.

    05a3:9331 ARC International

    A Google on that, doesn't indicate it is trouble free.

    It's probably mischief the camera is making, which
    is making the CPU look bad, when it's not actually
    the fault of the CPU.

    Maybe you could search through your collection of cameras
    and find another UVC one which is compliant. Then retest.
    If both cameras use MJPEG compression for frames, that
    would make it a "fair contest".

    I have my regular webcam, used for conferences, but I also
    have a cheap 640x480 camera, and it makes good test
    cases for verifying software works OK

    Paul
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Sat Apr 17 09:59:56 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 16/04/2021 23.29, Paul wrote:
    Michael F. Stemper wrote:
    On 16/04/2021 14.04, Big Bad Bob wrote:

    That's interesting but doesn't say what your camera or audio hardware
    is.

    How about a 'lsusb' output?


    Here's my camera, based on lsusb -v:

    05a3:9331 ARC International

    A Google on that, doesn't indicate it is trouble free.

    Is what you found consistent with the fact that this camera works
    flawlessly with the Windows 10 loaner box that's taking up my
    dining room table?

    Going ahead on the assumption that it is indeed the camera and not
    my computer, I did some looking and found: <https://www.amazon.com/Microphone-NexiGo-Computer-110-degree-Conferencing/dp/B088TSR6YJ/ref=sr_1_4?_encoding=UTF8&c=ts&dchild=1&keywords=Webcams&qid=1618666667&s=pc&sr=1-4&ts_id=172511>
    which claims:

    Compatible with [...] Ubuntu Version 10.04 or above.

    Claims are, of course, cheap. It also has a pointer to the next
    generation: <https://www.amazon.com/AutoFocus-Microphone-NexiGo-Streaming-Compatible-dp-B08931JJLV/dp/B08931JJLV/ref=dp_ob_title_ce>
    which makes the same claim about compatibility.

    If I can just buy a new webcam and solve my problems, that'd
    be great. Any suggestions on how to find problems like you found
    with my current webcam?

    It's probably mischief the camera is making, which
    is making the CPU look bad, when it's not actually
    the fault of the CPU.

    Maybe you could search through your collection of cameras

    This is my only webcam; I bought it about a year back when
    meetings went virtual. I never had any need for one before.

    and find another UVC one which is compliant. Then retest.
    If both cameras use MJPEG compression for frames, that
    would make it a "fair contest".

    The above cameras claim UVC compliance. Is that all that I
    need to worry about?

    I can't find my current webcam on Amazon any more; Wal-Mart makes
    no claims either way about its UVC compliance.

    Thanks for any help,
    --
    Michael F. Stemper
    Always use apostrophe's and "quotation marks" properly.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Paul@nospam@needed.invalid to alt.os.linux.ubuntu on Sat Apr 17 16:32:21 2021
    From Newsgroup: alt.os.linux.ubuntu

    Michael F. Stemper wrote:


    I can't find my current webcam on Amazon any more; Wal-Mart makes
    no claims either way about its UVC compliance.

    Thanks for any help,

    Well, it's weird that as the Linux driver tries to discover it,
    the UVC portion of reading the config space seems to fail.
    After about a minute, the software must be trying some other
    approach before it starts working. No messages indicating
    what necessarily was done.

    Another person reports that attempts to take timed pictures
    would find it dead, which means it might be entering a power
    save state. In which case you would attempt to change any
    power save settings so it stopped requesting power saving.

    NexiGo AutoFocus 1080p Webcam with Stereo Microphone and Privacy Cover, N930AF FHD USB
    05a3:9331 ARC International

    05a3 ARC International
    8388 Marvell 88W8388 802.11a/b/g WLAN
    9230 Camera <=== "auto-suspend" disabled
    9320 Camera
    9331 Camera <=== yours
    9332 Camera - 1080p
    9422 Camera
    9520 Camera

    dmesg

    [ 94.454526] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (05a3:9230)
    [ 94.496335] uvcvideo: auto-suspend is blacklisted for this device

    A third person found the camera having SMPS failures internally.
    5V comes in via VBUS. Devices with processing cores, they might
    run the compute core at 1.0V, the I/O at 3.3V, that kind of thing.
    The buck converter inside, converts the 5V to the lower
    voltages. It seemed to overheat at around 37C ambient.

    https://bbs.archlinux.org/viewtopic.php?id=264370

    ATTR{power/control}=="auto"

    The rest of the trace in that one, looks like even though the
    camera was unplugged and replugged, the inner part is not
    communicating, or the driver is confused about what
    instance this is. Normally instances would be sorted by
    each device presenting a "serial number". That's how OSes
    and the Plug and Play notion, track an item as the user moves
    it from one USB port to another USB port. Then, devices that
    have been "seen before", can be mated with info kept about
    them.

    Normally I would blame this solely on the driver, but
    the device appears to play some part.

    I'm sure that any driver tasked with running webcams,
    has its share of "quirk handling". This is normal for
    USB devices, but in the case of webcams, if you look at
    their config space, they are endlessly complex.

    UVC is a Class driver concept. Registers are in standard
    places. The driver does not need to be custom (any custom
    features have to be handled separately). UVC may have a
    resolution limit, incompatible with what the hardware
    is doing. For example Windows 10 thinks my camera is
    960 pixels across max, when it is something like 1600 pixels
    across. Yours is 1920 pixels across. And being USB2, it
    likely runs 5FPS if you select 1920x1080 pixels, and 30FPS
    if you select 640x480 resolution.

    When webcam drivers were moved from user space to kernel space,
    the first time I plugged in my Logitech, I got a picture.
    I unplugged the camera and plugged it back in. The kernel
    panicked. Things have come a long way since then :-) Now,
    mine is UVC, but the driver also picks up some of the
    features like autofocus. And who knows how quirks are
    handled in that driver. Like, if there were a couple hundred
    camera designs, the quirk list would be endless. Windows
    would have the same problem. A Chinese chip maker is no more
    likely to communicate with Microsoft, than with anyone else.

    "Nexigo 1080p Webcam Review *DON’T BUY!!!* ( N930AF )" https://www.youtube.com/watch?v=zrv5D7yOIKE

    I suspect, when dude there sees one of his "freezes",
    in your case, the Linux CPU goes to 300%. It means the
    connection, something happened to it in mid-flight.
    Would it be the power converter ? Dunno. Seems unlikely,
    because you'd think the USB connection would drop, and it
    would not just sit there. It sitting there, suggests
    some part of USB function is still there, but the data
    shoveling process has stopped.

    Maybe if you turn off auto-suspend, it'll stop doing
    that. That's assuming that it does not have a problem
    with overheating, inside. Feeling the chassis plastic,
    may give you some idea on the thermal aspect.

    Paul
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Michael F. Stemper@mstemper@gmail.com to alt.os.linux.ubuntu on Sun Apr 18 14:36:31 2021
    From Newsgroup: alt.os.linux.ubuntu

    On 17/04/2021 15.32, Paul wrote:
    Michael F. Stemper wrote:

    I can't find my current webcam on Amazon any more; Wal-Mart makes
    no claims either way about its UVC compliance.

    Well, it's weird that as the Linux driver tries to discover it,
    the UVC portion of reading the config space seems to fail.
    After about a minute, the software must be trying some other
    approach before it starts working. No messages indicating
    what necessarily was done.

    Another person reports that attempts to take timed pictures
    would find it dead, which means it might be entering a power
    save state. In which case you would attempt to change any
    power save settings so it stopped requesting power saving.

    NexiGo AutoFocus 1080p Webcam with Stereo Microphone and Privacy Cover, N930AF FHD USB
    05a3:9331 ARC International

    05a3  ARC International
        8388  Marvell 88W8388 802.11a/b/g WLAN
        9230  Camera           <=== "auto-suspend" disabled
        9320  Camera
        9331  Camera           <=== yours
        9332  Camera - 1080p
        9422  Camera
        9520  Camera

    Interesting that the one I have and the one my eyes first lit on
    have the same device id (if that's the right term).


    A third person found the camera having SMPS failures internally.
    5V comes in via VBUS. Devices with processing cores, they might
    run the compute core at 1.0V, the I/O at 3.3V, that kind of thing.
    The buck converter inside, converts the 5V to the lower
    voltages. It seemed to overheat at around 37C ambient.

    Well, the only time that my house would ever be that hot would be in
    the summer after an A/C failure. 15-20 is more my style.


    https://bbs.archlinux.org/viewtopic.php?id=264370


    Here is my demsg output:
    [2092530.656301] usb 2-1.3: New USB device found, idVendor=05a3, idProduct=9331
    [2092530.656309] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [2092530.656315] usb 2-1.3: Product: HD Web Camera
    [2092530.656319] usb 2-1.3: Manufacturer: HD Web Camera
    [2092530.656324] usb 2-1.3: SerialNumber: Ucamera001
    [2092530.673599] uvcvideo: Found UVC 1.00 device HD Web Camera (05a3:9331) [2092530.784278] input: HD Web Camera as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input22 [2092530.799221] usb 2-1.3: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
    [2092530.799228] usb 2-1.3: [6] FU [Mic Capture Volume] ch = 1, val = -1536/1536/1
    [2092530.954154] uvcvideo: Failed to query (GET_DEF) UVC control 9 on
    unit 2: -32 (exp. 2).

    Looks similar to what was shown on the (unanswered) archlinux post.


       ATTR{power/control}=="auto"


    Where did this come from, and should I try querying my camera
    similarly?


    UVC is a Class driver concept. Registers are in standard
    places. The driver does not need to be custom (any custom
    features have to be handled separately). UVC may have a
    resolution limit, incompatible with what the hardware
    is doing. For example Windows 10 thinks my camera is
    960 pixels across max, when it is something like 1600 pixels
    across. Yours is 1920 pixels across. And being USB2, it
    likely runs 5FPS if you select 1920x1080 pixels, and 30FPS
    if you select 640x480 resolution.

    There wasn't any control software included with this; simply the
    camera in a box. I just opened up "Settings" and didn't see anything
    about cameras.

    How would one select a resolution? Is there some command-line
    utility to manage cameras?

    "Nexigo 1080p Webcam Review *DON’T BUY!!!* ( N930AF )" https://www.youtube.com/watch?v=zrv5D7yOIKE

    Okay, dodged a bullet there. That freezes much faster than
    what I have. Interestingly, my CPU is now running up to
    about 150% -- just for "cheese", which is giving messages like:

    ==============================
    (cheese:13264): cheese-WARNING **: A lot of buffers are being dropped.: gstbasesink.c(2854): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
    There may be a timestamping problem, or this computer is too slow. ==============================



    I suspect, when dude there sees one of his "freezes",
    in your case, the Linux CPU goes to 300%. It means the
    connection, something happened to it in mid-flight.
    Would it be the power converter ? Dunno. Seems unlikely,
    because you'd think the USB connection would drop, and it
    would not just sit there. It sitting there, suggests
    some part of USB function is still there, but the data
    shoveling process has stopped.

    TBH, the current unit cost me all of about $20. [1] I'd be
    more than happy to write that off and just buy another one,
    one that will work.

    Have we established (with the above info) that it is indeed
    the camera?

    Maybe if you turn off auto-suspend, it'll stop doing
    that. That's assuming that it does not have a problem
    with overheating, inside. Feeling the chassis plastic,
    may give you some idea on the thermal aspect.

    Plastic case felt about room temp.


    [1] All together now: "You get what you pay for."
    --
    Michael F. Stemper
    This post contains greater than 95% post-consumer bytes by weight.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Paul@nospam@needed.invalid to alt.os.linux.ubuntu on Sun Apr 18 18:03:00 2021
    From Newsgroup: alt.os.linux.ubuntu

    Michael F. Stemper wrote:

    Have we established (with the above info) that it is indeed
    the camera?

    At this point, it's just a hint. Until some dialog
    admits it has lost contact with the camera.


    Maybe if you turn off auto-suspend, it'll stop doing
    that. That's assuming that it does not have a problem
    with overheating, inside. Feeling the chassis plastic,
    may give you some idea on the thermal aspect.

    Plastic case felt about room temp.


    [1] All together now: "You get what you pay for."

    I don't know the details of the suspend setting,
    whether you can force the webcam to be "always ON"
    or not.

    The intention is to eliminate buggy power-state
    code in the device firmware, by telling it to not
    be changing power states. I could find a reference
    to one webcam, where suspend is "blacklisted" by
    device ID value, so they know there is a problem
    with that one.

    There are several ways to do firmware on peripherals:

    1) right inside the chip, as the "top layer mask ROM".
    You can keep wafers in the drawer at the factory,
    put them in the machine and add the mask ROM as the
    top layer, then saw up the wafer and package the
    chips. The firmware cannot be updated. Generally, a
    minimum order of chips prepared this way, is around
    50,000 or so.

    2) Some chips use a serial EEPROM next to the main chip,
    and programs are loaded from there. Again, the device
    does not necessarily support upgrades. The chip might
    run at 33MHz.

    3) Chips where "dynamic loading" of firmware is design
    intent. For such devices, there is /lib/fw on Linux.
    Upon discovery at startup, the firmware can be loaded
    into them, before they're brought online. My TV Tuner
    works that way, needs firmware.

    Paul
    --- Synchronet 3.18a-Linux NewsLink 1.113