2.018 crashing (SOLVED)

mr. moon · 12-15-2007, 06:44 PM

Getting the following C++ error message (see attached) when Reaper opens up; it hasn't done this with any previous version. Reaper opens to a blank project by default, so it isn't due to a specific project files attempting to load. If I re-install Reaper, it works a few times, and then begins to do that same thing again.

Any ideas?

-mr moon

SOLVED

Justin · 12-15-2007, 07:16 PM

Hmm can you PM me your reaper.ini? Also try renaming it and see if that helps anything..

Also try unsetting your VST paths.. perhaps its a VST doing it?

-Justin

mr. moon · 12-15-2007, 08:07 PM

Justin,

After restarting my system, and then reinstalling Reaper, it will boot into Reaper without any problem, until I run a specific project that I have been working on today. Once it pukes on that specific project once, Reaper then gets a bit unpredictable. If I restart the system again, it will work perfectly fine ...until I run that same project, then all heck breaks loose again.

When Reaper pukes on this project, it's always at the same point: when it's loading the VSTs. However, I can't tell which plugin(s) may be causing the problem, as they flash by too quickly.

I'm going to do some more troubleshooting, but I wanted to let you know that it's looking like it is related to a specific project and/or plugin rather than Reaper itself. Is there any way (an error log or something?) I can find out exactly which plugin may be causing the problem, other than weeding them out one at a time?

Thanks.

-mr moon

mr. moon · 12-15-2007, 10:34 PM

UPDATE:

Looks like the "Dasample GlaceVerb" VST was the root of the problem. I didn't immediately think that this plug was the culpret, as I had it included in the project for a day or so without problems. However, everything returned to normal once I removed it.

Bummer, as it is a really nice verb!

-mr moon

jhardin · 12-16-2007, 12:16 AM

A couple of us have been having the same issue in previous versions of Reaper. It seems that the C++ Runtime Error notice was a result of GlaceVerb though... not Reaper. My symptoms were identical to yours.

http://www.cockos.com/forum/showthread.php?t=15685

I have been able to circumvent the problem by opening a project template first... then opening the project that I'm having problems with. No hang ups if I do it that way.

BTW: I'd really hate to have to give up GlaceVerb too, it's perfect for the project I'm working on.

Justin · 12-16-2007, 01:49 AM

I'm sure if you bug the devs about it they can get to the bottom of it, since it seems to be reproduceable..

Have you tried disabling all forms of SMP FX support to see if that helps? Perhaps their code isnt totally threadsafe...

jhardin · 12-16-2007, 11:20 AM

I'll do that. If anyone else has had this problem with GlaceVerb you can contact them here: http://www.dasample.com/

Rah · 12-16-2007, 01:28 PM

installed reaper 2018 a minute ago...

[everything except desktop icon]

: it scans my vst but doesn't start up further.

nothing.

nada.

anybody else?

namaste
j

DID A REBOOT...
REAPER OK
WINDOWS WAS 'BEING FUNKY' FOR WHATEVER REASON
[CHANGING DESKTOP THEMES ON ITS OWN ETC. WEIRD!]

andrew grove · 12-16-2007, 03:35 PM

Hi, I was using Reaper about a year ago and just stared using it again. It used to crash back then with that same message. I found it was when it tried to load DX plug-ins and after I un-checked the "use DX effects" under DX Plug-in the problem went away. I just started geting that same error message again so once again I un-checked the DX Plug-in enable but the program is now crashing like I did not even change it. Well I reinsatall Reaper and now also checked "don't scan for DX Plug-ins and guess what Reaper is still scaning for DX Plug-ins even though I said not to. SOoooo.... my conclusion is the DX plug-in section of Reaper aught to be scraped cause it been causing proplems now for over a year that I know of. Get the Reaper to take the life from DX Plug-ins hahahahaha.

Quote:

Originally Posted by mr. moon

Getting the following C++ error message (see attached) when Reaper opens up; it hasn't done this with any previous version. Reaper opens to a blank project by default, so it isn't due to a specific project files attempting to load. If I re-install Reaper, it works a few times, and then begins to do that same thing again.

Any ideas?

-mr moon

drew · 12-17-2007, 02:49 PM

jhardin & mr. moon - using GlaceVerb version 1.01 with REAPER 2.018 here & all seems well. No unusual tweaks re use of dual core etc that i can think of. Did you get it sorted? If not, hopefully this may be helpful to know in that it's configuration dependent or related to some other factor.

spikemullings · 12-17-2007, 03:18 PM

Drew, I think the problem is multiple instances of Glaceverb, and maybe even some other plugs.

I have a project that will cope with two GV on busses OK but if I have GV as an insert on start up then it crashes about 4 or 5 times in a row. If I bypass the insert GV when last working on that project and then start up I don't get any crashes and can just un-bypass. Just got to remember each time I finish working on it (doh).