In answer to myself - and so that it's not lost: Reserve card#0 for the 4th soundcard or snd_usb_audio - whatever comes first: # /etc/modprobe.d/alsa-base.conf options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 Now chromium still uses mic#0 of card#0 - which may or may not be the working virtual mic of the usb mic. In my case it's not a working mic, I have to select mic#1 of card#0. Anyway, it is fairly persistent and at least works across reboots in a consistent way - that is, till you have 2 snd_usb_audio devices or ... *sigh* And for the record: I even tried pulsaudio - but as my workaround does not mention it you can safely assume that I did not have great success with that thingie. Nik Anno domini 2021 Sat, 5 Jun 14:02:23 +0200 Dr. Nikolaus Klepp scripsit: > Hi all! > > This is in answer to all the postings in this thread. > > Anno domini 2021 Fri, 4 Jun 16:44:40 -0500 > Michael scripsit: > > > > "WebRTC allows websites to view your unique IP address and expose your > > > > identifying details, even if you are using a VPN." > > > > > > > > I guess if you don't care, but I'm a bit tired of G, FB, and the rest > > > > tracking everything everyone does... > > > > > > Sure. Problem is, I need jitsi working. Big surprise after todays update: > > > chromium is not able to select any mic but the one on card #0. All other > > > devices get a "resource busy" error - which is absolutely useless. BTW. > > > chromium_89 shows the same problem with kernel 5.10.40. But audacity works > > > like a charm :( > > > > Try Palemoon and/or Waterfox? That'd at least get you out of some of the > > Google hell Chromium is... > > Firefox and all its decendents use the first input source als mic and you cannot select any other. That is true for firfox, waterfox, icecat ... whatever. As the first input source may aor may not be anything real, it renders firefox quite useless for any browserbased (video)conference. > > It's in the very nature of WebRTC to expose your address, as it's using p2p for 2 client conversation. If that's a problem, don't use it. I myself use tox for secure conferences, but that does not allow videochat for more than 2 parties (well, you can work around that ...). > > So chrome/chromium is/was the only browser capable of selecting the correct input source. With kernel 5.10.40-1 chromium is not able to so any more for input source served by snd_usb_audio. I do not think it's directly related to snd_usb_audio but to all devices that only present input sources without output sinks like webcams, usb-mics etc., as multiple onboard soundcards and PCI soundcards on the same system are selectable within chromium and they all have source+sink. Looks like a classic "intelligent programmer made a sesible choice" problem to me :/ > > My workaround is for now: attach a analog mic to the onboard soundcard aka card#0. That mic is then used by firefox and chromium alike. Well, take what you get and run like hell ... aint there a config option for alsa to build assign the default/sysdefault mic to device and the output to an other? > > Niki > > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
