[00:39] <MauroGaspari[m]> <Eickmeyer[m] "Telegram should just talk to Pul"> Interesting, I found out that in telegram I can switch output from "Default" to "JACK Default". Strange that I cannot see the JACK-Pulse bridge in the output but I can see it in the input. Quite confusing this Telegram haha. Will try later and see if that helps.
[00:41] <Eickmeyer[m]> Mauro Gaspari: The Jack-Pulse bridge is going to show up as "jack-sink" or something to that effect.
[00:42] <MauroGaspari[m]> <Eickmeyer[m] "Mauro Gaspari: The Jack-Pulse br"> Yes, that is the standard. In Telegram However. I see this, which is a bit different. https://imgur.com/a/wnc68mF
[00:42] <MauroGaspari[m]> the input looks normal, output hmm. well I will have to test it out :)
[00:44] <MauroGaspari[m]> Anyway, I don't think this is a problem of Ubuntu Studio, but Telegram probably doing things a bit different.
[00:44] <Eickmeyer[m]> Did you look at a patchbay and see if any connection needs to be made?
[01:11] <MauroGaspari[m]> patchbay looks ok. and even with JACK Default, telegram escapes the settings and blasts at full sound. wow, the only way I found so far to tame the volume of telegram, is with QAS Mixer. I guess it is using ALSA directly? 
[01:12] <MauroGaspari[m]> How funny, because within Telegram I can control the input sound as with any other software. So input works fine, output doesn't behave 🤣🤣🤣
[01:13] <MauroGaspari[m]> Later as I have more time, I'll try to boot something that does not use studio-controls and only uses plain pulseaudio, and see how that works there. 
[02:05] <Eickmeyer[m]> Mauro Gaspari: Or, you can run Telegram through Jack Mixer.
[04:42] <MauroGaspari[m]> Also I will try on my laptop and see if there is a newer version of telegram that does not have this issue 
[05:52] <OvenWerks> MauroGaspari[m]: if you could.... while telegram is running, in a terminal type:
[05:52] <OvenWerks> cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[05:53] <OvenWerks> MauroGaspari[m]:  that is all one line by the way
[05:55] <OvenWerks> MauroGaspari[m]: you might want to wait untill tomorrow as I am going to bed soon. so around 1400 pacific time... 2100 utc (or is that 2200utc?)
[05:56]  * OvenWerks thinks he is -800 right now but -0700 in the summer.
[05:59] <OvenWerks> PDT so -0700 so 2100 was about right. but the idea is so the paste url is still valid :)
[06:05] <MauroGaspari[m]> OvenWerks thanks. You can ping me here when you are around. No rush. That issue is not a big deal for me, i am trying to figure things out so if i understand where the problem originates,  i can then go and open bug reports with the appropriate teams.
[06:13] <OvenWerks> MauroGaspari[m]: that command will give you a list of audio devices and which program has them open. this will tell you if telegram has directly grabbed the device.
[10:14] <MauroGaspari[m]> OvenWerks: interesting stuff I found out today. I tested telegram client, but on my laptop which is Ubuntu Budgie 20.10 with studio controls. And all seems to be working fine there. telegram can see correct bridge output, and does not blast out of volume controls. https://imgur.com/a/OfLgqow
[15:12] <OvenWerks> MauroGaspari[m]: at first glance that looks wrong... however that is not pavucontrol you are looking at. Whatever controller you are looking at should only show jack-sink. However it may be that the "default" shown there is just to use whatever is default in pulseaudio which should be the same as jack-sink. The command I gave above would give better information.
[15:16] <OvenWerks> certainly, for things to work right, I would expect jack-source and jack-sink to be the right choices. Opening pavucontrol from studio-controls should give a better idea of what is going on. Some of the newer audio controls hide information from the dumb user.
[15:17] <OvenWerks> Also, at this time, studio controls is not compatable with pipewire, so make sure your system is just pulseaudio and jack
[15:26] <OvenWerks> Last I checked, the version of pipewire ubuntu has would not auto connect to a running jack instance. There seems to be no manual way to set that up.
[15:41] <Eickmeyer[m]> OvenWerks: Considering it's supposed to be a drop-in replacement and not have a separate Jack instance, that makes sense. It's only meant to be run by itself in lieu of both Pulse and Jack.
[15:42]  * Eickmeyer[m] is off to get his second COVID jab.
[15:51] <MauroGaspari[m]> <OvenWerks "certainly, for things to work ri"> 
[16:20] <MauroGaspari[m]> OvenWerks:  🥳wohoo I am a wizard! I figured it out! 🎉
[16:20] <MauroGaspari[m]> ...ok actually I am not, and I have not figured it out. 😅. However, I removed and purged the telegram-desktop package installed via ubuntu 21.04 repos. And I installed the flatpak. and it works great out of the box, sound input and output are both the correct ones. Output Device = Jack sink (pulse_out), and Input Device = Jack source (pulse_in) . And telegram respects my volumes and does not blow my
[16:20] <MauroGaspari[m]> speakers at max volume as the package from ubuntu repos.
[16:47] <OvenWerks> Eickmeyer[m]: actually, pipewire is supposed to give a device to jack when asked and then connect to that jack instance with the right number of ports to connect to that device.
[18:14] <OvenWerks> Eickmeyer[m]: the problem is that in that case why not just use PW? The time when this is needed is generally when jack has to be used for one of the backends PW does not support such as netjack, FW, etc.