On Friday, 25 March 2022 16:47:22 GMT Jack wrote:

On 2022.03.25 12:16, Peter Humphrey wrote:

Have you also tried using a different browser?

Yes. Konqueror behaves the same way. I had the site open in FF just now, but not playing, and I hadn't restarted PA. Then I opened the same site in Konqueror. No sound yet. Then I restarted PA and Konqueror's sound came to life. I shut Konqueror down and started FF streaming. I heard it straight
away.

Next, abandoning Konqueror, I removed ~/.mozilla and started a new session. Without doing anything to FF I tried streaming again. Silence.

So it isn't any of the plugins I have in FF.

I haven't mentioned it before, but whenever I restart PA I get a plain window announcing something like "Audio Adapter Y247A. Analog audio". It only exists for a second or so and I haven't been able to capture it in a screen shot. It isn't a standard KDE window, or at least it has no colours or window decorations.

--
Regards,
Peter.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/26/22 07:12, Peter Humphrey wrote:

I haven't mentioned it before, but whenever I restart PA I get a plain window announcing something like "Audio Adapter Y247A. Analog audio". It only exists for a second or so and I haven't been able to capture it in a screen shot. It isn't a standard KDE window, or at least it has no colours or window decorations.

I have also see that and have assumed it's from pulseaudio, showing its
default sound device.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Mar 26, 2022 at 6:29 AM Jack <ostroffjh@users.sourceforge.net> wrote:

On 3/26/22 07:12, Peter Humphrey wrote:

I haven't mentioned it before, but whenever I restart PA I get a plain window
announcing something like "Audio Adapter Y247A. Analog audio". It only exists
for a second or so and I haven't been able to capture it in a screen shot. It
isn't a standard KDE window, or at least it has no colours or window decorations.

I have also see that and have assumed it's from pulseaudio, showing its default sound device.

Generically, isn't this what's shown in the PA Volume Control,
Configuration tab, in the profile pulldown for the USB audio device?

I have 3 devices. Most options in the profile pulldowns say
"(unavailable)" . I've never explored why.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Just a shot in the dark, but is alsasound service starting correctly?


Lee 😎

On Mar 26, 2022 at 6:29 AM, Jack <ostroffjh@users.sourceforge.net> wrote:

On 3/26/22 07:12, Peter Humphrey wrote:

I haven't mentioned it before, but whenever I restart PA I get a plain window announcing something like "Audio Adapter Y247A. Analog audio". It only exists for a second or so and I haven't been able to capture it in a screen shot. It isn't a standard KDE window, or at least it has no colours or window decorations.

I have also see that and have assumed it's from pulseaudio, showing its
default sound device.

<div id="edo-message"><div><div>Just a shot in the dark, but is alsasound service starting correctly?</div><div><br></div><div><br></div><div id="edo-signature"><pre>Lee 😎</pre></div></div></div><div id="edo-original"><div><blockquote type="cite"
style="margin:1ex 0 0 0!important;border-left:1px #ccc solid!important;padding-left:0.4ex!important"><div id="edo-meta">On Mar 26, 2022 at 6:29 AM, Jack &lt;<a href="mailto:ostroffjh@users.sourceforge.net">ostroffjh@users.sourceforge.net</a>&gt; wrote: <

<br></div><pre>On 3/26/22 07:12, Peter Humphrey wrote:

<br>&gt; I haven&#39;t mentioned it before, but whenever I restart PA I get a plain window
<br>&gt; announcing something like &quot;Audio Adapter Y247A. Analog audio&quot;. It only exists
<br>&gt; for a second or so and I haven&#39;t been able to capture it in a screen shot. It
<br>&gt; isn&#39;t a standard KDE window, or at least it has no colours or window
<br>&gt; decorations.

<br>I have also see that and have assumed it&#39;s from pulseaudio, showing its
<br>default sound device.


<br></pre></blockquote></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Saturday, 26 March 2022 15:14:11 GMT ny6p01 wrote:

Just a shot in the dark, but is alsasound service starting correctly?

It doesn't run at all, not even while I'm listening after restarting PA. I
have alsa-lib, alsa-topology-conf, alsa-ucm-conf and alsa-plugins installed, but 'ps -ax | grep alsa' finds nothing. Also, I have no alsasound service.

I assume that PA doesn't need a running alsa process to function.

--
Regards,
Peter.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Mar 26, 2022 at 10:02 AM Peter Humphrey <peter@prh.myzen.co.uk> wrote:

On Saturday, 26 March 2022 15:14:11 GMT ny6p01 wrote:

Just a shot in the dark, but is alsasound service starting correctly?

It doesn't run at all, not even while I'm listening after restarting PA. I have alsa-lib, alsa-topology-conf, alsa-ucm-conf and alsa-plugins installed, but 'ps -ax | grep alsa' finds nothing. Also, I have no alsasound service.

I assume that PA doesn't need a running alsa process to function.

--
Regards,
Peter.

PA might not (or doesn't - my system has no alsa processes) need alsa
processes but it almost certainly using Alsa drivers.

lsmod | grep snd
lsmod | sound

However those depend on what you build as modules vs hard code into
your kernel.

ls /proc/asound would give you a view into what function, if any, alsa is performing.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Saturday, 26 March 2022 17:14:52 GMT Mark Knecht wrote:

On Sat, Mar 26, 2022 at 10:02 AM Peter Humphrey <peter@prh.myzen.co.uk>

wrote:

On Saturday, 26 March 2022 15:14:11 GMT ny6p01 wrote:

Just a shot in the dark, but is alsasound service starting correctly?

It doesn't run at all, not even while I'm listening after restarting PA. I have alsa-lib, alsa-topology-conf, alsa-ucm-conf and alsa-plugins installed, but 'ps -ax | grep alsa' finds nothing. Also, I have no alsasound service.

I assume that PA doesn't need a running alsa process to function.

--
Regards,
Peter.

PA might not (or doesn't - my system has no alsa processes) need alsa processes but it almost certainly using Alsa drivers.

lsmod | grep snd
lsmod | sound

However those depend on what you build as modules vs hard code into
your kernel.

ls /proc/asound would give you a view into what function, if any, alsa is performing.

I think since this sound problem has been narrowed down to a difference
between users on the same machine, it must be a userspace process issue.
Kernel driver problems would be universal and dmesg would complain about it.

If the same ~./mozilla profile is reproducing the problem on the other user's account, which hitherto played sound without any desktop gymnastics, then the problem is firefox related. Starting with an empty firefox profile on the
same user will also help identify if the firefox configuration, addons and its sandboxing, or pa is to blame. Starting both firefox and pa from a terminal may also provide some related output.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmI/VH8ACgkQseqq9sKV ZxmdOxAA2xZC2mHiA7BGy656mXiMD5tvMvE2Jcc9MtkpuVnCSmTH1CX0TI3pqToa PQ8/P7N9wkpPzgdic3MebGz0/WovdR/zaCqQf9SZpiu4uwU/SLS4ANva1L2kLliI 0NhVO+ExARLcezoDrpM+moRVzqmRehM/wmcIBCW2TC0xkeY2SBoG5dVs07gvDS06 HkitPQHfCVfJIUkEYBlD7kdWy9Z9tsGN52pDeGM8BQ245bEvP1DfAgbv3VOxSF8P ZTUtwu7mW3tbpf5dTDongvmRrEj3mC2eJqAD7jf9px5tmnCyq9bOAeCdFjFUeumk BAV0hppA92CKVC4Mo0GTwOAFmp5kSSpO1SmV4uKeplKDXiW3A+VctJ16G3Vn/d7j EJ83xZAGslIpixnkyh9F0Zvtm1ziYUlNxTPWe4bBT22IxhtWXpLkHrMKlzNaFKWc ikhRkY6hx6qdRh5Jh+dX6K+topspmXWLiMYgXHk/Ww4DTYfOsIVZiAX2oxpi3ynb 3/e8aw8cn+swpQKIUnrZqurFw2acuxm7Dpab3R4BWZNWysTeDb97Y63KG+zy4TsC cHxHB/seRcGm3w0Y9BwfHKEZ33Mt7yfOU8wfRUjF5Guuo9qcEGD22NYz26T6QD71 HhKYk+VzUAeTbF1vgTLBzrJbZGRU0iW/GSHJp/yl5nQA+pL2830=
=fERE
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022.03.26 10:22, Mark Knecht wrote:

On Sat, Mar 26, 2022 at 6:29 AM Jack
<ostroffjh@users.sourceforge.net> wrote:

On 3/26/22 07:12, Peter Humphrey wrote:

I haven't mentioned it before, but whenever I restart PA I get a

plain window

announcing something like "Audio Adapter Y247A. Analog audio". It

only exists

for a second or so and I haven't been able to capture it in a

screen shot. It

isn't a standard KDE window, or at least it has no colours or

window

decorations.

I have also see that and have assumed it's from pulseaudio, showing

its

default sound device.

Generically, isn't this what's shown in the PA Volume Control,
Configuration tab, in the profile pulldown for the USB audio device?

I have 3 devices. Most options in the profile pulldowns say
"(unavailable)" . I've never explored why.

I only seen "unavailable" for one device - a set of Bluetooth noise
canceling headphones (Sony WH-CH700N) which shows High Fidelity
Playback (A2DP Sink), Headset Head Unit (HSP) (unavailable), Handsfree
Head Unit (HFP), and Off. I believe the unavailability is due to some combination of the driver for the USB BT dongle (with it's own
problems, being a cheap Chinese knockoff) and the BT sound drivers. I
assume the "unavailable" is for modes that the driver thinks the device
(or maybe just the type or class of device) should handle, but doesn't.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)