Hey, thanks for replying and for your suggestions.
I tested out some scenarios with the Anaglyph plug-in as it seems to make Reaper crash pretty fast. I'm having a hard time recreating the crash in other ways since I usually work for days without it happening. So this could just be the plug-in that crashes, I don't know.
I can't figure out how to implement your suggestion:
"To isolate crashing plug-in, try to run plug-ins in a separate process (one for all or one per plug-in, REAPER preferences)."
Is that under Preferences/Audio buffering settings somewhere?
Anaglyph crashed Reaper with all kinds of drivers: WaveOut, DirectSound, and ASIO (Roland Quad-Capture).
I looked for a Reaper process still running after the crash and there was one after Reaper crashed using the ASIO driver (there was no process after crashing with WaveOut or DirectSound).
When I tried to end the process in the task manager, I couldn't end it. I tried just for funsies to right click the Reaper process and click Debug. I tried debugging it with Visual Studios (not expected to see anything I would understand) but it gave me an error message reading: "Unable to attach to the crashing process. A device attached to the system is not functioning". (
https://imgur.com/a/K2N8DAr)
I don't know what this means, as I don't know what constitutes "a device", but maybe it could be the audio interface?
With the Reaper process still running, I can still immediately re-open Reaper. If it crashed using WaveOut or DirectSound drivers, there's no left-over process and I can immediately use my audio interface driver - it's when It crashed while using the ASIO drivers and there seem to be a Reaper process running after the crash, that I can't use the audio interface again without restarting.
I tried changing the buffer size (that's under Device/Request Block Size, right?) to something larger (4096) and something smaller (128) with a project of 15 tracks with 21 Rea-effects on each track. I tried this to recreate some under-runs. It used all the CPU (110 % at times) and there were lots of audio gaps, which I understand are caused by under-runs, but no crashes.
Does that mean anything to anyone? I'm totally ready to blame my audio interface for everything and go buy a new one, but this is mostly because I need a scapegoat. Not sure how to proceed otherwise.