Reaper crashes...

derbeerko · 10-27-2009, 01:13 AM

Reaper crashes too often

(( How do I figure out the reason why?

Fabian · 10-27-2009, 01:39 AM

Quote:

Originally Posted by derbeerko

How do I figure out the reason why?

This is the most important thing. Just saying that Reaper crashes is help to no-one...

Assuming you are on XP... Start by looking in the Event Viewer (Control Panel > Administrative Tools > Event Viewer).

stupeT · 10-27-2009, 02:38 AM

Quote:

Originally Posted by derbeerko

Reaper crashes too often

(( How do I figure out the reason why?

Work with REAPER without *any* foreign VSTs. Do use only these Rea-FX. If it is still crashing check your drivers or general system, like faulty memory etc...

Most probably REAPER will not crash anymore without the VSTs. If so, load and test one after the, slowly... only keep the VSTs which are 100% OK...

servachog · 10-27-2009, 02:48 AM

I always wanted to ask is there list of 100% ok VSTi/VST?

dub3000 · 10-27-2009, 04:14 AM

Quote:

Originally Posted by servachog

I always wanted to ask is there list of 100% ok VSTi/VST?

depends on the system. and any VST (or host) will crash if you run out of RAM.

basic guideline is: anything synthedit, or ancient and free, is probably a tiny-bit dicey. best to have those ones running in a separate process (search the forum) so they don't take reaper down if they crash.

schwa · 10-27-2009, 06:57 AM

If you ever get a crash, the most helpful thing is if you can do what is suggested in this post: http://forum.cockos.com/showthread.php?t=36653

If we get all of that information, we can usually pinpoint the cause of the crash quickly.

whatsup · 10-27-2009, 07:05 AM

Quote:

Originally Posted by Fabian

This is the most important thing. Just saying that Reaper crashes is help to no-one...

Assuming you are on XP... Start by looking in the Event Viewer (Control Panel > Administrative Tools > Event Viewer).

no such thing here
can you post a screen shot please

dub3000 · 10-27-2009, 07:37 AM

Quote:

Originally Posted by whatsup

no such thing here
can you post a screen shot please

right-click 'my computer', select 'manage', 'event viewer' should be near the top somewhere.

whatsup · 10-27-2009, 07:44 AM

thank you, now found it.

derbeerko · 11-07-2009, 05:06 AM

Crushed again and there was no event records in that log. That seems because after crashing, reaper hanged in Task Manager as process (reaper.exe) and I could not even make it close. But after about five minutes it disappeared from task manager and in event log appeared this record

-------------------------------------------------------------------
Тип события: Предупреждение
Источник события: MA_CMIDI
Категория события: Отсутствует
Код события: 54
Дата: 07.11.2009
Время: 12:38:08
Пользователь: Н/Д
Компьютер: SERVACHOG
Описание:
Не найдено описание для события с кодом ( 54 ) в источнике ( MA_CMIDI ). Возможно, на локальном компьютере нет нужных данных в реестре или файлов DLL сообщений для отображения сообщений удаленного компьютера. Попробуйте использовать ключ /AUXSOURCE= для получения этого описания, - дополнительные сведения об этом содержатся в справке. В записи события содержится следующая информация: \Device\evolmacmidi-0.
Данные:
0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 00 00 00 00 36 00 04 80 ....6..€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

dub3000 · 11-07-2009, 05:14 AM

Looks like something to do with m-audio midi driver. Search forum for MA_CMIDI, I think someone else had this problem and solved it.

derbeerko · 11-07-2009, 05:20 AM

Search for MA_CMIDI gave only two threads: this one current and this one http://forum.cockos.com/showthread.p...ht=MA_CMIDI#33

Both with no solution

Fabian · 11-07-2009, 05:47 AM

Quote:

Originally Posted by dub3000

Looks like something to do with m-audio midi driver.

Yesterday I had a crash that I think (from viewing the event log) had to do with my M-AUDIO MidiSport 2x2 driver. Reaper just vanished (from the screen) but the process hung around for awhile until it finally just disappears. I got ProcessExplorer started but the Reaper process quit before I had time to jot down any of the PE info. Only this morning did I think of looking at the event log, that's why I say that i think the crash had to do with the M-AUDIO driver; there were entries in the event log about MididSport complaining.

My event message looks almost exactly the same as the one above (though not in Cyrillic alphabet

).