Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Faulting module name: reaper_sws.dll Exception code: 0xc0000417 #598
From svlp...@gmx.com on September 22, 2013 22:55:44
What steps will reproduce the problem? I have a error log produced by Win7. Is there any way of knowing which piece of code is responsible from these errors?
Faulting application name: reaper.exe, version: 126.96.36.199, time stamp: 0x52291d3c
What version of SWS extension are you using?
What is your Reaper version number and CPU architecture
What operating system are you running?
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=598
From svlp...@gmx.com on September 23, 2013 14:58:11
The issues had arisen when we're enumerating a large list of user variables in a loop to write midi data to Reaper's midi editor, and then giving Reaper not enough time to open and close the midi take.
We've fixed this by opening a midi take before the loop runs and closing a midi take after the loop, instead of doing it inside a loop. Hope this makes sense?
From svlp...@gmx.com on September 23, 2013 15:32:01
Here is a more illustrated example in "pseudo code". We did something similar to this.
From jeffos...@gmail.com on September 30, 2013 11:10:48
Ok, thanks for the details! Will be fixed for the next release ( r1138 ).
Also, yes, your new code totally makes sense performance-wise but it does not solve the bug being disccused here (just lowers the probability it occurs...)