Matt,
yes, I was bragging about this (loading all active content in memory) last year on several occasions smile

I was thinking, How is the mechanism of previewing first 4 bars on style picker works? Why is it so fast? Can it be any random "4 or more bars"? Can the same technique be used to generate selected bar group, without regenerating whole song in the program itself?

Honestly, I think audio file handling architecture has to be re-thinked as a whole, giving high ceiling headroom for future development, not just squeezing "features" into it.

What bothers me the most, is that BIAB has fantastic library of Real styles and drums. It has the logical concept, which is also very strong, but implementation of some key features, GUI and general workflow is very cumbersome compared to most modern day music software titles. To me, re-generation time is also a big contributor to the negative factors of workflow. So why does it bother me so much? I just do not want to be in the same scenario as some of us were faced with Cakewalk not long ago. We, people who got attached to it on personal level, got lucky that Cake was preserved and greatly improved over the past year+ (Thank you Meng & Noel!), but it could have taken completely different and dark salvage path. I just do not want to be faced with similar scenario with BIAB, at least not anytime soon.

PG crew, please put some love into the program, not just some random screws to hold it in place. It deserves better!

Thank you.