==>3.03 pre bugs <==

Strange performance problems 

I'm not sure if this is a "feature" or bug, but to me it seems definitely ill behavior. I have a special performance testing project, where I've got lots of tracks at 32-bit / 96k, and Reacomp Standalone Instances running with 64x antialiasing setting. Reaper 3.03 suffers from elevated CPU usage. When looking at the image below, you can also see 2 instances of Reacomp (12 & 18) which seem to be using a lot more CPU than others. However, their settings are identical. This behavior doesn't happen with Reaper 2.58, neither with 3.00 (although generally it consumer more than 2.58).

strange left click bug 

Not sure how to describe this, but after completing an online render my mouse no longer works in the docker ( which i have on a separate screen )and on the main transport controls. Reaper still runs normally other than this and is back to normal again when i close and re-open ( that is until i do an online render again ) winXP sp2, RMe FF400, Intel Quad, Liquid Mix etc etc. FX wet/dry thingy is bloody marvelous though, and no more external midi drop out. cheers Pendle

bad badness 

I can click on things in the edit window, and sometimes in the track list. But any buttons, such as transport or anything in the mixer, I click, nothing happens. Heres a vid. ~RobRokken.

Ah ok, that has already been fixed for the next build.

A small nitpick: it would be nice if the resampling algorithms in the dropdown boxes for playback and rendering are sorted from worst to best.

I've got crashes. Don't really know what to upload, because it's one of those fun crashes where the program just decides to turn off. It's fine one moment, and I tell it to do something really simple (clicking an item, for example), and the program just disappears. No complaints, no crash notice, nothing. Just gone. edit: it seems to like to do it during playback. My RAM usage is high (1.5GB of 2GB in use), but CPU usage is low. It seems okay now that I've taken some of my effects offline, but maybe you guys should look into this? I've dealt with it going ridiculously slow (since that's what happens when you overload your resources), but the amount of resource usage was small enough where this wasn't the case.