Reaper 5.965 Crashing: A Comprehensive Analysis

In this article, we will delve into the issue of Reaper version 5.965 crashing and explore the various factors that contribute to its stability. We will also examine how different hosts handle automation recording and manual slider movement.

Firstly, it is worth noting that Reaper 5.965 has proven to be extremely stable even under heavy load conditions. I tested the software by creating multiple instantiations of the Gain slider with automation recording enabled, and then manually moving one of the sliders while observing the audio and animation. The results were surprising - the audio seemed to lag behind the manual movements of the slider, with no correlation between the two.

Interestingly, Cubase slowed down the frame rate of the animations for the automation recordings, giving the impression that the slider was moving slowly. However, when I manually manipulated one of the sliders, the animation followed my movements at a much faster pace. This suggests that there may be some underlying issue with the synchronization of audio and animation in Reaper.

Despite these findings, I did not encounter any crashes during my testing. In fact, Reaper 5.965 remained stable even when I used multiple instantiations of the Gain slider with automation recording enabled, as well as manually moving one of the sliders. This suggests that the software is capable of handling heavy load conditions without crashing.

In contrast to Reaper, Cubase Elements 10 version 10.0.10 proved to be just as stable during my testing. I used multiple instantiations of the Gain slider with automation recording enabled and did not encounter any crashes. This suggests that both Reaper and Cubase are capable of handling heavy load conditions without crashing.

One common issue that arose during my testing was the deletion of rectangles by another function. This can cause the 'end' rectangle to have invalid coordinates, leading to unexpected behavior. In some cases, this can even cause the software to crash.

To mitigate this issue, I tried commenting out lines containing CTextEdit in the file again.uidesc. While this did eliminate one type of crash, it did not solve all of the problems. Further investigation revealed that the most common symptom of this issue was a crash caused by looking at line 1926 of cframe.cpp.

In conclusion, Reaper 5.965 has proven to be an extremely stable piece of software, even under heavy load conditions. While there may be some underlying issues with synchronization between audio and animation, these do not seem to affect the overall stability of the software. In contrast, Cubase Elements 10 version 10.0.10 also proved to be stable during my testing.

It is worth noting that Samplitude Pro X3 Suite was more difficult to crash than Waveform 9, Mixcraft 8 Pro Studio, and VSTHost by Hermann Seib. Using the VS 2017 debugger attached to the Samplitude process, I was able to cause the software to crash using multiple instantiations of AGain.

In this article, we have covered the behavior of various hosts with AGain from VSTSDK 3.6.12, including my findings for hosts other than those mentioned by Will. While there are some underlying issues that can affect the stability of the software, Reaper 5.965 has proven to be an extremely stable piece of software, even under heavy load conditions.

Reaper 5.965 crashing