Reaper hangs when loading projects with Scaler 3.2

Scaler 3 Support Bug Reports
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.

In its current state, I don’t trust Scaler enough to use with confidence. The ‘save often’ maxim doesn’t apply here, as the problem manifests when you try to load a Reaper project with Scaler 3.2 on a track.

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.

Event viewer logs this when Reaper hangs

Fault bucket 2072707980255898245, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: reaper.exe
P2: 7.5.3.0
P3: 691357a5
P4: e898
P5: 67247104
P6:
P7:
P8:
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f3ea8d1c-3b11-46b2-8403-12655307eb4c.tmp.WERInternalMetadata.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_reaper.exe_301d3719ed771e096164cad53532edecb19bbe_77a7ec93_6c635010-260e-4c96-9328-e607bfafc02f

Analysis symbol:
Rechecking for solution: 0
Report Id: 8d7e837d-5934-4778-9ed5-df9b253dfb7c
Report Status: 268435456
Hashed bucket: 6baaf810bc39348cfcc3bced26452a85
Cab Guid: 0

2

Thanks for this, we have another similar report from another Reaper user so this will help our developers. Looking into this.

3

Hi Davide – same issue I think on Studio One Version 7.2

4

I will second this issue in Studio One 7.2. It worked the first time I used it but not after it was saved in a project and that project was re-opened.

5

“pmn” who describes the bug exactly as I experienced it. I’m running Reaper 7.56 on Win 10. Everything works, (even a complex setup loading multiple VSTs in both Scaler and Reaper) except whenever I save a project, (even a bare bones simple on) if I try to open it it locks up Reaper completely, reporting 6% CPU usage. Although it doesn’t report as “not reponding” the only solution is to kill Reaper with the task manager.