Here we are, I tried with a portable clean version of Reaper (all default), an older one, same behavior. Definitely not a DAW fault.

It crashes both with VST and VST3 version of the plugin.

The event viewer shows "Faulting module path: C:\WINDOWS\System32\ucrtbase.dll" as the cause of the crash. Always the same for all the crashes, both with my custom version of Reaper and the clean one.

I'm on Windows 10 22H2.

EDIT

Oh I forgot to say I tried without loading any venue, so I don't think the problem is in the folder where the venues are located.

Hi! Please send us the crash report to support@vsl.co.at so that our developers can look at what's happening. Thank you!

@Andreas8420 said:

Hi! Please send us the crash report to support@vsl.co.at so that our developers can look at what's happening. Thank you!

Do you mean the event viewer report or should I get some log in some way?

Thank you.

I uninstalled the venues and reinstalled them in the default folder, same problem with and without a venue loaded.

The problem seems related to Microsoft Visual C++ redistributable package because the ucrtbase.dll is the dynamic link library file associated with it.

I hope I will be able to test this plugin before the demo/sale time is out. I sent a report to support as you asked.

EDIT

This is what a Reaper dev said in an older post I found doing some research: Those crashes all indicate ucrtbase.dll, which is a run-time library that is not used by REAPER. It is most likely a plugin crashing, or the system simply running out of resources.

I did another little test, if I run the plugin in Reaper as "Separate Process" or "Dedicated Process" only the plugin crashes, without crashing Reaper of course. This make me think that is a plugin fault and not a Reaper fault.

Thanks, our developers will have a look at the crash report.

Hi @DANIELE-ES, we appreciate the time you spent on creating this report, it will help us resolve the issue! stand by and follow the updates in Vienna Assistant.

@Andreas8420 said:

Thanks, our developers will have a look at the crash report.

@Sasha-T said:

Hi @DANIELE-ES, we appreciate the time you spent on creating this report, it will help us resolve the issue! stand by and follow the updates in Vienna Assistant.

Thank you,

I'll wait for you then.

I remember seeing a review of the M1/M2 chips and the reviewer ran stuff on several different DAWs and Reaper was the only one that took advantage of the GPU cores. I wonder if it's the same case in Windows and it's maxing out those resources?

@winknotes_282 said:

I remember seeing a review of the M1/M2 chips and the reviewer ran stuff on several different DAWs and Reaper was the only one that took advantage of the GPU cores. I wonder if it's the same case in Windows and it's maxing out those resources?

From what I know Reaper doesn't use GPU resources and an RTX 4090 should be enough anyway.

Here's a little update: the developers seem to not be able to reproduce my issue and no matter what I do it crashes every single time instantly. I have no other problems in other softwares I use, I really don't understand what is going on.

1. I have no antivirus enabled: still crashes;
2. I have it allowed on the firewall: still crashes;
3. I reinstalled Mir Pro 3D: still crashes;
4. I reinstalled the video drivers: still crashes;
5. I installed the Windows SDK: still crashes;
6. I tried with other ASIO drivers (I really don't know what to do): still crashes.

In summary: still crashes, there's nothing I can do.

The only solution I found in a similar recent problem from another user is that the developers of that plugin fixed the issue.

The version that makes Reaper crash for me is the ucrtbase.dll 10.0.19041.3570, this update is contained in the Windows 10 cumulative update KB5031356. Please look if you have this update installed on your Windows system.

EDIT

I uninstalled the updated and...nothing...it still crashes even with the previous version of urctbase.dll...

@Sasha T may I ask you if you are using multiple displays in your configuration? I'm not in my studio right now and I'll try once I will be, in the mean time I'm trying to understand what could be the cause of this issue. Would you like to help me doing some debugging?

I found a post that talked about some VSTs that uses GPU acceleration crashes Reaper due to a multi-displays setup with an nVidia card, especially with a 3 displays setup, I have 3 displays connected to my card.

That post says that if you run the plugin on a different monitor different from the primary one the bug appears. I did all my tests by running Mir Pro 3D GUI on a secondary monitor and the plugin in Reaper on the primary one. It seems a stupid thing but I must consider everything.

That post also states that Nahimic service seems to be the cause of the problem. I don't think I have that service but I must look into to be sure.

Thank you.

@DANIELE-ES said:

@winknotes_282 said:

I remember seeing a review of the M1/M2 chips and the reviewer ran stuff on several different DAWs and Reaper was the only one that took advantage of the GPU cores. I wonder if it's the same case in Windows and it's maxing out those resources?

From what I know Reaper doesn't use GPU resources and an RTX 4090 should be enough anyway.

Sorry I got that wrong. It's the efficiency cores Reaper uses that other DAWs don't use, not the GPU.

@winknotes_282 said:

@DANIELE-ES said:

@winknotes_282 said:

I remember seeing a review of the M1/M2 chips and the reviewer ran stuff on several different DAWs and Reaper was the only one that took advantage of the GPU cores. I wonder if it's the same case in Windows and it's maxing out those resources?

From what I know Reaper doesn't use GPU resources and an RTX 4090 should be enough anyway.

Sorry I got that wrong. It's the efficiency cores Reaper uses that other DAWs don't use, not the GPU.

No problem.

Anyway I tried what I said in the post before and nothing worked. I also installed the nVidia drivers update that come yesterday and nothing changed, everything else is working on my computer. I really don't know what to do anymore.

Hi Daniele,

We'll definitely look into this.

For now, I'd suggest to wait and then contact us to get another demo version to evaluate when we have fixed more bugs.

@Paul said:

Hi Daniele,

We'll definitely look into this.

For now, I'd suggest to wait and then contact us to get another demo version to evaluate when we have fixed more bugs.

Thank you Paul for the update on this. If you need some more help or information from me please ask I'll do my best.

I'll wait and hope that I will make in time for the introductory price before it ends.

@DANIELE-ES said:

@Paul said:

Hi Daniele,

We'll definitely look into this.

For now, I'd suggest to wait and then contact us to get another demo version to evaluate when we have fixed more bugs.

Thank you Paul for the update on this. If you need some more help or information from me please ask I'll do my best.

I'll wait and hope that I will make in time for the introductory price before it ends.

Hi @DANIELE-ES, I replied in DM