Scaler 3.2 hangs in Reaper after loading project

Scaler 3 Support
1

Windows 11 24H2 build 26100.7171
Reaper 7.53
Scaler 3.2

Scaler 3.2 causes consistent ‘hangs’ when loading as part of a Reaper project.
Reaper is able to load the project in recovery mode (with all effects and instruments offline) but when I attempt to bring Scaler3 back on line within a track, Reaper hangs (spinning circle) and is totally unresponsive.
I waited 30 minutes but Reaper fails to respond (shows a consistent 6% CPU usage).
Reaper has to be killed with Task Manager.
The only way to recover the project is to load Reaper with FX offline, then delete the track containing Scaler 3.2, losing all work done within Scaler on that track. :sob:

It’s important to note that bug occurs when the project is loaded from disk. While the project is being created and worked on, Scaler works OK. The problem occurs when a saved project containing a Scaler 3.2 session is loaded.

EventViewer logs this:
The program reaper.exe version 7.5.3.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

3

Yes, 3.2 is freezing Reaper on project load or attempting to either add it as an insert or virtual instrument. Im guessing you fancy new routing is likely the culprit as this never happened in Scaler 2 or 3.0 - 3.1. Maybe make a version that doesn’t have routing or VST hosting to use in DAWs so I’m not concerned about bricking a project with your product I paid for?