"offset 0000d9d1" <- I assume in oatmeal.dll?

Crashes when editing or changing patches are a known Oatmeal issue on various hosts. So this is not really a Reaper issue. No idea if it can be fixed easily by our guys, I guess the Oatmeal author could do more about it.

hi stein

not really up to speed on the error report info... just thought the offset info was what was required...

it said oatmeal as the mod, if that helps. cant remember the rest.

didnt know oatmeal has cross platform issues - so will keep an eye out for it happening again.

cheers

If you feel adventurous, you could try the latest beta/prerelease - check this thread: http://forum.cockos.com/showthread.php?t=22836

The prerelease has a way to run plugins in a dedicated/separate process (right-click the plugin name in the FX browser and select 'Run as'->Separate process'.

It's Reaper's issue. Oatmeal works just fine in FLS8 and Sonar 7 to me... Reaper is the only causing the crash when working longer sessions with Oatmeal.

Oatmeal has some known issues, there are already special cases in the Reaper code to do special stuff just for Oatmeal. Can you make sure you have the latest Reaper release (3.104), so that we are sure you have all the current special cases? If it's still a problem, can you give a way to reproduce the crash?

For what it's worth, a lot of "this plugin works fine in other hosts, so Reaper must be broken" type of problems are because Reaper tends to do more multithreaded audio processing than other hosts. Plugins that are not threadsafe may crash in Reaper but not other hosts. The known problems with Oatmeal are exactly this type of problem.

I have tried it on 3.104 and 3.105pre2, it still crashes when switching presets from Reaper's preset list, after a while. Using scrollwheel up and down to switch presets faster makes crash happen sooner. On a bright side, I don't get a BSOD anymore.

I might try it with VST bridging, but I don't like undocked view of it...


EDIT: with bridging, ran as a separate process, it crashes the bridging host too, BUT NOT Reaper. Even using Oatmeal's patch changing interface :(

i'm using 3.104 . will try and recreate crash...although evildragon seems to have found another way...

schwa- i understand that reaper is doing more multithreading stuff, but at the end of the day, it still means that that other hosts have less issues with plug crashes..so unless these plugin makers make them more threadsafe (unlikely because they are stable on most hosts) is it possible that reaper could be tweaked so that it can accomodate these plugs?

believe me, i want reaper to do well, as it is such a great program, but this issues with plugs is a BIG thing and will put off a lot of people...

Try the 3.11rc (how to get it...see my post above). It should have another fix for Oatmeal.

i would try this version but i'm trying to find the reaper.ini file... as recommended to back it up.

where is it hiding? tried a search...

C:\Documents And Settings\%username%\Application Data\REAPER

thanks evilD

oh . while i'm still on this version...there seems to be a problem with adding saved fx chains. it either comes up with a box saying error reading file or it doesnt bring up all the fx in the chain...

I'm confirming no crashes on even the fastest preset switchings after 10 minutes of anxiously spinning that scrollwheel!

Thank you Cockos!

mmm, after rebooting reaper didnt do it again...also not doing it in beta version...

"didn't do it" meaning the bug exists, or the bug is gone?

cant say. i just mean that i went through the same processes ( or as close as i could remember) and i couldnt recreate the bug..

Then it's fixed :D