=== ErichEickmeyer is now known as Eickmeyer [19:38] Eickmeyer[m]: yes headphones are a thing... and jack doesn't deal with it. It is ok to make that a bug :) [19:41] Eickmeyer[m]: with regard to keyboard volum controls, I do think We can fix that. I would call that a -desktop bug. I don't have a keyboard with volume controls to play with. [19:47] isn't there a option to add shortcuts to control the volume with those? [19:47] Not an obvious one... but yes. [19:48] The volumcontrol sets this based on what pulse tells them the default output is [19:48] Thats not a great idea. So normally the volume control deals with hw:0,0,0 [19:49] On KDE it's easy to set up shortcuts to control the volume but on Xfce i'm struggling to find that and get it done [19:49] Pulse does have a @default which is always right. [19:50] If I had a keyboard with Volume controls... [19:50] * OvenWerks keyboard is old enough to have an xt-at switch... [19:51] i guess that's really old? [19:51] early 1980s I guess [19:52] Full size din plug on it and real switches. [19:52] holy keystrokes Batman [20:02] But yeah, knowing the volume up and down key names is the most important part of making a shortcut [20:05] pactl set-sink-volume @DEFAULT_SINK@ +1db [20:05] or something close to that [20:06] Actually that works. change to -1db for down of course. [20:33] OvenWerks: It's not a -desktop bug. xfce4-volumed automatically detects whether or not you have media controls on your keyboard and assigns them regardless of keyboard shortcuts. Unfortunately, it does not survive a backend change. Afaik, it's a known bug. [20:34] Xubuntu suffers from the exact same problem. [20:34] But if there is a keyboard shortcut in desktop that should override ? [20:35] Nope. xfce4-volumed does not depend on keyboard shortchuts. [20:37] I understand that, but adding a shortcut may still work around it... maybe it will send both commands [20:38] In which version did it start not working? [20:38] I don't remember. I know I found the fix from something 2016-2017-ish. [20:38] The problem is that not all keyboards send the same thing for the volume controls. [20:39] :P [20:39] Is there a small set of what they do send? [20:39] I don't know. [20:40] if it's only one or two or at least less than 10 and those ten are unique, it would be no problem. [20:41] I think a decent workaround would be to have -controls do something like "if ${XDG_DESKTOP}=="XFCE"; then killall xfce4-volumed; xfce4-volumed; fi". [20:41] ^when "Stop Jack" is pressed." [20:41] EEEww... [20:41] Yeah. It sucks. [20:42] smells anyway. [20:42] Very, very stinky, but the problem is that xfce4-volumed wasn't designed with Jack in mind. [20:44] Actually it is just incorrect, it should use @DEFAULT_SINK@ as the device [20:45] As it does, but for some strange reason it doesn't survive a sink change. [20:45] The process just hangs, and has to be killed. [20:50] Hmm The first person I talked to said it was using raw device names [20:50] like 0,0,0 [20:50] or 0 actually. [20:51] of course I have not gotten pactl set-sink-volume @DEFAULT_SINK@ +1db to not work here... [20:51] (18.04) [21:05] playing on 16.04 on my wife's computer. using Key-Mon it just shows "Vol+" and "Vol-" however when I make a short cut, it is shown as XF86AudioRaiseVolume [21:05] Found it. bug 1291855 [21:05] bug 1291855 in xfce4-volumed (Ubuntu) "After pulseaudio restart, volume keys no longer work" [Undecided,Confirmed] https://launchpad.net/bugs/1291855 [21:07] Eickmeyer: my understanding has always been that system or DE shortcuts grab the key stroke before any application sees it (causes trouble in Ardour) [21:07] Yes, but if we're using xfce, then the xfce "official" way is xfce4-volumed handles the volume control. [21:08] So does using the mouse wheel on top of the controller icon also not work? [21:09] No, that works too, but people would rather use the volume keys sometimes. [21:09] * OvenWerks has never had that happen [21:09] so the mouse wheel works but the keys don't? [21:09] Yes. [21:10] I would think the applet would use the same command for both. [21:10] Hence the ancient bug report. [21:10] Looking at the package, there has been no bump in version number for several cycles, so the bug hasn't been addressed afaik. [21:11] I'm hoping bluesabre has some insight. [21:14] [21:16] add to /etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml [21:16] The problem should go away. [21:16] Okay, so, according to Unit193 and brainwash, they don't even use xfce4-volumed anymore. They use xfce4-pulseaudio-plugin. [21:17] That handles the problem. [21:17] xfce4-volumed needs to be removed from our seed. [21:17] hello bitrot [21:17] Yep. [21:18] Which means we need to remove xfce4-volumed from our seed, make sure we have xfce4-pulseaudio-plugin in our seed, and make sure it's in the default panel. [21:18] The problem with our setup is that all the machines in the house that xfce run jackd from session start. [21:19] The one we have is an indicator so it puts itself in the panel by itself. [21:19] That's probably indicator-sound, which is also subject to bitrot, and needs to be removed from the seed. [21:20] * Eickmeyer is noticing Xfce is getting less and less friendly to Jack [21:20] So long as there is something there... and it does work. [21:21] * OvenWerks puts his Yf's machine back the way it was... [21:21] Yeah. Well, if it's working for Xubuntu, then it'll work for us. [21:25] OvenWerks: This too: https://bugzilla.xfce.org/show_bug.cgi?id=15332 [21:25] bugzilla.xfce.org bug 15332 in General "Automatically reconnect to PulseAudio" [Normal,New] [21:25] Looks like there's a patch. [21:31] If it's using dbus to connect and control, dbus should do that for the application [21:32] In otherwords sending a command message to pulse should make it start if it is stopped and it should not matter if the running instance is the same one or not. [21:33] So, shoddy coding? [23:46] Eickmeyer: just wondering if we should make a bunch of menu categories that are X-us-custom [23:59] OvenWerks: What would that do? [23:59] * Eickmeyer needs examples [23:59] Well it would make it really easy for our menu-item editor to place items exactly where th euser wants