The communication between Beam and Spacelab Interstellar plugin doesn't work, probably because of the network blocking. Can anyone confirm this same behavior?

 

Make sure that you have TEAM R2R Network Block Runtime installed.
This release is patched to load that runtime to avoid homecalling.

Dolby Atmos Composer No Connections
https://audiosex.pro/threads/dolby-atmos-composer-no-connections.81884

 

Everything is already installed. But the developer uses WinSock2 for inter process communications with Beam, but I think it might be blocked due to the WS2R2R. R2R has fixed Dolby Atmos Composer version, using original WS2_32.

 

Most all that stuff is broken (along with R2R SWAM, and maybe now except for the "composer") due to the R2R automated net block attempts (or possibly just the dev's crappy coding ). The one thing you could try (if you haven't already) is the v2.1.0 net block and see if that makes a difference? I would also suggest maybe trying out the previous (last year) V.R. release, but that seems to be more broken than this one. Maybe TCD will do a release of fiedler that simply works without trying to get cute with automated home-call blocking, and leave the net blocking stuff to the end user to deal with (as it should be). Until then, I just deleted the entire thing - too buggy, and the install/config is a bloody nightmare to endure for what little it does. I already have surround verb that just works, and don't really need atmos for much of anything...

 

Last edited: Oct 4, 2025 at 9:55 PM

SWAM and all other R2R releases on my systems work perfectly. Both Windows 10 and 11. This one was the only issue, but R2R Gods had already fixed it in the new release update.