Scaler 2 crashing Reason 13

Scaler 2 is crashing Reason. I sent them the crash log and their development team confirmed it was Scaler 2 causing the crash

Reason 13
OS Sequoia 15
Mac Studio M2 Ultra
192 Ram

Hi @lynnfield72 we’re not having any issues using Scaler 2 in Reason 13 on a Mac Studio running Mac OS Sequoia. Would you mind confirming a few things:

  1. Are you running the latest version of Scaler 2 which is version 2.9.1?
  2. Does this happen whenever you try to load the Scaler 2 plugin or does it happen after any specific event?
  3. Have you tried using both VST2 and VST3 versions of Scaler 2 in Reason?

Hi Tristan

Yes 2.9.1, I’ve tried both VST’s, nothing specific causes the crash. Would it be helpful if I send the Reason crash report?

Ian

Just to confirm, you are able to load the Scaler 2 plugin in Reason without crashing?

If so, does it seem to randomly but consistently crash at some point during use? Or are you doing anything in particular at the point of crash?

Any more specific details you can provide would be useful as we are unable to reproduce this and Scaler 2 has now been superseded by Scaler 3.

Hi
Yes it loads but crashes after a few minutes, no particular point or action causes the crash, it also happens with no other plugins in the rack.

Reason-2025-05-26-200240.ips.zip (23.1 KB)

I forgot to add, I thought I’d try Scaler 2 because Scaler 3 is pretty much unusable in Reason, because it crashes so much!

Hi @lynnfield72. I did not realise you were having existing issue with Scaler 3 and Reason. Very odd that both of these plugins are causing issues for you. Scaler 2 has been around for a long time and is generally very stable. We aren’t aware of any issues with Reason.

There has also been quite a bit of testing done with Scaler 3 and Reason 13 on Mac OS 15 and no issues have been discovered. The primary issue we have found potentially causing crashes with the current v1.0.7 of Scaler 3 regardless of DAW relates to the Scaler 3’s template presets. These will be updated in the Scaler 3.1 update to resolve this so for the moment we suggest always starting from a blank session in Scaler 3 rather than a preset.