home.social

#yabridge — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #yabridge, aggregated by home.social.

fetched live
  1. Решение проблемы Yabridge и свежих версий Wine

    Yabridge — это самый толковый на сегодняшний день способ использовать VST и CLAP плагины для Windows под Linux. Проблема в том, что последний стабильный Yabridge v5.1.1 пока не работает с версиями Wine выше 9.21, а держать настолько старую версию Wine только ради плагинов — такое себе. К счастью, решается это довольно просто. Я пользуюсь Arch Linux, кстати говоря, и на его примере покажу, как это решить, но пример легко адаптируется под другие дистрибутивы.
    #Linux #Yabridge #VST #CLAP #DAW #Reaper #Bitwig

  2. Решение проблемы Yabridge и свежих версий Wine

    Yabridge — это самый толковый на сегодняшний день способ использовать VST и CLAP плагины для Windows под Linux. Проблема в том, что последний стабильный Yabridge v5.1.1 пока не работает с версиями Wine выше 9.21, а держать настолько старую версию Wine только ради плагинов — такое себе. К счастью, решается это довольно просто. Я пользуюсь Arch Linux, кстати говоря, и на его примере покажу, как это решить, но пример легко адаптируется под другие дистрибутивы.
    #Linux #Yabridge #VST #CLAP #DAW #Reaper #Bitwig

  3. Music Production on #ArchLinux

    serge: "Hey everyone! Today we're going to be talking about music production on Linux. We'll discuss why you should or shouldn't use ..."
    youtube.com/watch?v=NGZbFMl9dqQ

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Yabridge #Wine #Pipewire #ReaperDAW #Linux

  4. Music Production on #ArchLinux

    serge: "Hey everyone! Today we're going to be talking about music production on Linux. We'll discuss why you should or shouldn't use ..."
    youtube.com/watch?v=NGZbFMl9dqQ

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Yabridge #Wine #Pipewire #ReaperDAW #Linux

  5. Music Production on #ArchLinux

    serge: "Hey everyone! Today we're going to be talking about music production on Linux. We'll discuss why you should or shouldn't use ..."
    youtube.com/watch?v=NGZbFMl9dqQ

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Yabridge #Wine #Pipewire #ReaperDAW #Linux

  6. Music Production on #ArchLinux

    serge: "Hey everyone! Today we're going to be talking about music production on Linux. We'll discuss why you should or shouldn't use ..."
    youtube.com/watch?v=NGZbFMl9dqQ

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Yabridge #Wine #Pipewire #ReaperDAW #Linux

  7. Music Production on #ArchLinux

    serge: "Hey everyone! Today we're going to be talking about music production on Linux. We'll discuss why you should or shouldn't use ..."
    youtube.com/watch?v=NGZbFMl9dqQ

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Yabridge #Wine #Pipewire #ReaperDAW #Linux

  8. I rarely use vocals in my music these days, but today I needed to test two mics on #LinuxAudio, and I found out the following:

    I need to set Block size to 128 samples, for the latency to be low enough for software monitoring.

    I very quickly need to reach for my Yabridge toolbox, to get the right sound

    Manley Voxbox (UADx) doesn’t save the settings when closing, so I need to find an alternative to that, which will be one of the Brainworx Channelstrips.

    I’m really happy for #Wine and #Yabridge

  9. I rarely use vocals in my music these days, but today I needed to test two mics on #LinuxAudio, and I found out the following:

    I need to set Block size to 128 samples, for the latency to be low enough for software monitoring.

    I very quickly need to reach for my Yabridge toolbox, to get the right sound

    Manley Voxbox (UADx) doesn’t save the settings when closing, so I need to find an alternative to that, which will be one of the Brainworx Channelstrips.

    I’m really happy for #Wine and #Yabridge

  10. I rarely use vocals in my music these days, but today I needed to test two mics on #LinuxAudio, and I found out the following:

    I need to set Block size to 128 samples, for the latency to be low enough for software monitoring.

    I very quickly need to reach for my Yabridge toolbox, to get the right sound

    Manley Voxbox (UADx) doesn’t save the settings when closing, so I need to find an alternative to that, which will be one of the Brainworx Channelstrips.

    I’m really happy for #Wine and #Yabridge

  11. I rarely use vocals in my music these days, but today I needed to test two mics on #LinuxAudio, and I found out the following:

    I need to set Block size to 128 samples, for the latency to be low enough for software monitoring.

    I very quickly need to reach for my Yabridge toolbox, to get the right sound

    Manley Voxbox (UADx) doesn’t save the settings when closing, so I need to find an alternative to that, which will be one of the Brainworx Channelstrips.

    I’m really happy for #Wine and #Yabridge

  12. I rarely use vocals in my music these days, but today I needed to test two mics on #LinuxAudio, and I found out the following:

    I need to set Block size to 128 samples, for the latency to be low enough for software monitoring.

    I very quickly need to reach for my Yabridge toolbox, to get the right sound

    Manley Voxbox (UADx) doesn’t save the settings when closing, so I need to find an alternative to that, which will be one of the Brainworx Channelstrips.

    I’m really happy for #Wine and #Yabridge

  13. @ercanbrack Yes, I personally use two #Tone2 plugins on Linux with Wine and Yabridge.

    I spoke with the developer of Tone2 about Linux. Since there won’t be any new Tone2 plugins - only updates to the existing ones - the effort and cost involved in adapting them natively for Linux would be too great. It just wouldn’t be worth it.

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Wine #Yabridge

  14. @ercanbrack Yes, I personally use two #Tone2 plugins on Linux with Wine and Yabridge.

    I spoke with the developer of Tone2 about Linux. Since there won’t be any new Tone2 plugins - only updates to the existing ones - the effort and cost involved in adapting them natively for Linux would be too great. It just wouldn’t be worth it.

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Wine #Yabridge

  15. @ercanbrack Yes, I personally use two #Tone2 plugins on Linux with Wine and Yabridge.

    I spoke with the developer of Tone2 about Linux. Since there won’t be any new Tone2 plugins - only updates to the existing ones - the effort and cost involved in adapting them natively for Linux would be too great. It just wouldn’t be worth it.

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Wine #Yabridge

  16. @ercanbrack Yes, I personally use two #Tone2 plugins on Linux with Wine and Yabridge.

    I spoke with the developer of Tone2 about Linux. Since there won’t be any new Tone2 plugins - only updates to the existing ones - the effort and cost involved in adapting them natively for Linux would be too great. It just wouldn’t be worth it.

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Wine #Yabridge

  17. @ercanbrack Yes, I personally use two #Tone2 plugins on Linux with Wine and Yabridge.

    I spoke with the developer of Tone2 about Linux. Since there won’t be any new Tone2 plugins - only updates to the existing ones - the effort and cost involved in adapting them natively for Linux would be too great. It just wouldn’t be worth it.

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #Linux #vst #Wine #Yabridge

  18. Linux как гитарная рабочая станция

    В далёком 2001 году я впервые увидел Linux и понял, что это моё. Шли годы, менялись дистрибутивы и мои требования к ним, но вот недавно я решил закрыть гештальт и научиться играть на электрогитаре. Покопавшись в интернете, наткнулся на кучу обзоров гитарных процессоров, комбиков и программ-эмуляций. Как это часто бывает, крутые коммерческие продукты есть под Windows и Mac, а вот про Linux как-то снова забыли. В принципе, это нормально — иметь две системы под разные нужды. Но иногда очень не хочется перезагружаться, и я решил попробовать настроить свой Manjaro под работу со звуком. Мои первые эксперименты с JACK во времена 4 рубля за мегабайт закончились неудачей, а вот сейчас и знаний, и терпения хватило. Моя система: Manjaro Linux, KDE, Wayland. Аудиоинтерфейс Motu M2.

    habr.com/ru/articles/1029056/

    #linux #гитара #manjaro #wine #yabridge #neuraldsp #reaper #pipewire #linuxaudio #vst

  19. Linux как гитарная рабочая станция

    В далёком 2001 году я впервые увидел Linux и понял, что это моё. Шли годы, менялись дистрибутивы и мои требования к ним, но вот недавно я решил закрыть гештальт и научиться играть на электрогитаре. Покопавшись в интернете, наткнулся на кучу обзоров гитарных процессоров, комбиков и программ-эмуляций. Как это часто бывает, крутые коммерческие продукты есть под Windows и Mac, а вот про Linux как-то снова забыли. В принципе, это нормально — иметь две системы под разные нужды. Но иногда очень не хочется перезагружаться, и я решил попробовать настроить свой Manjaro под работу со звуком. Мои первые эксперименты с JACK во времена 4 рубля за мегабайт закончились неудачей, а вот сейчас и знаний, и терпения хватило. Моя система: Manjaro Linux, KDE, Wayland. Аудиоинтерфейс Motu M2.

    habr.com/ru/articles/1029056/

    #linux #гитара #manjaro #wine #yabridge #neuraldsp #reaper #pipewire #linuxaudio #vst

  20. Linux как гитарная рабочая станция

    В далёком 2001 году я впервые увидел Linux и понял, что это моё. Шли годы, менялись дистрибутивы и мои требования к ним, но вот недавно я решил закрыть гештальт и научиться играть на электрогитаре. Покопавшись в интернете, наткнулся на кучу обзоров гитарных процессоров, комбиков и программ-эмуляций. Как это часто бывает, крутые коммерческие продукты есть под Windows и Mac, а вот про Linux как-то снова забыли. В принципе, это нормально — иметь две системы под разные нужды. Но иногда очень не хочется перезагружаться, и я решил попробовать настроить свой Manjaro под работу со звуком. Мои первые эксперименты с JACK во времена 4 рубля за мегабайт закончились неудачей, а вот сейчас и знаний, и терпения хватило. Моя система: Manjaro Linux, KDE, Wayland. Аудиоинтерфейс Motu M2.

    habr.com/ru/articles/1029056/

    #linux #гитара #manjaro #wine #yabridge #neuraldsp #reaper #pipewire #linuxaudio #vst

  21. @keefmarshall For editing, grading, compositing, mastering I use #DaVinciResolve (before that it was Avid MC). 2D/3D animations and VFX are done in my beloved #Blender. GFX elements I do with #GIMP. The visuals of my next project will be done completely on Linux (Fedora/Cinnamon). The only thing I can´t do there is the music itself. #Reaper works great on Linux, but my #NativeInstruments / #Arturia plug-ins can´t be activated, even though they would work with #Yabridge.

  22. @keefmarshall For editing, grading, compositing, mastering I use #DaVinciResolve (before that it was Avid MC). 2D/3D animations and VFX are done in my beloved #Blender. GFX elements I do with #GIMP. The visuals of my next project will be done completely on Linux (Fedora/Cinnamon). The only thing I can´t do there is the music itself. #Reaper works great on Linux, but my #NativeInstruments / #Arturia plug-ins can´t be activated, even though they would work with #Yabridge.

  23. @keefmarshall For editing, grading, compositing, mastering I use #DaVinciResolve (before that it was Avid MC). 2D/3D animations and VFX are done in my beloved #Blender. GFX elements I do with #GIMP. The visuals of my next project will be done completely on Linux (Fedora/Cinnamon). The only thing I can´t do there is the music itself. #Reaper works great on Linux, but my #NativeInstruments / #Arturia plug-ins can´t be activated, even though they would work with #Yabridge.

  24. @keefmarshall For editing, grading, compositing, mastering I use #DaVinciResolve (before that it was Avid MC). 2D/3D animations and VFX are done in my beloved #Blender. GFX elements I do with #GIMP. The visuals of my next project will be done completely on Linux (Fedora/Cinnamon). The only thing I can´t do there is the music itself. #Reaper works great on Linux, but my #NativeInstruments / #Arturia plug-ins can´t be activated, even though they would work with #Yabridge.

  25. @keefmarshall For editing, grading, compositing, mastering I use #DaVinciResolve (before that it was Avid MC). 2D/3D animations and VFX are done in my beloved #Blender. GFX elements I do with #GIMP. The visuals of my next project will be done completely on Linux (Fedora/Cinnamon). The only thing I can´t do there is the music itself. #Reaper works great on Linux, but my #NativeInstruments / #Arturia plug-ins can´t be activated, even though they would work with #Yabridge.

  26. I set up Bitwig 6.0 this evening with the Flatpak on Manjaro only to find that yabridge doesn't work with it, but I found this neat solution: github.com/xynydev/BitwigBox. It runs the Bitwig deb in an Ubuntu container with access to your existing files and plugin directories. As it's the deb package it can be updated with apt. #bitwig #yabridge #linuxmusic

  27. I set up Bitwig 6.0 this evening with the Flatpak on Manjaro only to find that yabridge doesn't work with it, but I found this neat solution: github.com/xynydev/BitwigBox. It runs the Bitwig deb in an Ubuntu container with access to your existing files and plugin directories. As it's the deb package it can be updated with apt. #bitwig #yabridge #linuxmusic

  28. I set up Bitwig 6.0 this evening with the Flatpak on Manjaro only to find that yabridge doesn't work with it, but I found this neat solution: github.com/xynydev/BitwigBox. It runs the Bitwig deb in an Ubuntu container with access to your existing files and plugin directories. As it's the deb package it can be updated with apt. #bitwig #yabridge #linuxmusic

  29. I set up Bitwig 6.0 this evening with the Flatpak on Manjaro only to find that yabridge doesn't work with it, but I found this neat solution: github.com/xynydev/BitwigBox. It runs the Bitwig deb in an Ubuntu container with access to your existing files and plugin directories. As it's the deb package it can be updated with apt. #bitwig #yabridge #linuxmusic

  30. I set up Bitwig 6.0 this evening with the Flatpak on Manjaro only to find that yabridge doesn't work with it, but I found this neat solution: github.com/xynydev/BitwigBox. It runs the Bitwig deb in an Ubuntu container with access to your existing files and plugin directories. As it's the deb package it can be updated with apt. #bitwig #yabridge #linuxmusic

  31. Owning the means of (Audio) Production

    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.

    https://heathenstorm.com/2026/03/01/owning-the-means-of-audio-production/ #alsa #ardour #audio #dante #daw #ikmultimedia #inferno #linux #pipewire #production #vst #yabridge
  32. RE: vocalounge.cafe/@bibbs/1160671

    This is hugely positive news for all who use Windows VST plugins on Linux through WINE!! This may be the biggest news in quite a while!!!

    In other news, the yabridge Wayland Wine problems for using Wine versions higher than v9.21 are nearly fixed too!

    Things are about to get usable again for Linux users with Windows plugins!!

    #LinuxAudio #Linux #MusicProduction #DAW #Music #WINE #Audio #Plugin #Windows #VST #yabridge #Juce #direct2d

  33. RE: vocalounge.cafe/@bibbs/1160671

    This is hugely positive news for all who use Windows VST plugins on Linux through WINE!! This may be the biggest news in quite a while!!!

    In other news, the yabridge Wayland Wine problems for using Wine versions higher than v9.21 are nearly fixed too!

    Things are about to get usable again for Linux users with Windows plugins!!

    #LinuxAudio #Linux #MusicProduction #DAW #Music #WINE #Audio #Plugin #Windows #VST #yabridge #Juce #direct2d

  34. RE: vocalounge.cafe/@bibbs/1160671

    This is hugely positive news for all who use Windows VST plugins on Linux through WINE!! This may be the biggest news in quite a while!!!

    In other news, the yabridge Wayland Wine problems for using Wine versions higher than v9.21 are nearly fixed too!

    Things are about to get usable again for Linux users with Windows plugins!!

    #LinuxAudio #Linux #MusicProduction #DAW #Music #WINE #Audio #Plugin #Windows #VST #yabridge #Juce #direct2d

  35. RE: vocalounge.cafe/@bibbs/1160671

    This is hugely positive news for all who use Windows VST plugins on Linux through WINE!! This may be the biggest news in quite a while!!!

    In other news, the yabridge Wayland Wine problems for using Wine versions higher than v9.21 are nearly fixed too!

    Things are about to get usable again for Linux users with Windows plugins!!

    #LinuxAudio #Linux #MusicProduction #DAW #Music #WINE #Audio #Plugin #Windows #VST #yabridge #Juce #direct2d

  36. RE: vocalounge.cafe/@bibbs/1160671

    This is hugely positive news for all who use Windows VST plugins on Linux through WINE!! This may be the biggest news in quite a while!!!

    In other news, the yabridge Wayland Wine problems for using Wine versions higher than v9.21 are nearly fixed too!

    Things are about to get usable again for Linux users with Windows plugins!!

    #LinuxAudio #Linux #MusicProduction #DAW #Music #WINE #Audio #Plugin #Windows #VST #yabridge #Juce #direct2d

  37. I couldn't resist. 🙈

    €59/$69 is a good deal for such a well-programmed VST synthesizer with 1022 presets.
    tone2.com/saurus.html

    I think the quality is top notch, just like with #uhe. No extra installation software needed. Just install it and enter the license key when you start it up. That's how it should be!

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #vst #tone2 #Saurus #Synth #Yabridge #Wine #MarkusKrause

  38. I couldn't resist. 🙈

    €59/$69 is a good deal for such a well-programmed VST synthesizer with 1022 presets.
    tone2.com/saurus.html

    I think the quality is top notch, just like with #uhe. No extra installation software needed. Just install it and enter the license key when you start it up. That's how it should be!

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #vst #tone2 #Saurus #Synth #Yabridge #Wine #MarkusKrause

  39. I couldn't resist. 🙈

    €59/$69 is a good deal for such a well-programmed VST synthesizer with 1022 presets.
    tone2.com/saurus.html

    I think the quality is top notch, just like with #uhe. No extra installation software needed. Just install it and enter the license key when you start it up. That's how it should be!

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #vst #tone2 #Saurus #Synth #Yabridge #Wine #MarkusKrause

  40. I couldn't resist. 🙈

    €59/$69 is a good deal for such a well-programmed VST synthesizer with 1022 presets.
    tone2.com/saurus.html

    I think the quality is top notch, just like with #uhe. No extra installation software needed. Just install it and enter the license key when you start it up. That's how it should be!

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #vst #tone2 #Saurus #Synth #Yabridge #Wine #MarkusKrause

  41. I couldn't resist. 🙈

    €59/$69 is a good deal for such a well-programmed VST synthesizer with 1022 presets.
    tone2.com/saurus.html

    I think the quality is top notch, just like with #uhe. No extra installation software needed. Just install it and enter the license key when you start it up. That's how it should be!

    #PeaceLoveMusic #MusicProduction #DAW #LinuxAudio #vst #tone2 #Saurus #Synth #Yabridge #Wine #MarkusKrause

  42. ok that wasn't so bad, there's an issue here with yabridge:
    github.com/robbert-vdh/yabridg

    I downloaded the fixed version and ran yabridgectl sync and it was all ok. YMMV

    $ wine --version
    wine-10.0 (Ubuntu 10.0~repack-11)

    #yabridge #linuxaudio #ubuntu #wine10

  43. ok that wasn't so bad, there's an issue here with yabridge:
    github.com/robbert-vdh/yabridg

    I downloaded the fixed version and ran yabridgectl sync and it was all ok. YMMV

    $ wine --version
    wine-10.0 (Ubuntu 10.0~repack-11)

    #yabridge #linuxaudio #ubuntu #wine10

  44. ok that wasn't so bad, there's an issue here with yabridge:
    github.com/robbert-vdh/yabridg

    I downloaded the fixed version and ran yabridgectl sync and it was all ok. YMMV

    $ wine --version
    wine-10.0 (Ubuntu 10.0~repack-11)

    #yabridge #linuxaudio #ubuntu #wine10

  45. ok that wasn't so bad, there's an issue here with yabridge:
    github.com/robbert-vdh/yabridg

    I downloaded the fixed version and ran yabridgectl sync and it was all ok. YMMV

    $ wine --version
    wine-10.0 (Ubuntu 10.0~repack-11)

    #yabridge #linuxaudio #ubuntu #wine10

  46. ok that wasn't so bad, there's an issue here with yabridge:
    github.com/robbert-vdh/yabridg

    I downloaded the fixed version and ran yabridgectl sync and it was all ok. YMMV

    $ wine --version
    wine-10.0 (Ubuntu 10.0~repack-11)

    #yabridge #linuxaudio #ubuntu #wine10

  47. To be honest I have bought way too many plugins through the years, and I rarely bought just one plugin at the time, but always some kind of bundle on sale.

    I turns out, that this is actually an advantage when you move to Linux, since Yabridge/Wine have a tendency to make some - but not all - plugins working. Because of my collection, if one comp./verb/channelstrip isn't working, I move on to the next, and in the end I have what I need.

    #Yabridge #LinuxAudio

  48. To be honest I have bought way too many plugins through the years, and I rarely bought just one plugin at the time, but always some kind of bundle on sale.

    I turns out, that this is actually an advantage when you move to Linux, since Yabridge/Wine have a tendency to make some - but not all - plugins working. Because of my collection, if one comp./verb/channelstrip isn't working, I move on to the next, and in the end I have what I need.

    #Yabridge #LinuxAudio

  49. To be honest I have bought way too many plugins through the years, and I rarely bought just one plugin at the time, but always some kind of bundle on sale.

    I turns out, that this is actually an advantage when you move to Linux, since Yabridge/Wine have a tendency to make some - but not all - plugins working. Because of my collection, if one comp./verb/channelstrip isn't working, I move on to the next, and in the end I have what I need.

    #Yabridge #LinuxAudio

  50. To be honest I have bought way too many plugins through the years, and I rarely bought just one plugin at the time, but always some kind of bundle on sale.

    I turns out, that this is actually an advantage when you move to Linux, since Yabridge/Wine have a tendency to make some - but not all - plugins working. Because of my collection, if one comp./verb/channelstrip isn't working, I move on to the next, and in the end I have what I need.

    #Yabridge #LinuxAudio