Reminder: Heroes meeting on Tuesday
Hello, the next heroes meeting will be on Tuesday (2020-10-06) at 18:00 UTC / 20:00 CEST. Important: We'll do a video meeting this time, so get your suit ready [1] and join the meeting at https://meet2.opensuse.org/heroes The planned topics are listed in https://progress.opensuse.org/issues/70813 Feel free to add your topics, or just bring them um during the meeting. Regards, Christian Boltz [1] just kidding ;-) -- And as Novell has shown with the packager: it's never too late for a beta, to add new features ;-) [Marcel Hilzinger in opensuse]
On 04/10/2020 20.51, Christian Boltz wrote:
Hello,
the next heroes meeting will be on Tuesday (2020-10-06) at 18:00 UTC / 20:00 CEST.
Important: We'll do a video meeting this time, so get your suit ready [1] and join the meeting at https://meet2.opensuse.org/heroes
Is there anyplace to test our setups? Find out if microphone and camera are working?
[1] just kidding ;-)
Or half of it :-P -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 05/10/2020 20.02, Carlos E. R. wrote:
On 04/10/2020 20.51, Christian Boltz wrote:
Hello,
the next heroes meeting will be on Tuesday (2020-10-06) at 18:00 UTC / 20:00 CEST.
Important: We'll do a video meeting this time, so get your suit ready [1] and join the meeting at https://meet2.opensuse.org/heroes
Is there anyplace to test our setups? Find out if microphone and camera are working?
I couldn't test (I don't know how), and on real time I found that none of my three working computers would work, so I lost most of what was said. First laptop. XFCE would not manage the BT earphones, so I switched to Gnome after a reboot. Gnome sound was just noise, but the microphone appeared to work. But when opening the meeting both cores went to 100% CPU, so sound had "interrupts". Camera worked in the meeting configuration, but refused on the meeting, because "camera does not support required video resolution". Resolution seems to set to HD, and I don't know if me changing it changes it for everybody, so I did not try. Same problem with FF and Chrome. Same problem on my second laptop (except no BT). On the desktop machine there is no cpu overload, so I can hear properly, but the integrated camera has never worked since I bought it, and the microphone appears not to work. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 05/10/2020 20.02, Carlos E. R. wrote:
On 04/10/2020 20.51, Christian Boltz wrote:
Hello,
the next heroes meeting will be on Tuesday (2020-10-06) at 18:00 UTC / 20:00 CEST.
Important: We'll do a video meeting this time, so get your suit ready [1] and join the meeting at https://meet2.opensuse.org/heroes
Is there anyplace to test our setups? Find out if microphone and camera are working?
I couldn't test (I don't know how),
Basically you open a conference and invite someone to test with you. Or even open a conference and watch/listen to yourself - works too. This is one I set up for testing: https://meet2.opensuse.org/test999
and on real time I found that none of my three working computers would work, so I lost most of what was said.
My setup - vanilla leap 15.2 with a Microsoft USB camera+microphone, two speakers connected with the normal minijack, a regular desktop machine, with KDE and Firefox. At first, I think I had to install pulseaudio-something, I think Gertjan suggested it. This has worked well with meet.o.o, with Cisco webex, with gotomeeting and with zoom. -- Per Jessen, Zürich (15.0°C) Member, openSUSE Heroes
On 07/10/2020 11.08, Per Jessen wrote:
Carlos E. R. wrote:
On 05/10/2020 20.02, Carlos E. R. wrote:
On 04/10/2020 20.51, Christian Boltz wrote:
Hello,
the next heroes meeting will be on Tuesday (2020-10-06) at 18:00 UTC / 20:00 CEST.
Important: We'll do a video meeting this time, so get your suit ready [1] and join the meeting at https://meet2.opensuse.org/heroes
Is there anyplace to test our setups? Find out if microphone and camera are working?
I couldn't test (I don't know how),
Basically you open a conference and invite someone to test with you. Or even open a conference and watch/listen to yourself - works too.
This is one I set up for testing: https://meet2.opensuse.org/test999
Huh, I'm still on pyjamas :-D
and on real time I found that none of my three working computers would work, so I lost most of what was said.
My setup - vanilla leap 15.2 with a Microsoft USB camera+microphone, two speakers connected with the normal minijack, a regular desktop machine, with KDE and Firefox. At first, I think I had to install pulseaudio-something, I think Gertjan suggested it.
This has worked well with meet.o.o, with Cisco webex, with gotomeeting and with zoom.
My problem is unsolvable by me. Laptop 1: CPU goes 100% and sound stutters. The meet system refuses the internal camera, "camera does not support required video resolution". Plus, I don't have a working earphones for it (single jack), and BT earphones are unusable. Laptop 2: CPU goes 90%, so it copes (barely), but the meet system refuses my camera, "camera does not support required video resolution". On both laptops, the camera is recognized and works in "setup", but not on the actual session. Desktop: Has ample CPU power, but the camera never worked (in more than a decade; the display has both camera and mic, only the mic is recognized some years, which is not this year). I'm not happy about buying a camera and earphones. (My personal needs were covered by whatsap) Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
My setup - vanilla leap 15.2 with a Microsoft USB camera+microphone, two speakers connected with the normal minijack, a regular desktop machine, with KDE and Firefox. At first, I think I had to install pulseaudio-something, I think Gertjan suggested it.
This has worked well with meet.o.o, with Cisco webex, with gotomeeting and with zoom.
My problem is unsolvable by me.
Laptop 1: CPU goes 100% and sound stutters. The meet system refuses the internal camera, "camera does not support required video resolution".
That is a Jitsi error message. If you google it, one suggestion is to go to https://test.webrtc.org to check out your hardware. I just did with my laptop, and it complained the microphone was not working or the volume set too low. For instance.
Plus, I don't have a working earphones for it (single jack), and BT earphones are unusable.
You don't actually need them, the speakers will do just fine.
Laptop 2: CPU goes 90%, so it copes (barely), but the meet system refuses my camera, "camera does not support required video resolution".
My hunch - those two are related. What happens if you just disable the camera, in jitsi ?
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information. -- Per Jessen, Zürich (14.9°C) Member, openSUSE Heroes
Per Jessen wrote:
Carlos E. R. wrote:
My setup - vanilla leap 15.2 with a Microsoft USB camera+microphone, two speakers connected with the normal minijack, a regular desktop machine, with KDE and Firefox. At first, I think I had to install pulseaudio-something, I think Gertjan suggested it.
This has worked well with meet.o.o, with Cisco webex, with gotomeeting and with zoom.
My problem is unsolvable by me.
Laptop 1: CPU goes 100% and sound stutters. The meet system refuses the internal camera, "camera does not support required video resolution".
That is a Jitsi error message.
FWIW, I get the same on my elderly Toshiba laptop, including a firefox thread using up a full CPU. The laptop has a UVC video camera, type CNF9055. In meet.o.o, it first reports "unable to access your camera", when I click it adds the blurb about resolution, which I read to be a side effect of not being able access the camera at all. Maybe bring up the issue on the general list, see what other people say. -- Per Jessen, Zürich (13.2°C) Member, openSUSE Heroes
On 07/10/2020 13.46, Per Jessen wrote:
Carlos E. R. wrote:
My setup - vanilla leap 15.2 with a Microsoft USB camera+microphone, two speakers connected with the normal minijack, a regular desktop machine, with KDE and Firefox. At first, I think I had to install pulseaudio-something, I think Gertjan suggested it.
This has worked well with meet.o.o, with Cisco webex, with gotomeeting and with zoom.
My problem is unsolvable by me.
Laptop 1: CPU goes 100% and sound stutters. The meet system refuses the internal camera, "camera does not support required video resolution".
That is a Jitsi error message. If you google it, one suggestion is to go to https://test.webrtc.org to check out your hardware. I just did with my laptop, and it complained the microphone was not working or the volume set too low. For instance.
I'll try that. Laptop 2. Microphone passes. Camera passes at 320*240, gets stuck at 640*480. Prints a small progress green line that stops at the end where it should say "ok". Doesn't do any more testing. Cpu load is 8 by pulse audio. Camera led is now off. Laptop-1 on wifi. Camera fails at 1280*720, network warning at ipv6, connectivity warning because "reflexive connectivity" video bandwidth throughput fails. Laptop-1 on eth. gets stuck when testing camera at 640*480, same as laptop-2 Restarting the test passes that point: Camera fails at 1280*720, network warning at ipv6, connectivity warning because "reflexive connectivity" video bandwidth throughput fails. No improvement. Video throughput says it failed because "frame rate mean is 0, can not test bandwidth without a working camera". Retesting laptop-2 Laptop 2. Microphone passes. Camera fails at 1280*720. Network warning, no ipv6. Video thorughput fails, same problem as laptop-1
Plus, I don't have a working earphones for it (single jack), and BT earphones are unusable.
You don't actually need them, the speakers will do just fine.
In my experience, they tend to work badly. I know that on laptop-2 the integrated microphone in the past captured the noise of the hard disk and the fan. Without a loopback test, this is impossible to know. Skype had it. On laptop-1, the speakers are bad quality, so I need earphones on it in order to understand people.
Laptop 2: CPU goes 90%, so it copes (barely), but the meet system refuses my camera, "camera does not support required video resolution".
My hunch - those two are related. What happens if you just disable the camera, in jitsi ?
Then no camera, I guess. Ah, you mean the cpu load? no, no change. I played a lot with camera settings, no difference.
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information.
I have never used meet, I don't know what is necessary. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 07/10/2020 13.46, Per Jessen wrote:
Carlos E. R. wrote:
My setup - vanilla leap 15.2 with a Microsoft USB camera+microphone, two speakers connected with the normal minijack, a regular desktop machine, with KDE and Firefox. At first, I think I had to install pulseaudio-something, I think Gertjan suggested it.
This has worked well with meet.o.o, with Cisco webex, with gotomeeting and with zoom.
My problem is unsolvable by me.
Laptop 1: CPU goes 100% and sound stutters. The meet system refuses the internal camera, "camera does not support required video resolution".
That is a Jitsi error message. If you google it, one suggestion is to go to https://test.webrtc.org to check out your hardware. I just did with my laptop, and it complained the microphone was not working or the volume set too low. For instance.
I'll try that.
Laptop 2. Microphone passes. Camera passes at 320*240, gets stuck at 640*480. Prints a small progress green line that stops at the end where it should say "ok". Doesn't do any more testing. Cpu load is 8 by pulse audio. Camera led is now off.
Laptop-1 on wifi.
Camera fails at 1280*720, network warning at ipv6, connectivity warning because "reflexive connectivity" video bandwidth throughput fails.
Laptop-1 on eth.
gets stuck when testing camera at 640*480, same as laptop-2
Restarting the test passes that point:
Camera fails at 1280*720, network warning at ipv6, connectivity warning because "reflexive connectivity" video bandwidth throughput fails.
No improvement.
Video throughput says it failed because "frame rate mean is 0, can not test bandwidth without a working camera".
Retesting laptop-2
Laptop 2. Microphone passes. Camera fails at 1280*720. Network warning, no ipv6. Video thorughput fails, same problem as laptop-1
Plus, I don't have a working earphones for it (single jack), and BT earphones are unusable.
You don't actually need them, the speakers will do just fine.
In my experience, they tend to work badly. I know that on laptop-2 the integrated microphone in the past captured the noise of the hard disk and the fan.
Without a loopback test, this is impossible to know. Skype had it.
On laptop-1, the speakers are bad quality, so I need earphones on it in order to understand people.
Laptop 2: CPU goes 90%, so it copes (barely), but the meet system refuses my camera, "camera does not support required video resolution".
My hunch - those two are related. What happens if you just disable the camera, in jitsi ?
Then no camera, I guess.
Ah, you mean the cpu load? no, no change. I played a lot with camera settings, no difference.
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information.
I have never used meet, I don't know what is necessary. Just wondering Carlos, is your user a member of the video group ? On my
Op woensdag 7 oktober 2020 19:50:43 CEST schreef Carlos E. R.: previous laptop I needed to do that. Don't know about my Tuxedo, did that anyway. -- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2020-10-07 at 19:59 +0200, Knurpht-openSUSE wrote:
I have never used meet, I don't know what is necessary. Just wondering Carlos, is your user a member of the video group ? On my previous laptop I needed to do that. Don't know about my Tuxedo, did that anyway.
The camera works fine when I click on the cogwheel for configuration. First it says it has no access, and a second later it activates and I see myself. But yes, at least on laptop-2 I see I'm in group "video". - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX34D1xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV4zYAnRFMmnmT/JjwPy7LHv/X Y4TCz2HWAJ9XaOYsku2QOHNSQzLCH4s6tpFTBQ== =HCqA -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information.
I have never used meet, I don't know what is necessary.
It's the usual when debugging/diagnosing a problem with hardware, model & type information - which cameras and such. -- Per Jessen, Zürich (11.3°C) Member, openSUSE Heroes
On 07/10/2020 20.11, Per Jessen wrote:
Carlos E. R. wrote:
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information.
I have never used meet, I don't know what is necessary.
It's the usual when debugging/diagnosing a problem with hardware, model & type information - which cameras and such.
It is not my hardware problem, except that it is old and not powerful. My hardware works fine, just not with meet. Notice there is another thread on the support mail list with the same info. I can post there the information link from https://test.webrtc.org -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 07/10/2020 20.11, Per Jessen wrote:
Carlos E. R. wrote:
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information.
I have never used meet, I don't know what is necessary.
It's the usual when debugging/diagnosing a problem with hardware, model & type information - which cameras and such.
It is not my hardware problem, except that it is old and not powerful. My hardware works fine, just not with meet.
I would still call that a hardware issue, we just don't know the culprit. Maybe jitsi does not support your camera, maybe your camera does indeed not provide the minimum required resolution, but unless we know which camera, it is difficult to tell. Looking at my elderly Toshiba laptop, the UVC CNF9055 camera only provides 640x480, but works fine in guvcviewer. I have a hunch our jitsi at meet2 might require minimum 720. Maybe there is server setting that needs tweaking? which resolution does your camera deliver ? -- Per Jessen, Zürich (10.6°C) Member, openSUSE Heroes
On 08/10/2020 09.21, Per Jessen wrote:
Carlos E. R. wrote:
On 07/10/2020 20.11, Per Jessen wrote:
Carlos E. R. wrote:
Someone has to explain to me what is the problem with the camera resolution and why does CPU power skyrocket.
It's very difficult to do with so little information.
I have never used meet, I don't know what is necessary.
It's the usual when debugging/diagnosing a problem with hardware, model & type information - which cameras and such.
It is not my hardware problem, except that it is old and not powerful. My hardware works fine, just not with meet.
I would still call that a hardware issue, we just don't know the culprit. Maybe jitsi does not support your camera, maybe your camera does indeed not provide the minimum required resolution, but unless we know which camera, it is difficult to tell.
I just posted the camera information to the thread Subject: Re: [opensuse-support] Can't use https://meet2.opensuse.org/ - camera description To: oS-sprt <opensuse-support@opensuse.org>
Looking at my elderly Toshiba laptop, the UVC CNF9055 camera only provides 640x480, but works fine in guvcviewer. I have a hunch our jitsi at meet2 might require minimum 720. Maybe there is server setting that needs tweaking? which resolution does your camera deliver ?
320*240 and 640*480 - full details on the other thread. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 06/10/2020 21.28, Carlos E. R. wrote:
On 05/10/2020 20.02, Carlos E. R. wrote:
On 04/10/2020 20.51, Christian Boltz wrote:
Hello,
Remember that yesterday I could not join? I created my own meet room, and there it worked fine. Thus there is something in the meeting room yesterday that impedes my machines to have video. Maybe it forces high resolution video which I don't have :-? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Hello, Am Mittwoch, 7. Oktober 2020, 21:39:12 CEST schrieb Carlos E. R.:
Remember that yesterday I could not join?
I created my own meet room, and there it worked fine. Thus there is something in the meeting room yesterday that impedes my machines to have video. Maybe it forces high resolution video which I don't have :-?
I didn't do any special settings for the meeting room. However, I noticed that you mentioned testing with meet.o.o on the support mailinglist, while we used meet2.o.o. On which of the two servers/domains did you test, meet or meet2? Also, does it break again if you use the other one? Regards, Christian Boltz -- ToFus entstehen oft aus der Bequemlichkeit des Anwenders heraus, der die Mail unbearbeitet dann übernimmt und seinen Senf ganz dick oben aufs Wurstbrot schmiert (oft auch, wenn Honig drunter war). [Thorsten Kettner in suse-linux]
On 08/10/2020 00.12, Christian Boltz wrote:
Hello,
Am Mittwoch, 7. Oktober 2020, 21:39:12 CEST schrieb Carlos E. R.:
Remember that yesterday I could not join?
I created my own meet room, and there it worked fine. Thus there is something in the meeting room yesterday that impedes my machines to have video. Maybe it forces high resolution video which I don't have :-?
I didn't do any special settings for the meeting room.
However, I noticed that you mentioned testing with meet.o.o on the support mailinglist, while we used meet2.o.o.
On which of the two servers/domains did you test, meet or meet2? Also, does it break again if you use the other one?
I tried "meet", I was not aware they were different. I'll try testing on meet2. [...] Right, it fails on meet2. It works on the "settings", fails on the meeting. Sigh :-( -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (4)
-
Carlos E. R. -
Christian Boltz -
Knurpht-openSUSE -
Per Jessen