Than you must stay with the mplayer plugin. One design goal is no need of this ** ** *** shell scripts.
When mplayer has problems with special streams, than fill bug reports to mplayer.
When mplayer is too stupid to know, that the deinterlacer is not needed, than fill a bug report there and don't work around the bugs.
It's not a matter of mplayer being stupid or not. There are plenty of times where the mpeg headers are incorrect and that is certainly not the fault of the user or mplayer. Of course you can take a cheap way out by saying go complain to every content provider where this is an issue, but how realistic is that? People have tried before and gotten nowhere. We don't live in a perfect world and ignoring that fact is really bad. You need to remember that all the mplayer command line options exist so that the user can set what is needed and/or what he prefers. It's impossible for a player to get it right 100% of the time and somehow know what the user wants in every scenario. I get what you want to accomplish but to achieve it you better not rely on mplayer.
Zitat
Yes it needs configuration. It requires the user create a whole symlink tree, which is more work than creating a sources list.
ZitatI thinking about using different browser roots (video/music/pictures/...).
This is actually a good idea and (mostly) eliminates the need for a sources list or a symlink tree.
In the end it's important to remember that for anything to be a serious alternative, it should be better & more functional that its' competition -- not crippled or less capable. That being said, I would like to see vdr-play improve and stick around for a while!