Please make anki use mplayer2 if it is installed, instead of pulling the rather large dependency mplayer (which is no longer developed either).
Wouldn't that additionally require changing what executable is called? Also, this looks like an optional run-time dependency that shouldn't be pulled in through a USE flag in the first place.
From the doc: "Anki uses a program called mplayer in order to support sounds and videos. A wide variety of file formats are supported, but not all of these formats will work on AnkiWeb and the mobile clients. MP3 audio and MP4 video seems to be the most universally supported." Are you sure that mplayer2 is supported? From looking at the source, it seems that anki simply calls the 'mplayer' executable using a system call. That will fail if you only have mplayer2. Even if we patch that accordingly, it is not clear what will happen regarding integration. It would be great if you could take this upstream, that is, talk to anki developers about mplayer2 support.
mplayer2 is not "supported". You would need to patch it. The integration sucks (I looked at the source). I could use alias mplayer=mplayer2 and everything would be cool beans as far as anki is concerned. They could add support for mplayer2 by making their command = ("mplayer", "mplayer2", [args]) and trying both of them. But the program doesn't even run from the git source -- it fails with Python syntax errors with both Python2 and Python3, so I shrugged and moved on with my day. I couldn't find any bug tracking service associated with anki either.
(In reply to Alexander Berntsen from comment #3) > mplayer2 is not "supported". You would need to patch it. The integration > sucks (I looked at the source). I could use alias mplayer=mplayer2 and > everything would be cool beans as far as anki is concerned. > > They could add support for mplayer2 by making their command = ("mplayer", > "mplayer2", [args]) and trying both of them. Well, a pull request on github is one way to raise things. E-mail is another. > But the program doesn't even > run from the git source -- it fails with Python syntax errors with both > Python2 and Python3, so I shrugged and moved on with my day. It does for me with no problems. Did you run tools/build_ui.sh? > I couldn't find any bug tracking service associated with anki either. I agree they are not the most open project out there.
