I am using HLC and I am tired of having to run in real-time, we should be able to use plugin without resorting to real time mode, the performance sucks.
I for one will not renew until all these playback issues are resolved.
Its not HLC, all vst via upnp wont function correctly under real time. It has nothing to do with the vst plugins or upnp but AS forcing realtime mode. I wish they would fix it.
As I see it, all signal processing plugins should run in “realtime”… I use the Hang Loose Convolver for Room Correction via FIR filters and another plugin for fine tuning EQ to taste… If it did not run in realtime then how would you expect it to perform its functions on the small signal stream?
The issues is that UPNP is not a realtime protocol nor is TCP/IP that UPNP runs on top of… So, the user interface to these plugins does not function as one might expect, if at all…
The performance on my 2015 MacBook Pro is more than acceptable using both plugins averaging about 4 to 6 percent CPU load using Audirvna streaming Qobuz to my U1 mini streamer via WiFi/UPNP…
Tried my i7 de-lid system running windoz11 with HLC+RC FIR filters and an EQ plugin via WiFi and onto the rest of the signal chain… Works as expected with performance reported by AV in the 3 to 7% range…
Apparently you have not been using plug-ins for very long… It is common for plug-ins not to function as expected when a host application updates… Sometimes it’s the Host application, sometimes it’s the plug-in designer not making changes quickly enough when they know the Host is being updated…
I don’t understand the logic of not having a plug-in run with real-time control… They all have a primary functionality that is premised on real-time control… It is illogical to insert a plug-in that doesn’t allow real-time parametric control.
The construct of compatibility can be more diverse…
I utilize Abbey Road Studio 3 (AU plug-in) for HRTF virtualization for headphone listening… When playing DXD 352.8kHz files I cannot access the real-time functions of the plug-in… This, primarily because of the processing demands at that sample-rate… everything is functional at lower PCM sample-rates, and this via USB transmission protocol. However, when I use 112db’s Redline Monitor (AU plug-in) for HRTF, I can use the real-time parametric controls at DXD 352.8kHz…
The OP has pointed out something that doesn’t work in the way he uses Audirvana with plugins. I don’t see the helpfulness of saying “But different plugins or different scenarios work for me.” Either Audirvana will be able to make the appropriate change to allow the OP to use his software as he wants or they won’t, and he will be able to respond accordingly.
I’m pointing out a basis for why there may be no reason to change the current plug-in architecture or to jump every-time a plug-in doesn’t function as expected when things change… and that the construct of ‘compatibility’ is much broader than a single playback scenario… Setting expectations that every-time a user has a problem with any given plug-in or plug-in format, etc., there must be a concerted effort to resolve or support… is not what you should be doing…
Finally a reasonable response. Its fine to be a fan boy. But to say plugins need to be run in real-time shows people dont understand plugins.
Give us back the ability to run plugins without having to turn on real time mode. Like all the other big audio engines. I find it hilarious that there is pushback from other users. “No its broke and don’t fix it!”
Oh, my picture is probably next to “Audirvana fan boy” in the dictionary. But I figure the forum is to help improve folks’ experience of Audirvana and/or help improve the software, and this thread didn’t seem to be headed that way.