Apparent false alarm with FS plugs and Reaper's bit bridge

[RJHollins]

I'd do the memory test .....

..... but I forgot what it is.

[noisenerd]

But again, I just want to see the issue solved. So, if it turns out to be a faulty Reaper version you're using, that's fine with me as well.

Right on, I do appreciate you trying to help! Hope I didn't offend, words are not my strong point. I agree with you that memory problems tend to be anything but regular, and that's just it: I generally don't have any problems... but like I said, it can't hurt. I only mentioned Linux because you don't seem to have much faith in the built-in Windows utility, and I'm not familiar enough with it myself to say otherwise, so I'm gonna stick with stuff I know. I'm pretty new to Win 7.

I'm leaning more & more towards something in the file, and thinking any previous SM/FS plug troubles were coincidental/caused by other things. It just seemed odd that it was the all-FS project that went kaput. I've still had no trouble with the new file I mentioned that has all the same plugins loaded. However, if I load up the problem project, it ends up crashing every time, usually when trying to bring one of the offline plugs back online.

If the mem test shows no problems, I'm gonna see if there's any plugins in the bad project I can get to come back online, and go from there I guess. If nothing else, I might try recreating the original project in a new file.

I'd do the memory test .....

..... but I forgot what it is.

I see what you did there...

[tulamide]

You got me wrong. I was trying to say that it doesn't matter for me what the real cause is, as long as we can narrow it down. So, no worries!

[noisenerd]

You got me wrong. I was trying to say that it doesn't matter for me what the real cause is, as long as we can narrow it down. So, no worries!

Cool, just making sure. So far so good btw... overnight mem test turned out ok. Played around more with that test project, and still no trouble.

Fluke? Gremlins? Operator error? I don't know, but it appears that it was indeed a false alarm. Thanks again to all of you for the help and confirmation that it wasn't Reaper.