VST plugin compliance in part or in full, at least v2.4

My setup with Roon and VSTs… Roon asio out>Voicemeeter>Vsthost with Plugins (NX for headphones and Ambiophonic for speakers>voicemeeter wasapi out> Dragonfly Red

Not ideal, and need some in deeph configuration, but works nice -SQ and smoothness with OS, both, very very good-

1 Like

I have a similar setup using SoundPimp Audio Enhancer as a standalone application from Roon ASIO out, and it works fine. However, there would be a tremendous gain in this setup, if Roon would offer itself as VST host. Why?

Because, the more nodes in the chain, the worse the sound (in principle). Roon as VST host would completely remove any jitter type of problematics since that solution would no longer involve the operating system for the integration of the VST plugin.

Another argument for VST compliance is that your solution may not be implemented with products like the extremely well reputed SOtM sMS-200 Ultra networked audio adaptor, having Roon built-in

2 Likes

For me Reaper proved more problematic than helpful.

So my RoonBridge endpoint is JR running as ASIO hosting A.O.M. plugins, then out to the Mutec, then Yggy. Works great…an improvement better than any dongle, thingy, etc add-on…

Now if either Roon would add VST support to RoonBridge, or someone writes an up-to-date program for ASIO support with VST hosting…

1 Like

What happened between December and February?
It went from:

Reaper works in my setup (works great!!!) running on the computer where RoonBridge resides and uses less resources compared to JR.

to:

For me Reaper proved more problematic than helpful.

I’m still hoping for some kind of VST support in Roon…
@brian

We are to with high hopes.

Stability issues crept in over time. JR as ASIO works okay for now.

Me as well.

Primarily as it will open up the possibility to use Dirac (hosted as a VST on Roon) and HQPlayer correctly.

But that’s just one use case - it would also allow for Dirac to be properly used with Roon network endpoints!

And more - it would open up an entire world of existing and future VSTs, all working correctly with Roon endpoints and Roon’s HQPlayer integration.

@Carl_Henrik_Janson Completely agree with your blunt Norwegian logic here. It won’t hurt any one not using it but would benefit more than the few (Dirac is popular!) who prefer this over the UI nuisance. I use a directly attached Roon setup and even if I’ll move to out of sight Roon Server I would prefer having it compatible with VSTs (which are mostly configured once anyway) for SQ functionality. Some don’t and that’s OK but why take sides when everything is possible in software?