Originally Posted by vitalker
Well, it's rather a bug.
I was going to put it under the Reaper Bug Reports section until I read this....
*What is a REAPER bug anyway?
+ Native Reaper functions misbehaving (used to work on previous version, unexpected change in behavior of that function, obvious regression)
+ Reaper crashes (without involvement of 3rd party software, crashing module is a part of Reaper.)
It doesn't really fall under either of those two categories exactly so I put it here...