I would take off the servers, multiple libraries, zones, user defined fields, video, TV, handheld support, camera connection, some of the tools, some of the DSP studio and simplify the search, playlists, tree and view options.
Okay, now
this I could see... When this thread started, I though the complaint was about bloat and feeping creatures. Meaning, broken stuff. Usability is a different beast entirely.
I wouldn't personally be interested in using it, but I can at least understand where you are headed with this idea. A player for Mom with the capabilties of MC. While I now can see that the idea has definate merit, I can still see three major problems with it:
1) How would you
actually go about designing the UI so that it would be FAR simpler to use (ala iTunes), yet retain some of the power and customizationability (is that a word?) that makes MC so valuable?
2) If you are proposing (and this was unclear above) that JRiver give this MC Lite away for free, how would you propose that they justify the massive expenditure it would require to maintain two separate products?
3) Competition. Currently MC has the benefit of being FAR more advanced than the other "free" players out there, which keeps them from being in direct competition with the heavyweights (Microsoft and Real for example). It looks to me like Microsoft, Real, and Apple are going to go head to head Netscape-style (or Quattro Pro or Wordperfect or whatever) in a Media Player war. I hate it, but I wouldn't bet on a little guy escaping unscathed (especially giving products away for free).
Relating to point 1... Many of the things you mentioned you would remove are definately "advanced" features (and wouldn't be needed by the user you are targeting with this MC Lite). However for the most part they also are more "behind the scenes" type of features and are things that you need to go looking for (for the most part - excepting video support). Removing those features wouldn't go very far towards making the UI cleaner. Now, you mentioned "simplify the search, playlists, tree and view options" but didn't really say how you would go about this. Since you convinced me, I'm now trying to envision what this MC Lite would look like (and whether my mom could really use it).
Relating to point 2... I know the plan would be to use the codebase from MC "Pro" to develop this potential MC Lite which should (if it works) relieve a bit of the additional cost of launching a new product. However, raw back-end coding is only a small portion of the cost of launching and maintaining a product. Especially if you gave it away for free (or vastly reduced cost), you are going to get far more of the "AOL Effect" (meaning mindless support inquiries from people who need to RTFM, weird system configurations, spyware/virus problems blamed on JRiver, etc, etc). Plus, there's servers (for the download locations), bandwidth, marketing, and administration (of all the new people you'd need to hire to do the above stuff - they'd need bosses). This leaves two options that I see... 1) charge
more for MC Pro - or - 2) charge a similar amount for MC Lite to what you charge for MC Pro (since it already isn't very expensive). Neither option is particularly palatable.