Whoa there tiger.. 
Take it easy on the new interface request angle. I'd caution to not follow the M$ approach of change because the box may look "well loved". I still have issued with the changes in the Office GUI. I laugh painfully when I see it referred to as "productivity software".
I would hope a GUI change (when ... IF) it happens gets a clear transition plan that caters for the dinosaurs in the group who belong to the "if it ain't broke don't fix it" mindset.
You are right, it definitely needs to be done in a considered way.. Maybe the option to toggle between the new gui and oldskool gui same as we swap between theater and mini view. I would imagine a new gui would take a few versions to get right, so switching between them would be good.
It wouldn't be easy to revamp the GUI but that doesn't mean it should never happen. It has to be done eventually!
It becomes a problem with all software when the developer tries to please absolutely everyone. sometimes you just have to start again fresh and concentrate on the most important features. Look at how it helped Apple when they started from scratch with OSX. It upset people but it was the best thing in the long run.
You know Im looking at this from the point of view of the music production software I use. There is a new DAW on the block called Bitwig. I can see from using it that they have designed it from scratch to solve a lot of the problems that haunt older DAWs on the market. For example its optimized for 64bit and multi-core support. It has built in plug-in crash protection. The workflow has been thought out from scratch so its really easy and quick to use. Bitwig is still version 1 so doesn't have quite as many features as the oldskool DAWs but its very refreshing to use. Compared to the older FL Studio which is now on version 11, with loads of features shoe horned in but still on the same old core. They are stuck with legacy, stuck trying not to upset anyone. Its only a matter of time before Bitwig catches up on features too, then what?
So how does that relate to MC? The main reason I use MC is because it supports Asio. when I strip it down to the basics that is the number one reason I use it, because its the best player available that supports Asio. what happens if a new fresh, good looking, easy to use music player was to be released that also supports Asio? Food for thought!
My view is JRiver should step back, think about the most important stand out features of what makes MC great then build based around that. Hey maybe even fork the software in two! Im just thinking aloud here but the overall vision is the most important thing not an endless list of features.
