#trinity-desktop < 2026/05/22
[01:01]076AAJ3NT has joined
[01:03]076AAJ3NT has quit (Client Quit)
[01:08]SlavekB: Ceux, interesting, I tried turning on second audio device (audio on usb), switching amarok to this device and back to first (to the internal sound card), then turning off second device again (audio on usb). And the column showing the current playback level stopped for Amarok. The overview for the device itself shows correctly (internal sound card), but for Amarok it does nothing.
[01:09]SlavekB: The Devices tab looks great!
[01:10]SlavekB: The only thing that looks weird is that when you switch Profile, the whole window flashes unpleasantly.
[01:13]SlavekB: Ceux, another very interesting thing - the overview of the current playback level for the device itself was delayed by a few seconds - about 10 to 20. Amarok was no longer playing anything, the Playback tab was empty, but the column on the device still showed some level before it also "caught up" with the current status and stopped displaying it.
[01:14]SlavekB: After stopping playback and restarting, the current playback level for Amarok is now displayed correctly in the Playback tab.
[01:20]SlavekB: Ceux, thank you! The ability to choose which device to use as the default is exactly what I was missing and what really annoyed me about pulseaudio!
[01:23]SlavekB: On Ubuntu 20.04 (Focal), which we still support, the libpulse version is 13.99.1-1ubuntu3, for which some API changes will need to be taken care of:
[01:24]SlavekB: ../src/ui/devicespage.cpp: In function ‘TQString portTypeIcon(uint32_t)’:
[01:24]SlavekB: ../src/ui/devicespage.cpp:22:14: error: ‘PA_DEVICE_PORT_TYPE_HEADPHONES’ was not declared in this scope
[01:24]SlavekB: 22 | case PA_DEVICE_PORT_TYPE_HEADPHONES: return "audio-headphones";
[01:24]SlavekB: | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[01:24]SlavekB: ../src/ui/devicespage.cpp:23:14: error: ‘PA_DEVICE_PORT_TYPE_HEADSET’ was not declared in this scope
[01:24]SlavekB: 23 | case PA_DEVICE_PORT_TYPE_HEADSET: return "audio-headset";
[01:24]SlavekB: | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
[01:24]SlavekB: ../src/ui/devicespage.cpp:24:14: error: ‘PA_DEVICE_PORT_TYPE_MIC’ was not declared in this scope; did you
[01:24]SlavekB: mean ‘PA_DEVICE_TYPE_SINK’?
[01:24]SlavekB: 24 | case PA_DEVICE_PORT_TYPE_MIC: return "audio-input-microphone";
[01:24]SlavekB: | ^~~~~~~~~~~~~~~~~~~~~~~
[01:24]SlavekB: | PA_DEVICE_TYPE_SINK
[01:24]SlavekB: ...and many others in the same sense.
[01:32]SlavekB: Very strange. It's been a few minutes since Amarok finished playing, nothing else is playing, but the bar showing the playback level of the device itself is still showing something.
[03:09]micheleC has joined
[06:47]SlavekB: Pitriss, if you have the extra component specified in your apt configuration for PTB, or the extra-r14 component for PSB, you can see a package called tdemix-trinity.
[06:48]SlavekB: Ceux, I was a little surprised that I had to use an additional patch not only for PTB, but also for PSB.
[07:17]Fat-Zer has quit (Ping timeout: 250 seconds)
[07:30]Fat-Zer has joined
[09:13]neoncortex has quit (Quit: ZNC 1.9.1+deb2+b3 - https://znc.in)
[10:21]micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[11:31]SlavekB has quit (*.net *.split)
[11:31]bleb has quit (*.net *.split)
[11:31]ccx has quit (*.net *.split)
[11:31]agneli has quit (*.net *.split)
[11:31]ChanServ has quit (*.net *.split)
[11:34]ccx has joined
[11:34]agneli has joined
[11:34]ChanServ has joined
[11:34]tantalum.libera.chat sets mode: +o ChanServ
[11:34]SlavekB has joined
[11:34]bleb has joined
[11:35]bleb has quit (Max SendQ exceeded)
[11:35]bleb_ has joined
[11:35]bleb_ is now known as bleb
[13:21]ElCaracho_ has joined
[13:21]ElCaracho has quit (Read error: Connection reset by peer)
[13:45]pitriss: SlavekB: I'll doublecheck that and will try to install it :) Thank you
[13:50]SlavekB: As you saw in the comments, I have already started testing on PSB.
[13:52]pitriss: It works.. I'll try to use it for a bit and I will tell you my impressions.. so far it looks good.. I might have some suggestions to the device tab after i will let to settle that in me.. :)
[13:54]SlavekB: For me, the mixer window opened very small at first, so nothing was visible on the Devices tab at first glance.
[13:54]pitriss: definitelly I would use some legend for the dot colors or so.. and yea, i needed to resize it too.. :)
[13:54]pitriss: and I imediatelly switched it to full mixer window..
[13:55]SlavekB: When I enlarged the window, I saw detailed information and was pleased with how much information there was.
[13:55]pitriss: If it will one day replace kmix, IMHO it should have manual selection for the backend I want to control.. as pulse stands on top of ALSA
[13:57]SlavekB: I expect this to be the successor to kmix.
[13:58]pitriss: And as person who completely lacks understanding of PA but have attention to detail.. I noticed that most pavu apps have volume range 0-150%, tmix have 0-100% might be different interpretation of the same, might limit PA funstionality.. I'm not able to tell whats true :)
[14:00]pitriss: if its the second option, I would like checkbox in the settings with "allow values over 100%"
[14:06]ceux: SlavekB: yes that flash is a problem. it does a total rebuild essentially of the screen. i need to fix it i think.
[14:06]ceux: SlavekB: there is a timer to 'let off the gas' on the audio, to smooth it out. I wonder if this is a problem.
[14:07]ceux: maybe the math is wrong
[14:07]ceux: as for the mixer tab options, it may be prudent to have a 3rd line of attack, if Pulse + Alsa, show additional information.
[14:08]ceux: pitriss: tmix is set to 0-100, this needs to get improved yes. pulse lets you crank stuff up to various, sometimes 150, 125, etc.
[14:08]SlavekB: I'll be away from the computer for a few hours now.
[14:08]ceux: thanks slavek, sorry I just sat down at work.
[14:08]ceux: Can we create a repository, do some PRs and get it moving more orderly?
[14:08]ceux: for example, i fixed a FTBFS in -Werr yesterday
[14:09]ceux: i have a branch for alsa+oss that needs to go to master.
[14:09]ceux: and i want feedback from everyone else...
[14:09]ceux: lastly, i am building against the older tdebase/libs, so maybe if i move to the PSB version i can fix the headers to go against tapplicationheader.h?
[14:10]ceux: I also have not signed a DCO for this code..
[14:10]SlavekB: TGW can be used to create PRs, so revisions can be made there.
[14:11]SlavekB: ...but now I really have to go... bye for now.
[14:11]pitriss: ceux: but those vu meters looks fantastic.. I am using something simillar on daily basic.. i found some random source code for "always on top PA Vu-bar" and for me as I have something playing constantly its nice addition.. :D One day I will fill feature request to make it official TDE addition :D :D
[14:12]ceux: thanks i hoped that you like them. Its for me good to see visually what is making noise.
[14:13]pitriss: yeah.. for me, that info is helpful to see how saturated output is as not every app have the same strenght at the output.. key differences are spotify vs web browsers
[14:21]ceux: thank you. any additional feedback about what is good or not helps immensely, as i just kind of 'did it'
[14:21]pitriss: - now I noticed, when bigger system font is used (yes my eyes suck :D) 100% vs two digits make column jump.. maybe it could be fixed for 3 digits value permanently
[14:23]ceux: i see, so we need to fix the width at 3 digits to avoid it moving?
[14:37]pitriss: yeah.. it would be great.. fix min-widht to 3 digits :)
[15:39]ceux: workin on it thank yu.
[15:41]pitriss: Thank you for your effort ceux.. :) I am only trying to help.. And take my oppinions with a grain of salt.. I am biased.. I don't like PA, i am tolerating that thing because these days we can't avoid it :)
[15:47]ceux: oh no problem at all i like the feedback
[15:47]ceux: its paramount others test and give feedback. the UI needs to be god and better than pavucontrol.
[16:07]ceux: pitriss: i deployed a fix.
[16:07]ceux: SlavekB: I thought 20.04 EOL was last year?
[16:10]a-865 has quit (Ping timeout: 246 seconds)
[16:28]a-865 has joined
[19:15]magnus_6 has joined
[19:16]magnus_6: Hey, guys. I have a question, does anyone of you use the bourbon menu found on q4os and if yes, where would I find it to install on my system?
[19:58]ceux: bourbon menu...
[19:58]ceux: sounds tasty
[20:15]ceux: SlavekB: I switched to the PSB builds, thinking I would see the tstandarddirs.h... is that no right?
[21:18]a-865 has quit (Ping timeout: 276 seconds)
[21:33]a-865 has joined
[22:19]ceux: oh got it. thanks using the PSB not PTB builds
[22:25]magnus_6 has quit (Ping timeout: 252 seconds)
[23:09]neoncortex has joined

#trinity-desktop < 2026/05/22