https://wiki.archlinux.org/api.php?action=feedcontributions&user=Barbariccow&feedformat=atomArchWiki - User contributions [en]2024-03-29T13:40:45ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:PulseAudio&diff=521476Talk:PulseAudio2018-05-17T04:45:13Z<p>Barbariccow: /* Can't build package with modern glibc */ new section</p>
<hr />
<div>==Configuration of the PulseAudio ALSA plugin==<br />
Can anybody give an example where to use the ''pcm.pulse'' setting? --[[User:BertiBoeller|BertiBoeller]] 12:33, 17 October 2009 (EDT)<br />
<br />
== Abandoned draft ==<br />
<br />
[[PulseAudio/Configuration]] was initially created to discuss PA configuration; then its goal was changed to be a replacement for this whole article; then it was abandoned. Currently it's marked for merge in [[PulseAudio#Configuration]]: is there anything worth being merged from there? -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:44, 30 November 2014 (UTC)<br />
<br />
:It seems to focus more on generic explanation/configuration, where the main article is mostly about troubleshooting (considering the size of that section, you'd consider moving it to [[PulseAudio/Troubleshooting]] ...) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:40, 30 November 2014 (UTC)<br />
<br />
::How much sense would it make to actually merge [[PulseAudio/Configuration#Easy_configuration]] and [[PulseAudio/Configuration#Advanced_configuration]] and then simply redirect [[PulseAudio/Configuration]] to [[PulseAudio#Configuration]]?<br />
::I'd agree with moving Troubleshooting to [[PulseAudio/Troubleshooting]].<br />
::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 12:01, 2 December 2014 (UTC)<br />
<br />
:::I do agree it makes sense to merge [[PulseAudio/Configuration#Easy_configuration]] and [[PulseAudio/Configuration#Advanced_configuration]] in [[PulseAudio/Configuration]]. I made an attempt in this way. [[User:Gabx|Gabx]] ([[User talk:Gabx|talk]]) 18:24, 28 December 2014 (UTC)<br />
<br />
::::I like what I see so far, more extensive configuration in the main article also allows to cut back on [[PulseAudio/Troubleshooting]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 23:29, 28 December 2014 (UTC)<br />
<br />
== Restore package list ==<br />
Why [https://wiki.archlinux.org/index.php?title=PulseAudio&diff=381413&oldid=381339 revert the list]? I think Arch News is just a temp reminder. Arch Wiki should keep all needed info.--[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:37, 1 August 2015 (UTC)<br />
<br />
:I'm not sure what the right policy is for this (hence my query in my edit summary) but I would just point out that the [https://www.archlinux.org/news/?page=12 archive] does stretch back to 2002 so I don't think it's unsafe to link to that material. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 16:34, 1 August 2015 (UTC)<br />
<br />
::That's true, but the set of split packages can change in the future... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:37, 1 August 2015 (UTC)<br />
::: Exactly, so at that time, the news page is out of date and only wiki page could be updated to keep up.--[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 12:57, 19 August 2015 (UTC)<br />
<br />
:::We should ask for a more extensive optdepends instead of maintaining this information here. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:03, 1 August 2015 (UTC)<br />
<br />
::::Alternatively creating a ''pulseaudio-modules'' group should be equally simple for the packager, more comprehensible to the user and most naturally referenceable from the wiki. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:14, 1 August 2015 (UTC)<br />
:::::Then before a group is created, should we restore the package list?--[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 12:57, 19 August 2015 (UTC)<br />
<br />
::::::I don't think any action need be taken until such a time that the set of split packages changes. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 17:14, 7 September 2015 (UTC)<br />
<br />
:::::::Considering [https://wiki.archlinux.org/index.php?title=PulseAudio&diff=next&oldid=408749], I think including the list explicitly is useful already. Restored in [https://wiki.archlinux.org/index.php?title=PulseAudio&diff=409861&oldid=409859]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:30, 22 November 2015 (UTC)<br />
<br />
== Equalizer module is unsupported ==<br />
<br />
As of {{pkg|pulseaudio}}-7.0-2, loading the {{ic|module-equalizer-sink}} module results in the following warning:<br />
<br />
pulseaudio[535]: W: [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently unsupported, and can sometimes cause PulseAudio crashes, increased latency or audible artifacts.<br />
pulseaudio[535]: W: [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try unloading this module as a potential workaround.<br />
<br />
Running ''qpaeq'' then makes PulseAudio crash with this error:<br />
<br />
pulseaudio[535]: E: [pulseaudio] iface-module.c: Assertion 'pa_dbus_protocol_add_interface(m->dbus_protocol, m->path, &module_interface_info, m) >= 0' failed at modules/dbus/iface-module.c:309, function pa_dbusiface_module_new(). Aborting.<br />
<br />
-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 08:43, 28 September 2015 (UTC)<br />
<br />
:This is not correct. Recently installed {{pkg|pulseaudio}}-7.0-2 and following the instructions in the wiki am successfully running the equalizer.<br />
<br />
:[[User:Brettski|brettski]] ([[User talk:Brettski|talk]]) 03:46, 13 October 2015 (UTC)<br />
<br />
::This is odd. You should have at least seen the first warning in your journal... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:01, 13 October 2015 (UTC)<br />
<br />
== Adding User to Audio Group ==<br />
<br />
Currently, the article says, "There is no need to add your user to audio group, as it uses udev and logind to dynamically give access to the currently "active" user". That is a little heavy-handed; perhaps a wording like "There is '''usually''' no need..."? For instance, on one of my machines running pulse audio, I was unable to play any sounds as "me", but could using root. The server is running headless, and I access it over SSH. It's understandable that udev doesn't consider "me" the currently "active" user in this scenario. It is essential to know that adding a user to the audio group helps in this circumstance, so I appreciate the explicit mention of that group. Does my rewording make sense, or is there a better rewording? [[User:Lmat|Lmat]] ([[User talk:Lmat|talk]]) 14:29, 1 March 2016 (UTC)<br />
:This looks like a reasonable rewording. Additionally I would considering explicitly describing in which cases it might make sense in the Wiki. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 14:56, 1 March 2016 (UTC)<br />
<br />
== Default sink @DEFAULT_SINK@ and keyboard control ==<br />
<br />
I got a hard time finding {{ic|pactl set-sink-volume @DEFAULT_SINK@ -5%}}.<br />
<br />
{{ic|@DEFAULT_SINK@}} comes very handy and fixes a long time frustration with PulseAudio (with sink indices changing each time I plug unplug a jack, or to get commands working across multiple machines with different sinks).<br />
<br />
It will probably help more people to make some changes or add a Tip about {{ic|@DEFAULT_SINK@}} somewhere ([[PulseAudio#Keyboard volume control]] ?).<br />
<br />
Only after finding about it, I found [[Xbindkeys#Xbindkeysrc]]. Maybe [[PulseAudio#Keyboard volume control]] could also Tip about [[Xbindkeys#Xbindkeysrc]].<br />
<br />
(I would have edit the page, if only I knew which changes was best: add a Tip and/or change the command lines and/or something else ?)<br />
<br />
-- [[User:Gravemind2a|Gravemind2a]] ([[User talk:Gravemind2a|talk]]) 09:55, 4 September 2016 (UTC)<br />
<br />
: I suppose changing the commands is the best approach. However for those who want to edit a specific sink a small note should be added. This is just my personal opinion on this matter. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 10:11, 4 September 2016 (UTC)<br />
<br />
:: I think it is better suited as a tip, because if you start directly with {{ic|@DEFAULT_SINK@}}, it's not clear at all what the shortcut is for. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:07, 4 September 2016 (UTC)<br />
<br />
:: I've added the tip and edited the [[xbindkeys]] page to link to both [[PulseAudio]] and [[ALSA]] pages for alternative commands. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:37, 4 September 2016 (UTC)<br />
<br />
::: Thanks. I also discovered {{ic|@DEFAULT_SOURCE@}} (for microphone) and I've added tips in [[PulseAudio/Examples#Set default input sources]] and [[PulseAudio/Examples#Set the default output source]] -- [[User:Gravemind2a|Gravemind2a]] ([[User talk:Gravemind2a|talk]]) 11:55, 4 September 2016 (UTC)<br />
<br />
: Hey, Gravemind2a, does {{ic|amixer -q -D pulse sset Master 5%+ unmute}} work for you? Take a look at my comment right above yours, in this Talk page. --[[User:Denilsonsa|Denilsonsa]] ([[User talk:Denilsonsa|talk]]) 11:03, 4 September 2016 (UTC)<br />
<br />
:: Yes it works. But if it also works directly with PulseAudio {{ic|@DEFAULT_SINK@}}, why go through alsa amixer ? (and also long time ago I had issues with fast repeating asynchronous amixer volume commands making left/right speaker unbalanced, that actually made me drop Alsa in favor to PulseAudio)-- [[User:Gravemind2a|Gravemind2a]] ([[User talk:Gravemind2a|talk]]) 11:29, 4 September 2016 (UTC)<br />
<br />
<br />
== Networked audio ==<br />
<br />
I have added a stub/[[PulseAudio#Networked_audio|section]] about sending/receiving audio through the network using PA. The relevant documentation is [https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Network/ here]. I have a working networked PulseAudio setup, it's available [https://github.com/nodiscc/srv01/tree/master/roles/pulseaudio here] as an ansible playbook, please allow for some time for me to port the most important information here. --[[User:Nodiscc|Nodiscc]] ([[User talk:Nodiscc|talk]]) 14:45, 21 November 2017 (UTC)<br />
<br />
== Note: Some confusion may occur ==<br />
<br />
confusion is even bigger after reading this. be more explicit, give examples, what is the advatage and aim of doing what they do? --[[User:UBF6|UBF6]] ([[User talk:UBF6|talk]]) 10:11, 1 May 2018 (UTC)<br />
<br />
== Can't build package with modern glibc ==<br />
<br />
Package (latest, version 11.1) fails to build with the latest (current) glibc headers.<br />
<br />
Applying the following patch will fix the build:<br />
<br />
'''fix-modern-glibc-memfd_create.patch'''<br />
<br />
--- a/src/pulsecore/memfd-wrappers.h 2018-05-17 00:31:19.000000000 -0400<br />
+++ b/src/pulsecore/memfd-wrappers.h 2018-05-17 00:32:02.000000000 -0400<br />
@@ -23,6 +23,7 @@<br />
#ifdef HAVE_MEMFD<br />
<br />
#include <sys/syscall.h><br />
+#include <sys/mman.h><br />
#include <fcntl.h><br />
<br />
/*<br />
@@ -33,10 +34,10 @@<br />
* a whole conflicts with the original glibc header <fnctl.h>.<br />
*/<br />
<br />
-static inline int memfd_create(const char *name, unsigned int flags) {<br />
+/*static inline int memfd_create(const char *name, unsigned int flags) {<br />
return syscall(SYS_memfd_create, name, flags);<br />
}<br />
-<br />
+*/<br />
/* memfd_create(2) flags */<br />
<br />
#ifndef MFD_CLOEXEC</div>Barbariccowhttps://wiki.archlinux.org/index.php?title=Talk:Linux-ck&diff=510122Talk:Linux-ck2018-02-08T05:15:59Z<p>Barbariccow: Remove my comments about maybe ck being discontinued, as it has been confirmed these rumors were false.</p>
<hr />
<div>== BFQ Scheduler auto loading ==<br />
<br />
Inspired by a forumpost i recommend to ad the following text and script to the Wiki at the end of section 2.2.5:<br />
<br />
When using more than one kernel at the same system, you can use the following script in {{ic|/etc/rc.local}}<br />
This will automitically load the BFQ Scheduler only when kernel26-ck is loaded. The BFQ status will be written to a logfile.<br />
<br />
#Enable BFQ for precompiled kernel26-ck from the unofficial repository<br />
TID=$(date +%c)<br />
KERN=$(uname -r | cut -d"-" -f2)<br />
if [ "$KERN" == 'ck' ]; then<br />
modprobe bfq-iosched<br />
echo bfq > /sys/block/sda/queue/scheduler<br />
echo "$TID $(uname -r) with $KERN patch so started bfq for sda" >> /var/log/bfq.log<br />
else<br />
echo "$TID $(uname -r) no bfq loaded" >> /var/log/bfq.log<br />
fi<br />
<br />
:Thanks for the suggestion. I modified the linux-ck package to actually compile in the BFQ (just not enabled by default). Once CK and Paolo get release their respective patches for 3.0.1, I'll update the repo and the wiki page. Thanks for the re-direct btw! [[User:Graysky|Graysky]] 17:12, 8 August 2011 (EDT)<br />
::It seems like BFQ was not compiled into linux-ck-core2 3.0.1-3 ("zcat /proc/config.gz | grep BFQ" shows nothing, and I'm running the -ck kernel).[[User:Jimreynold2nd|Jimreynold2nd]] 14:44, 15 August 2011 (EDT)<br />
:::Right, that's because BFQ for 3.0 does not yet exist. Paolo hasn't released the code for the 3.0 series :) I will update as soon as he does. [[User:Graysky|Graysky]] 04:32, 16 August 2011 (EDT)<br />
<br />
== Enabling BFQ selectively section ==<br />
<br />
This section should be updated: you say to put the "echo bfq" command in rc.local...there is no more support for it, and there is:<br />
1)the systemd-way -> tmpfiles<br />
2)the udev-rule way.<br />
<br />
May be you should report both, or choose what do you think is the best, i trust you!<br />
<br />
Thanks for your time (i preferred to open discussion rather than change it myself, did i the right thing?)<br />
<br />
== New section 2.2.3: rerun grub-mkconfig ==<br />
<br />
After the installation subsection, I would suggest adding a new subsection to remind folks to rerun grub-mkconfig (or the appropriate boot reconfig command for their bootloader) and reboot, so they will be able to see the new kernel and CPU scheduler in action right away. They will have to do this whether or not they want to enable bfq, as I just found out from a kind soul on the Arch Linux Google+ group.<br />
<br />
This step may be obvious to old hands, but as an Arch newb whose system was frequently maxing out, I needed to try BFS and bfq as soon as possible. I'm still getting used to generating a grub config file myself instead of having the installer do it for me...!<br />
<br />
<br />
== Should there be a BFQ section with MuQSS? ==<br />
<br />
I've noticed that it's recommended that one enables BFQ, shouldn't this be removed in place of MuQSS?<br />
<br />
{{unsigned|11:01, 4 August 2017|X89}}<br />
<br />
== ck patchset for linux-4.15 (Unofficial) ==<br />
<br />
This is a merge that I did unofficially to get the ck patchset onto 4.15. So I manually merged the last official patchset from 4.14, made a few minor additions required, some minor changes here and therem etc. There are no additional features or anything here, just a merge forward. I did not do extensive research on all of the recent kernel development work, and I haven't done significant kernel devleopment in years, but I believe everything provided here to be correct. It has been running now stable for me for 36 hours. No lockups, no glitches or lnong hangs, so it seems like everything scheduling-wise is working as intended, which is the core of the patchset and where all the changes I had to make went. Full disclosure: I did get 2 panics one time from ethernet driver (e1000) even though I'm not plugged into anything, but it was just like a tx receive error, didn't cause any noticable issue, and was more likely some artifact of the suspend of the parent OS (I am running linux on virtualbox on top of windows 10 for warrenty reasons on new laptop). I do not expect you to have any issues either.<br />
<br />
Enjoy!!<br />
<br />
Oh yeah, you can find the patches and README and such here: https://github.com/kata198/con-ck-patches<br />
<br />
{{unsigned|01:07, 4 February 2018|Barbariccow}}<br />
<br />
: While I applause your efforts to help port the ck patchset, announcing uncited and unconfirmed rumors as pretext is not cool. CK himself replied to me in a private email: '''"Yeah bullshit. It'll probably be a week or so though. CK"''' [[User:Graysky|Graysky]] ([[User talk:Graysky|talk]]) 11:23, 4 February 2018 (UTC)<br />
<br />
: I specifically noted in the text that I did not know if they were true or not. I do not see what the big issue is with this; maybe if I said "Con Kolivas is no longer doing patchsets" there would be an issue, but I did not say this. I said that I had read unconfirmed rumors, which was part of the impetus behind me doing the merge myself and making it available. I appreciate you taking the time to confirm that these rumors were NOT true, but I also feel like you oculd have approached it with more tact, such as stating "I have confirmed with Con that he is not discontinuing work on the -ck patchset, and will have an official release out in about a weeks time." I'm not trying to start an issue or start drama, just pointing out that we should be friendly and kind towards one another, practicing Right Speech wherever possible. Thank you again for taking the time out of your day to confirm that the officials will still be rolling in -- this is certainly good news! [[User:Barbariccow|Barbariccow]] ([[User talk:Barbariccow|talk]]) 05:14, 8 February 2018 (UTC)</div>Barbariccowhttps://wiki.archlinux.org/index.php?title=Talk:Linux-ck&diff=509548Talk:Linux-ck2018-02-04T01:07:42Z<p>Barbariccow: /* ck patchset for 4.15 */ new section</p>
<hr />
<div>== BFQ Scheduler auto loading ==<br />
<br />
Inspired by a forumpost i recommend to ad the following text and script to the Wiki at the end of section 2.2.5:<br />
<br />
When using more than one kernel at the same system, you can use the following script in {{ic|/etc/rc.local}}<br />
This will automitically load the BFQ Scheduler only when kernel26-ck is loaded. The BFQ status will be written to a logfile.<br />
<br />
#Enable BFQ for precompiled kernel26-ck from the unofficial repository<br />
TID=$(date +%c)<br />
KERN=$(uname -r | cut -d"-" -f2)<br />
if [ "$KERN" == 'ck' ]; then<br />
modprobe bfq-iosched<br />
echo bfq > /sys/block/sda/queue/scheduler<br />
echo "$TID $(uname -r) with $KERN patch so started bfq for sda" >> /var/log/bfq.log<br />
else<br />
echo "$TID $(uname -r) no bfq loaded" >> /var/log/bfq.log<br />
fi<br />
<br />
:Thanks for the suggestion. I modified the linux-ck package to actually compile in the BFQ (just not enabled by default). Once CK and Paolo get release their respective patches for 3.0.1, I'll update the repo and the wiki page. Thanks for the re-direct btw! [[User:Graysky|Graysky]] 17:12, 8 August 2011 (EDT)<br />
::It seems like BFQ was not compiled into linux-ck-core2 3.0.1-3 ("zcat /proc/config.gz | grep BFQ" shows nothing, and I'm running the -ck kernel).[[User:Jimreynold2nd|Jimreynold2nd]] 14:44, 15 August 2011 (EDT)<br />
:::Right, that's because BFQ for 3.0 does not yet exist. Paolo hasn't released the code for the 3.0 series :) I will update as soon as he does. [[User:Graysky|Graysky]] 04:32, 16 August 2011 (EDT)<br />
<br />
== Enabling BFQ selectively section ==<br />
<br />
This section should be updated: you say to put the "echo bfq" command in rc.local...there is no more support for it, and there is:<br />
1)the systemd-way -> tmpfiles<br />
2)the udev-rule way.<br />
<br />
May be you should report both, or choose what do you think is the best, i trust you!<br />
<br />
Thanks for your time (i preferred to open discussion rather than change it myself, did i the right thing?)<br />
<br />
== New section 2.2.3: rerun grub-mkconfig ==<br />
<br />
After the installation subsection, I would suggest adding a new subsection to remind folks to rerun grub-mkconfig (or the appropriate boot reconfig command for their bootloader) and reboot, so they will be able to see the new kernel and CPU scheduler in action right away. They will have to do this whether or not they want to enable bfq, as I just found out from a kind soul on the Arch Linux Google+ group.<br />
<br />
This step may be obvious to old hands, but as an Arch newb whose system was frequently maxing out, I needed to try BFS and bfq as soon as possible. I'm still getting used to generating a grub config file myself instead of having the installer do it for me...!<br />
<br />
<br />
== Should there be a BFQ section with MuQSS? ==<br />
<br />
I've noticed that it's recommended that one enables BFQ, shouldn't this be removed in place of MuQSS?<br />
<br />
{{unsigned|11:01, 4 August 2017|X89}}<br />
<br />
== ck patchset for 4.15 ==<br />
<br />
<br />
== ck patchset for linux-4.15 (Unofficial) ==<br />
<br />
<br />
Hey guys, so I've read some rumors that Con Kolivas is taking a break / no longer maintaining the ck patchset; that 4.14 was the last version for a while. I'm not sure if these stories were accurate or not, but it's been like a week and no comments on his blog and no updated patchset..<br />
<br />
So anyway, whether they were true or not, I still wanted to be able to use 4.15 with the ck patchset (which is GREAT btw.) So I manually merged the last official patchset from 4.14, made a few minor additions required, some minor changes here and therem etc. There are no additional features or anything here, just a merge forward. I did not do extensive research on all of the recent kernel development work, and I haven't done significant kernel devleopment in years, but I believe everything provided here to be correct. It has been running now stable for me for 36 hours. No lockups, no glitches or lnong hangs, so it seems like everything scheduling-wise is working as intended, which is the core of the patchset and where all the changes I had to make went. Full disclosure: I did get 2 panics one time from ethernet driver (e1000) even though I'm not plugged into anything, but it was just like a tx receive error, didn't cause any noticable issue, and was more likely some artifact of the suspend of the parent OS (I am running linux on virtualbox on top of windows 10 for warrenty reasons on new laptop). I do not expect you to have any issues either.<br />
<br />
Enjoy!!<br />
<br />
Oh yeah, you can find the patches and README and such here: https://github.com/kata198/con-ck-patches</div>Barbariccow