EZD2 Crash upon plugin scan in Reason (Monterey)

[Teloch]

MacBook Pro M1Max
Monterray 12.01
Propellerheads Reason 11 Suite 11.3.9d22 (Build 12405)

It freezes Reason whenever I start the program, it scans for new plugins and freeze at the EzDrummer plugging. I have to disable it to load up Reason proper.
EZD App works fine as stand alone.

I tried uninstalling everything about 6 times here now (via Product manager and manual deleting files in 3 folders there was ezdrummer files) and reinstalling, rebooted every time.

My install steps has been:
Product Manager
EZD2 2.1.8
EZD2 2.2.2 Update

No crash log created in the logs, but attached some screenshots of what Im seeing.
Any idea? I know Monterey is not supported yet, but maybe you have some workaround trics

Cheers!

T.

EZdrummer version: 2.2.2
Operating system: macOS Monterey (12)

Topic

[Olof]

When it is frozen, please use Activity Monitor (in Applications > Utilities) to save a sample of the Reason process.

Olof Hermansson - Toontrack
Coder

[Teloch]

Olof wrote:

When it is frozen, please use Activity Monitor (in Applications > Utilities) to save a sample of the Reason process.

EZdrummer version: 2.2.2
Operating system: macOS Monterey (12)

[Teloch]

Olof wrote:

When it is frozen, please use Activity Monitor (in Applications > Utilities) to save a sample of the Reason process.

Oops, here

[Olof]

Okay sorry, Reason apparently scans plug-ins in a separate process, because EZdrummer was not loaded in the Reason process there. Look for the process “PlugInspector” in Activity Monitor instead and save a sample of it.

Olof Hermansson - Toontrack
Coder

[Teloch]

Olof wrote:

Okay sorry, Reason apparently scans plug-ins in a separate process, because EZdrummer was not loaded in the Reason process there. Look for the process “PlugInspector” in Activity Monitor instead and save a sample of it.

I don’t have any process named that afraid

Thanks for looking into this for me Olof

[Olof]

Hm, are you sure there is no crash log then? You can use “Go > Go to Folder” in Finder to go to ~/Library/Logs/DiagnosticReports/ (because this Library folder within the user home folder is hidden).

Olof Hermansson - Toontrack
Coder

[Teloch]

Yes I checked that folder before writing you guys. Attached image of latest events in that folder

[Olof]

All right. I think you’d better contact Reason support about this. Include the Reason sample text and say that there’s no PlugInspector process and no crash log.

Olof Hermansson - Toontrack
Coder

[Teloch]

Copy, cheers and have a nice weekend!

1

Thanked by: Olof

[Teloch]

No dice there, they are still testing Monterey.

One thing though, been meaning to upgrade to Superior drummer 3 for some time now, do you think I would run into the same problem with that?

[Olof]

Teloch wrote:

No dice there, they are still testing Monterey.

One thing though, been meaning to upgrade to Superior drummer 3 for some time now, do you think I would run into the same problem with that?

Unfortunately it’s quite possible you would have the same problem with SD3, since I don’t know what could be causing this issue with EZD2 in Reason. We haven’t found any problems with EZD2 or SD3 on Monterey (except in Pro Tools but turned out to be because the current Pro Tools version is not compatible with Monterey).

Olof Hermansson - Toontrack
Coder

[Olof]

We’ve been able to reproduce the issue with Reason 12 on Monterey (and it’s probably the same with Reason 11). All our plug-ins except SD3 and EZbass seem to be affected. It’s not clear whether we or Reason need to fix it though.

Olof Hermansson - Toontrack
Coder

[Teloch]

Yessir, confirming this. Upgraded here to SD3 here now.

I got in touch with Reason last week, they are still testing Monterey so couldn’t advice.

Cheers

[Author]

Replies