Re: I see no way to report a bug on "How to report a bug" wiki page

2024-03-11 Thread Patrick May
It's not your fault. There is really nothing there under "how to report 
a bug" about, you know, how to actually report a bug. Maybe this is one 
reason why pulseaudio has had so many "BLAST AT 100% FULL VOLUME THROUGH 
YOUR HEADPHONES" bugs.


On 11/03/2024 09:28, Martin Guy wrote:

Hi!

   A pulseaudio bug has surfaced today - the server running out of file 
descriptors when playing short music tracks continuously for over a week 
- but on the "How to report a bug" wiki page


https://www.freedesktop.org/wiki/Software/PulseAudio/BugReports

I see nothing saying how to report a bug, and the gitlab project does 
not seem to have an "Issues" section.



Now, I know I am old and going blind, but am I really not seeing 
something that should be obvious?



Thanks


     M



Re: [pulseaudio-discuss] pactl percentage bug fix

2022-06-04 Thread Patrick May

I tested it with

pactl -- set-sink-volume 0 0db

and it sets the volume to 100%. So the ability to specify absolute 
decibel values is only useful if you like blasting stuff at greater than 
or equal to 100% volume


On 04/06/2022 08:48, Sean Greenslade wrote:


While debugging, I did notice another issue that I was uncertain of how
to solve. The detection of absolute values vs. relative values is based
on the presence of a plus or minus at the start of the value. This is
fine for everything except decibels, since absolute decibel values will
often be negative numbers. The way the code sits now, it's impossible to
pass an absolute negative decibel value. Probably not a huge deal, but
it seemed worth pointing out.

--Sean



[pulseaudio-discuss] pactl percentage bug fix

2022-06-03 Thread Patrick May

Here is the problem:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blob/master/src/utils/pactl.c

In src/utils/pactl.c:

Between line 2530 and line 2535, in function parse_volume:

These two 'if' statements will BOTH execute if the input string contains 
both a '.' and ends with a '%'.


This results in vol_flags having VOL_PERCENT and VOL_LINEAR or'd in and 
set, which is equivalent in effect to '*vol_flags |= VOL_DECIBEL'
(because VOL_PERCENT is 1 and VOL_LINEAR is 2, and VOL_DECIBEL is 3. 
Refer to line 76)
So from then on the function is erroneously acting as if the input 
string was a decibel value, instead of a percentage.


Suggested fix:
Change line 2532 from this
if (pa_endswith(vs, "%")) {
To this:
else if (pa_endswith(vs, "%")) {

I apologise for my rudeness earlier but this was not the first time 
pulseaudio bugs have BLASTED EXTREMELY LOUD NOISE AT 100% THROUGH MY 
HEADPHONES and I was very upset.


I don't have a git account or any of the stuff necessary to actually 
submit a patch so I would appreciate if someone or pulseaudio dev would 
take note of this and make the necessary change


[pulseaudio-discuss] Pulse audio is designed to destroy your hearing and your equipment

2022-06-02 Thread Patrick May

Here's a warning that if you try this command

pactl -- set-sink-volume 0 10.5%

Pulseaudio will set your volume to 150% and destroy your ears as well as 
your headphones.
This is the latest in the very long list of times pulseaudio has blasted 
loud noise at me due to poor design and programming. Fuck you.


[pulseaudio-discuss] Pulseaudio is designed to damage your hearing

2021-12-28 Thread Patrick May
I've lost count of the number of times Pulseaudio has been responsible 
for noise being blasted through my headphones at 100% maximum volume or 
my speakers suddenly blasting audio at 100% maximum loudness


[pulseaudio-discuss] Streaming audio from a game to voice chat, mixed with audio from microphone

2021-09-28 Thread Patrick May

Hello,

I want to stream audio from a game to discord, while also sharing my mic 
at the same time.


This is a very common thing that people do all the time on other 
operating systems. For some reason this seems to be almost impossible to 
do with Pulseaudio.


Why is it so difficult?



[pulseaudio-discuss] How to use module-loopback

2021-09-28 Thread Patrick May

Hello

I want to create a loopback, to record from one specific device, and to 
play back on another specific device.


My problem is, I have no idea how to specify the devices to read from 
and write to when I load the module to create the loopback.


Everything I have tried so far just results in the module not loading at 
all. And very helpfully, it just silently fails and doesn't give any 
kind of console output or error message or anything to let me know wtf 
is wrong.


So far I have tried these commands:

pacmd load-module module-loopback source="Blue Snowball Mono" 
sink="EMU10k1 [Sound Blaster Live! Series] (SB0105 SBLive! 5.1)"


The documentation I found suggests that you can specify by name the 
source and destination 'sink' when you load the module, but I have had 
no luck working this out.


Can anyone help?


[pulseaudio-discuss] Does Pulseaudio support capturing audio stream from a specific app?

2020-10-22 Thread Patrick May

Hello,

Does Pulseaudio give the ability to capture the audio output stream from 
a specific app?
I can't seem to find an option for this. The only capture options I have 
in pavucontrol are Monitors of the sound devices, and audio captures of 
the sound devices.


Is this feature implemented as part of pulseaudio? If so, how do you 
make use of this?


If not, why not? It's a pretty essential feature for stuff like sharing 
audio over services like Discord.


PM
___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss


[pulseaudio-discuss] Pulseaudio likes to set my volume to ABSOLUTE MAXIMUM LOUD

2020-08-04 Thread Patrick May

Hello,

If I switch to a virtual terminal and back (eg, ctrl+alt+fX and then 
ctrl+alt+f7) pulseaudio sets my alsa mixer settings to either 100% 
MAXIMALLY FUCKING LOUD VOLUME or totally silent.


Why is this happening?
___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] Pulseaudio keeps messing up my ALSA mixer settings at random times

2020-04-20 Thread Patrick May
Actually I was wrong -- it's not necessary to log in, just switching to 
a virtual terminal with Ctrl + Alt + Fx is enough to trigger this stupid 
behavior.


How do you tell pulseaudio to stop doing this?

On 20/04/2020 00:23, Patrick May wrote:

I've now worked out exactly when it's happening.
When I log in at a virtual terminal (and I'm already logged in with 
another session with pulseaudio daemon running), that's when pulseaudio 
decides it's the right time to set my ALSA mixer volume to absolute 100%.


It seems to be a bit random though - it either sets it to 100% or 0%. 
But it always does it one way or the other.


It also seems to happen when I log out at a virtual terminal.

Does anyone know why this is happening?

On 19/04/2020 17:52, Patrick May wrote:

Hello,

Pulseaudio seems to like to set my ALSA mixer settings to ABSOLUTE 
COMPLETELY MAXED OUT VOLUME seemingly at random, it seems like it 
happens usually when I reboot the computer but I'm not sure.


I guess it's happening when the pulseaudio daemon gets started.

This is resulting in REALLY LOUD sound getting blasted at me through 
my headphones without warning and I'm sick of it.


Is there a way to tell the pulseaudio daemon or whatever to leave the 
ALSA mixer settings as they are when it starts up?


By the way I already had to add "load-module module-alsa-sink 
control=Master" to my default.pa file because for some reason, it 
would either set the volume to ABSOLUTELY MAXED OUT LOUD or completely 
muted (PCM set to 0) presumably because my soundcard (sound blaster 
live emu10k1) is not well supported by pulseaudio.


thanks.
PM

___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] Pulseaudio keeps messing up my ALSA mixer settings at random times

2020-04-19 Thread Patrick May

I've now worked out exactly when it's happening.
When I log in at a virtual terminal (and I'm already logged in with 
another session with pulseaudio daemon running), that's when pulseaudio 
decides it's the right time to set my ALSA mixer volume to absolute 100%.


It seems to be a bit random though - it either sets it to 100% or 0%. 
But it always does it one way or the other.


It also seems to happen when I log out at a virtual terminal.

Does anyone know why this is happening?

On 19/04/2020 17:52, Patrick May wrote:

Hello,

Pulseaudio seems to like to set my ALSA mixer settings to ABSOLUTE 
COMPLETELY MAXED OUT VOLUME seemingly at random, it seems like it 
happens usually when I reboot the computer but I'm not sure.


I guess it's happening when the pulseaudio daemon gets started.

This is resulting in REALLY LOUD sound getting blasted at me through my 
headphones without warning and I'm sick of it.


Is there a way to tell the pulseaudio daemon or whatever to leave the 
ALSA mixer settings as they are when it starts up?


By the way I already had to add "load-module module-alsa-sink 
control=Master" to my default.pa file because for some reason, it would 
either set the volume to ABSOLUTELY MAXED OUT LOUD or completely muted 
(PCM set to 0) presumably because my soundcard (sound blaster live 
emu10k1) is not well supported by pulseaudio.


thanks.
PM

___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss


[pulseaudio-discuss] Pulseaudio keeps messing up my ALSA mixer settings at random times

2020-04-19 Thread Patrick May

Hello,

Pulseaudio seems to like to set my ALSA mixer settings to ABSOLUTE 
COMPLETELY MAXED OUT VOLUME seemingly at random, it seems like it 
happens usually when I reboot the computer but I'm not sure.


I guess it's happening when the pulseaudio daemon gets started.

This is resulting in REALLY LOUD sound getting blasted at me through my 
headphones without warning and I'm sick of it.


Is there a way to tell the pulseaudio daemon or whatever to leave the 
ALSA mixer settings as they are when it starts up?


By the way I already had to add "load-module module-alsa-sink 
control=Master" to my default.pa file because for some reason, it would 
either set the volume to ABSOLUTELY MAXED OUT LOUD or completely muted 
(PCM set to 0) presumably because my soundcard (sound blaster live 
emu10k1) is not well supported by pulseaudio.


thanks.
PM
___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss