So I recently made over the switch to Reaper and have been customizing a template for my band's upcoming full length. While I haven't learned everything yet like I do with my old DAW, I am coming across an issue that is a real pain in the ass. The audio (ASIO) driver is disabled every time the main Reaper window is not selected. Adjusting audio settings, preferences, listening to reaper in the background is impossible, but it gets worse. Having a 64-bit OS with 8GB of memory I opt to use 64-bit reaper. While opening and tweaking with FX based pop up windows don't cause a drop out, but the 64-bit bridge pop out screen causes Reaper to disable the audio driver/engine. Kind of annoying when you have to go back and forth between tweeks and listening to the effect. Its actually not a drop out though, as soon as Reaper is in the foreground again it plays back where it left off, its pausing itself when its in the background, and apparently an x86 bridged effect puts Reaper in the Background. Its not the ASIO driver, it is still up and running, Reaper's audio engine disconnects itself from the ASIO driver when it isn't in the foreground. My old DAW Sonar did this but there is a setting that allows the engine to work alongside other audio applications and will run in the background, I have looked around in the preferences for a setting that will always keep the Reaper's Engine on regardless if it is background or not. Maybe someone can help, using ASIO4ALL for the ASIO driver, latest version for Win7 64-bit. Also is there a way to prevent the x86 bridge from having is own pop out window, the two separate windows and not being able to tweak 32-bit effects in the main FX window is annoying. EDIT: And it looks like Trigger isn't recognized, reset and re-scanned twice and not showing up in the FX menu. It scans it during the re-scan, wonder if its crashing when being scanned. EDIT again, not just slate, all my iLok FX. Seems to be working just fine in Sonar, Reaper have a problem with scanning iLok FX or something?