Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.
On 10/02/2024 21:48, Maureen Thomas wrote: So can I please get some help. I have a portable CD/DVD and I made a USB with a ISO on it. The computer does not have a cd/dvd burner but I have a portable one. Can some one tell me if there are any special things I need to do to put Debian 12 on this machine. I really hate windows and need to get it gone. Your help is always appreciated by this old lady. Thank you in advance> If you'd prefer to read some documentation before getting started, the Debian Installation Guide ( https://www.debian.org/releases/stable/amd64/ ) is a VERY good place to start. Chapter 3 ( https://www.debian.org/releases/stable/amd64/ch03.en.html ) in particular, covers things like: * What the installation process consists of * Minimum Hardware Requirements * Some potential pitfalls to be aware of But the whole document is quite well written, actually. OpenPGP_signature.asc Description: OpenPGP digital signature
Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.
On Sun, Feb 11, 2024 at 12:48:52AM -0500, Jeffrey Walton wrote: > On Sat, Feb 10, 2024 at 12:27 AM Maureen Thomas wrote: > > > > Do you really _not_ know how to use email? > > Or is this Phase II of the Sophie experiment? Jeffrey, please. Having a bad day? Cheer up -- tomás signature.asc Description: PGP signature
Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.
On Sat, Feb 10, 2024 at 12:27 AM Maureen Thomas wrote: > Do you really _not_ know how to use email? Or is this Phase II of the Sophie experiment? Jeff
Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm
https://fostips.com/6-ways-create-bootable-debian-ubuntu-usb-installer/ On Sat, 2024-02-10 at 21:48 +, Maureen Thomas wrote: > So can I please get some help. I have a portable CD/DVD and I made a USB > with a ISO on it. The computer does not have a cd/dvd burner but I have a > portable one. Can some one tell me if there are any special things I need to > do to put Debian 12 on this machine. I really hate windows and need to get > it gone. Your help is always appreciated by this old lady. Thank you in > advance> > On Friday, February 9, 2024 at 08:10:24 PM EST, Maureen Thomas > wrote: > > > ,, 1
Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm
On Sat, Feb 10, 2024 at 09:48:52PM +, Maureen Thomas wrote: > So can I please get some help. I have a portable CD/DVD and I made a USB > with a ISO on it. The computer does not have a cd/dvd burner but I have a > portable one. Can some one tell me if there are any special things I need to > do to put Debian 12 on this machine. I really hate windows and need to get > it gone. Your help is always appreciated by this old lady. Thank you in > advance> > On Friday, February 9, 2024 at 08:10:24 PM EST, Maureen Thomas > wrote: > > > ,, 1 Hi Maureen, It will very much depend if your computer will boot from an exteral CD/DVD which is USB connected. If it will - check in the BIOS / firmware, then you should be fine. If not, many machines will boot from a USB stick. You may find that yours will do so, in which case the only thing you will need to do is to get the image written appropriately to a USB drive. We can help, potentially - there's enough expertise on the list to help debug problems as they arise. (Andy, just having done *lots* of Debian installs as part of the release testing for the media team - but not one from an external CD/DVD drive - from what I can see, the laptops I have do boot from external devices connected via USB, though a CD/DVD might also be seen as a hard drive. Your mileage may vary :) ) With every good wish, as ever, Andy (amaca...@debian.org)
Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm
So can I please get some help. I have a portable CD/DVD and I made a USB with a ISO on it. The computer does not have a cd/dvd burner but I have a portable one. Can some one tell me if there are any special things I need to do to put Debian 12 on this machine. I really hate windows and need to get it gone. Your help is always appreciated by this old lady. Thank you in advance> On Friday, February 9, 2024 at 08:10:24 PM EST, Maureen Thomas wrote: ,, 1
-new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm. Ca
,, 1
Re: Bookworm: Analog audio disappeared
On 20/12/23 16:31, glasswings wrote: > DG2 sounds like an Intel GPU and HDMI, so it's also something I would ignore for now. Indeed, I can confirm now that the "DG Audio Controller Pro" device at PCI address 04:00.0 is the Intel i950 GPU and HDMI controller and I am able to use my screen's headphone output as a workaround for listening and the USB webcam's mic as an input. Still like to get the built-in analog controller at PCI address 00:1f.3 working though. > My next steps would be > > * reboot into the firmware menu and poke around, just in case there's a new option OK, so I'm not sure that option is new, but I found a switch that allows me to enable/disable the "Intel HD Audio Controller". Here is the full `sudo dmesg` output after disabling it: https://pastebin.com/rMeKuyC7 And after re-enabling it: https://pastebin.com/xLm2CjQt Here are some differences I found noteworthy: ``` [0.308734] pci :00:1f.3: [8086:7a50] type 00 class 0x040300 [0.308775] pci :00:1f.3: reg 0x10: [mem 0x420142-0x4201423fff 64bit] [0.308826] pci :00:1f.3: reg 0x20: [mem 0x420130-0x42013f 64bit] [0.308926] pci :00:1f.3: PME# supported from D3hot D3cold ``` and `[4.567449] snd_hda_intel :00:1f.3: no codecs found!` appears in the `sudo dmesg` output only when enabled. The `sudo lspci -v` output only contains ``` 00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11) DeviceName: Onboard - Sound Subsystem: Micro-Star International Co., Ltd. [MSI] Device 9e02 Flags: bus master, fast devsel, latency 32, IRQ 159, IOMMU group 10 Memory at 420142 (64-bit, non-prefetchable) [size=16K] Memory at 420130 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl ``` when enabled in the BIOS. Interestingly, `cat /etc/modprobe.d/alsa-base.conf` shows two `snd_hda_intel` entries when enabled but a single one when disabled, I'm guessing since the i950's DG2 Audio Controller is also an Intel device, it shows up in both cases. At this point, I'm suspecting a problem with the loading of the snd_hda_codec_realtek hdaudioC1D0 driver, as the following block used to be in my boot log and disappeared, along with my analog audio: ``` Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC897: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0:inputs: Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 Dec 18 14:42:22 gar kernel: snd_hda_codec_realtek hdaudioC1D0: Line=0x1a ``` Is this what you were referring to when you said > The big question in my mind is whether the correct Alsa module is > being detected and loaded, or perhaps some idea of whether it's > failing. ? I'll look at your other comment as soon as I solve the "no codecs found" error and still don't get any sound: > I also wonder whether the jack task assignment changed. Many HDA > devices can switch an analog jack between several kinds of input and > output (line-level vs microphone with DC bias vs headphone out) and I > could imagine those settings being changed. hdajackretask, which I > think is part of alsa-tools-gui, is the usual way to change those > settings. Thanks, Christian
Re: Extraction de CD audio [RESOLU]
J'ai pas mal de temps aujourd'hui à ripper quelques CD. Voici mes observations: - certains CD (60%) sont immédiatement reconnus comme CD audio: Sound Juicer ou Asunder savent extraire la musique et retrouver les titres du disque et des chansons - pour les 40% restant: - en répétant l'opération, elle peut inexplicablement réussir quand elle avait auparavant échoué dans des conditions en apparence strictement identiques (pour l'anecdote, j'ai un CD qui est passé à 6ème tentative et un autre à la 8ème) - après 4 échecs sur un CD assez long (77 minutes), j'ai essayé avec un autre lecteur de CD/DVD: réussite du 1er coup ! - idem pour un autre CD d'une durée normalement (<40 min) - pour un double CD, le 1er est passé du coup et pas le 2nd ! À chaud: - la protection anti-copie, si elle existe, n'est pas un facteur d'échec - la "qualité" du lecteur de CD/DVD semble à l'inverse déterminante. Merci à tous pour vos réponses Le mar. 19 déc. 2023 à 21:08, Jean Bernon a écrit : > > > > C'est bien ma version 3.38.0-2. Mais il refuse les cd non trouvés sur > > musicbrainz. Tu le lances avec des options ? Des greffons ? > > Je n'ai pas d'option ou de greffon particulier. Je suis sous Gnome. J'utilise > deux méthodes, soit : > 1 je charge le CD, j'attends qu'il soit monté et visible dans le gestionnaire > de fichiers et ensuite j'ouvre sound juicer qui met 10 à 20 secondes avant > d'afficher les pistes, que tu peux ensuite lire et extraire ; > 2 tu vas dans paramètres/media amovibles/cd audio et tu choisis sound juicer, > ensuite quand tu ouvres le cd dans le gestionnaire de fichiers, il te propose > de l'ouvrir avec sound juicer (en haut à droite de la liste des pistes). > > > Oui je veux du mp3 pour la compatibilité et la compression. > > D'où recompilation avec la qualité adhoc lors de l'encodage > > Dans les préférences, tu peux choisir mp3. J'évoquais FLAC seulement parce > que quelqu'un de la liste disait qu'il y avait un problème de qualité du > codage avec sound juicer. >
Re: Extraction de CD audio
Le mardi 19 décembre 2023, 19:30:19 CET Jean-François Bachelet a écrit : > oups ! c'est vrai c'est sur mageia linux que je fait mes rips... > debian c'est sur les autres machines (serveurs, nas, ect...) > > mais bon il doit bien être possible de le compiler pour debian aussi :) > va voir la : https://sourceforge.net/projects/grip/ Je le confirme c'est relativement facile de compiler grip pour Debian, il suffit de suivre les instructions du INSTALL il y a un paragraphe pour Debian. J'ai suivi la deuxième procédure. Faire un paquet Debian j'ai reculé mais cela doit être faisable. N'ayant pas de CD à tester je me suis arrêter là. > jeff > > Le 19/12/2023 à 16:40, nicolas.patr...@gmail.com a écrit : > > On 19/12/2023 09:05:49, Jean-François Bachelet wrote: > >> perso pour ce faire j'utilise Grip, en mode paranoiaque ;) (correction > >> d'erreurs, il lâche rien) avec un taux de 100% de réussite :) > > > > Tu m’intéresses parce que ce grip-là n’existe plus dans Debian depuis un > > bail. Ouin. À la place j’ai un bidule qui va sur Github. > > > > nicolas patrois : pts noir asocial
Re: Bookworm: Analog audio disappeared
Oof, I would be frustrated. It doesn't sound like a Pipewire problem. It's more likely related to a firmware upgrade, and I wouldn't try to troubleshoot Pipewire (etc.) until I could see the audio hardware in amixer or alsamixer. Also the CPU microcode seems less likely than the motherboard firmware. DG2 sounds like an Intel GPU and HDMI, so it's also something I would ignore for now. Almost certainly it's the Intel 7a50. My next steps would be * reboot into the firmware menu and poke around, just in case there's a new option * review the dmesg log after a fresh boot, see what in there is audio-related. The big question in my mind is whether the correct Alsa module is being detected and loaded, or perhaps some idea of whether it's failing. On top of that some Googling suggests "sof-firmware". But it sounds a little like people throwing things at the wall and seeing if it sticks. I would try to identify the sound device a little better before installing more software, but it does look like it's compatible with some recent Intel integrated IO. => https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html And it does look like you have a version of sof-firmware installed so I wonder if it's not up to date. This isn't something I'm familiar with; I haven't needed it for my AMD machine. I also wonder whether the jack task assignment changed. Many HDA devices can switch an analog jack between several kinds of input and output (line-level vs microphone with DC bias vs headphone out) and I could imagine those settings being changed. hdajackretask, which I think is part of alsa-tools-gui, is the usual way to change those settings.
Bookworm: Analog audio disappeared
Dear Debian community,
I'm running Bookworm with XFCE; Linux version 6.1.0-15-amd64
(debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU
ld (GNU Binutils for Debian) 2.40) and since yesterday, I cannot seem to
use the analog audio card any more.
The card isn't showing up in `pavucontrol` or in `aplay` and `arecord`:
```
cgelinek@gar:/tmp$ aplay -l
List of PLAYBACK Hardware Devices
card 2: PCH_1 [HDA Intel PCH], device 3: HDMI 0 [Q32V3WG5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: PCH_1 [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: PCH_1 [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: PCH_1 [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
cgelinek@gar:/tmp$ arecord -l
List of CAPTURE Hardware Devices
card 0: U0x46d0x825 [USB Device 0x46d:0x825], device 0: USB Audio [USB
Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
cgelinek@gar:/tmp$ aplay -L | grep -A 1 default
sysdefault
Default Audio Device
--
default
Default ALSA Output (currently PipeWire Media Server)
```
Note that the USB Audio device is a webcam and its microphone is
working. I don't have speakers on my monitors, so I can't test the HDMI
playback devices. The analog devices (front audio, line-in/out) are now
completely missing.
Other debug info:
```
cgelinek@gar:/tmp$ cat /proc/asound/modules
0 snd_usb_audio
1 snd_hda_intel
2 snd_hda_intel
cgelinek@gar:/tmp$ sudo lspci -v | grep -A7 -i "audio"
00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11)
DeviceName: Onboard - Sound
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 9e02
Flags: bus master, fast devsel, latency 32, IRQ 159, IOMMU group 10
Memory at 420142 (64-bit, non-prefetchable) [size=16K]
Memory at 420130 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14
--
04:00.0 Audio device: Intel Corporation DG2 Audio Controller
Subsystem: Intel Corporation DG2 Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 160, IOMMU group 15
Memory at 8130 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 3
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Latency Tolerance Reporting
Kernel driver in use: snd_hda_intel
cgelinek@gar:/tmp$ lsof /dev/snd/*
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1007/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pipewire 1764 cgelinek 48u CHR 116,1 0t0 381 /dev/snd/seq
pipewire 1764 cgelinek 49u CHR 116,1 0t0 381 /dev/snd/seq
wireplumb 1766 cgelinek 32u CHR 116,10 0t0 788 /dev/snd/controlC0
wireplumb 1766 cgelinek 34u CHR 116,8 0t0 769 /dev/snd/controlC2
```
PipeWire and its PulseAudio interface seem to be running OK:
```
cgelinek@gar:/tmp$ pactl info | grep '^Server Name'
Server Name: PulseAudio (on PipeWire 0.3.65)
cgelinek@gar:/tmp$ for s in wireplumber pipewire-pulse.service
pipewire-pulse.socket ; do
systemctl --user status $s |head -n3
done
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service;
enabled; preset: enabled)
Active: active (running) since Wed 2023-12-20 09:51:24 ACDT; 1h
43min ago
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service;
enabled; preset: enabled)
Active: active (running) since Wed 2023-12-20 09:51:24 ACDT; 1h
43min ago
● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket;
enabled; preset: enabled)
Active: active (running) since Wed 2023-12-20 09:51:24 ACDT; 1h
43min ago
cgelinek@gar:/tmp$ aplay -L | grep -A 1 default
sysdefault
Default Audio Device
--
default
Default ALSA Output (currently PipeWire Media Server)
```
...but there is [a known
issue](https://wiki.debian.org/PipeWire#pacmd_fails_with_.22No_PulseAudio_daemon_running.22)
with `pacmd` - `pactl` works but also doesn't show the analog audio
interface I'm interested in:
```
cgelinek@gar:/tmp$ pacmd list-sinks
No PulseAudio daemon running, or not running as session daemon.
cgelinek@gar:/tmp$ pactl list short
1 libpipewire-module-rt {
nice.level = -11
#rt.prio = 88
#rt.time.soft = -1
#rt.time.hard = -1
}
2 libpipewire-module-protocol-native
3 libpipewire-module-profiler
5 libpipewire-module-metadata
7 libpipewire-module-spa-device-factory
9 libpipewire-module-spa-node-factory
11 libpipewire-module-client-node
13 libpipew
Re: Extraction de CD audio
> C'est bien ma version 3.38.0-2. Mais il refuse les cd non trouvés sur > musicbrainz. Tu le lances avec des options ? Des greffons ? Je n'ai pas d'option ou de greffon particulier. Je suis sous Gnome. J'utilise deux méthodes, soit : 1 je charge le CD, j'attends qu'il soit monté et visible dans le gestionnaire de fichiers et ensuite j'ouvre sound juicer qui met 10 à 20 secondes avant d'afficher les pistes, que tu peux ensuite lire et extraire ; 2 tu vas dans paramètres/media amovibles/cd audio et tu choisis sound juicer, ensuite quand tu ouvres le cd dans le gestionnaire de fichiers, il te propose de l'ouvrir avec sound juicer (en haut à droite de la liste des pistes). > Oui je veux du mp3 pour la compatibilité et la compression. > D'où recompilation avec la qualité adhoc lors de l'encodage Dans les préférences, tu peux choisir mp3. J'évoquais FLAC seulement parce que quelqu'un de la liste disait qu'il y avait un problème de qualité du codage avec sound juicer.
Re: Re : Extraction de CD audio
oups ! c'est vrai c'est sur mageia linux que je fait mes rips... debian c'est sur les autres machines (serveurs, nas, ect...) mais bon il doit bien être possible de le compiler pour debian aussi :) nan ? parce que lui il marche impec, au debut j'utilisai RubyRipper mais il avait les mêmes problème que le tien avec 50% des disques, même flambants neufs. va voir la : https://sourceforge.net/projects/grip/ jeff Le 19/12/2023 à 16:40, nicolas.patr...@gmail.com a écrit : On 19/12/2023 09:05:49, Jean-François Bachelet wrote: perso pour ce faire j'utilise Grip, en mode paranoiaque ;) (correction d'erreurs, il lâche rien) avec un taux de 100% de réussite :) Tu m’intéresses parce que ce grip-là n’existe plus dans Debian depuis un bail. Ouin. À la place j’ai un bidule qui va sur Github. nicolas patrois : pts noir asocial
Re : Extraction de CD audio
On 19/12/2023 09:05:49, Jean-François Bachelet wrote: > perso pour ce faire j'utilise Grip, en mode paranoiaque ;) (correction > d'erreurs, il lâche rien) avec un taux de 100% de réussite :) Tu m’intéresses parce que ce grip-là n’existe plus dans Debian depuis un bail. Ouin. À la place j’ai un bidule qui va sur Github. nicolas patrois : pts noir asocial -- RÉALISME M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ? P : Non... Une carte bleue suffirait...
Re: Extraction de CD audio
Le 18 décembre 2023 Jean Bernon a écrit : > En effet, il commence par chercher les métadonnées sur MusicBrainz, mais s'il > ne les trouve pas, il le dit et il lit bien les pistes en leur donnant des > titres anonymes titre01, titre02 etc. et on peut les extraire (du moins ça se > passe ainsi pour moi - Sound Juicer 3.38). C'est bien ma version 3.38.0-2. Mais il refuse les cd non trouvés sur musicbrainz. Tu le lances avec des options ? Des greffons ? > Dans les préférences de Sound Juicer, on peut choisir le format de > sortie et utiliser par exemple FLAC ou OGG qui assure une qualité > correcte (FLAC est une compression sans aucune perte). Oui je veux du mp3 pour la compatibilité et la compression. D'où recompilation avec la qualité adhoc lors de l'encodage
Re: Extraction de CD audio
Hello :) Le 18/12/2023 à 10:58, Olivier a écrit : Bonjour, J'ai un PC sous Bullseye/Gnome (je compte bientôt le remplacer par un autre sous Bookworm) avec un lecteur externe de CD/DVD connecté par USB. J'ai décidé il y quelques jours de numériser ma collection de CD audio, chose que je n'avais pas essayé depuis plusieurs années. J'ai essayé avec Sound Juicer. Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à lire ou extraire le contenu des CD que dans environ 50% des cas. 1. Par expérience, quelle est la cause la plus probable d'un échec ? Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection du CD ? 2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou Bookworm) qui change sensiblement ce taux de lecture ? perso pour ce faire j'utilise Grip, en mode paranoiaque ;) (correction d'erreurs, il lâche rien) avec un taux de 100% de réussite :) Jeff
Re: Extraction de CD audio
> J'utilise abondamment sound juicer. Le problème est qu'il cherche les > infos sur musicbrainz. S'il ne les trouve pas il renvoit le message > qu'il > n'arrive aps à lire le cd. En effet, il commence par chercher les métadonnées sur MusicBrainz, mais s'il ne les trouve pas, il le dit et il lit bien les pistes en leur donnant des titres anonymes titre01, titre02 etc. et on peut les extraire (du moins ça se passe ainsi pour moi - Sound Juicer 3.38). > Dans tous les cas j'utilise ensuite picard pour rajouter les infos > musicbrainz. Ensuite je récupère les métadonnées avec puddletag > L'autre problème de sound juicer est qu'il n'y a pas de réglage de la > qualité de l'encodage. Du coup je l'ai recompilé pour obtenir une > meilleure qualité. Si ça t'intéresse je te donne la marche à suivre. Dans les préférences de Sound Juicer, on peut choisir le format de sortie et utiliser par exemple FLAC ou OGG qui assure une qualité correcte (FLAC est une compression sans aucune perte).
Re: Extraction de CD audio
Hello, J'ai numérisé toute ma CDthèque il y a 1an sous Bullseye via le programme ` abcde` (très pratique car autonome via un fichier de conf : tu rentres le CD, lances l'exécutable, vérifies les noms de pistes récupérées voire l'image d'illustration, puis l'outil gère toute la suite, piste par piste, avec d'éventuelles multiples transcodages au passage). Mais, vu les retours des autres, pas certain de toute façon que la cause racine soit à chercher côté logiciel dans ton cas... l0f4r0
Re : Extraction de CD audio
On 18/12/2023 10:58:37, Olivier wrote: > J'ai essayé avec Sound Juicer. > Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à > lire ou extraire le contenu des CD que dans environ 50% des cas. J’utilise XCFA qui permet de convertir en même temps dans un grand nombre de formats. > 1. Par expérience, quelle est la cause la plus probable d'un échec ? > Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection > du CD ? En plus de la liste fournie par Didier, j’ajoute : - le CD muni de protections à la con, comme le SACD. nicolas patrois : pts noir asocial -- RÉALISME M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ? P : Non... Une carte bleue suffirait...
Re: Extraction de CD audio
Le lundi 18 décembre 2023 à 10:58 +0100, Olivier a écrit : > Bonjour, > Bonjour, > J'ai un PC sous Bullseye/Gnome (je compte bientôt le remplacer par un > autre sous Bookworm) avec un lecteur externe de CD/DVD connecté par > USB. > > J'ai décidé il y quelques jours de numériser ma collection de CD > audio, chose que je n'avais pas essayé depuis plusieurs années. > > J'ai essayé avec Sound Juicer. > Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à > lire ou extraire le contenu des CD que dans environ 50% des cas. > > 1. Par expérience, quelle est la cause la plus probable d'un échec ? > Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de > protection > du CD ? > > 2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou > Bookworm) qui change sensiblement ce taux de lecture ? > J'utilise ripperX dans ce cas depuis plusieurs années; qui lui même emploie cdparanoia. Il faut juste veiller à lui donner une adresse de base de données de cd valide, c'est plus pratique... la dernière en date: http://gnudb.gnudb.org/~cddb/cddb.cgi > Slts > Christophe
Re: Extraction de CD audio
Bonjour à tous, J'utilise free:ac qui fait très bien le boulot :-D https://www.lesnumeriques.com/telecharger/fre-ac-free-audio-converter-bonkenc-53292 Belle journée Sylvie Le 18/12/2023 à 12:48, Michel Verdier a écrit : Le 18 décembre 2023 Olivier a écrit : J'ai essayé avec Sound Juicer. Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à lire ou extraire le contenu des CD que dans environ 50% des cas. 1. Par expérience, quelle est la cause la plus probable d'un échec ? Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection du CD ? J'utilise abondamment sound juicer. Le problème est qu'il cherche les infos sur musicbrainz. S'il ne les trouve pas il renvoit le message qu'il n'arrive aps à lire le cd. 2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou Bookworm) qui change sensiblement ce taux de lecture ? Je fais tout avec sound juicer et pour ceux qu'il refuse j'utilise asunder. Dans tous les cas j'utilise ensuite picard pour rajouter les infos musicbrainz. L'autre problème de sound juicer est qu'il n'y a pas de réglage de la qualité de l'encodage. Du coup je l'ai recompilé pour obtenir une meilleure qualité. Si ça t'intéresse je te donne la marche à suivre.
Re: Extraction de CD audio
Le 18 décembre 2023 Olivier a écrit : > J'ai essayé avec Sound Juicer. > Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à > lire ou extraire le contenu des CD que dans environ 50% des cas. > > 1. Par expérience, quelle est la cause la plus probable d'un échec ? > Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection > du CD ? J'utilise abondamment sound juicer. Le problème est qu'il cherche les infos sur musicbrainz. S'il ne les trouve pas il renvoit le message qu'il n'arrive aps à lire le cd. > 2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou > Bookworm) qui change sensiblement ce taux de lecture ? Je fais tout avec sound juicer et pour ceux qu'il refuse j'utilise asunder. Dans tous les cas j'utilise ensuite picard pour rajouter les infos musicbrainz. L'autre problème de sound juicer est qu'il n'y a pas de réglage de la qualité de l'encodage. Du coup je l'ai recompilé pour obtenir une meilleure qualité. Si ça t'intéresse je te donne la marche à suivre.
Re: Extraction de CD audio
Bonjour Essaie avec asunder. Chez moi ça fait bien le boulot. Roger Le 18 décembre 2023 04 h 58 min 37 s HNE, Olivier a écrit : >Bonjour, > >J'ai un PC sous Bullseye/Gnome (je compte bientôt le remplacer par un >autre sous Bookworm) avec un lecteur externe de CD/DVD connecté par >USB. > >J'ai décidé il y quelques jours de numériser ma collection de CD >audio, chose que je n'avais pas essayé depuis plusieurs années. > >J'ai essayé avec Sound Juicer. >Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à >lire ou extraire le contenu des CD que dans environ 50% des cas. > >1. Par expérience, quelle est la cause la plus probable d'un échec ? >Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection >du CD ? > >2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou >Bookworm) qui change sensiblement ce taux de lecture ? > >Slts > -- Envoyé depuis /e/OS Mail.
Re: Extraction de CD audio
Le 18/12/2023 à 10:58, Olivier a écrit : [...] 1. Par expérience, quelle est la cause la plus probable d'un échec ? Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection du CD ? [...] Bonjour, dans le désordre, pour les causes matérielles: - des CD sales ou rayés - des CD gravés (et non pas des CD pressés) qui se dégradent suivant la qualité du support après quelques mois ou quelques années - le lecteur CD qui vieillit mal et refuse de lire, partiellemet ou totalement - de la condensation qui s'est formée sur la lentille du lecteur CD (un coup de sèche-cheveux dans le lecteur, trappe ouverte, sur la lentille peut peut-être aider) - la lentille sale à l'intérieur du lecteur. - le câble USB du lecteur CD défectueux (essayer avec un autre) ça fait très longtemps que je n'ai plus extrait de CD audio et les ressources matérielles des PC actuels sont bien supérieures à celles d'avant, mais autrefois fallait aussi faire gaffe à la charge CPU à alléger (pas d'autres applis en même temps) pendant l'extraction. ça dépend aussi de l'encodage de sortie (WAV consomme moins vu qu'il y a extraction mais pas codage ensuite). Et sinon en GUI je me souviens avoir utilisé Asunder en remplacement de Sound-Juicer. En CLI avec cdparanoia on peut paramétrer plus finement (Asunder utilise cdparanoia mais sans possibilité de paramétrer finement, je viens de regarder)
Re: Extraction de CD audio
J'utilise Sound Juicer depuis longtemps, aujourd'hui sous Bookworm, mais auparavant sous Bullseye, avec un lecteur de CD/DVD intégré à mon laptop. Je ne rencontre pas de difficulté. Quels CD ne peux-tu pas extraire ? > Bonjour, > J'ai un PC sous Bullseye/Gnome (je compte bientôt le remplacer par un > autre sous Bookworm) avec un lecteur externe de CD/DVD connecté par > USB. > J'ai décidé il y quelques jours de numériser ma collection de CD > audio, chose que je n'avais pas essayé depuis plusieurs années. > J'ai essayé avec Sound Juicer. > Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à > lire ou extraire le contenu des CD que dans environ 50% des cas. > 1. Par expérience, quelle est la cause la plus probable d'un échec ? > Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de > protection > du CD ? > 2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou > Bookworm) qui change sensiblement ce taux de lecture ? > Slts
Extraction de CD audio
Bonjour, J'ai un PC sous Bullseye/Gnome (je compte bientôt le remplacer par un autre sous Bookworm) avec un lecteur externe de CD/DVD connecté par USB. J'ai décidé il y quelques jours de numériser ma collection de CD audio, chose que je n'avais pas essayé depuis plusieurs années. J'ai essayé avec Sound Juicer. Avec lui, sur une demie douzaine d'essais, j'observe qu'il n'arrive à lire ou extraire le contenu des CD que dans environ 50% des cas. 1. Par expérience, quelle est la cause la plus probable d'un échec ? Le lecteur de CD/DVD ? Le logiciel utilisé ? Les mesures de protection du CD ? 2. Existe-t-il un logiciel disponible (CLI ou GUI) sur Bullseye (ou Bookworm) qui change sensiblement ce taux de lecture ? Slts
Re: Displayport et audio => ko
Je sèche... La seule chose que je peux suggérer c'est d'installer aussi le paquet firmware-sof-signed (Sound Open Firmware, Intel) si il n'est pas déjà installé parce que si je comprends correctement, bien qu'au départ ça semble un projet majoritairement pour développeurs, il y a des PC qui ne fonctionnent pas correctement sans... Bonne chance :-)
Re: Displayport et audio => ko
Le Thu, 23 Nov 2023 11:14:15 +0100, didier gaumet a écrit : > As-tu les firmwares nécessaires installés? > explorer les logs système pour trouver les fichiers de firmwares > manquants (puis pour chaque fichier un apt-file search nom_du_fichier > pour le paquet à installer) > > à vue de nez, déjà vérifier que intel-microcode ou amd64-microcode > est installé, ainsi que alsa-firmware-loaders, firmware-intel-sound, > firmware-misc-nonfree. Ils étaient installés sauf alsa-firmware-loaders qui n'est pas connu même par un apt-cache search , ensuite j'ai ajouté "contrib" pour pouvoir l'installer > > Il peut aussi y avoir un firmware graphique manquant vu que > Displayport c'est de l'audio/video > Vaut mieux avoir trop de firmwares que pas assez: sans ceux > appropriés, ça ne fonctionne pas et il n'y a généralement aucune > alternative libre. j'ai les firmware intel : firmware-intel-sound intel-microcode j'ai installé firmware-linux-nonfree manquant > > Si ensuite ça ne fonctionne toujours pas, peut-être regarder du côté > de la doc Alsa pour paramétrer en fonction de tes besoins: > https://www.alsa-project.org/wiki/Asoundrc > https://alsa.opensrc.org/MultipleCards > (plus d'autres éventuelels pages du wiki alsa) Je pense bien qu'une fois la partie hardware fonctionnelle ... je devrais fouiller la dedans :-D Je commence a avoir des doutes sur la possiblité d'envoyer du son "numérique" (par opposition à analogique) cat /proc/asound/pcm 00-00: AD1984A Analog : AD1984A Analog : playback 1 : capture 1 00-02: AD1984A Alt Analog : AD1984A Alt Analog : playback 1 : capture 1 /sbin/alsactl info # # Sound card # - card: 0 id: Intel name: HDA Intel longname: HDA Intel at 0xf7adc000 irq 33 driver_name: HDA-Intel mixer_name: Analog Devices AD1984A components: HDA:11d4194a,10280420,00100400 controls_count: 35 pcm: - stream: PLAYBACK devices: - device: 0 id: AD1984A Analog name: AD1984A Analog subdevices: - subdevice: 0 name: subdevice #0 - device: 2 id: AD1984A Alt Analog name: AD1984A Alt Analog subdevices: - subdevice: 0 name: subdevice #0 - stream: CAPTURE devices: - device: 0 id: AD1984A Analog name: AD1984A Analog subdevices: - subdevice: 0 name: subdevice #0 - device: 2 id: AD1984A Alt Analog name: AD1984A Alt Analog subdevices: - subdevice: 0 name: subdevice #0 /sbin/alsactl: rawmidi_device_list:105: snd_ctl_rawmidi_next_device
Re: Displayport et audio => ko
Bonjour, Le 2023-11-23 09:24, Grégory Bulot a écrit : Je n'ais pas d'interface graphique sur cette machine , donc pas de pavucontrol possible (pas a ma connaissance) ;-) (Si le sous-entendu est que tant mieux qu'il n'y ait pas pulseaudio, alors la suite ne t'intéressera probablement pas…) Si tu es plus à l'aise avec pulseaudio, tu peux le lancer même si tu n'as pas d'interface graphique : ``` pulseaudio --start ``` Si tu ajoutes cette ligne au fichier `/etc/pulse/default.pa`, alors tu pourras le piloter via le réseau : ``` load-module module-native-protocol-tcp auth-anonymous=1 auth-ip-acl=127.0.0.1;192.168.1.0/24 ``` (n'oublie pas de redémarrer pulseaudio après la modification) Depuis ton poste de travail qui a une interface graphique : ``` export PULSE_SERVER=...# Adresse IP de la machine sans interface graphique pavucontrol ``` Sébastien
Re: Displayport et audio => ko
Le 23/11/2023 à 09:24, Grégory Bulot a écrit : Bonjour Sous debian 12.2 (6.1.0-13-amd64) j'ai espoir d'avoir le son via le display port (la video fonctionne)... c'est mal engagé pour l'instant, je sollicite vos lumières. c'est un OptiPlex 780 (SFF) core2duo Je n'ais pas d'interface graphique sur cette machine , donc pas de pavucontrol possible (pas a ma connaissance) ;- aplay -l [...] carte 0 : Intel [HDA Intel], périphérique 0 : AD1984A Analog [AD1984A Analog] Sous-périphériques : 1/1 Sous-périphérique #0 : subdevice #0 carte 0 : Intel [HDA Intel], périphérique 2 : AD1984A Alt Analog [AD1984A Alt Analog] aplay -L (n'affiche que des cartes "Analog"), exemple : hw:CARD=Intel,DEV=0 HDA Intel, AD1984A Analog Direct hardware device without any conversions [...] As-tu les firmwares nécessaires installés? explorer les logs système pour trouver les fichiers de firmwares manquants (puis pour chaque fichier un apt-file search nom_du_fichier pour le paquet à installer) à vue de nez, déjà vérifier que intel-microcode ou amd64-microcode est installé, ainsi que alsa-firmware-loaders, firmware-intel-sound, firmware-misc-nonfree. Il peut aussi y avoir un firmware graphique manquant vu que Displayport c'est de l'audio/video Vaut mieux avoir trop de firmwares que pas assez: sans ceux appropriés, ça ne fonctionne pas et il n'y a généralement aucune alternative libre. Si ensuite ça ne fonctionne toujours pas, peut-être regarder du côté de la doc Alsa pour paramétrer en fonction de tes besoins: https://www.alsa-project.org/wiki/Asoundrc https://alsa.opensrc.org/MultipleCards (plus d'autres éventuelels pages du wiki alsa)
Displayport et audio => ko
Bonjour Sous debian 12.2 (6.1.0-13-amd64) j'ai espoir d'avoir le son via le display port (la video fonctionne)... c'est mal engagé pour l'instant, je sollicite vos lumières. c'est un OptiPlex 780 (SFF) core2duo Je n'ais pas d'interface graphique sur cette machine , donc pas de pavucontrol possible (pas a ma connaissance) ;-) aplay -l [...] carte 0 : Intel [HDA Intel], périphérique 0 : AD1984A Analog [AD1984A Analog] Sous-périphériques : 1/1 Sous-périphérique #0 : subdevice #0 carte 0 : Intel [HDA Intel], périphérique 2 : AD1984A Alt Analog [AD1984A Alt Analog] [...] aplay -L (n'affiche que des cartes "Analog"), exemple : hw:CARD=Intel,DEV=0 HDA Intel, AD1984A Analog Direct hardware device without any conversions LANG=C lshw -c display,sound *-display:0 description: VGA compatible controller product: 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation [...] *-display:1 UNCLAIMED (<= j'imagine que le problème est là) description: Display controller product: 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 [...] *-multimedia description: Audio device product: 82801JD/DO (ICH10 Family) HD Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D2c logical name: /dev/snd/pcmC0D2p version: 02 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 lspci -nn | grep -i -e audio -e display 00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e13] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801JD/DO (ICH10 Family) HD Audio Controller [8086:3a6e] (rev 02) inxi -A Audio: Device-1: Intel 82801JD/DO HD Audio driver: snd_hda_intel API: ALSA v: k6.1.0-13-amd64 status: kernel-api lshw | grep -A11 multimedia *-multimedia description: Audio device produit: 82801JD/DO (ICH10 Family) HD Audio Controller fabriquant: Intel Corporation identifiant matériel: 1b information bus: pci@:00:1b.0 nom logique: card0 nom logique: /dev/snd/controlC0 nom logique: /dev/snd/hwC0D2 nom logique: /dev/snd/pcmC0D0c nom logique: /dev/snd/pcmC0D0p nom logique: /dev/snd/pcmC0D2c lsmod | grep -i -e display -e snd -e audio -e sound snd_hda_codec_analog20480 1 snd_hda_codec_generic98304 1 snd_hda_codec_analog ledtrig_audio 16384 1 snd_hda_codec_generic snd_hda_intel 57344 0 snd_intel_dspcfg 36864 1 snd_hda_intel snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg snd_hda_codec 184320 3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_analog snd_hda_core 122880 4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_analog,snd_hda_codec snd_hwdep 16384 1 snd_hda_codec snd_pcm 159744 3 snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 49152 1 snd_pcm snd 126976 7 snd_hda_codec_generic,snd_hwdep,snd_hda_intel,snd_hda_codec_analog,snd_hda_codec,snd_timer,snd_pcm soundcore 16384 1 snd drm_display_helper184320 1 i915 cec61440 2 drm_display_helper,i915 drm_kms_helper204800 2 drm_display_helper,i915 drm 614400 7 drm_kms_helper,drm_display_helper,drm_buddy,i915,ttm Voilà qu'en pensez-vous ?
changing default pulse audio output destination
Hello all, On one of systems, I have three different possible output destinations for sound: USB headset, system speaker, HDMI speaker. By default, pulse audio (or whatever the tool is these days on Debian 12) sends output to the headset, not what I want. So I change the destination but, whenever my screensave blanks the screen, when I reawaken it the destination goes to the headset again. I assume this is because the HDMI port goes to sleep or disappears? Is there any easy way to tell pulseaudio/pipewire/? to automatically route to the HDMI when the screen awakes and the HDMI is available again? Thank you, eric -- Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.1
Re: chromecast: no audio when casting screen
Hello, I'm trying to repply to an old thread, not sure if it will work (I'm using the link from https://lists.debian.org/debian-user/2021/02/msg00394.html openned with thunderbird) *** Old thread *** I have just find a posible solution https://www.linuxuprising.com/2020/04/how-to-cast-your-gnome-shell-desktop-to.html?m=1 I will test it in unstable Regards El jue., 17 dic. 2020 10:19, Andrea Borgia escribió: Il giorno gio 17 dic 2020 alle ore 07:12 Javier Barroso ha scritto: It is a known issue , see https://support.google.com/chromecast/thread/27045993?hl=en Great find, thanks for the quick response too :) *** Current repply *** Now it is working without any workaround Regards
Re: Bug with audio muting - which package?
пн, 5 июн. 2023 г. в 05:36, Paul Martz : > If I mute audio in the desktop, then reboot into console mode, the SpeakUp > screen reading software is also muted. I think this is a bug - muting the > desktop should be a desktop property and should not affect the console screen > reader. But I’m not sure which package I should file the bug against. Any > help would be appreciated. Thanks. You may try to bugreport for pulseaudio, but i think this bug will be rejected — pulseaudio (sound service) and alsa (hardware interface) is systemwide, not desktop-only. -- Stanislav
Bug with audio muting - which package?
Hi all. If I mute audio in the desktop, then reboot into console mode, the SpeakUp screen reading software is also muted. I think this is a bug - muting the desktop should be a desktop property and should not affect the console screen reader. But I’m not sure which package I should file the bug against. Any help would be appreciated. Thanks. Paul Martz PaulMartz.com
Re: How to enable the audio on the Kinect 1 so that I can talk without having the microphone attached to my mouth...on Debian.
I have even compiled it from source : root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio# git clone git:// git.ao2.it/kinect-audio-setup.git Clone in 'kinect-audio-setup' in corso... remote: Counting objects: 651, done. remote: Compressing objects: 100% (641/641), done. remote: Total 651 (delta 401), reused 0 (delta 0) Ricezione degli oggetti: 100% (651/651), 92.48 KiB | 635.00 KiB/s, fatto. Risoluzione dei delta: 100% (401/401), fatto. root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-setup# make install make -C kinect_upload_fw install make[1]: ingresso nella directory «/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-setup/kinect_upload_fw» cc -std=c99 -pedantic -Wall -Wextra -O2 -fno-common -Wall -Wextra -Wformat=2 -Winit-self -Winline -Wpacked -Wp,-D_FORTIFY_SOURCE=2 -Wpointer-arith -Wlarger-than-65500 -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wnested-externs -Wold-style-defini tion -Wredundant-decls -Wsign-compare -Wstrict-aliasing=2 -Wstrict-prototypes -Wswitch-enum -Wundef -Wunreachable-code -Wwrite-strings -Wunsafe-lo op-optimizations -I/usr/include/libusb-1.0 -c -o endian.o endian.c cc endian.o -lusb-1.0 -o endian rm -f endian.h ./endian > endian.h cc -std=c99 -pedantic -Wall -Wextra -O2 -fno-common -Wall -Wextra -Wformat=2 -Winit-self -Winline -Wpacked -Wp,-D_FORTIFY_SOURCE=2 -Wpointer-arith -Wlarger-than-65500 -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wnested-externs -Wold-style-defini tion -Wredundant-decls -Wsign-compare -Wstrict-aliasing=2 -Wstrict-prototypes -Wswitch-enum -Wundef -Wunreachable-code -Wwrite-strings -Wunsafe-lo op-optimizations -I/usr/include/libusb-1.0 -c -o kinect_upload_fw.o kinect_upload_fw.c In file included from kinect_upload_fw.c:38: /usr/include/libusb-1.0/libusb.h:937:1: warning: packed attribute is unnecessary for ‘libusb_control_setup’ [-Wpacked] 937 | } LIBUSB_PACKED; | ^ kinect_upload_fw.c: In function ‘main’: kinect_upload_fw.c:270:9: warning: ‘libusb_set_debug’ is deprecated: Use libusb_set_option instead [-Wdeprecated-declarations] 270 | libusb_set_debug(NULL, 3); | ^~~~ In file included from kinect_upload_fw.c:38: /usr/include/libusb-1.0/libusb.h:1362:18: note: declared here 1362 | void LIBUSB_CALL libusb_set_debug(libusb_context *ctx, int level); | ^~~~ cc kinect_upload_fw.o -lusb-1.0 -o kinect_upload_fw install -d /usr/local/sbin install -m 755 kinect_upload_fw /usr/local/sbin make[1]: uscita dalla directory «/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-setup/kinect_upload_fw» root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-setup# make install_udev_rules FIRMWARE_PATH=/lib/firmware/kinect/UACFirmware LOADER_PATH=/usr/local/sbin/kinect_upload_fw install -d /lib/udev/rules.d install -m 644 contrib/55-kinect_audio.rules.in /lib/udev/rules.d/55-kinect_audio.rules ./kinect_patch_udev_rules \ "/lib/firmware/kinect/UACFirmware" \ "/usr/local/sbin/kinect_upload_fw" \ "/lib/udev/rules.d/55-kinect_audio.rules" root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-setup# ./kinect_fetch_fw /lib/firmware/kinect This script is going to download the UAC Firmware for the Microsoft Kinect Sensor device from the Microsoft Kinect for Windows SDK: http://kinectforwindows.org/ The full license of the SDK can be found at: http://research.microsoft.com/en-us/um/legal/kinectsdk-tou_noncommercial.htm --2023-04-04 17:04:23-- http://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi Risoluzione di download.microsoft.com (download.microsoft.com)... 23.59.69.117, 2a02:26f0:1d00:29b::317f, 2a02:26f0:1d00:2ad::317f Connessione a download.microsoft.com (download.microsoft.com)|23.59.69.117|:80... connesso. Richiesta HTTP inviata, in attesa di risposta... 302 Moved Temporarily Posizione: https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi [segue] --2023-04-04 17:04:23-- https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi Connessione a download.microsoft.com (download.microsoft.com)|23.59.69.117|:443... connesso. Richiesta HTTP inviata, in attesa di risposta... 200 OK Lunghezza: 21823488 (21M) [application/octet-stream] Salvataggio in: ‘KinectSDK-v1.0-beta2-x86.msi’ KinectSDK-v1.0-beta2-x86.msi 100%[>] 20.81M 8.51MB/sin 2.4s 2023-04-04 17:04:25 (8.51 MB/s) - ‘KinectSDK-v1.0-beta2-x86.msi’ salvato [21823488/21823488] Extracting the UAC firmware... done. root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-setup# udevadm control --reload-rules root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio/kinect-audio-s
Re: How to enable the audio on the Kinect 1 so that I can talk without having the microphone attached to my mouth...on Debian.
I have installed the package on Ubuntu 22.04. Same situation that I have on Debian 11. It is not recognized as sound device : root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio# lsb_release -a LSB Version:core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy root@Z390-AORUS-PRO-DEST:/mnt/zroot2/zroot2/kinect-1-audio# cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8933 irq 159 1 [Device ]: USB-Audio - USB Audio Device C-Media Electronics Inc. USB Audio Device at usb-:00:14.0-3.1.2, full speed 4 [Device_1 ]: USB-Audio - USB Audio Device C-Media Electronics Inc. USB Audio Device at usb-:00:14.0-3.1.3, full speed On Tue, Apr 4, 2023 at 4:43 PM Mario Marietto wrote: > I've fixed the issue and I have installed the deb package : > > root@marietto:/mnt/zroot2/zroot2/kinect-1-audio# dpkg -i > hark-kinect_1.2.0.4440_amd64.deb > > (Lettura del database... 347122 file e directory attualmente installati.) > Preparativi per estrarre hark-kinect_1.2.0.4440_amd64.deb... > Estrazione di hark-kinect (1.2.0.4440) su (1.2.0.4440)... > Configurazione di hark-kinect (1.2.0.4440)... > > This script is going to download the UAC Firmware for the Microsoft > Kinect Sensor device from the Microsoft Kinect for Windows SDK: > http://kinectforwindows.org/ > > The full license of the SDK can be found at: > http://www.kinectforwindows.org/download/EULA.htm > > --2023-04-04 16:22:19-- > http://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi > Risoluzione di download.microsoft.com (download.microsoft.com)... > 23.59.69.117, 2a02:26f0:8d00:686::317f, 2a02:26f0:8d00:691::317f > Connessione a download.microsoft.com > (download.microsoft.com)|23.59.69.117|:80... > connesso. > Richiesta HTTP inviata, in attesa di risposta... 302 Moved Temporarily > Posizione: > https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi > [segue] > --2023-04-04 16:22:19-- > https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi > Connessione a download.microsoft.com > (download.microsoft.com)|23.59.69.117|:443... > connesso. > Richiesta HTTP inviata, in attesa di risposta... 200 OK > Lunghezza: 21823488 (21M) [application/octet-stream] > Salvataggio in: «KinectSDK-v1.0-beta2-x86.msi» > > KinectSDK-v1.0-beta2-x86 100%[==>] 20,81M > 8,58MB/sin 2,4s > > 2023-04-04 16:22:21 (8,58 MB/s) - «KinectSDK-v1.0-beta2-x86.msi» salvato > [21823488/21823488] > > 945806927702b2c47c32125ab9a80344 > 945806927702b2c47c32125ab9a80344 > Extracting the UAC firmware... > 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 > p7zip Version 16.02 (locale=it_IT.UTF-8,Utf16=on,HugeFiles=on,64 bits,16 > CPUs Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (906ED),ASM,AES-NI) > > Scanning the drive for archives: > 1 file, 21823488 bytes (21 MiB) > > Extracting archive: KinectSDK-v1.0-beta2-x86.msi > -- > Path = KinectSDK-v1.0-beta2-x86.msi > Type = Compound > Physical Size = 21823488 > Extension = msi > Cluster Size = 4096 > Sector Size = 64 > > Path = media1.cab > Size = 20488022 > Packed Size = 20488192 > -- > Path = media1.cab > Type = Cab > Physical Size = 20488022 > Method = MSZip > Blocks = 10 > Volumes = 1 > Volume Index = 0 > ID = 0 > > Everything is Ok > > Files: 4 > Size: 434176 > Compressed: 21823488 > done. > Elaborazione dei trigger per man-db (2.9.4-2)... > > I don't see errors,but I still don't see the kinect between the sounds > cards : > > root@marietto:/mnt/zroot2/zroot2/kinect-1-audio# cat /proc/asound/cards > > 0 [Device_1 ]: USB-Audio - USB Audio Device > C-Media Electronics Inc. USB Audio Device at > usb-:00:14.0-3.1.3, full speed > 1 [Device ]: USB-Audio - USB Audio Device > C-Media Electronics Inc. USB Audio Device at > usb-:00:14.0-3.1.2, full speed > 2 [PCH]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0x8933 irq 160 > 3 [NVidia ]: HDA-Intel - HDA NVidia > HDA NVidia at 0x8708 irq 17 > 4 [NVidia_1 ]: HDA-Intel - HDA NVidia > HDA NVidia at 0x8308 irq 18 > > What should I do now ? > > On Tue, Apr 4, 2023 at 2:13 PM Mario Marietto > wrote: > >> Seems like they moved them, I found the devs here: >
Re: How to enable the audio on the Kinect 1 so that I can talk without having the microphone attached to my mouth...on Debian.
I've fixed the issue and I have installed the deb package : root@marietto:/mnt/zroot2/zroot2/kinect-1-audio# dpkg -i hark-kinect_1.2.0.4440_amd64.deb (Lettura del database... 347122 file e directory attualmente installati.) Preparativi per estrarre hark-kinect_1.2.0.4440_amd64.deb... Estrazione di hark-kinect (1.2.0.4440) su (1.2.0.4440)... Configurazione di hark-kinect (1.2.0.4440)... This script is going to download the UAC Firmware for the Microsoft Kinect Sensor device from the Microsoft Kinect for Windows SDK: http://kinectforwindows.org/ The full license of the SDK can be found at: http://www.kinectforwindows.org/download/EULA.htm --2023-04-04 16:22:19-- http://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi Risoluzione di download.microsoft.com (download.microsoft.com)... 23.59.69.117, 2a02:26f0:8d00:686::317f, 2a02:26f0:8d00:691::317f Connessione a download.microsoft.com (download.microsoft.com)|23.59.69.117|:80... connesso. Richiesta HTTP inviata, in attesa di risposta... 302 Moved Temporarily Posizione: https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi [segue] --2023-04-04 16:22:19-- https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi Connessione a download.microsoft.com (download.microsoft.com)|23.59.69.117|:443... connesso. Richiesta HTTP inviata, in attesa di risposta... 200 OK Lunghezza: 21823488 (21M) [application/octet-stream] Salvataggio in: «KinectSDK-v1.0-beta2-x86.msi» KinectSDK-v1.0-beta2-x86 100%[==>] 20,81M 8,58MB/sin 2,4s 2023-04-04 16:22:21 (8,58 MB/s) - «KinectSDK-v1.0-beta2-x86.msi» salvato [21823488/21823488] 945806927702b2c47c32125ab9a80344 945806927702b2c47c32125ab9a80344 Extracting the UAC firmware... 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=it_IT.UTF-8,Utf16=on,HugeFiles=on,64 bits,16 CPUs Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (906ED),ASM,AES-NI) Scanning the drive for archives: 1 file, 21823488 bytes (21 MiB) Extracting archive: KinectSDK-v1.0-beta2-x86.msi -- Path = KinectSDK-v1.0-beta2-x86.msi Type = Compound Physical Size = 21823488 Extension = msi Cluster Size = 4096 Sector Size = 64 Path = media1.cab Size = 20488022 Packed Size = 20488192 -- Path = media1.cab Type = Cab Physical Size = 20488022 Method = MSZip Blocks = 10 Volumes = 1 Volume Index = 0 ID = 0 Everything is Ok Files: 4 Size: 434176 Compressed: 21823488 done. Elaborazione dei trigger per man-db (2.9.4-2)... I don't see errors,but I still don't see the kinect between the sounds cards : root@marietto:/mnt/zroot2/zroot2/kinect-1-audio# cat /proc/asound/cards 0 [Device_1 ]: USB-Audio - USB Audio Device C-Media Electronics Inc. USB Audio Device at usb-:00:14.0-3.1.3, full speed 1 [Device ]: USB-Audio - USB Audio Device C-Media Electronics Inc. USB Audio Device at usb-:00:14.0-3.1.2, full speed 2 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8933 irq 160 3 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0x8708 irq 17 4 [NVidia_1 ]: HDA-Intel - HDA NVidia HDA NVidia at 0x8308 irq 18 What should I do now ? On Tue, Apr 4, 2023 at 2:13 PM Mario Marietto wrote: > Seems like they moved them, I found the devs here: > > http://archive.hark.jp/harkoldrepos/dists/precise/non-free/binary-amd64/ > > but It does not work : > > marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo dpkg -i > hark-kinect_1.2.0.4440_amd64.deb > > Selezionato il pacchetto hark-kinect non precedentemente selezionato. > (Lettura del database... 347111 file e directory attualmente installati.) > Preparativi per estrarre hark-kinect_1.2.0.4440_amd64.deb... > Estrazione di hark-kinect (1.2.0.4440)... > Configurazione di hark-kinect (1.2.0.4440)... > > This script is going to download the UAC Firmware for the Microsoft > Kinect Sensor device from the Microsoft Kinect for Windows SDK: > http://kinectforwindows.org/ > > The full license of the SDK can be found at: > http://www.kinectforwindows.org/download/EULA.htm > > --2023-04-04 14:10:22-- > http://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi > Risoluzione di download.microsoft.com (download.microsoft.com)... > 92.122.248.205, 2a02:26f0:8d00:691::317f, 2a02:26f0:8d00:686::317f > Connessione a download.microsoft.com > (download.microsoft.com)|92.122.248.205|:80... > connesso. > Richiesta HTTP inviata, in attesa di risposta... 302 Moved Temporarily > Posizione: > https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x
Re: How to enable the audio on the Kinect 1 so that I can talk without having the microphone attached to my mouth...on Debian.
Mario Marietto wrote: > Seems like they moved them, I found the devs here: > > http://archive.hark.jp/harkoldrepos/dists/precise/non-free/binary-amd64/ > > but It does not work : > > marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo dpkg -i > hark-kinect_1.2.0.4440_amd64.deb That repository is for a version of Ubuntu, not Debian. You probably want to talk to the author, and try compiling it yourself. -dsr-
Re: How to enable the audio on the Kinect 1 so that I can talk without having the microphone attached to my mouth...on Debian.
Seems like they moved them, I found the devs here: http://archive.hark.jp/harkoldrepos/dists/precise/non-free/binary-amd64/ but It does not work : marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo dpkg -i hark-kinect_1.2.0.4440_amd64.deb Selezionato il pacchetto hark-kinect non precedentemente selezionato. (Lettura del database... 347111 file e directory attualmente installati.) Preparativi per estrarre hark-kinect_1.2.0.4440_amd64.deb... Estrazione di hark-kinect (1.2.0.4440)... Configurazione di hark-kinect (1.2.0.4440)... This script is going to download the UAC Firmware for the Microsoft Kinect Sensor device from the Microsoft Kinect for Windows SDK: http://kinectforwindows.org/ The full license of the SDK can be found at: http://www.kinectforwindows.org/download/EULA.htm --2023-04-04 14:10:22-- http://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi Risoluzione di download.microsoft.com (download.microsoft.com)... 92.122.248.205, 2a02:26f0:8d00:691::317f, 2a02:26f0:8d00:686::317f Connessione a download.microsoft.com (download.microsoft.com)|92.122.248.205|:80... connesso. Richiesta HTTP inviata, in attesa di risposta... 302 Moved Temporarily Posizione: https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi [segue] --2023-04-04 14:10:22-- https://download.microsoft.com/download/F/9/9/F99791F2-D5BE-478A-B77A-830AD14950C3/KinectSDK-v1.0-beta2-x86.msi Connessione a download.microsoft.com (download.microsoft.com)|92.122.248.205|:443... connesso. Richiesta HTTP inviata, in attesa di risposta... 200 OK Lunghezza: 21823488 (21M) [application/octet-stream] Salvataggio in: «KinectSDK-v1.0-beta2-x86.msi» KinectSDK-v1.0-beta2-x86 100%[==>] 20,81M 8,57MB/sin 2,4s 2023-04-04 14:10:25 (8,57 MB/s) - «KinectSDK-v1.0-beta2-x86.msi» salvato [21823488/21823488] kinect_fetch_fw: Invalid hash for file 'KinectSDK-v1.0-beta2-x86.msi'. == Error : Non Download File Please Remove & Re-install hark-kinect Remove Command : sudo apt-get remove hark-kinect Insatll Command : sudo apt-get hark-kinect == dpkg: errore nell'elaborare il pacchetto hark-kinect (--install): il sottoprocesso installato pacchetto hark-kinect script post-installation ha restituito lo stato di errore 1 Elaborazione dei trigger per man-db (2.9.4-2)... Si sono verificati degli errori nell'elaborazione: hark-kinect On Tue, Apr 4, 2023 at 1:33 PM Mario Marietto wrote: > Hello to everyone, > > I would like to enable the audio on my old kinect 1 so that I can talk > without having the microphone attached to my mouth. I see that in the past > this could be done installing the package called "hark-kinect",as explained > here : > > > https://gist.github.com/awesomebytes/924493bcdb358f5e71fdff93c2896730 > > > https://github.com/uts-magic-lab/hark_sound_localization/blob/master/pr2_kinect_audio.md > > > I'm using Debian 11 at the moment. The problem is that it seems that it > does not exist anymore. The repo is the following : > > > deb [arch=amd64 signed-by=/usr/share/keyrings/hark-archive-keyring.asc] > http://archive.hark.jp/harkrepos precise non-free > deb-src [arch=amd64 signed-by=/usr/share/keyrings/hark-archive-keyring.asc] > http://archive.hark.jp/harkrepos precise non-free > > > but it does not exists : > > > marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo apt update > > Found:1 http://security.debian.org/debian-security bullseye-security InRelease > Found:2 http://deb.debian.org/debian bullseye InRelease > Getting of:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB] > Found:4 https://linux.teamviewer.com/deb stable InRelease > Found:5 https://dl.google.com /linux/chrome/deb stable InRelease > Found:6 https://packages.microsoft.com/repos/edge stable InRelease > Found:7 https://packages.microsoft.com/debian/11/prod bullseye InRelease > Ignored:8 http://archive.hark.jp/harkrepos precise InRelease > Getting of:9 http://archive.hark.jp/harkrepos precise Release [8.157 B] > Getting of:10 http://archive.hark.jp/harkrepos precise Release.gpg [473 B] > Getting of:11 http://archive.hark.jp/harkrepos precise/non-free Sources > [9.117 B] > Getting of:12 http://archive.hark.jp/harkrepos precise/non-free amd64 > Packages [7.427 B] > Downloaded 69,2 kB in 3s (26,0 kB/s) > All the packages are updated. > > > marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo apt-get install > hark-kinect > E: can't find package hark-kinect > > > Just in case I can't use this hack,do you know about any alternative > method ? thanks. > > -- > Mario. > -- Mario.
How to enable the audio on the Kinect 1 so that I can talk without having the microphone attached to my mouth...on Debian.
Hello to everyone, I would like to enable the audio on my old kinect 1 so that I can talk without having the microphone attached to my mouth. I see that in the past this could be done installing the package called "hark-kinect",as explained here : https://gist.github.com/awesomebytes/924493bcdb358f5e71fdff93c2896730 https://github.com/uts-magic-lab/hark_sound_localization/blob/master/pr2_kinect_audio.md I'm using Debian 11 at the moment. The problem is that it seems that it does not exist anymore. The repo is the following : deb [arch=amd64 signed-by=/usr/share/keyrings/hark-archive-keyring.asc] http://archive.hark.jp/harkrepos precise non-free deb-src [arch=amd64 signed-by=/usr/share/keyrings/hark-archive-keyring.asc] http://archive.hark.jp/harkrepos precise non-free but it does not exists : marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo apt update Found:1 http://security.debian.org/debian-security bullseye-security InRelease Found:2 http://deb.debian.org/debian bullseye InRelease Getting of:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB] Found:4 https://linux.teamviewer.com/deb stable InRelease Found:5 https://dl.google.com /linux/chrome/deb stable InRelease Found:6 https://packages.microsoft.com/repos/edge stable InRelease Found:7 https://packages.microsoft.com/debian/11/prod bullseye InRelease Ignored:8 http://archive.hark.jp/harkrepos precise InRelease Getting of:9 http://archive.hark.jp/harkrepos precise Release [8.157 B] Getting of:10 http://archive.hark.jp/harkrepos precise Release.gpg [473 B] Getting of:11 http://archive.hark.jp/harkrepos precise/non-free Sources [9.117 B] Getting of:12 http://archive.hark.jp/harkrepos precise/non-free amd64 Packages [7.427 B] Downloaded 69,2 kB in 3s (26,0 kB/s) All the packages are updated. marietto@marietto:/mnt/zroot2/zroot2/AlexaChatGPT$ sudo apt-get install hark-kinect E: can't find package hark-kinect Just in case I can't use this hack,do you know about any alternative method ? thanks. -- Mario.
Re: Debian bullseye et sortie audio
Le 26/02/2023 à 20:49, Kohler Gerard a écrit : j'ai installé pipewire, mais il me plante tout, je l'ai donc desinstallé. bon je cherche encore, merci Bonjour, Sans trop savoir, je hasarde: éventuellement ça pourrait venir: - d'un bug apparu dans un paquet de Bullseye - de paquets mal ou pas configurés suite à ta dernière mise à jour. auquel cas un apt update puis apt upgrade pourrait aider. verifier le résultat d'un dpkg --configure -a et chercher les paquets à moitié configurés par aptitude search '~c'. apt-get check permet aussi normalement de voir si il ya des dépendances incorrectes ou manquantes. - du paquet kexec-tools (c'est moins probable car de ce que je comprends ça poserait problème en sortie de veille mais pas vraiment au boot)
Re: Debian bullseye et sortie audio
j'ai installé pipewire, mais il me plante tout, je l'ai donc desinstallé. bon je cherche encore, merci Gérard Le 26/02/2023 à 09:47, Haricophile a écrit : Le Sun, 26 Feb 2023 00:18:26 +0100 (CET), Bernard Schoenacker a écrit : Bonjour Gérard, Puisque tu es dans les choux, je te conselle de remplacer le serveur de son en service par pipewire merci Moi c'est l'inverse, comme je n'ai pas Gnome je vire pipewire qui s'installe tout seul et me pose plus de problème qu'il n'en résoud. -- == https://www.leregardduchat.fr/ ==
Re: Debian bullseye et sortie audio
Le Sun, 26 Feb 2023 00:18:26 +0100 (CET), Bernard Schoenacker a écrit : > Bonjour Gérard, > > Puisque tu es dans les choux, je te conselle de remplacer > le serveur de son en service par pipewire > > merci Moi c'est l'inverse, comme je n'ai pas Gnome je vire pipewire qui s'installe tout seul et me pose plus de problème qu'il n'en résoud.
Re: Debian bullseye et sortie audio
Bonjour Gérard, Puisque tu es dans les choux, je te conselle de remplacer le serveur de son en service par pipewire merci @+ Bernard bonjour, je suis sous Debian bullseye à jour, et depuis ma dernière mise à jour j'ai un problème de sortie son assez énervant que je n'arrive pas à résoudre. voici ma config : KDE plasma 5.20.5 KDE Frameworks 5.78.0 Qt 5.15.2 kernel 5.10.0-18-amd64 carte graphique NVIDIA GeForce GTX 660 ma sortie audio se fait par la carte vidéo à l'aide du contrôleur GK106 HDMI Controller le problème : lors du démarrage du système ou après une mise en veille le contrôleur s'éteint ou ne démarre pas, et je suis obligé de lancer le programme pavucontrol pour relancer le contrôleur. Je n'ai pas trouvé d'autre solution. avant cette mise à jour je n'avais pas ce problème. merci de voter aide Gérard -- == https://www.leregardduchat.fr/ ==
Debian bullseye et sortie audio
bonjour, je suis sous Debian bullseye à jour, et depuis ma dernière mise à jour j'ai un problème de sortie son assez énervant que je n'arrive pas à résoudre. voici ma config : KDE plasma 5.20.5 KDE Frameworks 5.78.0 Qt 5.15.2 kernel 5.10.0-18-amd64 carte graphique NVIDIA GeForce GTX 660 ma sortie audio se fait par la carte vidéo à l'aide du contrôleur GK106 HDMI Controller le problème : lors du démarrage du système ou après une mise en veille le contrôleur s'éteint ou ne démarre pas, et je suis obligé de lancer le programme pavucontrol pour relancer le contrôleur. Je n'ai pas trouvé d'autre solution. avant cette mise à jour je n'avais pas ce problème. merci de voter aide Gérard -- == https://www.leregardduchat.fr/ ==
Re: Audio
Ya lo resolví, instale debian 12 alfa 1 la imagen ISO híbrido dvd, luego de intentar lo que hice fue, apt update y mejoro parcialmente, reinstale gnome y reinicie y listo ya tengo sonido, en la intalación seguro no cargo bien, Gracias por la ayuda El dom., 5 de febrero de 2023 1:56 a. m., Camaleón escribió: > El 2023-02-04 a las 10:11 -0600, Deiby Herrera escribió: > > > Tarjeta Hda - intel - hda- nvidia - Hda ATI sb, > > Sólo te faltó decir Azalia/Realtek y Creative/Sound Blaster. > Vamos, de todo un poco :-D > > ¿Qué versión de Debian tienes instalada y qué entorno gráfico? > > > Vlc tiene audio > > Audacity también > > Firefox y Chrome en Youtube no > > Y cualquier otra aplicación tampoco > > Alguna sugerencia > > Los leo > > Empieza con los pasos que indican en la wiki de Debian para depurar > problemas con el sonido: > > Troubleshooting > https://wiki.debian.org/Sound > > Saludos, > > -- > Camaleón > >
Audio
Tarjeta Hda - intel - hda- nvidia - Hda ATI sb, Vlc tiene audio Audacity también Firefox y Chrome en Youtube no Y cualquier otra aplicación tampoco Alguna sugerencia Los leo
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Mon, Jan 30, 2023 at 12:59 PM Georgi Naplatanov wrote: > On 1/28/23 12:04, Timothy M Butterworth wrote: > > All, > > > > I just upgraded to the 1/28/23 updates to KF5 102 and now I have no > > audio devices found. My USB headset is plugged in but KDE does not see > it. > > > > lsusb lists my USB headphones: > > Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540 > > > > lspci lists my audio devices > > 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] > > ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) > > 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h > > HD Audio Controller > > > > This appears to be a KDE issue. Is anyone else having this problem? > > Please note the problem started after installing KF5-102 and a reboot. > > > > Hi Timothy! > > These are a few things to check > > - run alsamixer in console as your user and check that needed channels > are not muted and volume levels are high enough > - be sure that you use one of these - PulseAudio or PipeWire (not both) > I had PulseAudio and Pipewire installed. I uninstalled PipeWire and now my sound cards show up again. Thanks > - chances for missing firmware are small for this device but Debian has > a new section "non-free-firmware" so check output of dmesg command and > in case of missing firmware you can add "non-free-firmware" to > /etc/apt/sources.list (something like this) > > deb http://deb.debian.org/debian/ bookworm main non-free > non-free-firmware contrib > > Files containing firmware files, you can find with "apt-file" > package/command. Example: > > # apt-file search firware101.bin > > Kind regards > Georgi > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On 1/28/23 12:04, Timothy M Butterworth wrote: All, I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio devices found. My USB headset is plugged in but KDE does not see it. lsusb lists my USB headphones: Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540 lspci lists my audio devices 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller This appears to be a KDE issue. Is anyone else having this problem? Please note the problem started after installing KF5-102 and a reboot. Hi Timothy! These are a few things to check - run alsamixer in console as your user and check that needed channels are not muted and volume levels are high enough - be sure that you use one of these - PulseAudio or PipeWire (not both) - chances for missing firmware are small for this device but Debian has a new section "non-free-firmware" so check output of dmesg command and in case of missing firmware you can add "non-free-firmware" to /etc/apt/sources.list (something like this) deb http://deb.debian.org/debian/ bookworm main non-free non-free-firmware contrib Files containing firmware files, you can find with "apt-file" package/command. Example: # apt-file search firware101.bin Kind regards Georgi
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sun, Jan 29, 2023 at 12:59 PM Brad Rogers wrote:
> On Sun, 29 Jan 2023 12:11:33 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I did not try a new user. I did try deleting "~/.config/pulseaudio"
>
> Sorry to say, I've reached the limit of my knowledge on the subject.
> :-(
>
> --
> Regards _ "Valid sig separator is {dash}{dash}{space}"
> / ) "The blindingly obvious is never immediately apparent"
> / _)rad "Is it only me that has a working delete key?"
> All these things are mine!
> Money is Not Our God - Killing Joke
>
sudo alsactl init
Found hardware: "HDA-Intel" "ATI R6xx HDMI"
"HDA:1002aa01,00aa0100,00100700" "0x103c" "0x87c5"
Hardware is initialized using a generic method
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0a37" "" ""
Hardware is initialized using a generic method
Found hardware: "acp" "" "" "" ""
Hardware is initialized using a generic method
I also fixed alsa-state daemon.
sudo vim /lib/systemd/system/alsa-state.service, I know I should have put
this in /etc but I am not concerned at the moment.
added ! to ConditionPathExists
systemctl daemon-reload
systemctl restart alsa-state
sudo systemctl status alsa-state
● alsa-state.service - Manage Sound Card State (restore and store)
Loaded: loaded (/lib/systemd/system/alsa-state.service; static)
Active: active (running) since Mon 2023-01-30 10:59:40 EST; 11min ago
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sun, 29 Jan 2023 12:11:33 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I did not try a new user. I did try deleting "~/.config/pulseaudio"
Sorry to say, I've reached the limit of my knowledge on the subject.
:-(
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
All these things are mine!
Money is Not Our God - Killing Joke
pgpcVPMwvALzC.pgp
Description: OpenPGP digital signature
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sun, Jan 29, 2023 at 12:11 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers wrote:
>
>> On Sun, 29 Jan 2023 07:22:02 -0500
>> Timothy M Butterworth wrote:
>>
>> Hello Timothy,
>>
>> >I upgraded to 5.27beta so far no new issues. I just installed Wayland
>>
>> Good to know. Thanks for the info.
>>
>> >so I can try it out. My sound cards are still not working though.
>>
>> Have you tried;
>>
>> (a) checking volume levels
>> because sometimes things get 'fiddled with' on update.
>>
>
> It is not a volume or a mute problem. KDE does not register any sound
> cards being installed. The hardware has drivers and it is installed. I can
> see the hardware with aplay.
>
> aplay -l
> List of PLAYBACK Hardware Devices
> card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [SAMSUNG]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287
> Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 2: H540 [Logitech USB Headset H540], device 0: USB Audio [USB Audio]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
> (b) with a new user
>> to try and ascertain whether it's unique to your usual
>> user or an across the board problem.
>>
>
> I did not try a new user. I did try deleting "~/.config/pulseaudio"
>
I tried creating a new user, it still has the same problem.
> --
>> Regards _ "Valid sig separator is {dash}{dash}{space}"
>> / ) "The blindingly obvious is never immediately apparent"
>> / _)rad "Is it only me that has a working delete key?"
>> Success defined by acquisition stinks
>> Money is Not Our God - Killing Joke
>>
>
>
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀
>
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers wrote:
> On Sun, 29 Jan 2023 07:22:02 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I upgraded to 5.27beta so far no new issues. I just installed Wayland
>
> Good to know. Thanks for the info.
>
> >so I can try it out. My sound cards are still not working though.
>
> Have you tried;
>
> (a) checking volume levels
> because sometimes things get 'fiddled with' on update.
>
It is not a volume or a mute problem. KDE does not register any sound cards
being installed. The hardware has drivers and it is installed. I can see
the hardware with aplay.
aplay -l
List of PLAYBACK Hardware Devices
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [SAMSUNG]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: H540 [Logitech USB Headset H540], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
(b) with a new user
> to try and ascertain whether it's unique to your usual
> user or an across the board problem.
>
I did not try a new user. I did try deleting "~/.config/pulseaudio"
> --
> Regards _ "Valid sig separator is {dash}{dash}{space}"
> / ) "The blindingly obvious is never immediately apparent"
> / _)rad "Is it only me that has a working delete key?"
> Success defined by acquisition stinks
> Money is Not Our God - Killing Joke
>
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sun, 29 Jan 2023 07:22:02 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I upgraded to 5.27beta so far no new issues. I just installed Wayland
Good to know. Thanks for the info.
>so I can try it out. My sound cards are still not working though.
Have you tried;
(a) checking volume levels
because sometimes things get 'fiddled with' on update.
(b) with a new user
to try and ascertain whether it's unique to your usual
user or an across the board problem.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Success defined by acquisition stinks
Money is Not Our God - Killing Joke
pgpdNPZcrEvD0.pgp
Description: OpenPGP digital signature
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sun, Jan 29, 2023 at 5:19 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 10:41:38 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I am looking forward to 5.27beta! It has a lot of good improvements.
>
> As I suggested, the migration to testing has started today. I'm holding
> off for a few days to be sure (well, as sure as I can be) that
> everything necessary for a smooth upgrade has migrated.
>
I upgraded to 5.27beta so far no new issues. I just installed Wayland so I
can try it out. My sound cards are still not working though.
> --
> Regards _ "Valid sig separator is {dash}{dash}{space}"
> / ) "The blindingly obvious is never immediately apparent"
> / _)rad "Is it only me that has a working delete key?"
> I ain't got no time for intellectual music, e.g. Hergest Ridge
> Heads Down No Nonsense Mindless Boogie - Alberto y Lost Trios Paranoias
>
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sat, 28 Jan 2023 10:41:38 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I am looking forward to 5.27beta! It has a lot of good improvements.
As I suggested, the migration to testing has started today. I'm holding
off for a few days to be sure (well, as sure as I can be) that
everything necessary for a smooth upgrade has migrated.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
I ain't got no time for intellectual music, e.g. Hergest Ridge
Heads Down No Nonsense Mindless Boogie - Alberto y Lost Trios Paranoias
pgpXNRkgfbFlP.pgp
Description: OpenPGP digital signature
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sat, Jan 28, 2023 at 7:50 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 05:04:59 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >This appears to be a KDE issue. Is anyone else having this problem?
> >Please note the problem started after installing KF5-102 and a reboot.
>
> KDE Plasma is undergoing big changes ATM. Soon(1) Plasma 5.27beta
> (2) will start transitioning to testing.
I am looking forward to 5.27beta! It has a lot of good improvements.
> Things are going
> to be sticky until everything is in sync. That said you could, of
> course, still have run into some bug or other, I couldn't say.
>
> When large numbers of suite(3) packages start arriving in testing(4), I
> usually hold off a day or two before I update in an attempt to be sure
> everything upgrades in sync. Because, as you've found out, although
> things can upgrade without any apparent issue, they may leave your
> desktop in an undesirable state.
>
> That's all part of running testing, of course. In fact, it's the reason
> testing exists.
>
> (1) Probably tomorrow
> (2) Versioned as 4:5.26.90-1
> (3) By which I mean things like Plasma, Gnome, etc.
> (4) In this particular case KDE packages from 5.101.* to 5.102.*
>
> --
> Regards _ "Valid sig separator is {dash}{dash}{space}"
> / ) "The blindingly obvious is never immediately apparent"
> / _)rad "Is it only me that has a working delete key?"
> There's no point in asking you'll get no reply
> Pretty Vacant - Sex Pistols
>
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sat, 28 Jan 2023 05:04:59 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>This appears to be a KDE issue. Is anyone else having this problem?
>Please note the problem started after installing KF5-102 and a reboot.
KDE Plasma is undergoing big changes ATM. Soon(1) Plasma 5.27beta
(2) will start transitioning to testing. Things are going
to be sticky until everything is in sync. That said you could, of
course, still have run into some bug or other, I couldn't say.
When large numbers of suite(3) packages start arriving in testing(4), I
usually hold off a day or two before I update in an attempt to be sure
everything upgrades in sync. Because, as you've found out, although
things can upgrade without any apparent issue, they may leave your
desktop in an undesirable state.
That's all part of running testing, of course. In fact, it's the reason
testing exists.
(1) Probably tomorrow
(2) Versioned as 4:5.26.90-1
(3) By which I mean things like Plasma, Gnome, etc.
(4) In this particular case KDE packages from 5.101.* to 5.102.*
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
There's no point in asking you'll get no reply
Pretty Vacant - Sex Pistols
pgpkO9o3RTu6V.pgp
Description: OpenPGP digital signature
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sat, 28 Jan 2023 07:37:01 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I forgot to mention that I am using Bookworm.
It *was* in the subject header. :-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
I can't do a thing 'cause I can't relax
Independence Day - Comsat Angels
pgpI2I3pOiayf.pgp
Description: OpenPGP digital signature
Re: Bookworm 1/28/23 updates - No Audio Devices Found
On Sat, Jan 28, 2023 at 5:04 AM Timothy M Butterworth < timothy.m.butterwo...@gmail.com> wrote: > All, > > I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio > devices found. My USB headset is plugged in but KDE does not see it. > I forgot to mention that I am using Bookworm. > lsusb lists my USB headphones: > Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540 > > lspci lists my audio devices > 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] > ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) > 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD > Audio Controller > > This appears to be a KDE issue. Is anyone else having this problem? Please > note the problem started after installing KF5-102 and a reboot. > > Thanks > > Tim > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄⠀⠀ > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Bookworm 1/28/23 updates - No Audio Devices Found
All, I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio devices found. My USB headset is plugged in but KDE does not see it. lsusb lists my USB headphones: Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540 lspci lists my audio devices 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller This appears to be a KDE issue. Is anyone else having this problem? Please note the problem started after installing KF5-102 and a reboot. Thanks Tim -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Issues with audio after updating
Alsa works fine, I'm able to play sound over jack with software that let's you pick the audio device (Reaper in my case) Removing and reinstalling piperwire fixed the issue, but I have no idea why El lun, 10 oct 2022 a las 23:16, Joel Roth () escribió: > > On Sun, Oct 09, 2022 at 10:37:18AM +0200, Maximiliano Estudies wrote: > > After an update yesterday my audio stopped working. I'm currently on > > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 > > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) > > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > > > > The issue seems to be with pulseaudio, but I'm not really sure. > > pavucontrol shows "no available cards for configuration" on the > > configuration tab, and ```pactl list cards``` returns nothing but > > ```pacmd list-cards``` does returns all the available cards. There is > > a similar behavior when listing the sinks, pactl returns only the > > dummy sink and pacmd returns the alsa sink, but with state: IDLE > > > > I have no idea how to debug this further so any tips are much appreciated! > > Hiya Maximiliano, > > That the two pulseaudio utilities disagree on what devices > are present, it seems plausible that some part of pa is to blame. > > You may like to verify that your ALSA subsystem is working properly, > and include this in your bug report. > > For that, disable pulseaudio[1], > > systemctl --user stop pulseaudio.socket > systemctl --user stop pulseaudio.service > > test play an audio file with aplay, mpv, etc. > to a device listed by aplay -l, or cat /proc/asound/cards > > To start pulse audio again: > > systemctl --user start pulseaudio.socket > systemctl --user start pulseaudio.service > > 1. > https://askubuntu.com/questions/8425/how-to-temporarily-disable-pulseaudio-while-running-a-game-under-wine > > I've not tested this myself. > > cheers, > > -- > Joel Roth >
Re: Issues with audio after updating
On Sun, Oct 09, 2022 at 10:37:18AM +0200, Maximiliano Estudies wrote: > After an update yesterday my audio stopped working. I'm currently on > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > > The issue seems to be with pulseaudio, but I'm not really sure. > pavucontrol shows "no available cards for configuration" on the > configuration tab, and ```pactl list cards``` returns nothing but > ```pacmd list-cards``` does returns all the available cards. There is > a similar behavior when listing the sinks, pactl returns only the > dummy sink and pacmd returns the alsa sink, but with state: IDLE > > I have no idea how to debug this further so any tips are much appreciated! Hiya Maximiliano, That the two pulseaudio utilities disagree on what devices are present, it seems plausible that some part of pa is to blame. You may like to verify that your ALSA subsystem is working properly, and include this in your bug report. For that, disable pulseaudio[1], systemctl --user stop pulseaudio.socket systemctl --user stop pulseaudio.service test play an audio file with aplay, mpv, etc. to a device listed by aplay -l, or cat /proc/asound/cards To start pulse audio again: systemctl --user start pulseaudio.socket systemctl --user start pulseaudio.service 1. https://askubuntu.com/questions/8425/how-to-temporarily-disable-pulseaudio-while-running-a-game-under-wine I've not tested this myself. cheers, -- Joel Roth
Re: Issues with audio after updating
pipewire-pusle is installed ``` pipewire-pulse/testing,now 0.3.59-1 amd64 [installed,automatic] PipeWire PulseAudio daemon ``` El lun, 10 oct 2022 a las 6:07, Dekks Herton () escribió: > > Maximiliano Estudies writes: > > > After an update yesterday my audio stopped working. I'm currently on > > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 > > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) > > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > > > > The issue seems to be with pulseaudio, but I'm not really sure. > > pavucontrol shows "no available cards for configuration" on the > > configuration tab, and ```pactl list cards``` returns nothing but > > ```pacmd list-cards``` does returns all the available cards. There is > > a similar behavior when listing the sinks, pactl returns only the > > dummy sink and pacmd returns the alsa sink, but with state: IDLE > > > > I have no idea how to debug this further so any tips are much appreciated! > > Hi > > Has pipewire-pulse been removed in the update? > > My Bookworm audio broke on a new pipewire update in the last week > > -- > regards. > > Thinkpad T60p 2.33Ghz 2GB SXGA+ >
Re: Issues with audio after updating
Maximiliano Estudies writes: > After an update yesterday my audio stopped working. I'm currently on > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > > The issue seems to be with pulseaudio, but I'm not really sure. > pavucontrol shows "no available cards for configuration" on the > configuration tab, and ```pactl list cards``` returns nothing but > ```pacmd list-cards``` does returns all the available cards. There is > a similar behavior when listing the sinks, pactl returns only the > dummy sink and pacmd returns the alsa sink, but with state: IDLE > > I have no idea how to debug this further so any tips are much appreciated! Hi Has pipewire-pulse been removed in the update? My Bookworm audio broke on a new pipewire update in the last week -- regards. Thinkpad T60p 2.33Ghz 2GB SXGA+
Re: Issues with audio after updating
pipewire-pulse is installed ``` pipewire-pulse/testing,now 0.3.59-1 amd64 [installed,automatic] PipeWire PulseAudio daemon ``` El dom, 9 oct 2022 a las 16:30, Javier Barroso () escribió: > > > > El dom., 9 oct. 2022 15:42, Maximiliano Estudies > escribió: >> >> that's a very good tip, thanks. I'm using testing and the log shows >> that pulseaudio was updated with some dependencies, I see >> >> pulseaudio:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) >> pulseaudio-utils:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) >> libkf5pulseaudioqt3:amd64 (1.3-2, 1.3-2+b1) >> pulseaudio-module-jack:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) >> were part of the update that broke pulseaudio, so I think I'll use >> reportbug to report this issue. >> Thanks for the help! > > > Some weeks ago I needed (on unstable) to install pipewire-pulse to get the > sound working again > > Regards >> >> >>
Re: Issues with audio after updating
El dom., 9 oct. 2022 15:42, Maximiliano Estudies escribió: > that's a very good tip, thanks. I'm using testing and the log shows > that pulseaudio was updated with some dependencies, I see > > pulseaudio:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) > pulseaudio-utils:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) > libkf5pulseaudioqt3:amd64 (1.3-2, 1.3-2+b1) > pulseaudio-module-jack:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) > were part of the update that broke pulseaudio, so I think I'll use > reportbug to report this issue. > Thanks for the help! > Some weeks ago I needed (on unstable) to install pipewire-pulse to get the sound working again Regards > > >
Re: Issues with audio after updating
that's a very good tip, thanks. I'm using testing and the log shows that pulseaudio was updated with some dependencies, I see pulseaudio:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) pulseaudio-utils:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) libkf5pulseaudioqt3:amd64 (1.3-2, 1.3-2+b1) pulseaudio-module-jack:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2) were part of the update that broke pulseaudio, so I think I'll use reportbug to report this issue. Thanks for the help! El dom, 9 oct 2022 a las 13:39, local10 () escribió: > > Oct 9, 2022, 08:37 by maxiestud...@gmail.com: > > > After an update yesterday my audio stopped working. I'm currently on > > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 > > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) > > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > > > > The issue seems to be with pulseaudio, but I'm not really sure. > > pavucontrol shows "no available cards for configuration" on the > > configuration tab, and ```pactl list cards``` returns nothing but > > ```pacmd list-cards``` does returns all the available cards. There is > > a similar behavior when listing the sinks, pactl returns only the > > dummy sink and pacmd returns the alsa sink, but with state: IDLE > > > > I have no idea how to debug this further so any tips are much appreciated! > > > > Are you running Bookworm? Am running Bookworm with seemingly the same kernel > but I don't have any issues with audio and it doesn't look like pulseaudio > had any upgrades in Bookworm in the last two days. > > # uname -a > Linux tst 5.19.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > x86_64 GNU/Linux > > If you're using aptitude check the aptitude log to see what was upgraded > lately: > > # less /var/log/aptitude > > Regards, >
Re: Issues with audio after updating
Oct 9, 2022, 08:37 by maxiestud...@gmail.com: > After an update yesterday my audio stopped working. I'm currently on > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) > > The issue seems to be with pulseaudio, but I'm not really sure. > pavucontrol shows "no available cards for configuration" on the > configuration tab, and ```pactl list cards``` returns nothing but > ```pacmd list-cards``` does returns all the available cards. There is > a similar behavior when listing the sinks, pactl returns only the > dummy sink and pacmd returns the alsa sink, but with state: IDLE > > I have no idea how to debug this further so any tips are much appreciated! > Are you running Bookworm? Am running Bookworm with seemingly the same kernel but I don't have any issues with audio and it doesn't look like pulseaudio had any upgrades in Bookworm in the last two days. # uname -a Linux tst 5.19.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) x86_64 GNU/Linux If you're using aptitude check the aptitude log to see what was upgraded lately: # less /var/log/aptitude Regards,
Issues with audio after updating
After an update yesterday my audio stopped working. I'm currently on Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) The issue seems to be with pulseaudio, but I'm not really sure. pavucontrol shows "no available cards for configuration" on the configuration tab, and ```pactl list cards``` returns nothing but ```pacmd list-cards``` does returns all the available cards. There is a similar behavior when listing the sinks, pactl returns only the dummy sink and pacmd returns the alsa sink, but with state: IDLE I have no idea how to debug this further so any tips are much appreciated!
Re: No HDMI Audio
On Sun, Jul 24, 2022 at 01:37:34PM -0400, Timothy M Butterworth wrote: > All, > > I am not getting any sound through HDMI. I have an AMD Ryzen 7 4700U CPU > with integrated Renior Graphics. I checked the device and it is not muted. > Does anyone have any ideas? > > inxi -F > Audio:Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel > Device-2: Advanced Micro Devices [AMD] > Raven/Raven2/FireFlight/Renoir Audio Processor driver: snd_rn_pci_acp3x > Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: > snd_hda_intel > Sound Server: ALSA v: k5.10.0-16-amd64 > > *aplay -l* > card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 > Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > *lspci* > 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637 > 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] > Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01) > 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 10h-1fh) HD Audio Controller I would stop pulseaudio and test `aplay sample.wav` using the device option to target various alsa devices. Once you've found the HDMI device that works, you can set it as the default device. -- Joel Roth
Re: No HDMI Audio
Just caught the tail end of this and thought I'd add in my $0,02 worth of experience. Using the latest Debian stable with KDE I had my PCMCIA sound come up "silent." Toying with KDE's controls and changing the sound driver and output (a confusing thing because there are multiple locations/widgets to do this) would fix the problem. At the same time the video (again, PCMCIA) would intermittently "blink" hinting at a driver issue. But sometime an apt-get update (or a reboot?) somehow seemed to fix things -- it no longer experiences those problems. -- "A king who does not protect the environment does not deserve to be called king." -- Chinese philosopher and politician Guan Zhong 700 B.C.
Re: No HDMI Audio
On 7/25/2022 7:25 AM, Marco wrote: Am Sun, 24 Jul 2022 17:40:23 -0400 schrieb Timothy M Butterworth : One thing I do not get is that the device is AMD but it is using Intel's sound driver. Some of the HD-Audio chips use an Intel driver. They are also on AMD socket motherboards. I also have such a motherboard and sound works. But the HD-Audio on the Motherboard is NOT the HDMI output. The HDMI output is on the graphics card. +1, The HDMI might be more useful from a graphic card point of view. On the sound card you might have a digital connection (£EG: SPDIF) or sound connections. -- John Doe
Re: No HDMI Audio
Am Sun, 24 Jul 2022 17:40:23 -0400 schrieb Timothy M Butterworth : > One thing I do not get is that the device is AMD but it is using > Intel's sound driver. Some of the HD-Audio chips use an Intel driver. They are also on AMD socket motherboards. I also have such a motherboard and sound works. But the HD-Audio on the Motherboard is NOT the HDMI output. The HDMI output is on the graphics card. This might also be the snd_hda_intel kernel module, here GeForce 210. 09:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1) Subsystem: ZOTAC International (MCO) Ltd. High Definition Audio Controller [19da:7214] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
Re: No HDMI Audio
On Sun, Jul 24, 2022 at 3:33 PM Marco wrote: > Am Sun, 24 Jul 2022 13:37:34 -0400 > schrieb Timothy M Butterworth : > > > I am not getting any sound through HDMI. I have an AMD Ryzen 7 4700U > > CPU with integrated Renior Graphics. I checked the device and it is > > not muted. Does anyone have any ideas? > > Maybe a stupid question, but is your output stream directed to the > output your want? > Check pavucontrol. > > Everything looks good in pavucontrol. HDMI2 is the port I am trying to get working. https://drive.google.com/file/d/19HzoVZC1-XpWSVhc8y8d_vjmPaGijR_1/view?usp=sharing One thing I do not get is that the device is AMD but it is using Intel's sound driver. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: No HDMI Audio
Am Sun, 24 Jul 2022 13:37:34 -0400 schrieb Timothy M Butterworth : > I am not getting any sound through HDMI. I have an AMD Ryzen 7 4700U > CPU with integrated Renior Graphics. I checked the device and it is > not muted. Does anyone have any ideas? Maybe a stupid question, but is your output stream directed to the output your want? Check pavucontrol.
No HDMI Audio
All, I am not getting any sound through HDMI. I have an AMD Ryzen 7 4700U CPU with integrated Renior Graphics. I checked the device and it is not muted. Does anyone have any ideas? inxi -F Audio:Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: snd_rn_pci_acp3x Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.10.0-16-amd64 *aplay -l* card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 *lspci* 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: AMD Ryzen 7 4700U No HDMI Audio
Timothy M Butterworth wrote: > I have an AMD Ryzen 7 4700U with Radeon Graphics. It shows two HDMI Output > devices. One device has a connection, HDMI2. When I select this device I > get no sound output. I know the cable is good because I tested it with my > notebook and it worked fine. Has this ever worked before, or is this a new setup? Possibilities: 1. one of your HDMI ports doesn't support sound. Try the other one. 2. your sound is flowing out the wrong port; use alsa, pulseaudio or pipejack tools as appropriate to select the right port. 3. something is muted or set to very low volume. Unmute, raise volumes. 4. something is actually wrong in hardware Give us more information. -dsr-
AMD Ryzen 7 4700U No HDMI Audio
All, I have an AMD Ryzen 7 4700U with Radeon Graphics. It shows two HDMI Output devices. One device has a connection, HDMI2. When I select this device I get no sound output. I know the cable is good because I tested it with my notebook and it worked fine. Any help is appreciated. Thanks Tim
Re: Salida audio en mini PC
El lun, 20 dic 2021 a las 8:05, Josu Lazkano () escribió: > Gracias a los dos, > > ¡Ya lo tengo funcionando! He copiado los ficheros de esta web [ > http://davidegironi.blogspot.com/2019/10/linux-mint-on-z83-f-intel-atom-x5-z8350.html] > y ajustado los volumenes con alsamixer. > > Ya no casca el speaker-test y tengo sonido. > > Muchísimas gracias por vuestra ayuda. > Que bueno te sirvió y se pudo resolver, saludos. > > Un saludo. > > -- > Josu Lazkano > -- L.J.Marín Usando: Debian Testing
Re: Salida audio en mini PC
Gracias a los dos, ¡Ya lo tengo funcionando! He copiado los ficheros de esta web [ http://davidegironi.blogspot.com/2019/10/linux-mint-on-z83-f-intel-atom-x5-z8350.html] y ajustado los volumenes con alsamixer. Ya no casca el speaker-test y tengo sonido. Muchísimas gracias por vuestra ayuda. Un saludo. -- Josu Lazkano
Re: Salida audio en mini PC
El 2021-12-19 a las 18:18 +0100, Josu Lazkano escribió: > El dom, 19 dic 2021 a las 13:42, Camaleón () escribió: > > > El 2021-12-19 a las 12:07 +0100, Josu Lazkano escribió: > > > > > Tengo un mini PC (Z83II) corriendo Debian Buster, quiero usarlo para > > > reproducir música, lo tengo sin interfaz gráfico, en modo servidor. > > > > > > Pero no acierto a hacer un test: > > > > > > $ speaker-test -D default -c 8 > > > speaker-test 1.2.4 > > > > > > Playback device is default > > > Stream parameters are 48000Hz, S16_LE, 8 channels > > > Using 16 octaves of pink noise > > > Rate set to 48000Hz (requested 48000Hz) > > > Buffer size range from 96 to 204768 > > > Period size range from 48 to 102384 > > > Using max buffer size 204768 > > > Periods = 4 > > > Unable to set hw params for playback: Argumento inválido > > > Setting of hwparams failed: Argumento inválido > > > > (...) > > > > Dale un vistado a la página de MythTV donde explican bastante bien cómo > > probar con esa utilidad y cómo pasarle los parámetros adecuados, aunque > > me temo que el éxito de tu misión va a ser una cuestión de prueba-error > > :-): > > > > Using ALSA's speaker-test utility > > https://www.mythtv.org/wiki/Using_ALSA%27s_speaker-test_utility > > > Se me ha escapado el correo antes de tiempo... sigo: > > $ speaker-test > > speaker-test 1.2.4 > > El dispositivo de reproducción es default > Los parámetros del flujo son 48000Hz, S16_LE, 1 canales > Usando 16 octavas de ruido rosa > Frecuencia establecida a 48000Hz (se solicitó 48000Hz) > El rango del tamaño del buffer va desde 192 hasta 2097152 > El rango del tamaño del perído va desde 64 hasta 699051 > Utilizando el tamaño máximo de buffer 2097152 > Periodos = 4 > fue establecido period_size = 524288 > fue establecido buffer_size = 2097152 > 0 - Frontal izquierdo > ^CTiempo por período = 10,933915 > > Pero parece que el mini PC este no asigna bien el dispositivo por defecto, > o al menos me casca si no le pongo un dispositivo: > > $ speaker-test > > speaker-test 1.2.4 > > Playback device is default > Stream parameters are 48000Hz, S16_LE, 1 channels > Using 16 octaves of pink noise > Rate set to 48000Hz (requested 48000Hz) > Buffer size range from 96 to 204768 > Period size range from 48 to 102384 > Using max buffer size 204768 > Periods = 4 > Unable to set hw params for playback: Argumento inválido > Setting of hwparams failed: Argumento inválido > > No se que poner en el parámetro -D, he probado con diferentes opciones, > pero todos dan error. > > Me gustaría probar a instalar Buster con escritorio, pero tengo bastantes > servicios corriendo y no puedo formatearlo. > > ¿Se os ocurre qué más puedo probar? Compara el contenido del archivo .asoundrc en ambos equipos, y en cualquier caso, prueba a renombrarlo en el minipc para que ALSA no lo tome, quizá tengas definidia alguna configuración que le dé problemas a la utilidad speaker-test. También puedes buscar por el error que te saca cuando lo ejecutas sin parámetros, por si te diea alguna pista del problema: https://www.google.com/search?q=speaker-test+unable+to+set+hw+params+for+playback+invalid+argument Saludos, -- Camaleón
Re: Salida audio en mini PC
En tantos años de usar debian con openbox nunca tuve problemas con el audio, ni con el sonido trasero o el del panel frontal, siempre lo manejé con alsamixer desde la consola, el icono de la barra solo lo tenia para subir y bajar el volumen, este año armé un desktop nuevo y si tuve problemas con el sonido en openbox, de plano no escuchaba nada o solo un ruido como de interferencia, en algún sitio leí que para resolver sin tanto alboroto lo mejor era instalar pulseaudio, eso hice y en mi caso funcionó perfecto, aunque igual se puede ajustar por alsamixer algunas cosas como el volumen del micrófono, lo que instalo de alsa es: alsa-oss alsa-tools alsa-utils y del pulseadio solo me aparece instalado: pulseaudio pulseaudio-utils su pueden instalar algunos otros módulos de pulseaudio pero con eso ya me funciona, creo existen paquetes para poder configurar pulseaudio desde la consola al estilo alsamixer pero no he probado, y encontré esta pagina que quizas te pueda ayudar/interesar http://davidegironi.blogspot.com/2019/10/linux-mint-on-z83-f-intel-atom-x5-z8350.html#.Yb9jUnVBwkk para terminar yo tengo openbox con solo lo que necesito y de entrada solo carga en memoria según htop unos 450mb +/- eso si no abras firefox o chrome porque se van al chancho los mb, esos dos trastes cargan más mb en memoria que el mismo sistema completo :) El dom, 19 dic 2021 a las 8:08, Josu Lazkano () escribió: > Hola a todos, > > Tengo un mini PC (Z83II) corriendo Debian Buster, quiero usarlo para > reproducir música, lo tengo sin interfaz gráfico, en modo servidor. > > Pero no acierto a hacer un test: > > $ speaker-test -D default -c 8 > speaker-test 1.2.4 > > Playback device is default > Stream parameters are 48000Hz, S16_LE, 8 channels > Using 16 octaves of pink noise > Rate set to 48000Hz (requested 48000Hz) > Buffer size range from 96 to 204768 > Period size range from 48 to 102384 > Using max buffer size 204768 > Periods = 4 > Unable to set hw params for playback: Argumento inválido > Setting of hwparams failed: Argumento inválido > > Esta es la info de mi tarjeta: > > $ aplay -l > List of PLAYBACK Hardware Devices > card 0: bytcrrt5651 [bytcr-rt5651], device 0: Audio (*) [] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: bytcrrt5651 [bytcr-rt5651], device 1: Deep-Buffer Audio (*) [] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel > HDMI/DP LPE Audi] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel > HDMI/DP LPE Audi] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel > HDMI/DP LPE Audi] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > $ aplay -L > null > Discard all samples (playback) or generate zero samples (capture) > hw:CARD=bytcrrt5651,DEV=0 > bytcr-rt5651, > Direct hardware device without any conversions > hw:CARD=bytcrrt5651,DEV=1 > bytcr-rt5651, > Direct hardware device without any conversions > plughw:CARD=bytcrrt5651,DEV=0 > bytcr-rt5651, > Hardware device with all software conversions > plughw:CARD=bytcrrt5651,DEV=1 > bytcr-rt5651, > Hardware device with all software conversions > default:CARD=bytcrrt5651 > bytcr-rt5651, > Default Audio Device > sysdefault:CARD=bytcrrt5651 > bytcr-rt5651, > Default Audio Device > dmix:CARD=bytcrrt5651,DEV=0 > bytcr-rt5651, > Direct sample mixing device > dmix:CARD=bytcrrt5651,DEV=1 > bytcr-rt5651, > Direct sample mixing device > hw:CARD=Audio,DEV=0 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Direct hardware device without any conversions > hw:CARD=Audio,DEV=1 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Direct hardware device without any conversions > hw:CARD=Audio,DEV=2 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Direct hardware device without any conversions > plughw:CARD=Audio,DEV=0 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Hardware device with all software conversions > plughw:CARD=Audio,DEV=1 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Hardware device with all software conversions > plughw:CARD=Audio,DEV=2 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Hardware device with all software conversions > default:CARD=Audio > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Default Audio Device > sysdefault:CARD=Audio > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi > Default Audio Device > hdmi:CARD=Audio,DEV=0 > Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Au
Re: Salida audio en mini PC
El dom, 19 dic 2021 a las 13:42, Camaleón () escribió: > El 2021-12-19 a las 12:07 +0100, Josu Lazkano escribió: > > > Tengo un mini PC (Z83II) corriendo Debian Buster, quiero usarlo para > > reproducir música, lo tengo sin interfaz gráfico, en modo servidor. > > > > Pero no acierto a hacer un test: > > > > $ speaker-test -D default -c 8 > > speaker-test 1.2.4 > > > > Playback device is default > > Stream parameters are 48000Hz, S16_LE, 8 channels > > Using 16 octaves of pink noise > > Rate set to 48000Hz (requested 48000Hz) > > Buffer size range from 96 to 204768 > > Period size range from 48 to 102384 > > Using max buffer size 204768 > > Periods = 4 > > Unable to set hw params for playback: Argumento inválido > > Setting of hwparams failed: Argumento inválido > > (...) > > Dale un vistado a la página de MythTV donde explican bastante bien cómo > probar con esa utilidad y cómo pasarle los parámetros adecuados, aunque > me temo que el éxito de tu misión va a ser una cuestión de prueba-error > :-): > > Using ALSA's speaker-test utility > https://www.mythtv.org/wiki/Using_ALSA%27s_speaker-test_utility > > Saludos, > > -- > Camaleón > > Se me ha escapado el correo antes de tiempo... sigo: $ speaker-test speaker-test 1.2.4 El dispositivo de reproducción es default Los parámetros del flujo son 48000Hz, S16_LE, 1 canales Usando 16 octavas de ruido rosa Frecuencia establecida a 48000Hz (se solicitó 48000Hz) El rango del tamaño del buffer va desde 192 hasta 2097152 El rango del tamaño del perído va desde 64 hasta 699051 Utilizando el tamaño máximo de buffer 2097152 Periodos = 4 fue establecido period_size = 524288 fue establecido buffer_size = 2097152 0 - Frontal izquierdo ^CTiempo por período = 10,933915 Pero parece que el mini PC este no asigna bien el dispositivo por defecto, o al menos me casca si no le pongo un dispositivo: $ speaker-test speaker-test 1.2.4 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 96 to 204768 Period size range from 48 to 102384 Using max buffer size 204768 Periods = 4 Unable to set hw params for playback: Argumento inválido Setting of hwparams failed: Argumento inválido No se que poner en el parámetro -D, he probado con diferentes opciones, pero todos dan error. Me gustaría probar a instalar Buster con escritorio, pero tengo bastantes servicios corriendo y no puedo formatearlo. ¿Se os ocurre qué más puedo probar? Gracias y un saludo. -- Josu Lazkano
Re: Salida audio en mini PC
El dom, 19 dic 2021 a las 13:42, Camaleón () escribió: > El 2021-12-19 a las 12:07 +0100, Josu Lazkano escribió: > > > Tengo un mini PC (Z83II) corriendo Debian Buster, quiero usarlo para > > reproducir música, lo tengo sin interfaz gráfico, en modo servidor. > > > > Pero no acierto a hacer un test: > > > > $ speaker-test -D default -c 8 > > speaker-test 1.2.4 > > > > Playback device is default > > Stream parameters are 48000Hz, S16_LE, 8 channels > > Using 16 octaves of pink noise > > Rate set to 48000Hz (requested 48000Hz) > > Buffer size range from 96 to 204768 > > Period size range from 48 to 102384 > > Using max buffer size 204768 > > Periods = 4 > > Unable to set hw params for playback: Argumento inválido > > Setting of hwparams failed: Argumento inválido > > (...) > > Dale un vistado a la página de MythTV donde explican bastante bien cómo > probar con esa utilidad y cómo pasarle los parámetros adecuados, aunque > me temo que el éxito de tu misión va a ser una cuestión de prueba-error > :-): > > Using ALSA's speaker-test utility > https://www.mythtv.org/wiki/Using_ALSA%27s_speaker-test_utility > > Saludos, > > -- > Camaleón > > Gracias Camaleón, No doy con la tecla. He probado con mi PC de escritorio y funciona perfecto, suena un ruido por los alatavoces: -- Josu Lazkano
Re: Salida audio en mini PC
El 2021-12-19 a las 12:07 +0100, Josu Lazkano escribió: > Tengo un mini PC (Z83II) corriendo Debian Buster, quiero usarlo para > reproducir música, lo tengo sin interfaz gráfico, en modo servidor. > > Pero no acierto a hacer un test: > > $ speaker-test -D default -c 8 > speaker-test 1.2.4 > > Playback device is default > Stream parameters are 48000Hz, S16_LE, 8 channels > Using 16 octaves of pink noise > Rate set to 48000Hz (requested 48000Hz) > Buffer size range from 96 to 204768 > Period size range from 48 to 102384 > Using max buffer size 204768 > Periods = 4 > Unable to set hw params for playback: Argumento inválido > Setting of hwparams failed: Argumento inválido (...) Dale un vistado a la página de MythTV donde explican bastante bien cómo probar con esa utilidad y cómo pasarle los parámetros adecuados, aunque me temo que el éxito de tu misión va a ser una cuestión de prueba-error :-): Using ALSA's speaker-test utility https://www.mythtv.org/wiki/Using_ALSA%27s_speaker-test_utility Saludos, -- Camaleón
Salida audio en mini PC
Hola a todos, Tengo un mini PC (Z83II) corriendo Debian Buster, quiero usarlo para reproducir música, lo tengo sin interfaz gráfico, en modo servidor. Pero no acierto a hacer un test: $ speaker-test -D default -c 8 speaker-test 1.2.4 Playback device is default Stream parameters are 48000Hz, S16_LE, 8 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 96 to 204768 Period size range from 48 to 102384 Using max buffer size 204768 Periods = 4 Unable to set hw params for playback: Argumento inválido Setting of hwparams failed: Argumento inválido Esta es la info de mi tarjeta: $ aplay -l List of PLAYBACK Hardware Devices card 0: bytcrrt5651 [bytcr-rt5651], device 0: Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: bytcrrt5651 [bytcr-rt5651], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 $ aplay -L null Discard all samples (playback) or generate zero samples (capture) hw:CARD=bytcrrt5651,DEV=0 bytcr-rt5651, Direct hardware device without any conversions hw:CARD=bytcrrt5651,DEV=1 bytcr-rt5651, Direct hardware device without any conversions plughw:CARD=bytcrrt5651,DEV=0 bytcr-rt5651, Hardware device with all software conversions plughw:CARD=bytcrrt5651,DEV=1 bytcr-rt5651, Hardware device with all software conversions default:CARD=bytcrrt5651 bytcr-rt5651, Default Audio Device sysdefault:CARD=bytcrrt5651 bytcr-rt5651, Default Audio Device dmix:CARD=bytcrrt5651,DEV=0 bytcr-rt5651, Direct sample mixing device dmix:CARD=bytcrrt5651,DEV=1 bytcr-rt5651, Direct sample mixing device hw:CARD=Audio,DEV=0 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Direct hardware device without any conversions hw:CARD=Audio,DEV=1 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Direct hardware device without any conversions hw:CARD=Audio,DEV=2 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Direct hardware device without any conversions plughw:CARD=Audio,DEV=0 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Hardware device with all software conversions plughw:CARD=Audio,DEV=1 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Hardware device with all software conversions plughw:CARD=Audio,DEV=2 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Hardware device with all software conversions default:CARD=Audio Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Default Audio Device sysdefault:CARD=Audio Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Default Audio Device hdmi:CARD=Audio,DEV=0 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi HDMI Audio Output hdmi:CARD=Audio,DEV=1 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi HDMI Audio Output hdmi:CARD=Audio,DEV=2 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi HDMI Audio Output dmix:CARD=Audio,DEV=0 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Direct sample mixing device dmix:CARD=Audio,DEV=1 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Direct sample mixing device dmix:CARD=Audio,DEV=2 Intel HDMI/DP LPE Audio, Intel HDMI/DP LPE Audi Direct sample mixing device El sonido lo quiero sacar por el conector jack que dispone el mini PC. ¿Estoy haciendo algo mal? Sin interfaz gráfica no se como poder configurar el sonido. Un saludo y gracias por todo. -- Josu Lazkano
Re: Re: bluetooth audio
Thanks! -- WLM
Re: bluetooth audio
Luis Mochan wrote: > After a recent update/upgrade in debian/bookworm my bluetooth > earphones and my bluetooth earphones stopped working. > I found a solution in the discussion of at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862=no=no=no > > related to bug #997862 which seemed to work for me, that is, > installing a package libspa-0.2-bluetooth. FYI: Same is up on the pulseaudio devel list Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones
bluetooth audio
After a recent update/upgrade in debian/bookworm my bluetooth earphones and my bluetooth earphones stopped working. I found a solution in the discussion of at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862=no=no=no related to bug #997862 which seemed to work for me, that is, installing a package libspa-0.2-bluetooth. I'm not sure what is happening, but I guess it should have been installed automatically if it was required not to break my system (and I guess others). I would like to file a bug report, but I'm not sure the origin is in the wireplumber package (I don't know why it got installed in my system). I will appreciate any advice. Regards, Luis -- o W. Luis Mochán, | tel:(52)(777)329-1734 /<(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `>/ /\ Av. Universidad s/n CP 62210 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16 C2DF 5F0A C52B 791E B9EB
Re: Persistent names for audio devices.
From: David Wright Date: Wed, 29 Sep 2021 22:35:11 -0500 > ... your case is like playing it later by pressing a key. Acknowledged. > As for the gain, you might always start at some default, but it would > surely be useful to be able to adjust it for mumblers and shouters > while it was playing. > > You can of course just play the message with play, but there are > advantages in popping up a player of some sort; for example, you > can jog it backwards if you miss, say, an unclear word, and jog it > forward if you're replaying a somewhat rambling message. Keeping in mind for future use, thanks. > It depends how imaginative you want to be about setting it up. > I'd start with the ~/a42.WAV business. If VoIP calls are being > recorded, I'd use a fixed directory, with files named by the > calls' starting times, like 2021-09-29-123456.wav. That would > give the flexibility to play/skip/delete messages in some sort > of circular fashion with a minimal number of key bindings. For interest, I use the Diamondcard PSTN-VoIP gateway service. https://en.wikipedia.org/wiki/Public_switched_telephone_network https://en.wikipedia.org/wiki/Voice_over_IP https://www.diamondcard.us/ They name a voice message dd.WAV. To my understanding dd is just a serial number. Haven't broached the time notation to them. According to a configuration, messages are sent to my email address. I can change the name of the attachment after receiving. Currently delete the first 8 digits and prefix "a". Hence the example a42.WAV. An old message can be overwritten but it's rare and never been a concern. The bigger chore is deleting old messages. > As for what happens when you press your play key, it would run > a script that would first set the audio controls to a set of > initial values. These have been determined using alsamixer when > setting this up (see top of post), and are set with commands like > > amixer -c "$Card" -- sset "Speaker" 70% on > > where $Card is the appropriate card number. The script would then > run play (which you've cracked) or sox (where "default" doesn't > point to the desired output device) on an appropriate file. Keeping in mind for future. > $ sox -q foo.wav -t alsa plughw:0 (my AiO PC) > $ sox -q foo.wav -t alsa plughw:PCH(the same, using card name) > $ sox -q foo.wav -t alsa plughw:PCH,0 (this AiO's PCH only has one > device: 0) > $ sox -q foo.wav -t alsa plughw:XXX man sox has "-t, --type FILE-TYPE" and cites soxformat(7) which has these examples. " alsa (optional) Advanced Linux Sound Architecture device driver; supports both playing and recording audio. ALSA is only used in Linux-based operating systems, though these often support OSS (see below) as well. Examples: sox infile -t alsa sox infile -t alsa default sox infile -t alsa plughw:0,0 sox -b 16 -t alsa hw:1 outfile See also play(1), rec(1), and sox(1) -d." > I think this thread has been around for a couple of years now. > I assume the penny dropped that names like Live and ICH5 are > the persistent items you were looking for. Acknowledged but using the names properly is non-trivial, for me at least. A self-inflicted difficulty was using play rather than sox. According to the manual, play doesn't have outfile. Hence the monkeying with shell and environment variables. Better to use sox and specify outfile directly. I'll hypothesize that alsa devices aren't represented in /dev/. According to https://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture ALSA was initially released in 1998. According to https://en.wikipedia.org/wiki/Udev udev was initially released in 2003. In Debian releases, udev isn't applied to alsa devices. The official manuals have plenty of dense information but a wiki.debian.org/sox could explain elementary concepts and provide useful examples. Thx,... P. -- 48.7693 N 123.3053 W mobile: +1 778 951 5147 VoIP: +1 604 670 0140
Re: silence audio on locked screen?
On Thu, Sep 30, 2021, 8:03 AM wrote: > On Wednesday, September 29, 2021 11:34:42 PM David Wright wrote: > > On Wed 29 Sep 2021 at 16:48:11 (+1300), Richard Hector wrote: > > > As I say, I consider this to be a security flaw - people can hear > > > something of what my computer's doing when I'm not there and it's > > > supposedly locked. > > > > > > Do others agree with that? > > > > No (ie I concur with Dan). > > It would have been helpful (to me, at least) if you had quoted Dan, which > I am > now doing: > > > It can be a security issue, but it can also be desired > behavior. I have an old laptop in my living room which has the > sole purpose of being connected to my stereo to play music. I > would be rather upset if it were to pause whenever the > screensaver kicks in. > > So I would class this as a desirable configurable element. > > +1 > > Insofar as it is apparently not a configurable element, I would consider > it a > security issue at least, and would (if I were the OP) file a bug or an RFP > (if > that is the right acronym (Request For ) > I also often play Classical Music (i.e. Symphonies and Operas), and also prefer to "start it" interactively (I use the Command Line "play" Command, found in the sox Package), but then let it fill my alarm, while the Power Save actions (Display to Sleep, and system Locked, in case I have visitors). And then, when the Piece ends, I unlock the Display and, perhaps play something else. So this *has* to be Configurable. Kenneth Parker
Re: silence audio on locked screen?
On Wednesday, September 29, 2021 11:34:42 PM David Wright wrote: > On Wed 29 Sep 2021 at 16:48:11 (+1300), Richard Hector wrote: > > As I say, I consider this to be a security flaw - people can hear > > something of what my computer's doing when I'm not there and it's > > supposedly locked. > > > > Do others agree with that? > > No (ie I concur with Dan). It would have been helpful (to me, at least) if you had quoted Dan, which I am now doing: It can be a security issue, but it can also be desired behavior. I have an old laptop in my living room which has the sole purpose of being connected to my stereo to play music. I would be rather upset if it were to pause whenever the screensaver kicks in. So I would class this as a desirable configurable element. Insofar as it is apparently not a configurable element, I would consider it a security issue at least, and would (if I were the OP) file a bug or an RFP (if that is the right acronym (Request For )
Re: Persistent names for audio devices.
On Wed 29 Sep 2021 at 12:25:49 (-0700), pe...@easthope.ca wrote:
> From: David Wright
> Date: Tue, 28 Sep 2021 18:31:34 -0500
> > No, you'd use alsamixer where you were taking an active rôle during
> > record/playback, or for discovering, inspecting and setting up a
> > system. Typically, you'd play "an audio message", or anything else,
> > with some sort of application, unless it was a disembodied
> > notification, say.
> >
> > Some applications include volume/balance controls and so on; others
> > don't. I have keys set up for adjusting the volume on the various
> > controls, using the multimedia keys XF86Audio{Mute,LowerVolume,RaiseVolume}
> > (F1/F2/F3 where not present), with Ctrl/Alt/Shift to select between
> > Master/Speakers/Headphones/PCM.
>
> Understood, but to listen to an audio message from VoIP (not opera) a
> simple command should suffice. (play ~/a42.WAV) Speakers rather than
> headphones for a voice message. I'd rather not adjust volume except
> maybe "play ~/a42.WAV gain 1". A typical message is "Please call J.
> Doe." In a worst case I might shut off the RCA AM radio made in 1960
> to hear the message better. =8~) Seems we're at crossed purposes
> here.
Not really. A disembodied notification is like an answerphone that
plays a message out loud during the call, whereas your case is like
playing it later by pressing a key.
As for the gain, you might always start at some default, but it would
surely be useful to be able to adjust it for mumblers and shouters
while it was playing.
You can of course just play the message with play, but there are
advantages in popping up a player of some sort; for example, you
can jog it backwards if you miss, say, an unclear word, and jog it
forward if you're replaying a somewhat rambling message.
> > How otherwise would you make explicit what you're happy to use
> > implicitly?
>
> No offense but isn't that analogous to saying to a ten year old
> "Johnny, please eat your lunch with your mouth." =8~)
>
> A default which isn't unique is a bad default. If it is unique,
> there's nothing to disambiguate. Crossed purposes again?
More like "Breathe through your nose!"
> > (When I write a script, I try to be as explicit as
> > possible, avoiding short-cuts, abbreviations, assumptions, etc.)
>
> Absolutely good policy. I try to follow it also but tend to fail. =8~)
>
> > sox /home/peter/a42.WAV -t alsa default
>
> Good.
>
> The machine here has sound hardware on the system board. Also it can
> have a PCI sound card. Sound devices reported here.
> https://lists.debian.org/debian-user/2021/07/msg01272.html
>
> Assume speakers are plugged to output on the system board; headphones
> plugged to the PCI card. A Linphone ring and a voice message (play
> ~/a42.WAV) should always go to the speakers. VoIP I/O (a
> conversation) and ring can be configured in Linphone; no problem.
> "play ~/a42.WAV" delivering to the headphones in random cases is an
> unacceptable failure. How would you make it work without frequent
> configuration adjustments?
It depends how imaginative you want to be about setting it up.
I'd start with the ~/a42.WAV business. If VoIP calls are being
recorded, I'd use a fixed directory, with files named by the
calls' starting times, like 2021-09-29-123456.wav. That would
give the flexibility to play/skip/delete messages in some sort
of circular fashion with a minimal number of key bindings.
As for what happens when you press your play key, it would run
a script that would first set the audio controls to a set of
initial values. These have been determined using alsamixer when
setting this up (see top of post), and are set with commands like
amixer -c "$Card" -- sset "Speaker" 70% on
where $Card is the appropriate card number. The script would then
run play (which you've cracked) or sox (where "default" doesn't
point to the desired output device) on an appropriate file.
Examples of the latter would be:
$ sox -q foo.wav -t alsa plughw:0 (my AiO PC)
$ sox -q foo.wav -t alsa plughw:PCH(the same, using card name)
$ sox -q foo.wav -t alsa plughw:PCH,0 (this AiO's PCH only has one
device: 0)
$ sox -q foo.wav -t alsa plughw:XXX
XXX could be any of Live, ICH5, Set (headphones), but not
U0x46d0x807 I think, as that looks like only an input.
Alsamixer would help you determine which is which, if you don't
already know. (I thought you had already determined this in, eg,
https://lists.debian.org/debian-user/2021/08/msg00133.html
but it's difficult to follow both the threading and which
commands make noises from which actual physical things).
I think this thread has been around for a couple of years now.
I assume the penny dropped that names like Live and ICH5 are
the persistent items you were looking for.
Disclaimers: I don't know anything about the hardware you're using,
and I've ignored your pulseaudio because I don't use it.
Cheers,
David.
Re: silence audio on locked screen?
On Wed 29 Sep 2021 at 16:48:11 (+1300), Richard Hector wrote: > As I say, I consider this to be a security flaw - people can hear > something of what my computer's doing when I'm not there and it's > supposedly locked. > > Do others agree with that? No (ie I concur with Dan). > Also, I don't know how much of the screen locking function is shared > between the many tools that are available for this purpose. Ideally, > this problem (if it's a problem) should be fixed in all such tools. > > Does it sound reasonable then to submit a bug report to light-locker, > with the suggestion that the maintainers contact the maintainers of > similar/related packages as they see fit? It might be worth reading around dbus: there may be hooks for running scripts whenever locking changes the state, however caused. This would probably only cover X11, not console blanking or monitors' green behaviour. And for vlock (deliberate locking), a script to mute/restore. Cheers, David.
Re: Persistent names for audio devices.
From: David Wright Date: Tue, 28 Sep 2021 18:31:34 -0500 > sox /home/peter/a42.WAV -t alsa default OK, good. I can replace the PCI sound card. Then that or the system board hardware will be the default. How can a non-default device be specified? Conceptually, sox /home/peter/a42.WAV -t alsa non-default Devices were reported here. https://lists.debian.org/debian-user/2021/07/msg01272.html Thx, ... P. -- 48.7693 N 123.3053 W mobile: +1 778 951 5147 VoIP: +1 604 670 0140
Re: Persistent names for audio devices.
Trimmed the reference list. =8~)
From: David Wright
Date: Tue, 28 Sep 2021 18:31:34 -0500
> No, you'd use alsamixer where you were taking an active rôle during
> record/playback, or for discovering, inspecting and setting up a
> system. Typically, you'd play "an audio message", or anything else,
> with some sort of application, unless it was a disembodied
> notification, say.
>
> Some applications include volume/balance controls and so on; others
> don't. I have keys set up for adjusting the volume on the various
> controls, using the multimedia keys XF86Audio{Mute,LowerVolume,RaiseVolume}
> (F1/F2/F3 where not present), with Ctrl/Alt/Shift to select between
> Master/Speakers/Headphones/PCM.
Understood, but to listen to an audio message from VoIP (not opera) a
simple command should suffice. (play ~/a42.WAV) Speakers rather than
headphones for a voice message. I'd rather not adjust volume except
maybe "play ~/a42.WAV gain 1". A typical message is "Please call J.
Doe." In a worst case I might shut off the RCA AM radio made in 1960
to hear the message better. =8~) Seems we're at crossed purposes
here.
> How otherwise would you make explicit what you're happy to use
> implicitly?
No offense but isn't that analogous to saying to a ten year old
"Johnny, please eat your lunch with your mouth." =8~)
A default which isn't unique is a bad default. If it is unique,
there's nothing to disambiguate. Crossed purposes again?
> (When I write a script, I try to be as explicit as
> possible, avoiding short-cuts, abbreviations, assumptions, etc.)
Absolutely good policy. I try to follow it also but tend to fail. =8~)
> sox /home/peter/a42.WAV -t alsa default
Good.
The machine here has sound hardware on the system board. Also it can
have a PCI sound card. Sound devices reported here.
https://lists.debian.org/debian-user/2021/07/msg01272.html
Assume speakers are plugged to output on the system board; headphones
plugged to the PCI card. A Linphone ring and a voice message (play
~/a42.WAV) should always go to the speakers. VoIP I/O (a
conversation) and ring can be configured in Linphone; no problem.
"play ~/a42.WAV" delivering to the headphones in random cases is an
unacceptable failure. How would you make it work without frequent
configuration adjustments?
Thanks,... P.
--
48.7693 N 123.3053 W
mobile: +1 778 951 5147
VoIP: +1 604 670 0140
Re: usb audio interface recommendation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 ‐‐‐ Original Message ‐‐‐ On Wednesday, September 29, 2021 1:20 AM, Russell L. Harris wrote: > On Wed, Sep 29, 2021 at 03:12:06AM +, ghe2001 wrote: > > > I started to by a Scarlett, my dealer insisted on > selling me a MOTU M2 because MOTU claims "class compatibility" (as it > turns out, for Macintosh only). The build quality of the MOTU is > impressive, but it has problems (noise) on every Linux machine I have > tried with it. So tomorrow the MOTU gets returned for a Scarlett. You'll be just ever so much happier. 1) It works flawlessly with Debian (Audacity, anyway) 2) I heard (not at all verified) that Rupert Neve designed the mic amps -- Glenn English -BEGIN PGP SIGNATURE- Version: ProtonMail wsBzBAEBCAAGBQJhVMdxACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG MYKsjDIQiwf+K3I5If7MPfXk+AoDNfJ2C2RLtoALrI3Gxga0vrwnveXbKw7L S7sGcE9zf/yzqB3/6B9uo5oj8J/basldCafOurr391AkyVaGDs+fhn/Ye90y anTGrrGIiGLliZZ2HRbfn78A4GoZk0cQ//8gBgDRbFAy7AxavEPsK24MId6/ csQ57qG/XlWyTwYBRr4Fu8g5z379gkaIV+4xSHLLY+uJyqJk4JdMpDcw4KUa iBHTvzmzZi11m8csqMfCs6/GOTQ+cnbj2AHMFVdLI8GvZRp6UMkd5uKPgxjb xtvEAYLaR6V4bXAl21vPOIn/zdOqaHYGH2sGvT6BLtnvh0rZevwITA== =BHVQ -END PGP SIGNATURE-
