I have Logitech USB stereo headphones with boom mic plugged into USB. If I use its in-line control to change the volume, a volume indicator appears on-screen. The progress bar is blue when the volume is at the low setting, then gradually changes to white when the volume is increased.
Except, the volume coming out of the headphones, is not changing.
If I need to adjust the volume, I must launch the PulseAudio Volume Control and change it there.
Is what I'm describing above, the correct behavior? It would seem that when the volume is increased with the in-line control, the actual volume coming out of them /should/ increase?
Thanks in advance.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Thu, 22 Jul 2021 15:35:04 -0400 Edward epp@caramail.com wrote:
I have Logitech USB stereo headphones with boom mic plugged into USB. If I use its in-line control to change the volume, a volume indicator appears on-screen. The progress bar is blue when the volume is at the low setting, then gradually changes to white when the volume is increased.
Except, the volume coming out of the headphones, is not changing.
If I need to adjust the volume, I must launch the PulseAudio Volume Control and change it there.
Is what I'm describing above, the correct behavior? It would seem that when the volume is increased with the in-line control, the actual volume coming out of them /should/ increase?
If it were a normal pair of 3.5mm audio jack headphones, I would say "yes" immediately, but with something more complex, I'm always skeptical.
Have you tried plugging them into something else—phone, tablet, other computer, anything with a suitable jack—and seeing whether the volume control works as expected there? That's the first step: rule out the simple possibility of broken hardware.
(My next step would be to kill PulseAudio with fire regardless of whether there was a hardware problem or not, but I have no use for its extra features and it's possible that you do.)
E. Liddell
On 7/22/21 4:08 PM, E. Liddell wrote:
On Thu, 22 Jul 2021 15:35:04 -0400 Edward epp@caramail.com wrote:
I have Logitech USB stereo headphones with boom mic plugged into USB. If I use its in-line control to change the volume, a volume indicator appears on-screen. The progress bar is blue when the volume is at the low setting, then gradually changes to white when the volume is increased.
Except, the volume coming out of the headphones, is not changing.
If I need to adjust the volume, I must launch the PulseAudio Volume Control and change it there.
Is what I'm describing above, the correct behavior? It would seem that when the volume is increased with the in-line control, the actual volume coming out of them /should/ increase?
If it were a normal pair of 3.5mm audio jack headphones, I would say "yes" immediately, but with something more complex, I'm always skeptical.
Have you tried plugging them into something else—phone, tablet, other computer, anything with a suitable jack—and seeing whether the volume control works as expected there? That's the first step: rule out the simple possibility of broken hardware.
(My next step would be to kill PulseAudio with fire regardless of whether there was a hardware problem or not, but I have no use for its extra features and it's possible that you do.)
E. Liddell
My other desktop also has Debian 10/Trinity installed, so if I plugged these into that, I believe would have the same result. Only difference between the desktops, is the insides. Both systems are using plug-in audio cards (both Creative SoundBlasters, but different models).
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Anno domini 2021 Thu, 22 Jul 16:17:17 -0400 Edward scripsit:
On 7/22/21 4:08 PM, E. Liddell wrote:
On Thu, 22 Jul 2021 15:35:04 -0400 Edward epp@caramail.com wrote:
I have Logitech USB stereo headphones with boom mic plugged into USB. If I use its in-line control to change the volume, a volume indicator appears on-screen. The progress bar is blue when the volume is at the low setting, then gradually changes to white when the volume is increased.
Except, the volume coming out of the headphones, is not changing.
If I need to adjust the volume, I must launch the PulseAudio Volume Control and change it there.
Is what I'm describing above, the correct behavior? It would seem that when the volume is increased with the in-line control, the actual volume coming out of them /should/ increase?
If it were a normal pair of 3.5mm audio jack headphones, I would say "yes" immediately, but with something more complex, I'm always skeptical.
Have you tried plugging them into something else—phone, tablet, other computer, anything with a suitable jack—and seeing whether the volume control works as expected there? That's the first step: rule out the simple possibility of broken hardware.
(My next step would be to kill PulseAudio with fire regardless of whether there was a hardware problem or not, but I have no use for its extra features and it's possible that you do.)
E. Liddell
My other desktop also has Debian 10/Trinity installed, so if I plugged these into that, I believe would have the same result. Only difference between the desktops, is the insides. Both systems are using plug-in audio cards (both Creative SoundBlasters, but different models).
Please do the test. And check the symbols on the soundblaster cards, there might be surprises.
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64) ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 7/22/21 4:35 PM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Thu, 22 Jul 16:17:17 -0400 Edward scripsit:
My other desktop also has Debian 10/Trinity installed, so if I plugged these into that, I believe would have the same result. Only difference between the desktops, is the insides. Both systems are using plug-in audio cards (both Creative SoundBlasters, but different models).
Please do the test. And check the symbols on the soundblaster cards, there might be surprises.
Nik
Symbols?
--
Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Anno domini 2021 Thu, 22 Jul 16:37:55 -0400 Edward scripsit:
On 7/22/21 4:35 PM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Thu, 22 Jul 16:17:17 -0400 Edward scripsit:
My other desktop also has Debian 10/Trinity installed, so if I plugged these into that, I believe would have the same result. Only difference between the desktops, is the insides. Both systems are using plug-in audio cards (both Creative SoundBlasters, but different models).
Please do the test. And check the symbols on the soundblaster cards, there might be surprises.
Nik
Symbols?
The synbols imprinted on the soundblaster that telly you which plus is for what. My SB has 8 of them ...
Nik
--
Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64) ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 7/22/21 4:44 PM, Dr. Nikolaus Klepp wrote:
The synbols imprinted on the soundblaster that telly you which plus is for what. My SB has 8 of them ...
Nik
The card in this system is a Creative Sound Blaster Audigy FX (PCIe 1x). Outputs on the back are: Line In, Microphone In, Front Out/Headphone Out, Rear Out and Center/Subwoofer.
The other system has a Creative Sound Blaster Live! 5.1 (legacy PCI). Per the user guide, it has: Digital Out, Front Line Out, Rear Line Out, Microphone and Headphone.
The jacks on both cards are all 3.5mm, the headphones are USB.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On 7/22/21 5:24 PM, Edward wrote:
On 7/22/21 4:44 PM, Dr. Nikolaus Klepp wrote:
The synbols imprinted on the soundblaster that telly you which plus is for what. My SB has 8 of them ...
Nik
The card in this system is a Creative Sound Blaster Audigy FX (PCIe 1x). Outputs on the back are: Line In, Microphone In, Front Out/Headphone Out, Rear Out and Center/Subwoofer.
The other system has a Creative Sound Blaster Live! 5.1 (legacy PCI). Per the user guide, it has: Digital Out, Front Line Out, Rear Line Out, Microphone and Headphone.
The jacks on both cards are all 3.5mm, the headphones are USB.
Test results: same on both, volume does not change on either system when the inline volume control is used.
One difference on the other system (with the Creative SB Live! card) is that when the volume progress window appears, the white bar as described previously, is dark blue on this system and only advances once, regardless of how many times the + on the switch is pressed.
On both systems when using these headphones, the Kmix icon in the TDE panel shows the volume at 0%.
-- Linux. A Continual Learning Experience.
Trinity Desktop Environment: 14.0.10 - Debian: 10.10 (amd64)
On 2021-07-22 16:37:03 Edward wrote:
On 7/22/21 5:24 PM, Edward wrote:
On 7/22/21 4:44 PM, Dr. Nikolaus Klepp wrote:
The synbols imprinted on the soundblaster that telly you which plus is for what. My SB has 8 of them ...
Nik
The card in this system is a Creative Sound Blaster Audigy FX (PCIe 1x). Outputs on the back are: Line In, Microphone In, Front Out/Headphone Out, Rear Out and Center/Subwoofer.
The other system has a Creative Sound Blaster Live! 5.1 (legacy PCI). Per the user guide, it has: Digital Out, Front Line Out, Rear Line Out, Microphone and Headphone.
The jacks on both cards are all 3.5mm, the headphones are USB.
Test results: same on both, volume does not change on either system when the inline volume control is used.
One difference on the other system (with the Creative SB Live! card) is that when the volume progress window appears, the white bar as described previously, is dark blue on this system and only advances once, regardless of how many times the + on the switch is pressed.
On both systems when using these headphones, the Kmix icon in the TDE panel shows the volume at 0%.
I would guess, then, that Logitech has helpfully installed an incompatible 'improvement' to your headphones' built-in firmware. I know that their mice, whose basic (3 buttons, scroll wheel) features work fine in Linux, have additional features that Linux isn't able to take advantage of because Logitech doesn't release details of those features' APIs.
Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0
On 2021-07-22 16:37:03 Edward wrote:
On 7/22/21 5:24 PM, Edward wrote:
On 7/22/21 4:44 PM, Dr. Nikolaus Klepp wrote:
The synbols imprinted on the soundblaster that telly you which plus is for what. My SB has 8 of them ...
Nik
The card in this system is a Creative Sound Blaster Audigy FX (PCIe 1x). Outputs on the back are: Line In, Microphone In, Front Out/Headphone Out, Rear Out and Center/Subwoofer.
The other system has a Creative Sound Blaster Live! 5.1 (legacy PCI). Per the user guide, it has: Digital Out, Front Line Out, Rear Line Out, Microphone and Headphone.
The jacks on both cards are all 3.5mm, the headphones are USB.
Test results: same on both, volume does not change on either system when the inline volume control is used.
One difference on the other system (with the Creative SB Live! card) is that when the volume progress window appears, the white bar as described previously, is dark blue on this system and only advances once, regardless of how many times the + on the switch is pressed.
On both systems when using these headphones, the Kmix icon in the TDE panel shows the volume at 0%.
For what it's worth, there is a product called Solaar which provides an interface to Logitech devices, but it's no help for your purposes because it just supports keyboards and pointing devices with wireless USB interfaces. Maybe you can get them to think about supporting headsets as well? https://pwr-solaar.github.io/Solaar/
Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0
Anno domini 2021 Thu, 22 Jul 21:35:53 -0500 J Leslie Turriff scripsit:
On 2021-07-22 16:37:03 Edward wrote:
On 7/22/21 5:24 PM, Edward wrote:
On 7/22/21 4:44 PM, Dr. Nikolaus Klepp wrote:
The synbols imprinted on the soundblaster that telly you which plus is for what. My SB has 8 of them ...
Nik
The card in this system is a Creative Sound Blaster Audigy FX (PCIe 1x). Outputs on the back are: Line In, Microphone In, Front Out/Headphone Out, Rear Out and Center/Subwoofer.
The other system has a Creative Sound Blaster Live! 5.1 (legacy PCI). Per the user guide, it has: Digital Out, Front Line Out, Rear Line Out, Microphone and Headphone.
The jacks on both cards are all 3.5mm, the headphones are USB.
Test results: same on both, volume does not change on either system when the inline volume control is used.
One difference on the other system (with the Creative SB Live! card) is that when the volume progress window appears, the white bar as described previously, is dark blue on this system and only advances once, regardless of how many times the + on the switch is pressed.
On both systems when using these headphones, the Kmix icon in the TDE panel shows the volume at 0%.
For what it's worth, there is a product called Solaar which provides an interface to Logitech devices, but it's no help for your purposes because it just supports keyboards and pointing devices with wireless USB interfaces. Maybe you can get them to think about supporting headsets as well? https://pwr-solaar.github.io/Solaar/
The said Audigy FX (PCIe 1x) and Solaar are basicly identical. The FX has a PCIe-to-USB converter on board. I had that card some months ago for testing - had to return it, 'cause it did not play well with 600 Ohm headphones. But at least the volume control worked.
Nik
Leslie
Operating System: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0 ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On Thu, Jul 22, 2021 at 04:08:27PM -0400, E. Liddell wrote:
(My next step would be to kill PulseAudio with fire regardless of whether there was a hardware problem or not, but I have no use for its extra features and it's possible that you do.)
It seems odd to me that your suggestion is to kill the package which *does* change the volume on Edward's headphones, which would leave him literally unable to change the volume at all. In my ignorance, that seems pretty counter-intuitive and unhelpful. Can you educate me please?
On Fri, 23 Jul 2021 10:22:36 +1000 "Steven D'Aprano" steve@pearwood.info wrote:
On Thu, Jul 22, 2021 at 04:08:27PM -0400, E. Liddell wrote:
(My next step would be to kill PulseAudio with fire regardless of whether there was a hardware problem or not, but I have no use for its extra features and it's possible that you do.)
It seems odd to me that your suggestion is to kill the package which *does* change the volume on Edward's headphones, which would leave him literally unable to change the volume at all. In my ignorance, that seems pretty counter-intuitive and unhelpful. Can you educate me please?
PulseAudio is an additional layer on top of the *actual* Linux audio system (ALSA). While it's no longer as buggy as it was when first introduced, more software layers = more difficult to figure out what's actually wrong.
It is possible that the cause of Edward's problem is Pulse grabbing onto something that it shouldn't. It's also possible I'm barking up the wrong tree entirely; what I saw of Pulse in its early days makes me inclined to distrust it, perhaps unfairly.
(And now someone else who has a Logitech headset is going to point to the exact problem, which will have nothing to do with any of this, and I'm going to look like an idiot. That's okay—it won't be the first time.)
E. Liddell
Anno domini 2021 Thu, 22 Jul 21:59:13 -0400 E. Liddell scripsit:
On Fri, 23 Jul 2021 10:22:36 +1000 "Steven D'Aprano" steve@pearwood.info wrote:
On Thu, Jul 22, 2021 at 04:08:27PM -0400, E. Liddell wrote:
(My next step would be to kill PulseAudio with fire regardless of whether there was a hardware problem or not, but I have no use for its extra features and it's possible that you do.)
It seems odd to me that your suggestion is to kill the package which *does* change the volume on Edward's headphones, which would leave him literally unable to change the volume at all. In my ignorance, that seems pretty counter-intuitive and unhelpful. Can you educate me please?
PulseAudio is an additional layer on top of the *actual* Linux audio system (ALSA). While it's no longer as buggy as it was when first introduced, more software layers = more difficult to figure out what's actually wrong.
It is possible that the cause of Edward's problem is Pulse grabbing onto something that it shouldn't. It's also possible I'm barking up the wrong tree entirely; what I saw of Pulse in its early days makes me inclined to distrust it, perhaps unfairly.
Which happend on my devuan (and former debian) systems any time. Kmix just does not work work with pulseaudio (on my systems). What's worse: alsamixer may work or not, depending on air pressure. So my suggestion is: If kmix should change volume, remove anything pulsaudio, then reboot, doublecheck if PA is really gone. Check if the firmware for soundblaster is loaded:
# dmesg |grep firm [ 5.889395] snd_hda_intel 0000:04:00.0: firmware: direct-loading firmware ctefx-desktop.bin
.. and the try alsamixer to change volume.
(And now someone else who has a Logitech headset is going to point to the exact problem, which will have nothing to do with any of this, and I'm going to look like an idiot. That's okay—it won't be the first time.)
If the headset is battery powerd it might have auto-gain, but I have never seen that in real live (most likely 'cause I run from battery powerd audio stuff). If the headset has a mic, it might also have auto-gain which is powered by the mic ghost voltage. Anyway, you should be able to figure that out .. my bet is, there's no auto-gain but PA doing "interesting" things.
Nik
E. Liddell ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
In TDE Control Center/Sound & Multimedia/Sound System/Hardware, it shows it's using Advanced Linux Sound Architecture (ALSA). The other options are:
* Autodetect * No Audio Input/Output * Open Sound System * Threaded Open Sound System
Should that setting be on something else?
I recall installing the PulseAudio Volume Control previously, when I was trying to diagnose a problem using Bluetooth headsets. Should this volume control now be uninstalled, since Kmix already has many controls itself? I would prefer to keep my computers lean and not have anything installed that I do not, or no longer, need.
Thanks.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
/Sent earlier today, apparently didn't make it to the list./
In TDE Control Center/Sound & Multimedia/Sound System/Hardware, it shows it's using Advanced Linux Sound Architecture (ALSA). The other options are:
* Autodetect * No Audio Input/Output * Open Sound System * Threaded Open Sound System
Should that setting be on something else?
I recall installing the PulseAudio Volume Control previously, when I was trying to diagnose a problem using Bluetooth headsets. Should this volume control now be uninstalled, since Kmix already has many controls itself? I would prefer to keep my computers lean and not have anything installed that I do not, or no longer, need.
Thanks.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Friday 23 July 2021 05:31:52 pm Edward wrote:
/Sent earlier today, apparently didn't make it to the list./
In TDE Control Center/Sound & Multimedia/Sound System/Hardware, it shows it's using Advanced Linux Sound Architecture (ALSA). The other options are:
- Autodetect
- No Audio Input/Output
- Open Sound System
- Threaded Open Sound System
Should that setting be on something else?
Mine's on Autodetect
I recall installing the PulseAudio Volume Control previously, when I was trying to diagnose a problem using Bluetooth headsets. Should this volume control now be uninstalled, since Kmix already has many controls itself? I would prefer to keep my computers lean and not have anything installed that I do not, or no longer, need.
If you only have the TDE desktop then most likely you can remove PulseAudio. You'll most likely also have to reconfigure the {default?} sound afterwards (in TCC somewhere).
Do a /home/user backup first ;)
Best, Michael
On 7/23/21 7:20 PM, Michael via tde-users wrote:
On Friday 23 July 2021 05:31:52 pm Edward wrote:
/Sent earlier today, apparently didn't make it to the list./
In TDE Control Center/Sound & Multimedia/Sound System/Hardware, it shows it's using Advanced Linux Sound Architecture (ALSA). The other options are:
- Autodetect
- No Audio Input/Output
- Open Sound System
- Threaded Open Sound System
Should that setting be on something else?
Mine's on Autodetect
I recall installing the PulseAudio Volume Control previously, when I was trying to diagnose a problem using Bluetooth headsets. Should this volume control now be uninstalled, since Kmix already has many controls itself? I would prefer to keep my computers lean and not have anything installed that I do not, or no longer, need.
If you only have the TDE desktop then most likely you can remove PulseAudio. You'll most likely also have to reconfigure the {default?} sound afterwards (in TCC somewhere).
Do a /home/user backup first ;)
Best, Michael
I used the Debian LXQt image to install Debian, then installed the TDE packages afterwards. The installed packages are pavucontrol-qt and pavucontrol-qt-l10n. There is another package pavucontrol, described as 'PulseAudio Volume Control". I could also install that.
If I attempt to remove pulaeaudio-qt, it wants to install the LXQt desktop with other packages.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Anno domini 2021 Fri, 23 Jul 19:29:02 -0400 Edward scripsit:
On 7/23/21 7:20 PM, Michael via tde-users wrote:
On Friday 23 July 2021 05:31:52 pm Edward wrote:
/Sent earlier today, apparently didn't make it to the list./
In TDE Control Center/Sound & Multimedia/Sound System/Hardware, it shows it's using Advanced Linux Sound Architecture (ALSA). The other options are:
- Autodetect
- No Audio Input/Output
- Open Sound System
- Threaded Open Sound System
Should that setting be on something else?
Mine's on Autodetect
I recall installing the PulseAudio Volume Control previously, when I was trying to diagnose a problem using Bluetooth headsets. Should this volume control now be uninstalled, since Kmix already has many controls itself? I would prefer to keep my computers lean and not have anything installed that I do not, or no longer, need.
If you only have the TDE desktop then most likely you can remove PulseAudio. You'll most likely also have to reconfigure the {default?} sound afterwards (in TCC somewhere).
Do a /home/user backup first ;)
Best, Michael
I used the Debian LXQt image to install Debian, then installed the TDE packages afterwards. The installed packages are pavucontrol-qt and pavucontrol-qt-l10n. There is another package pavucontrol, described as 'PulseAudio Volume Control". I could also install that.
If I attempt to remove pulaeaudio-qt, it wants to install the LXQt desktop with other packages.
Sure it does - as we all know, audio is essential to DEs, so no sane user ever wants to remove that. And if you want to, think twice, 'cause the packages know better ;)
But you could install "equivs" and build a dummy pulaeaudio-qt package.
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64) ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 7/24/21 2:29 AM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Fri, 23 Jul 19:29:02 -0400 Edward scripsit:
I used the Debian LXQt image to install Debian, then installed the TDE packages afterwards. The installed packages are pavucontrol-qt and pavucontrol-qt-l10n. There is another package pavucontrol, described as 'PulseAudio Volume Control". I could also install that.
If I attempt to remove pulaeaudio-qt, it wants to install the LXQt desktop with other packages.
Sure it does - as we all know, audio is essential to DEs, so no sane user ever wants to remove that. And if you want to, think twice, 'cause the packages know better ;)
But you could install "equivs" and build a dummy pulaeaudio-qt package.
Nik
Hi Nik,
I briefly installed the regular pavucontrol package, which required some additional dependencies and the screens were somewhat different, but since the Qt variant works as is, I removed the regular package and dependencies and kept the Qt variant installed.
Although I don't know if this is a TDE-specific issue, with either or both pavucontrol packages installed, when they appear on TDE's Multimedia menu, neither entry displays an icon to the left.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Saturday 24 July 2021 06:41:16 am Edward wrote:
On 7/24/21 2:29 AM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Fri, 23 Jul 19:29:02 -0400
Edward scripsit:
I used the Debian LXQt image to install Debian, then installed the TDE packages afterwards. The installed packages are pavucontrol-qt and pavucontrol-qt-l10n. There is another package pavucontrol, described as 'PulseAudio Volume Control". I could also install that.
If I attempt to remove pulaeaudio-qt, it wants to install the LXQt desktop with other packages.
Hi Edward,
If it really bugs you, install Debian base* and then install TDE. I've done this several times in the past, it creates a very lean machine.
* Or whatever Deb calls it that leaves you with network available but no desktop.
Best, Michael
Michael via tde-users wrote:
On Saturday 24 July 2021 06:41:16 am Edward wrote:
On 7/24/21 2:29 AM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Fri, 23 Jul 19:29:02 -0400
Edward scripsit:
I used the Debian LXQt image to install Debian, then installed the TDE packages afterwards. The installed packages are pavucontrol-qt and pavucontrol-qt-l10n. There is another package pavucontrol, described as 'PulseAudio Volume Control". I could also install that.
If I attempt to remove pulaeaudio-qt, it wants to install the LXQt desktop with other packages.
Hi Edward,
If it really bugs you, install Debian base* and then install TDE. I've done this several times in the past, it creates a very lean machine.
- Or whatever Deb calls it that leaves you with network available but no
desktop.
Best, Michael
It doesn't bug me at all, the Qt variant is accessible and works, so I'll leave that as it is. :)
/I made this desktop leaner already, by uninstalling over 700Mb of fonts that aren't needed./
-- Linux. A Continual Learning Experience.
Trinity Desktop Environment: R14.0.10 - Debian 10.10 (amd64)
Question to Edward (sorry for off-topic): Why are your timestamps all messed up? Your replies are dated *before* the questions are asked. (See attached screenshot for proof.) It seems that you or your system are living about 35+ hours ahead of the rest of us.
I seem to recall that somebody else had this going on. It can probably be rediscovered in the threads.
Usually visitors from the future travel from some far distant period -- at least years or decades or centuries. If you have journeyed here to give us some dire warning, you really ought to coordinate better with your technical people. A few hours of advance warning doesn't give us much time to act.
Bill
On 7/26/21 4:55 PM, William Morder via tde-users wrote:
Question to Edward (sorry for off-topic): Why are your timestamps all messed up? Your replies are dated *before* the questions are asked. (See attached screenshot for proof.) It seems that you or your system are living about 35+ hours ahead of the rest of us.
I seem to recall that somebody else had this going on. It can probably be rediscovered in the threads.
Usually visitors from the future travel from some far distant period -- at least years or decades or centuries. If you have journeyed here to give us some dire warning, you really ought to coordinate better with your technical people. A few hours of advance warning doesn't give us much time to act.
Bill
Hi Bill,
😂
I don't believe it's my system. I'm in the Eastern Time Zone in the U.S. which is currently on Eastern Daylight (or Summer) Time (EDT) until 2:00 AM local time Sunday November 7, the UTC/GMT offset is currently -0400. I checked the Time Zone setting in the TDE Control Center and it is correctly set to America/New York (EDT).
FWIW, the mail service is GMX, their UTC/GMT offset is currently +0200 per the headers.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Monday 26 July 2021 15:08:02 Edward wrote:
On 7/26/21 4:55 PM, William Morder via tde-users wrote:
Question to Edward (sorry for off-topic): Why are your timestamps all messed up? Your replies are dated *before* the questions are asked. (See attached screenshot for proof.) It seems that you or your system are living about 35+ hours ahead of the rest of us.
I seem to recall that somebody else had this going on. It can probably be rediscovered in the threads.
Usually visitors from the future travel from some far distant period -- at least years or decades or centuries. If you have journeyed here to give us some dire warning, you really ought to coordinate better with your technical people. A few hours of advance warning doesn't give us much time to act.
Bill
Hi Bill,
😂
I don't believe it's my system. I'm in the Eastern Time Zone in the U.S. which is currently on Eastern Daylight (or Summer) Time (EDT) until 2:00 AM local time Sunday November 7, the UTC/GMT offset is currently -0400. I checked the Time Zone setting in the TDE Control Center and it is correctly set to America/New York (EDT).
FWIW, the mail service is GMX, their UTC/GMT offset is currently +0200 per the headers.
It's not a *big* deal, but it makes me search to find the missing unread emails, or to sort them according to when they were received rather than the date and time on the email itself.
Bill
On 7/26/21 6:14 PM, William Morder via tde-users wrote:
It's not a *big* deal, but it makes me search to find the missing unread emails, or to sort them according to when they were received rather than the date and time on the email itself.
Bill
Could the problem be with Trinity's mail server?
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Mon July 26 2021 15:14:30 William Morder via tde-users wrote:
I don't believe it's my system. I'm in the Eastern Time Zone in the U.S. which is currently on Eastern Daylight (or Summer) Time (EDT) until 2:00 AM local time Sunday November 7, the UTC/GMT offset is currently -0400. I checked the Time Zone setting in the TDE Control Center and it is correctly set to America/New York (EDT).
FWIW, the mail service is GMX, their UTC/GMT offset is currently +0200 per the headers.
It's not a *big* deal, but it makes me search to find the missing unread emails, or to sort them according to when they were received rather than the date and time on the email itself.
FWIW I'm seeing Edward's emails in R14.0.10 kmail-trinity with what appear to be the correct timestamps given their position in various threads.
His TBird email Date header is in TZ GMT-4 but he also uses another client - - perhaps a GMX webmail - which uses GMT TZ. However this still seems to generate the correct display here in the few samples I checked.
--Mike
On 7/26/21 6:45 PM, Mike Bird wrote:
FWIW I'm seeing Edward's emails in R14.0.10 kmail-trinity with what appear to be the correct timestamps given their position in various threads.
His TBird email Date header is in TZ GMT-4 but he also uses another client -
- perhaps a GMX webmail - which uses GMT TZ. However this still seems to
generate the correct display here in the few samples I checked.
--Mike
I used the Vivaldi Mail client for one of my emails on July 24 and noticed the TZ in that header was +0000.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Monday 26 July 2021 15:50:40 Edward wrote:
On 7/26/21 6:45 PM, Mike Bird wrote:
FWIW I'm seeing Edward's emails in R14.0.10 kmail-trinity with what appear to be the correct timestamps given their position in various threads.
His TBird email Date header is in TZ GMT-4 but he also uses another client - - perhaps a GMX webmail - which uses GMT TZ. However this still seems to generate the correct display here in the few samples I checked.
--Mike
I used the Vivaldi Mail client for one of my emails on July 24 and noticed the TZ in that header was +0000.
It could be that something is getting messed up between the sending and my receiving those emails.
If it is a problem in my own system, then I would expect that I have problems with other emails, too; but last time this happened was 16 September 2020. (I checked, and have a screenshot of that one, too.) Also, so far as I can tell, it only happens with my TDE mailing list.
A problem that keeps repeating like that, however minor it may appear, could signify something bigger; although who ought to care -- myself, or all of us on the list, or some other group that includes us (?) -- remains to be seen.
Just making a note of it, if it matters.
Bill
On Mon July 26 2021 13:55:59 William Morder via tde-users wrote:
Question to Edward (sorry for off-topic): Why are your timestamps all messed up? Your replies are dated *before* the questions are asked. (See attached screenshot for proof.) It seems that you or your system are living about 35+ hours ahead of the rest of us.
What am I missing in your screenshot Bill?
It looks to me that Edward at 07/24 08:45 replied to Michael (timestamp omitted but thread shows 07/24 08:35) who replied to Edward from 07/24 06:41 who replied to Nick from 07/24 02:29 which timestamp is shown again from a different timezone as 07/23 19:29.
To me that all appears to be "in order".
FWIW your messages are sorted by order of arrival. Personally I prefer sorting by date.
--Mike
On Monday 26 July 2021 16:31:52 Mike Bird wrote:
On Mon July 26 2021 13:55:59 William Morder via tde-users wrote:
Question to Edward (sorry for off-topic): Why are your timestamps all messed up? Your replies are dated *before* the questions are asked. (See attached screenshot for proof.) It seems that you or your system are living about 35+ hours ahead of the rest of us.
What am I missing in your screenshot Bill?
It looks to me that Edward at 07/24 08:45 replied to Michael (timestamp omitted but thread shows 07/24 08:35) who replied to Edward from 07/24 06:41 who replied to Nick from 07/24 02:29 which timestamp is shown again from a different timezone as 07/23 19:29.
To me that all appears to be "in order".
FWIW your messages are sorted by order of arrival. Personally I prefer sorting by date.
--Mike
Edward (7.24.2021 08:45) replied to E.Liddell (7.25.2021 19:46).
Also, I always sort by date; it is only when Kmail's icon displays unread emails, which don't appear at the top of the list (earliest at the top). Then I switch to display "order of arrival" so that I don't have to scroll down through the list. And when I've found it, I switch back.
Like I said, not such a big deal; it only takes a few seconds of my time. But if it might signify some bigger problem, then it is worth noting.
And I repeat, it only happens to me with the TDE mailing list.
Bill
On 7/26/21 7:43 PM, William Morder via tde-users wrote:
On Monday 26 July 2021 16:31:52 Mike Bird wrote:
On Mon July 26 2021 13:55:59 William Morder via tde-users wrote:
Question to Edward (sorry for off-topic): Why are your timestamps all messed up? Your replies are dated *before* the questions are asked. (See attached screenshot for proof.) It seems that you or your system are living about 35+ hours ahead of the rest of us.
What am I missing in your screenshot Bill?
It looks to me that Edward at 07/24 08:45 replied to Michael (timestamp omitted but thread shows 07/24 08:35) who replied to Edward from 07/24 06:41 who replied to Nick from 07/24 02:29 which timestamp is shown again from a different timezone as 07/23 19:29.
To me that all appears to be "in order".
FWIW your messages are sorted by order of arrival. Personally I prefer sorting by date.
--Mike
Edward (7.24.2021 08:45) replied to E.Liddell (7.25.2021 19:46).
Also, I always sort by date; it is only when Kmail's icon displays unread emails, which don't appear at the top of the list (earliest at the top). Then I switch to display "order of arrival" so that I don't have to scroll down through the list. And when I've found it, I switch back.
Like I said, not such a big deal; it only takes a few seconds of my time. But if it might signify some bigger problem, then it is worth noting.
And I repeat, it only happens to me with the TDE mailing list.
Bill
My Sent folder shows three e-mails to the list on July 24. From the message source (headers):
via Thunderbird:
* 07:41 AM -0400
via SeaMonkey:
* 11:45 AM -0400
via Vivaldi Mail:
* 17:23 PM +0000 (The Date column in Thunderbird correctly displays '7/24/21, 1:23 PM' (local time, -0400)).
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Mon July 26 2021 16:43:46 William Morder via tde-users wrote:
Edward (7.24.2021 08:45) replied to E.Liddell (7.25.2021 19:46).
I'm sorry but I don't see anything that indicates Edward reply was a response to Lidell. The >>> in the message appear to be correct, albeit somebody removed Michael's timestamp.
I've attached a screenshot showing the threading (Folder/Options).
--Mike
Anno domini 2021 Sat, 24 Jul 07:41:16 -0400 Edward scripsit:
On 7/24/21 2:29 AM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Fri, 23 Jul 19:29:02 -0400 Edward scripsit:
I used the Debian LXQt image to install Debian, then installed the TDE packages afterwards. The installed packages are pavucontrol-qt and pavucontrol-qt-l10n. There is another package pavucontrol, described as 'PulseAudio Volume Control". I could also install that.
If I attempt to remove pulaeaudio-qt, it wants to install the LXQt desktop with other packages.
Sure it does - as we all know, audio is essential to DEs, so no sane user ever wants to remove that. And if you want to, think twice, 'cause the packages know better ;)
But you could install "equivs" and build a dummy pulaeaudio-qt package.
Nik
Hi Nik,
I briefly installed the regular pavucontrol package, which required some additional dependencies and the screens were somewhat different, but since the Qt variant works as is, I removed the regular package and dependencies and kept the Qt variant installed.
Although I don't know if this is a TDE-specific issue, with either or both pavucontrol packages installed, when they appear on TDE's Multimedia menu, neither entry displays an icon to the left.
Question still is: can you control volume with pulseaudio installed?
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64) ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 7/25/21 1:01 PM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Sat, 24 Jul 07:41:16 -0400 Edward scripsit:
Hi Nik,
I briefly installed the regular pavucontrol package, which required some additional dependencies and the screens were somewhat different, but since the Qt variant works as is, I removed the regular package and dependencies and kept the Qt variant installed.
Although I don't know if this is a TDE-specific issue, with either or both pavucontrol packages installed, when they appear on TDE's Multimedia menu, neither entry displays an icon to the left.
Question still is: can you control volume with pulseaudio installed?
Nik
Technically.
If I am listening to an MP3 using Audacious, I can successfully adjust the volume with the control marked Audacious.
There are three other controls on the same tab (Playback) labeled:
* speech-dispatcher-espeak-ng * speech-dispatcher-generic * speech-dispatcher-dummy
with 'playback on' defaulting to the Audigy FX sound card. If I move the volume control on the headset, the progress bars for the above three all move in-sync, but does not change the volume itself. If I change the playback option for those three to the headphones, the volume controls drop to 50% (half-way across), but do not move when the volume is changed. Only the Audacious entry will change the volume. Screenshot is attached.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Anno domini 2021 Sun, 25 Jul 15:58:47 -0400 Edward scripsit:
On 7/25/21 1:01 PM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Sat, 24 Jul 07:41:16 -0400 Edward scripsit:
Hi Nik,
I briefly installed the regular pavucontrol package, which required some additional dependencies and the screens were somewhat different, but since the Qt variant works as is, I removed the regular package and dependencies and kept the Qt variant installed.
Although I don't know if this is a TDE-specific issue, with either or both pavucontrol packages installed, when they appear on TDE's Multimedia menu, neither entry displays an icon to the left.
Question still is: can you control volume with pulseaudio installed?
Nik
Technically.
If I am listening to an MP3 using Audacious, I can successfully adjust the volume with the control marked Audacious.
There are three other controls on the same tab (Playback) labeled:
- speech-dispatcher-espeak-ng
- speech-dispatcher-generic
- speech-dispatcher-dummy
with 'playback on' defaulting to the Audigy FX sound card. If I move the volume control on the headset, the progress bars for the above three all move in-sync, but does not change the volume itself. If I change the playback option for those three to the headphones, the volume controls drop to 50% (half-way across), but do not move when the volume is changed. Only the Audacious entry will change the volume. Screenshot is attached.
Oh, I see, your headset is on USB :) That means that audio playback is not managed by your soundlbaster card, but by the USB headset itself - it's a different soundcard. But your volume keys change volume of the soundblaster aka default soundcard only. That will not work as intended.
I don't know how you persuade PA to change the volume of all soundcards using the keys of your USB headset, but that's what you should look for.
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Sun, 25 Jul 2021 22:41:34 +0200 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Oh, I see, your headset is on USB :) That means that audio playback is not managed by your soundlbaster card, but by the USB headset itself - it's a different soundcard. But your volume keys change volume of the soundblaster aka default soundcard only. That will not work as intended.
If the problem is indeed that the headset is being treated as a second soundcard, I can see two potential solutions:
Change the config (probably the ALSA config) to make the headset the default (first) soundcard.
More radically, blacklist the driver for the Audigy soundcard so that it (hopefully) doesn't get picked up at all.
If you're ever using the main soundcard, either of those things might cause other problems, of course.
E. Liddell
On 7/25/21 10:46 PM, E. Liddell wrote:
On Sun, 25 Jul 2021 22:41:34 +0200 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Oh, I see, your headset is on USB :) That means that audio playback is not managed by your soundlbaster card, but by the USB headset itself - it's a different soundcard. But your volume keys change volume of the soundblaster aka default soundcard only. That will not work as intended.
If the problem is indeed that the headset is being treated as a second soundcard, I can see two potential solutions:
Change the config (probably the ALSA config) to make the headset the default (first) soundcard.
More radically, blacklist the driver for the Audigy soundcard so that it (hopefully) doesn't get picked up at all.
If you're ever using the main soundcard, either of those things might cause other problems, of course.
02:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01) Subsystem: Creative Labs SB1570 SB Audigy Fx Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K] Memory at fe9f8000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
Output of lsusb -v for the Logitiech headphones, attached.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Anno domini 2021 Mon, 26 Jul 17:56:08 -0400 Edward scripsit:
On 7/25/21 10:46 PM, E. Liddell wrote:
On Sun, 25 Jul 2021 22:41:34 +0200 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Oh, I see, your headset is on USB :) That means that audio playback is not managed by your soundlbaster card, but by the USB headset itself - it's a different soundcard. But your volume keys change volume of the soundblaster aka default soundcard only. That will not work as intended.
If the problem is indeed that the headset is being treated as a second soundcard, I can see two potential solutions:
Change the config (probably the ALSA config) to make the headset the default (first) soundcard.
More radically, blacklist the driver for the Audigy soundcard so that it (hopefully) doesn't get picked up at all.
If you're ever using the main soundcard, either of those things might cause other problems, of course.
02:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01) Subsystem: Creative Labs SB1570 SB Audigy Fx Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K] Memory at fe9f8000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
Output of lsusb -v for the Logitiech headphones, attached.
can you post the output of
$ cat /proc/asound/cards
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On 7/27/21 2:01 AM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Mon, 26 Jul 17:56:08 -0400 Edward scripsit:
On 7/25/21 10:46 PM, E. Liddell wrote:
On Sun, 25 Jul 2021 22:41:34 +0200 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Oh, I see, your headset is on USB :) That means that audio playback is not managed by your soundlbaster card, but by the USB headset itself - it's a different soundcard. But your volume keys change volume of the soundblaster aka default soundcard only. That will not work as intended.
If the problem is indeed that the headset is being treated as a second soundcard, I can see two potential solutions:
Change the config (probably the ALSA config) to make the headset the default (first) soundcard.
More radically, blacklist the driver for the Audigy soundcard so that it (hopefully) doesn't get picked up at all.
If you're ever using the main soundcard, either of those things might cause other problems, of course.
02:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01) Subsystem: Creative Labs SB1570 SB Audigy Fx Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K] Memory at fe9f8000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
Output of lsusb -v for the Logitiech headphones, attached.
can you post the output of
$ cat /proc/asound/cards
Nik
~$ cat /proc/asound/cards 0 [Creative ]: HDA-Intel - HDA Creative HDA Creative at 0xfe9fc000 irq 18 1 [Headset ]: USB-Audio - Logitech USB Headset Logitech USB Headset Logitech USB Headset at usb-0000:00:12.0-1, full speed
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
oops, I forgot ...
Anno domini 2021 Mon, 26 Jul 17:56:08 -0400 Edward scripsit:
On 7/25/21 10:46 PM, E. Liddell wrote:
On Sun, 25 Jul 2021 22:41:34 +0200 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Oh, I see, your headset is on USB :) That means that audio playback is not managed by your soundlbaster card, but by the USB headset itself - it's a different soundcard. But your volume keys change volume of the soundblaster aka default soundcard only. That will not work as intended.
If the problem is indeed that the headset is being treated as a second soundcard, I can see two potential solutions:
Change the config (probably the ALSA config) to make the headset the default (first) soundcard.
More radically, blacklist the driver for the Audigy soundcard so that it (hopefully) doesn't get picked up at all.
If you're ever using the main soundcard, either of those things might cause other problems, of course.
02:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01) Subsystem: Creative Labs SB1570 SB Audigy Fx Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K] Memory at fe9f8000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
Output of lsusb -v for the Logitiech headphones, attached.
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Tue, 27 Jul 2021 13:12:10 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
Try /etc/modprobe.d/alsa.conf (that's the standard location, I believe).
E. Liddell
On 7/27/21 2:05 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 13:12:10 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
Try /etc/modprobe.d/alsa.conf (that's the standard location, I believe).
$ cat /etc/modprobe.d/alsa.conf cat: /etc/modprobe.d/alsa.conf: No such file or directory
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Anno domini 2021 Tue, 27 Jul 14:07:26 -0400 Edward scripsit:
On 7/27/21 2:05 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 13:12:10 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
Try /etc/modprobe.d/alsa.conf (that's the standard location, I believe).
$ cat /etc/modprobe.d/alsa.conf cat: /etc/modprobe.d/alsa.conf: No such file or directory
Ah, no, you don't have these files. That file /etc/modprobe.d/alsa-base.conf is what I use to configure my soundcards. You can use it as it is to place the usb sound device on index 0 and sb on index 1. Or you can experiment with the entries - e.g. with those that I commented out.
Nik
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64) ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On Tue, 27 Jul 2021 14:07:26 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:05 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 13:12:10 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
Try /etc/modprobe.d/alsa.conf (that's the standard location, I believe).
$ cat /etc/modprobe.d/alsa.conf cat: /etc/modprobe.d/alsa.conf: No such file or directory
Hmm. /etc/asound.conf ? ~/.asoundrc ? I suspect the correct location may depend on whether you have alsa installed as a kernel built-in, a kernel module, or a separate package.
E. Liddell
On 7/27/21 2:45 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 14:07:26 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:05 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 13:12:10 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
Try /etc/modprobe.d/alsa.conf (that's the standard location, I believe).
$ cat /etc/modprobe.d/alsa.conf cat: /etc/modprobe.d/alsa.conf: No such file or directory
Hmm. /etc/asound.conf ? ~/.asoundrc ? I suspect the correct location may depend on whether you have alsa installed as a kernel built-in, a kernel module, or a separate package.
No file named asound.conf in /etc. The only package installed with 'alsa' in its name is alsa-utils.
-- Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On Tue, 27 Jul 2021 15:21:48 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:45 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 14:07:26 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:05 PM, E. Liddell wrote:
On Tue, 27 Jul 2021 13:12:10 -0400 Edward epp@caramail.com wrote:
On 7/27/21 2:18 AM, Dr. Nikolaus Klepp wrote:
oops, I forgot ...
This is my /etc/modprobe.d/alsa-base.conf. It ensures that USB mics get index 0 - otherwise chromium cannot use them as audio source - and my builtin cards (Nvidia HDMI, soundblaster, onboard sound) are 1/2/3. Last line shows how to deactivate all but the last internal card and give it the index 1.
$ cat /etc/modprobe.d/alsa-base.conf #options snd_hda_intel model=thinkpad options snd_usb_audio index=0 options snd_hda_intel index=1,2,3 #options snd_hda_intel index=3,2,1 enable=0,0,1
Nik
~$ cat /etc/modprobe.d/alsa-base.conf cat: /etc/modprobe.d/alsa-base.conf: No such file or directory
Try /etc/modprobe.d/alsa.conf (that's the standard location, I believe).
$ cat /etc/modprobe.d/alsa.conf cat: /etc/modprobe.d/alsa.conf: No such file or directory
Hmm. /etc/asound.conf ? ~/.asoundrc ? I suspect the correct location may depend on whether you have alsa installed as a kernel built-in, a kernel module, or a separate package.
No file named asound.conf in /etc. The only package installed with 'alsa' in its name is alsa-utils.
Okay, looks like your distro doesn't install a default file. I would suggest that you check their alsa documentation to see where they want you to put any config files, then apply Nikolaus Klepp's information accordingly.
E. Liddell
-
Dr. Nikolaus Klepp -
E. Liddell -
Edward -
J Leslie Turriff -
Michael -
Mike Bird -
Steven D'Aprano -
William Morder