I agree, it takes a bit of knowledge to make it work right with the multiple tools involved.
A bit?!? hehe, I think you underestimate your knowledge in this area. the general public has NO IDEA what any of this is
It seems that as part of v16, JRiver will be working to make this easy for the "out of the box" experience.
it does, and I hope we're correct in thinking so
But, I think you've missed my point re: FFDshow as the container formats. If you use FFDshow, by making the Coded Settings as I listed, all you need is FFDshow to decode all 3 of the formats which may be in the MKV container. There is no need for another decoder.
You're correct, I did miss your point, and in re-reading, I see what you're suggesting, and it makes more sense now. However, I think that just strengthens my 'argument' for making it easier.
I have a bit over an 'average' working knowledge of this stuff (ignoring those that have NO IDEA about it), and it's still not a straight forward setup process.
In addition to needing to configure MC to use FFDshow (there are SEVERAL FFDshow options to choose from in MC's selection drop-down), one then needs to get into the guts of FFDshow setup to get those settings applied/configured, which isn't the easiest thing to do either, plus you still need to deal with subtitles, and chapters, and audio configuration! AND, one has to do this with the knowledge of what to do already in place, there is NO HELP in making this work (inside MC; this forum is great).
It just seems to me there are a few (very few?) ways this *can* work, so why provide 30+ options, each needing to be configured separately, when most are unnecessary, and just muddy the waters?
I fully, completely trust the MC developers to know what works well/best in MC to playback my media, and would think most people would also, and just let MC "make it work" for us. Yes, having the ability to tweak is great, and *some* people will want to customize everything they can, and this should still be allowed, but not *necessary*, in my opinion
It just seems a big waste of time to force every single user to do all of this setup work themselves, when the devs already know what works and how.
MC must know what filters are available on a system, or it couldn't use them to playback, so it seems that MC could/should just look for the filter that works "best" and use it, without involving me, and if it can't find that filter, go to the second "best" choice, and so on. if/when it gives up searching, ask the user for guidance in finding what they wish to use, or MORE LIKELY, suggest they install whatever works "best", and help them do it where possible.
forcing users to rely on this forum (and thorough searching) to find the answers and get this all working just won't work for 90% of the users, they will just install something else that doesn't make them go thru all this. I think that's a bad thing for everyone involved, as MC loses customers, and those customers are forced to settle for an inferior product, for simplicity's sake.
For example, it's way easier to just install MPC player and play a file, and everything works; easy. In fact, I'm using it by default because I usually don't want to mess with MC to play a movie. I REALLY don't want to continue doing this, but it works, and I can spend my time on other stuff.
I would say this same line of thinking applies to audio as well. Why do I need to tell it to play at 48k or 44.1k or 96k or to convert to something else, or not, or whatever? I want MC to send every media file to my receiver/pre-amp/speakers at the highest quality possible, with the least amount of processing possible. the devs know the best way to do this, why ask me??? yes, allowing people to tweak/adjust is great, but it shouldn't be *necessary* for me to mess about with this stuff.
Again, I'm not complaining, just trying to help guide development towards areas where I see the possibility for improvement.