#alsa — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #alsa, aggregated by home.social.
-
No sound on reboot tablet #sound #pulseaudio #alsa #tablet
-
Lenovo IdeaPad Slim 5 15ARP10 (83J3) - No speaker sound with Conexant SN6140 on Ubuntu 26.04 #sound #pulseaudio #lenovo #alsa
-
🎙️ Spent ~35 hours reverse-engineering the Apogee ONEv2 USB audio interface on Linux:
• 2 kernel patches to sound/usb/
• Vendor init sequence found via Wireshark on macOS
• Hardware watchdog keepalive daemon
• ALSA sees Playback and Capture PCMs
• Playback PCM opens — stable streaming not yet crackedAnyone want to pick this up?
https://github.com/stevebrodie/apogee-one2-linux
#Linux #LinuxAudio #ALSA #Apogee #KernelHacking #ReverseEngineering #OpenSource -
ich möchte Schallplatten per Receiver Bluetooth Audiostream auf meinen Linux-Mint-Rechner digitalisieren (Audacity).
Übertragung BT-Box: OK
BT-Verbindung Receiver to Linux: OK
-wireplumber: BT (codec SBC-XQ)
-Audio-Gateway (A2DP-Quelle und HSP/HFP AG)
es hat schon einmal funktioniert und ich habe Platten digitalisiert
hab mit aber das HowTo nicht aufgeschrieben..... :(
für eine Anleitung wäre ich sehr dankbar :) -
Mic works on Windows but not in Ubuntu - ASUS Laptop #sound #alsa #microphone
-
MSI Thin A15 B7UC internal microphone is not working on Ubuntu 24.04 #sound #pulseaudio #2404 #alsa #microphone
-
Fedi, I'm at a total loss on how to sort this one out. I've got an Elgato wave: 3 that worked great for 18 months and one day after updates it stopped registering input.
Its odd, it shows up normally in ALSA and pipewire. Volume and mute status work in software and hardware and accurately update when one is changed.
It just won't let me talk into it 😥.
#alsa #elgato #linuxaudio #Linux #pipewire #wave3 #troubleshooting
-
У меня нет звука, но я должен слышать: история одной регрессии ядра
Что делать, если после очередного обновления Linux на старом ноутбуке намертво отвалился звук, а в логах висит зловещее CORB reset timeout и 0xFFFF ? Переустановка аудио-серверов не поможет, параметры загрузчика GRUB система упорно игнорирует, а LTS-ядро больше не гарантирует стабильности. В этой статье разбираем, как спуститься в логи dmesg , понять, почему устройство «задыхается» на шине PCI, и заставить ядро заново проинициализировать аудиокарту «на горячую» с помощью sysfs и systemd. Найти звук
https://habr.com/ru/articles/1022090/
#linux #dmesg #pci #systemd #troubleshooting #sndhdaintel #kernel #alsa #старое_железо #archlinux
-
A couple of my installation DVDs containing Open Source distributions from the CD and DVD era of storage.
#Linux #distro #distribution #Xorg #Legacy #programming #ALSA #OSS #technology #OpenSource #POSIX
-
Habs wieder hinbekommen. Aber nur, weil ich das Bild im #Sendegate gefunden habe. So funktioniert wenigstens wieder alles. Ich würde dieses Bild nur gern verstehen. #vocaster #ALSA #Audiorouting
-
Hat jemand das #Vocaster Pro 2 unter #Linux im Betrieb und kennt sich mit dem #Audiorouting mit #ALSA Scarlett2 Control Center aus? welcher Ein-/Ausgang ist denn was? Tipps oder Dokulinks welcome.
-
@vermaden @omar
I always use alsamixer -c0 up to cxx from the OSS ALSA period since it's ncurses based & faster than GUI programs.Many things in Linux were changed for good reason, but some are questionable. I don't use systemD init is easier to maintain. It aint broke so KISS
Pipewire is fun to add FX in my signal chain to my DAW, but for serious work I have a physical FX rack.
I love pavucontrolI understand why Wayland was made and only have it on my SBC Raspberry Pi5
#Ifconfig #ip #init #systemD #Xorg #Wayland #programming #pipewire #ALSA #OSS
-
Hello I need some help about connecting a #RolandFP-90X -> bluetooth midi -> Ubuntu.
aconnect shows
client 128: 'FP-90X MIDI'
0 'FP-90X MIDI Bluetooth'aseqdump -p 128:0 do not shows any midi event arriving to the computer..
It seems that the keyboard is transmitting throught chanel 1..
-
- The monolithic way. By using one application, like a DAW, you only have to fire up one application that sets up your music making environment for you. The advantage is that you don't have to start any other application like #JACK and/or a session manager, especially when you use plain #ALSA as the audio backend. The disadvantage then of course is that any other application won't be able to play or record audio anymore.
/2
-
ALSA are drivers to talk to hardware - 90% of audio interfaces (whatever enables you to plug an audio cable into your computer) use ALSA. (exceptions are FireWire interfaces and some other). if a new audio interface is 'incompatible' with Linux, it means it doesn't have an ALSA driver (aka kernel module) - yet.
on top of #ALSA drivers (so, using those drivers) there were two systems in last decade:
PulseAudio - designed to be invisible way to handle all desktop audio - mutiple application would be able to send sound to your audio output (to ALSA). not capable of low-latency audio needed for professional music/audio work. if you had multiple outputs (ALSA), like HDMI or analog out, you could choose one of those for a particular application (like web browser), and similarly for inputs (microphones etc)
JACK audio server - low latency, designed for pro audio work, allowed completely free patching between multiple applications (ins and outs), standalone audio plugins, and audio interface(s) - essentially infinite patchbay among "everything". all decent audio apps work with JACK, but not 'desktop' apps, something like web browsers for example.
at first #JACK and #PulseAudio were incompatible - you were supposed to suspend (or uninstall) PulseAudio in order to use JACK and vice-versa. they fought for access to ALSA. Later on, bridges were developed so you could send sound from web browser (that was using PulseAudio) to your DAW (that was using JACK) or output from DAW to OBS or Zoom...
audio apps needed code to talk to any of these two systems. they needed to be compatible with JACK, or/and PulseAudio.
last few years PipeWire ( @pipewire ) appeared to replace JACK and Pulse at the same time and be very transparent and invisible but still configurable if you so needed. Like JACK and PulseAudio it also sits on top of ALSA drivers, but "acts" like it's Pulse and/or JACK. the idea seems to be that replacing JACK and PulseAudio is easy if nothing needs to be changed in those apps. so applications think they are sending audio to JACK but are actually sending it to PipeWire 'in disguise'. it's extremely good at pretending (tech speak: it uses same API). So, if you are using (running) PipeWire, you cannot use (run) JACK or/and PulseAudio.
PipeWire is amazing solution. it also automatically discoveres new audio devices like usb headphones, or Bluetooth speakers and makes the default audio output. you can unplug your audio devices and apps won't notice. It's still a bit rough on the edges, but it's getting better and better.
MIDI? well, it's complicated: there's ALSA MIDI and JACK MIDI. Just two different systems trying to do patching between apps. So some apps will show one, and some the other. I think PipeWire tries to make this irrelevant by bridging these two, but it's not always successful. It should be accessible in PipeWire patchbay app like 'qpwgraph'.
Sorry if that's too long, but I hope it is understandable enough. And sorry for so many edits.
-
i finally got around to enabling 4ch mode on my motherboard sound card and attaching that extra pair of speakers for REAR left and REAR right. mwahaha!! some utilities I needed include: alsa-utils alsa-tools. this script was useful too. https://github.com/hello2himel/linux-audio-fix
I had just fixed an old pair of Altec Lansing ACS91 speakers and thought that I could use them as Rear speakers and what do you know, they actually sound really nice.
-
Was meinst du mit "Lautsprecher"-Treiber? Ausgabe über die eingebauten Lautsprecher ging nicht, über HDMI und Bluetooth schon? Hatte zuletzt ein fieses Erlebnis mit @lesensfreude|s gelinuxtem #Chromebook und #Alsa in dieser Richtung.
-
-
/* only one ? nonsense! */
https://elixir.bootlin.com/linux/v6.16/source/sound/usb/mixer.c#L2755
-
#CanfrancEstación
Now to my big surprise there are - at least at the moment, which is peak summer season - three departures a day of the "Canfranc Express" operated/commercialised by #Alsa with historic cars from AZAFT | ASOCIACIÓN ZARAGOZANA DE AMIGOS DEL FERROCARRIL Y TRANVÍAS https://azaft.org (an expert source tells me).#Canfranc #Transpyrénéen #Pyrénées #Somport #TranspyrénéenOccidental
-
#PipeWire 1.4.7 has been released (#PulseAudio / #JACK / #JACKAudio / #ALSA / #AdvancedLinuxSoundArchitecture / #GStreamer / #SoundServer / #SoundSystem / #AudioLinux / #VideoServer / #VideoSystem / #VideoLinux / #MultimediaFramework / #FreeDesktop / #RedHat) https://pipewire.org/
-
For a while now I haven't been able to access both mic and earphones of this headset with the plug/unplug/replug dance.
HOWEVER, I've noticed that both are correctly detected by #ALSA (alsamixer shows both, at least), so this appears to be a problem further down the line (either in #PulseAudio or #Pipewire).
I don't suppose anyone has an idea how to debug (or even better solve) this? Google isn't being helpful.
-
Daily driving a Pixel 3a while on a three week holiday wrap-up
https://my-place.social/display/e599373b-7168-6c62-c6a3-b86258671760
-
Three ways to play your audio file in reverse order:
1) sox <audiofile> -t alsa default reverse
2) ffmpeg -i <audiofile> -af areverse -f alsa default
3) mpv --play-direction=backward <audiofile> -
Solved my #Alsa #BT problem using #sox:
Created a loopback device in alsa and then use sox to record and play back to BT. sox doesn't care about overruns/underruns.
```
AUDIODEV="hw:Loopback,1,0" \
rec -q -b 16 -r 48000 -L -e signed-integer -p | \
AUDIODEV="bluealsa:DEV=XX:XX:XX:XX:XX:X" \
play -q -b 16 -r 48000 -L -e signed-integer -p
```Still needs some love with sometimes bad BT connection.
-
When building alsa-utils with a custom toolchain + sysroot, I get this error:
libtool: error: cannot find the library '/usr/lib/libasound.la' or unhandled argument '/usr/lib/libasound.la'
However, the file does exist inside of the sysroot, and configure claims to use the sysroot that the compiler specifies.
How do I solve this?
-
I learnt something important about Linux audio last night.
I noticed that I had no sound in X-Plane 12 (a flight simulator) while also being in a Discord call in Firefox. Apparently, certain FMOD applications check if PulseAudio is installed and fall back to ALSA if it isn't. Now, I have PipeWire installed to fix the mess that is Linux audio once and for all. So TECHNICALLY PulseAudio is not installed. And that's exactly what X-Plane detected, which then tried to gain complete control over the sound hardware through ALSA, which it couldn't.
The "fix" was to symlink `/bin/pulseaudio` to `/bin/true` to make it look like PulseAudio is available which tricked X-Plane into going through PulseAudio (and therefore through PipeWire) instead.
That was one of the weirdest problems I've ever encountered.
#linux #audio #xplane #xplane12 #discord #firefox #alsa #pulseaudio #pipewire #fmod #flightsim
