Ok, it seems to be an issue with the Windows version. I need to look at this with Damien.
I have been able to reproduce this, but after restarting the software, the issue was not there anymore. Nevertheless, there seems to be an issue here.
Ok, it seems to be an issue with the Windows version. I need to look at this with Damien.
I have been able to reproduce this, but after restarting the software, the issue was not there anymore. Nevertheless, there seems to be an issue here.
@Antoine This is the link for the FLAC stream by the way, https://hls.somafm.com/hls/groovesalad/FLAC/program.m3u8
I haven’t tried HLS radios other than SomaFM, maybe they work including metadata.
Just to be sure that you’re aware that this problem persist in version .20
We have not addressed the issue on our end for the moment.
I didn’t notice the logs the first time.
2026-03-12 02:46:34.579 [debug]: FLAC decoder: HTTP reader returned less bytes 2528 than requested 0
2026-03-12 02:48:41.041 [error]: AudioStreamHlsLoader error no audio decoder found for mime type audio/m4a
Try another format at SomaFM: Groove Salad: Direct Stream Links for other media players fren…
I stream from SomaFM from time to time with Audirvana with no issues…
It seems to be a bug, or an opportunity to improve the app. I know I can stream from other links but FLAC is the lossless one.
With Audirvana Linux, Remote Android when you are on preferred track in the middle of the list, it return to the beginning and it is a pain… When your preferred track list is long it is horrible to use…
I get the same thing, so we might be able to look at this ![]()
I think the current Audirvana FLAC decoder does not like that HLS protocol that FLAC stream is wrapped in…
Non HLS FLAC streams from Radio Paradise work fine…
Toggling the equalizer on and off in real-time mode consistently crashes the app, especially when returning to the DSP window.
I have the crash dumps, but the logs show nothing, even with debugging enabled.
What is the status of the Plug-ins module problems with loading some plug-ins for configuration and implementation?
Plug-ins that will no longer load for configuration or implementation:
Note: no change in (2.99.21)
Now that multi-channel is getting more attention… It would be nice if I could apply the Waves Abbey Road Studio 3 plug-in or Waves NX plugin so to listen to my 5.1 SACD rips and my 5.1 DSD files at 96kHz… Any thoughts on this?
![]()
Do you have this setting enabled in the Audio Unit plugin section?

Yes... and was previously able to load, configure and apply these plug-ins before the Beta… I have been trying to load only the stereo iteration(s)… Previously I gave you a video of the loading problem and the ticket was subsequently closed without resolution… I’m committed to Studio v3 now…
A post was merged into an existing topic: Exciting News: Public Beta Launch for Audirvāna Android Remote App!
@Antoine It might be time to get some of these “legacy features” (plugins) working properly again…
Doesn’t @mitchco have a solution for you/Devo?
Cordially,
-DD-
When this is enabled, you are using the Audio Unit v3 of Apple.
Does it happen only when you are outputting to a Multichannel device?
Some menu change on Android make infinite waiting… (with Audirvana Linux)
Yes, although it doesn’t happen all the time. When I restart the app it’s okay. Hopefully next update will fix this.
I am using a stereo DAC when testing the Plug-in module function. My multichannel DAC is not being employed at this point with Audirvāna… it is currently employed in my Logic Pro system.
I have tested my collection of Apple AU plug-ins in the stereo scenario and have found that the Apple virtualization/surround and stereo reverb plug-ins do not load… Most of the Apple plug-ins will load and display properly, however a couple of the Apple plug-ins do not display with any functional controls… The 112dB “Redline Monitor” is a stereo plug-in only… The Waves plug-ins I am trying to load are the stereo versions.… It appears that plug-ins having to do with HRTF virtualization or cross-feed are being discriminated against being loaded.
In Audirvāna Studio I would like to take advantage of these HRTF virtualization plug-ins for multichannel-surround playback via headphones… I can apply these in a Logic Pro project… It seems that Audirvāna is not looking for the Waves and 112db Monitor plug-ins in the ‘Library → Audio → Plug-ins → Components’ folder hierarchy… What is weird is the 112dB “Equalizer” will load and can be configured and it is in the same ‘Components’ folder with “Redline Monitor”…
Note: I have rescanned the AU plug-ins and created a fresh com.apple.audiounits.cache file by moving the existing AU cache file to the desktop and restarting the computer and opening Audirvāna Studio v3 Beta (2.99.21) and this does not change the condition of not being able to load the AU plug-ins in question…
It appears Audirvāna is not scanning the ‘Applications’ folder for those plug-ins (Waves and 112dB)… I am reticent to move the plug-ins in the ‘Applications’ folder to the ‘Library’ Plug-ins folder… maybe some confusion here, but Logic Pro finds them.
All of my plug-ins are showing ‘Compatible’ in the Logic Pro Plug-ins Manager. (Logic Pro 12.0.1)
Edit: I am now able to load “Abbey Road Studio 3” (2-channel), “NX” (2-channel) and “Redline Monitor”… I don’t know if rescanning the plug-ins is the reason or not… I also removed some Waves ‘Waveshell’ components from the plug-ins folder so to only have v16 files…
I understand that the multichannel variations need to see a proper multichannel DAC and speaker layout in Audio MIDI… It would be nice to be able to use the multichannel HRTF virtualization → stereo headphone processing of these plug-ins without having to change the DAC… Audio MIDI does not allow making a “dummy” multichannel speaker layout when the DAC is 2-channel.
To rescan the Audio Units for all applications: (macOS)
Open ‘Library’ → ‘Caches’ → ‘AudioUnitCache’ → move com.apple.audiounits.cache to the desktop–> Restart the computer → (a new com.apple.audiounits.cache file is created) → Open Audirvāna → load the plug-in(s) … Apparently, the scanning of the plug-ins can take time to make them all available to use… But I am not certain if rescanning made the difference here…
*The Apple virtualization plug-ins do not display controls or graphics.