FX chain problems: bug or not?

two VST plugins resist change and crash REAPER (2.58) when moved or removed from a an FX chain. They are vnoPhones and Kufinkle's (spelling?) SIR impulse reverb convoluter. Does anyone know if the problem is with these two plugins, or with something else. REAPER is in stopped mode when I try to move/remove them.

Welcome to the forums! I just tried vnoPhones and I can move/remove it all I want. I don't have SIR but I know that some here use that. Sometimes a combination of plugins doesn't play nice with each other and leads to issues like this. - Can you create a little example project that has this behavior, upload it to and post the link? - Can you post the crash log? You will find it in Event Viewer: [XP] Go 'Start Menu->Run' and type EVENTVWR <Enter>. In Event Viewer, open the 'Applications' branch and look for the latest "Error" entries. [Vista] Basically the same, you probably have to use Search to find the "Run" window though. Alternatively go 'Control Panel'=>'Administrative Tools'=>'Event Viewer'. The Vista Event Viewer has more branches, go 'Windows Logs'=>'Application'. Creating a fresh crash may help you finding the right error entry if there are too many of them. It should contain a crash log with the faulting module and the fault offset. Post both please.

I'll try to put one together in the next day or so.

whatever error info I could gather. 

I will concentrate on the VNoPhones problem. It is easier to reproduce. I am running REAPER v2.58. I got VNoPhones from File Name: VNoPhones.dll Size: 80,896 bytes Size on disk: 81,920 bytes I put the VNoPhones dll in its own directory. In REAPER: I went to Options -> Preferences -> VST then erased the VST plug-in path clicked on "Clear cache and rescan directory" then entered the directory with the VNoPhones dll as the only dir in the VST plug-in path and clicked once more on "Clear cache and rescan directory." This froze REAPER. Here is what I can gather from the Vista event viewer: General: Faulting application reaper.exe, version 2.5.8.0, time stamp 0x49beb951, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id 0xe90, application start time 0x01c9d37bb954cc27. Details: (friendly view) - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2009-05-13T03:37:02.000Z EventRecordID 19411 Channel Application Computer Owner-PC69 Security - EventData reaper.exe 2.5.8.0 49beb951 ntdll.dll 6.0.6001.18000 4791a7a6 c0000374 000b015d e90 01c9d37bb954cc27 (XML view) - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-05-13T03:37:02.000Z" /> <EventRecordID>19411</EventRecordID> <Channel>Application</Channel> <Computer>Owner-PC69</Computer> <Security /> </System> - <EventData> <Data>reaper.exe</Data> <Data>2.5.8.0</Data> <Data>49beb951</Data> <Data>ntdll.dll</Data> <Data>6.0.6001.18000</Data> <Data>4791a7a6</Data> <Data>c0000374</Data> <Data>000b015d</Data> <Data>e90</Data> <Data>01c9d37bb954cc27</Data> </EventData> </Event>

So did I get that right, you get these crashes with VNoPhones as the only plugin in the project? By coincidence I tried to reproduce that in Vista SP1 as well and it didn't crash. The error message looks more like something underneath Reaper is going wrong, maybe a driver and/or OS related problem. 3 things to narrow down the issue: 1.) Clean configuration - Backup your Reaper user folder ( C:\USERS\<username>\AppData\Roaming\Reaper ) - Start Reaper with a clean configuration: Go Start->Programs->Reaper->Reaper (reset configuration data to factory defaults) 2.) Check other driver models - Check if that problem persists when you use a different driver model in the Reaper prefs. After you did 1.), Reaper will come up with the standard Waveout driver selected, check WDM as well before you set it to your ASIO driver again. 3.) Check a different device - What is your audio interface? Try onboard sound with ASIO4ALL instead.

3) by itself did not help. I will try 1) and 2) tomorrow. Too late now. And yes, I was bringing in VNoPhones as the only VST (or at least trying to).

sequence of button clicks worked 

Glad you got it working so far. Which is odd, since the two "save" options you mentioned are not related to the scan and cache options AFAIK. This makes me think that a borked .ini may be (or have been) the problem. If the problem returns or another one comes up, you know where you can find us... :)

bad .ini not likely