198,768 users have contributed to 43,134 threads and 258,840 posts.
In the past 24 hours, we have 3 new thread(s), 14 new post(s) and 58 new user(s).
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.
@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
