If there were a compelling advantage to re-writing BIAB as a 64-bit app, I would jump on the bandwagon, but actually I see none (except for plug-ins) which appears to be inexpensively rectified. I am not a big plug in user, personally.

I would prefer to see resources spent on modernizing the UI, and making it more cutomizeable , adding Music XML or enhancing the notation (which Music XML would satisfy.)

The new Realtracks, etc. are great, but I don't consider them FEATURES per se compared to changing the functionality of the base code. I would really never tell the difference between running 2014 and 2015.

Demanding 64-bit just because this "is the 21st Century" is not a valid argument IMO. If it does not enhance the speed or usability of the base program, it is nothing more than "bragging rights." I never see BIAB swapping to disk because it is running out of RAM.

Really, the program does more than I ever need (for its intended purpose.) Again, all I would ask is more user-customization to fit various scenarios (live performance vs. composition etc.)

Jan - 12 Core AMD Ryzen 9 3900X
32GB DDR4
Win 10 64-bit
Samsung m.2 SSD Boot drive,other SSD internal and USB drives.
MOTO 2
Ketron SD4,SD1000
Yamaha RX-v381amp
VB-Audio virtual cables