#alsa — Public Fediverse posts

First interesting Linux hardware issue on Fedora 44 Workstation. 😄

My Lenovo IdeaPad Slim 5 16AKP10 (83HY) detects its internal mic, but recordings are silent except for clicks at start/stop.

ALSA discussion for the exact model:
https://github.com/alsa-project/alsa-ucm-conf/pull/792

I only understand the low-level hardware/kernel side very roughly, so I’m not confident judging whether to wait for a fix, report the model upstream, or try a local workaround. 😅

#fedora #linux #alsa

First interesting Linux hardware issue on Fedora 44 Workstation. 😄

My Lenovo IdeaPad Slim 5 16AKP10 (83HY) detects its internal mic, but recordings are silent except for clicks at start/stop.

ALSA discussion for the exact model:
https://github.com/alsa-project/alsa-ucm-conf/pull/792

I only understand the low-level hardware/kernel side very roughly, so I’m not confident judging whether to wait for a fix, report the model upstream, or try a local workaround. 😅

#fedora #linux #alsa

Fallout - New California released

"It just works"
Seriously, I just installed New Vegas in #Lutris, and ran the installer in the #WINE prefix.

Tip because I've been having this issue with Fallout: London as well with no success in finding anything about it on the net: setting audio driver to #ALSA in Lutris fixed the deafening buzzing sound that happens with the opening cutscene. (I don't have ALSA installed, so it must install it to the WINE prefix). Fixed the same issue with Fallout London as well. Been trying to fix this for a while now, and now I can actually play!

#FalloutNewCalifornia #FalloutNewVegas #FalloutLondon #MO2 #LinuxGaming #GOG

[Перевод] Как я добавлял gapless playback

Некоторые альбомы должны звучать как один длинный трек. Рассказываю, как это устроено в Kalinka Player.

https://habr.com/ru/articles/1063126/

#c++ #alsa #linux #raspberry_pi #аудио #gapless #бесшовное_воспроизведение #open_source

Как я три года пилю свой музыкальный сервер: часть вторая. Архитектура Kalinka и её место среди музыкальных систем

Как устроен KalinkaPlayer: модульный бэкенд, нативный аудиоплеер, пайплайн метаданных и мобильное управление в одном проекте. Изучить архитектуру

https://habr.com/ru/articles/1061144/

#Linux #Raspberry_Pi #Python #C++ #FastAPI #ALSA #open_source #selfhosted #звук_и_музыка #аудио

Only Open Source Operating Systems give me this detailed level of error output

`$ tail -f /var/log/syslog`

```
2026-07-16T12:09:30.085095-03:00 krasiwati pulseaudio[3062]: [alsa-sink-USB Audio] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
2026-07-16T12:09:30.085110-03:00 krasiwati pulseaudio[3062]: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
2026-07-16T12:09:30.085119-03:00 krasiwati pulseaudio[3062]: [alsa-sink-USB Audio] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
```

#syslog #log #output #errors #alsa #details #programming #great #ease

Only Open Source Operating Systems give me this detailed level of error output

`$ tail -f /var/log/syslog`

```
2026-07-16T12:09:30.085095-03:00 krasiwati pulseaudio[3062]: [alsa-sink-USB Audio] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
2026-07-16T12:09:30.085110-03:00 krasiwati pulseaudio[3062]: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
2026-07-16T12:09:30.085119-03:00 krasiwati pulseaudio[3062]: [alsa-sink-USB Audio] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
```

#syslog #log #output #errors #alsa #details #programming #great #ease

Рояль на даче: использую ПЛК на Linux как real-time-синтезатор фортепиано

Я играю на пианино с детства. Классика, саундтреки, импровизации – репертуар меняется, но привычка спонтанно сесть за клавиши остается. Лучший способ отдохнуть, переключить голову после сложной работы или вообще просто так! На моей домашней рабочей станции установлен профессиональный синтезатор фортепиано Pianoteq от Modartt — он полностью меня устраивает: не только реалистичностью звучания, но и возможностью экспериментировать со звуком. Достаточно давно я собрал умную дачу на базе ПЛК под Linux и даже написал об этом статью . Контроллер исправно управляет освещением, водоснабжением и отоплением. Потом я прочитал статью о запуске Doom на этом контроллере и задумался: смогу ли приспособить его под свое хобби? Получится ли играть на даче не хуже, чем дома? Doom — задача хоть и культовая, но все-таки относительно простая. А справится ли контроллер с real-time-синтезом аудио? Здесь недостаточно просто воспроизводить заранее записанный звук — нужно в реальном времени рассчитывать его по физической модели инструмента. Сборки Pianoteq существуют под разные архитектуры, но чаще всего его используют на студийных Mac и рабочих станциях — на сцене, в студиях и при работе над киномузыкой. Итак, для своего эксперимента я привез на дачу USB-ЦАП, MIDI-клавиатуру с педалью и подключил их к контроллеру…

https://habr.com/ru/companies/wirenboard/articles/1047860/

#Wiren_Board #Pianoteq #Linux #MIDI #ALSA #USB_DAC #Realtime_аудио #ARM_Linux #Пересборка_ядра #Синтез_звука

Poz ya está en pruebas el paquete del "#ALSA Use Case Manager" con el parche para revertir (regresión de esas) las funciones avanzadas del #DualSense en #Archlinux. ¡Grande el David!

Poz ya está en pruebas el paquete del "#ALSA Use Case Manager" con el parche para revertir (regresión de esas) las funciones avanzadas del #DualSense en #Archlinux. ¡Grande el David!

#Alsa-#Hundewelt - 14% #Gutscheincode #Coupon | MKW: -
https://www.preishals.de/gutscheine/alsa-hundewelt/

#Alsa-#Hundewelt - 18% #Gutscheincode #Rabattcode #Coupon
https://www.preishals.de/gutscheine/alsa-hundewelt/

OSS alsa fun

I typed in alsamixer -c2because one of my audio interfaces suddenly had only output on one of the two channels.

As a rule, in Linux and any other Open Source OS, you don't reboot like a moronic end user, to fix a problem:

• troubleshoot the problem
• Isolate the problem
• when hardware relation is established
• check which kernel module needs to be flused
• rmmod mod_name
• insmod mod_name
• read the man-page for the kernel_mod

I executed the above steps (stepping over the kernel mod slush) and came in the alsamixer to see that there finally is a massive update to the alsamixer for this interface

What I needed to do is pull one fader up in the mixer and get the audio balance again. As a bonus I can now balance the output of the device in alsamixer, instead of on the rack-mount instrument mixer in my effects rack.

sources:

man alsamixer
man rmmod
man insmod

#kernel #module #ALSA #OSS #alsamixer #rmmod #insmod

OSS alsa fun

I typed in alsamixer -c2because one of my audio interfaces suddenly had only output on one of the two channels.

As a rule, in Linux and any other Open Source OS, you don't reboot like a moronic end user, to fix a problem:

• troubleshoot the problem
• Isolate the problem
• when hardware relation is established
• check which kernel module needs to be flused
• rmmod mod_name
• insmod mod_name
• read the man-page for the kernel_mod

I executed the above steps (stepping over the kernel mod slush) and came in the alsamixer to see that there finally is a massive update to the alsamixer for this interface

What I needed to do is pull one fader up in the mixer and get the audio balance again. As a bonus I can now balance the output of the device in alsamixer, instead of on the rack-mount instrument mixer in my effects rack.

sources:

man alsamixer
man rmmod
man insmod

#kernel #module #ALSA #OSS #alsamixer #rmmod #insmod

This is how the Linux kernel mailing list looks like from a browser.

From a mobile browser it looks less polished.

It's a *mailing list* you should read it from a email client, not a memory hungry browser, but if you are in the links browser it will look fine. Links is light ;)

The message is important; if you keep up with kernel development on the Linux side section audio drivers, you may find it interesting

https://lkml.org/lkml/2026/5/18/133

#Programming #Linux #kernel #module #Audio #ALSA #c #C_Lang #development #coding

This is how the Linux kernel mailing list looks like from a browser.

From a mobile browser it looks less polished.

It's a *mailing list* you should read it from a email client, not a memory hungry browser, but if you are in the links browser it will look fine. Links is light ;)

The message is important; if you keep up with kernel development on the Linux side section audio drivers, you may find it interesting

https://lkml.org/lkml/2026/5/18/133

#Programming #Linux #kernel #module #Audio #ALSA #c #C_Lang #development #coding

#Alsa-#Hundewelt - 20 € #Gutscheincode #Coupon #Osterfest | MKW: 100 €
https://www.preishals.de/gutscheine/alsa-hundewelt/

🎙️ 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 cracked

Anyone want to pick this up?
https://github.com/stevebrodie/apogee-one2-linux
#Linux #LinuxAudio #ALSA #Apogee #KernelHacking #ReverseEngineering #OpenSource​​​​​​​​​​​​​​​​

🎙️ 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 cracked

Anyone want to pick this up?
https://github.com/stevebrodie/apogee-one2-linux
#Linux #LinuxAudio #ALSA #Apogee #KernelHacking #ReverseEngineering #OpenSource​​​​​​​​​​​​​​​​

#FediHilfe #linux #audio

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 :)

#pipewire #alsa #blueman #bluetooth #audacity #qpwgraph

#FediHilfe #linux #audio

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 :)

#pipewire #alsa #blueman #bluetooth #audacity #qpwgraph

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

#Alsa-#Hundewelt - 12% #Gutscheincode #Coupon #Osterfest | MKW: 20 €
https://www.preishals.de/gutscheine/alsa-hundewelt/

#Alsa-#Hundewelt - 18% #Gutscheincode #Rabattcode #Coupon
https://www.preishals.de/gutscheine/alsa-hundewelt/

Les treballadores d’ALSA a la Fonteta, organitzades en la Confederació General del Treball (CGT), convoquen vaga els dies 3,4 i 5 de març davant la reiteració en els errors i retallades en les nòmines https://www.cgtvalencia.org/vaga-en-la-plantilla-de-ferroviaris-dalsa-en-lestacio-classificatoria-font-sant-lluis-de-valencia/ #alsa #CGT #cgtvalencia #valencia #huelga #buses #transporte

I’ve been spending some laptop time in one of our louder studios of late. Since switching to Linux for philosophical reasons, the challenge emerged to integrate this sometimes under-supported operating system into the workflow expected of an audio professional. This article will be updated on the go as I plough through the pitfalls, while sharing tips and workarounds I’ve discovered along the way to make the music flow. It will evolve as I learn.

Although many Linux distributions exist, some specialised for creatives, my explorations have been using stock Linux Mint 22.3. Often using base packages provided by the Software Manager for maintenance and stability, rather than the latest and greatest. With that in mind, the journey can begin.

Caution: The command line lurks ahead…

Not only Pulses and Pipes, but ALSA

Although the “Plug and Play”-ability of Linux hardware has improved dramatically over the years, use of audio hardware demands a deeper understanding of the different layers that come together to control sound output.

At the base level, there is ALSA, the Advanced Linux Sound Architecture. This is a kernel-level device layer that connects to the hardware directly. Offering the basics for sound capture and playback, but nothing much more than that. Software-based Virtual Devices can also be configured at this level, which I’ll touch on later.

Historically, PulseAudio was implemented as a user-level layer on top of ALSA, allowing the mixing of multiple audio streams. Individual volume levels could be set for each application, and sound routing could also be switched on the fly, such as when headphones were plugged in. Applications would use the PulseAudio API to connect to this sound server instead of hitting the hardware directly, with the complexities abstracted away.

Another audio server, JACK (JACK Audio Connection Kit. Gotta love a recursive acronym!) was used at a professional level, also abstracting ALSA. Designed for low-latency studio applications, it would allow for accurate synchronisation and explicit audio routing. However, this server was incompatible with PulseAudio, as only one or the other could connect to ALSA at a time. Systems running both required a lot of workarounds and bridging.

PipeWire is a modern evolution and replacement of both PulseAudio and JACK, revised to handle the needs of both audio and video processing as well as MIDI transfer. Able to emulate both the API and toolset of its predecessors, this layer is low-latency by design.

Modern audio implementations mostly use PipeWire, although some applications may hit ALSA directly. A few caveats remain when switching between the two.

The DAW is the Law

Although I’ve limped along with GarageBand on other devices, the job demands a Digital Audio Workstation (DAW) with a bit more control.

Many professional options are available, with Ableton Live, Avid Pro Tools, and Apple Logic Pro coming highly regarded for Windows and MacOS. Native Linux options are somewhat more limited, but Reaper offers a version of their. All these options come with a price-tag, often shifting to a subscription licence instead of owning outright.

Ever the zealot, I went with Ardour – which has the advantage of being free-as-in-speech Open Source software. Donations to the developers are welcome for a ready-to-run supported binary version, but the source code is available for anyone who wishes to build their own.

As for me, I grabbed the pre-built version 8.4 package from the Linux Mint Software Manager. It’s a few versions behind, but sufficient to the task.

sudo apt install ardour

(Using a DAW effectively is beyond the scope of this article, mostly because I’m still learning the intricacies itself!)

One thing I did notice when connecting straight to ALSA is my Dock audio only permits a 48 kHz sample rate, which made importing CD-rate 44.1 kHz stems (individual audio tracks) a little troublesome, with clicks and pops aplenty. As expected, ALSA also takes sole control of the device, removing it from the available list in Sound Settings.

Switching to the PulseAudio system (running through Pipewire as explained earlier) enabled sample rates from 8 kHz to 192 kHz through the ‘Default Playback’ device, which outputted onto the Laptop’s speakers instead of through the dock. Switching the default through the Sound Settings panel soon got things coming out of the expected speakers at the right rate, without stealing control.

Pull the Plug-in

Ardour comes with a bevy of workable LV2 ACE plugins to handle the basics of Compression, Gating, et al. But most of these rely a little too much on sliders and numbers than the familiar knobs and blinkies of a real mixing desk. Downloading the pre-built binary improves the look, but nonetheless the effects chain is easy to navigate, allowing drag and drop visualisation of where everything clicks together.

It is also compatible with industry-standard plugin formats such as Virtual Studio Technology (VST), offering a more familiar interface, but here is where Linux users hit a snag. The underlying format of these plugins has been designed for Windows, and thus incompatible.

Undismayed, I found yabridge able to convert the plugins so that they work just fine, with full custom interface intact. Utilising the Windows compatibility layer offered by Wine, yabridge relinks the VSTs to the equivalent native libraries, allowing them to be added to Ardour. The Software Manager has an older version of wine, but again it does the job:

sudo apt install wine-installer

Once wine has installed, grab a prebuilt yabridge release, (current version 5.1.1), as a tarball, then extract it to ~/.local/share. (‘~’ being the home directory.)

tar -C ~/.local/share -xavf yabridge-5.1.1.tar.gz

Copy your .vst files into ~/.vst3, then just run the following from ~/.local/share/yabridge:

yabridgectl add ~/.vst3
yabridgectl sync

After a little churning, a bunch of new directories will be created under ~/.vst3, storing .so files for each of the plugins. The original files can be deleted if need be, (they’ll just show up as Errors), but ultimately the working versions are easy to find in Ardour’s Plugin Manager, where they can be enabled and added to the chain:

Donning my Electric AXE

Now we’re mixing it up, the next challenge is to get audio in and out.

I’ve been using the IK Multimedia AXE I/O One as external soundcard of choice for a few years now. An ideal device that can receive 1/4″ jack and balanced XLR input, sending the post-DAW signal to headphones, amp, and line-out. Connecting via USB-C, it works with just about everything. Although IK does not formally support Linux, a little tweaking can coax it into life.

When first plugging it in, the first surprise is that nothing happens. Checking sound settings reveals a new analogue input source, but nothing else. Time to troubleshoot.

First thing I tried was listing the USB devices to make sure it had been picked up properly.

lsusb

[...]
Bus 001 Device 007: ID 1963:00bb IK Multimedia AXE IO One
[...]

So at least it exists. Next I checked the ALSA hardware layer.

aplay -l

[...]
card 2: One [AXE IO One], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[...]

So it’s there as a playback device. Next comes the USB Audio kernel module, just to make sure that’s working:

lsmod | grep snd_usb_audio

[...]
snd_usb_audio         573440  4
[...]

At this point I was able to see the card as an ALSA device in Ardour, but it still wasn’t available elsewhere. So, I needed to go higher up to Pipewire:

pactl list cards | grep -A20 -i axe

[...]
Name: alsa_card.usb-IK_Multimedia_AXE_IO_One_0700624-02
[...]
Profiles:
		off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
		output:multichannel-output+input:mono-fallback: Multichannel Output + Mono Input (sinks: 1, sources: 1, priority: 101, available: yes)
		output:multichannel-output: Multichannel Output (sinks: 1, sources: 0, priority: 100, available: yes)
		pro-audio: Pro Audio (sinks: 1, sources: 1, priority: 1, available: yes)
		input:mono-fallback: Mono Input (sinks: 0, sources: 1, priority: 1, available: yes)
	Active Profile: pro-audio
[...]

So, looking at this, it seems the card IS visible to Pipewire, with an audio sink (output), but the pro-audio active profile doesn’t play nice with desktop.

Investigating the Pipewire sinks further:

pactl list short sinks

[...]
61	alsa_output.usb-IK_Multimedia_AXE_IO_One_0700624-02.pro-output-0	PipeWire	s32le 3ch 48000Hz	SUSPENDED
[...]

Now I know it’s visible, I can set it as the default sink and send a test signal to the PulseAudio device exposed by PipeWire:

(I could also have sent it to the plughw:2,0 PipeWire device which wraps the raw hardware.)

pactl set-default-sink alsa_output.usb-IK_Multimedia_AXE_IO_One_0700624-02.pro-output-0

speaker-test -D pulse -c 2 -f 4000 -r 48000 -t sine -l 0

It was at this point I realised my headphone volume was maxed, and 4000 Hz really is an unpleasant frequency.

The card was working at the desktop level, and after a swift blast of ‘Procreation (Of the Wicked)’ to soothe my delicate ears, I went to see if I could use it this way in Ardour. After some starting and stopping of the DAW’s sound server, it worked!

However, the card was still not available in Sound Settings, probably due to the aforementioned pro-audio profile. So I just needed to map it into something Pipewire could use elsewhere:

(Note to the overwhelmed reader: THIS IS THE IMPORTANT BIT!!!!!)

pactl load-module module-remap-sink sink_name=AXE_IO_STEREO master=alsa_output.usb-IK_Multimedia_AXE_IO_One_0700624-02.pro-audio channels=2 master_channel_map=front-left,front-right channel_map=front-left,front-right

And with that, the AXE popped up in the Sound Settings with a somewhat mangled name – but at least it works and I could test it from there.

Going back to Ardour, the default PulseAudio device could be changed from this control panel, and the audio switched seamlessly. Success!

Finally, all I had to do was add the remap to a script to run whenever I wanted to plug the card in. Automating this can be finessed later, but it’ll do for now.

Welcome to Helvum

Helvum is a great little tool to help visualise audio flow. Acting as a virtual patchbay, signals can be dragged from application to audio sink, with the remapped AXE sink appearing as both a Playback input and output.

The AXE itself appears with three playback_AUX channels. AUX0 and AUX1 are Left and Right headphone/line out respectively, and AUX2 the amp output.

If patches are lost for whatever reason, they can be remapped here. Counter-intuitively, patches are deleted by dragging the same link from node to node again, but this soon becomes second nature.

sudo apt install helvum

A Divine Comedy of Compatibility

Broadcasting beyond the confines of my laptop into a wider world of connectivity, the next step is to get it to speak the Dante protocol. Developed by Audinate, Dante is the media industry standard for synchronising and transmitting low-latency multi-track audio (and video) digital data across Ethernet, with bandwidth far in excess of the multicores of old. And of course, it isn’t supported on Linux.

Fortunately, a clean-room reverse-engineering of the protocol exists. Appropriately named Inferno, it is a software-only implementation thatis still very much experimental and not recommended for real-world productions. However, it should be sufficient for my goal of sending a ‘Band in a Box’ from my laptop to a mixing desk.

Like the author’s depiction of the afterlife, getting this working requires purgatorial levels of fault finding and configuration hacking. As of writing, I’m not quite there yet, but here’s what I have so far…

First, I needed to build everything. Following the instructions at the main code repository, I soon realised I needed to obtain a second package – statime – to allow for network clock synchronisation.

git clone --recurse-submodules -b inferno-dev https://github.com/teodly/statime

git clone --recursive https://gitlab.com/lumifaza/inferno.git

This got me all the code I needed. As both projects are written in the Rust language, I also had to install the latest version of the language via rustup, despite my reluctance to pipe random code from the Internet into the shell.

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

With the code in place, I built statime with cargo build, and edited the inferno-ptpv1.toml file to include my correct ethernet interface, enp4s0. Then I kicked everything off:

sudo target/debug/statime -c inferno-ptpv1.toml

Lots of trace messages scrolled up, so I thought I’d better stop it for now to build the main virtual ALSA device. First I needed some extra development libraries:

sudo apt install libasound2-dev

And then I ran another cargo build from the alsa_pcm_inferno directory. This created a library which needed to be linked into the correct directory.

cd /usr/lib/x86_64-linux-gnu/alsa-lib

sudo ln -s ~/Development/inferno/target/debug/libasound_module_pcm_inferno.so .

With the virtual device library in place, the next step was to get it to appear to ALSA. Taking hints from both the readme documentation and a useful set of forum posts, I created an .asoundrc file in my home directory, roughly containing the following:

pcm.fixed {
	type plug
	slave.pcm "inferno"
	hint {
		show on
		description "Plug - Inferno ALSA"
	}
}

pcm.inferno {
	type inferno
	rate 48000
	NAME "daryl_phantom"
	SAMPLE_RATE "48000"
	TX_CHANNELS 2
	RX_CHANNELS 2
	BIND_IP "enp4s0"
	hint {
		show on
		description "RAW - Inferno ALSA"
	}
}

ctl.fixed {
	type hw
	card 10
}

ctl.inferno {
	type hw
	card 11
}

This would create a raw ALSA device, as well as a plug for that device to allow it to be called from Pipewire. I knocked the available receive and transmit channels down to two apiece, just to make it easier to test by sending two-channel audio from the command line.

Happily, the virtual devices became visible to ALSA:

aplay -L

[...]
fixed
    Plug - Inferno ALSA
inferno
    RAW - Inferno ALSA
[...]

But not to aplay -l, which only lists physical hardware.

At this point I was ready for testing, so I chained my laptop’s Ethernet to a pre-existing ad-hoc Dante network consisting of a Midas M32, DigiCo Quantum 225, and a MacBook running Dante Controller and Reaper. Making sure to set my Ethernet’s IP to a similar range to the rest. The intent being to run some test sounds over the network to see if they work.

ffmpeg -y -i /usr/share/sounds/alsa/Front_Center.wav -ac 2 -f wav -acodec pcm_s32le /tmp/Front_Center_32.wav

aplay -D inferno /tmp/Front_Center_32.wav

The main issue in all of this was the clock. My Ethernet port has no hardware timing, so I also experimented with setting up a software clock with ptp4l:

sudo apt install linuxptp

sudo ptp4l -i enp4s0 -m -S

Eventually, I was able to get a positive response from playing audio into the virtual device, showing that the clock was eventually found and stabilised. However, the device still wasn’t appearing in Ardour, despite my trying other ways to access the plug.

At this point the studio session was over so I had to continue at home, where the clock didn’t work at all. After subsequent digging, I conclude a physical Dante hardware device must be available to provide a reliable clock signal, even when the software clock is acting as master, so my investigations have paused for now.

Hopefully I’ll be able to get these last few tweaks working when I’ve got access to a Dante-compatible desk again.

The journey continues

Although I’m a lot closer than I was when I started, there are still a few things that could be better to ensure Linux has its place in a professional audio environment. More research and experimentation is essential, and this article will be expanded accordingly as I go.

#Alsa-#Hundewelt - 12% #Gutscheincode #Coupon #Valentinstag | MKW: -
https://www.preishals.de/gutscheine/alsa-hundewelt/

#Alsa-#Hundewelt - 12% #Gutscheincode #Coupon #Valentinstag | MKW: -
https://www.preishals.de/gutscheine/alsa-hundewelt/

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

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

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.

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.

#Alsa-#Hundewelt - 14% #Gutscheincode #Coupon #Valentinstag | MKW: -
https://www.preishals.de/gutscheine/alsa-hundewelt/

@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 pavucontrol

I understand why Wayland was made and only have it on my SBC Raspberry Pi5

#Ifconfig #ip #init #systemD #Xorg #Wayland #programming #pipewire #ALSA #OSS

@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 pavucontrol

I 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..

I'm stuck here, still searching :)
#alsa #midi #music

#Alsa-Hundewelt - 15% #Gutscheinaktion #Rabattcode #Coupon | MKW: 20 € https://www.preishals.de/gutscheine/alsa-hundewelt/

- 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

#LinuxAudio

@jwcph

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:

1. 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)

2. 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.

#LinuxAudio

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.

#linux #debian #alsa #sound

@Nowhereman

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.

Recording audio from #youtube via #alsa loopback. Every little step counts right?

If you are on #linux and have to use #zoom and your linux says it dose have no audio devices on only some of them zoom just might for some reason connected it self to alsa and block you in my case #pipewire from that #alsa device

/* only one ? nonsense! */

https://elixir.bootlin.com/linux/v6.16/source/sound/usb/mixer.c#L2755

#linux #kernel #sound #alsa

#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