vlc vs mplayer vs mpv vs other?

I think that OP should just compile VLC from ports, with every single knob turned on. I do that. And I discovered that if I do that, VLC is capable of playing anything, no need to research other players and features 😤 It can even stream from the box to your phone or let you use your phone as a wifi-based remote!
 
I think that OP should just compile VLC from ports, with every single knob turned on. I do that. And I discovered that if I do that, VLC is capable of playing anything, no need to research other players and features 😤 It can even stream from the box to your phone or let you use your phone as a wifi-based remote!
For most users watching common media in English this is basically true. The issue with VLC (and most every other media player regardless of OS) is real time rendering of subtitles that offer features beyond simple text+timing (.srt).

The appropriately named ASS format (an evolution of the old SubStation Alpha (.ssa) format) is well...ass. While it does allow for some very advanced typesetting to do things like overlay signs in real-time on top of video and do advanced text effects (e.g. fonts, colors, weights, position) rendering is broken on a variety of players in common use (including VLC) or very slow (most Windows players). Without getting too far into the weeds here mpv is basically the only player that renders such subtitles correctly in this admittedly broken standard. But that's what everyone agreed on targeting years ago because it was all we had. So use continues today even by large publishers.

While mpv and libass have their problems at least they can both render the subtitles correctly and not bring a high-end system to its knees while doing it.

The situation is so dire the W3C along with the larger streaming companies got together and tried to come up with a new standard called TTML. But it already has two versions (see: https://en.wikipedia.org/wiki/Timed_Text_Markup_Language) and almost no one is using it. Since almost no devices or software support it out of the box. So use of .ass continues.

So if you don't care about subtitles yes VLC will probably work fine for you 99% of the time. But if you're in that 1% (and a lot of people are now) it will cause issues and no one producing such content will listen to your pleas to have it fixed. They will simply direct you to use mpv or something based upon it. Don't ask me why things are like this. It has been like this since the 90s. I don't know why a certain segment of multimedia producers/providers feel the need to continue using this horrible standard.

The good news is Kodi and most popular set-top boxes have started to standardized around mpv or offer it as an option. Which mostly solves the problem when providing such content to the less technically inclined. I personally also offer the option of .srt as a fall-back in media I produce when possible. But there are very few people that do that. So your best bet is to just use mpv or something based upon it.

I do apologize for being verbose. VLC has its share of other problems related to codec support. I understand why people like it because it offers an all-in-one set-up with little configuration. If it works for you great. Just understand that no one "upstream" in content production is going to care if you send in reports of it rendering things incorrectly. That's been a long standing tradition going back decades now.
 
So if you don't care about subtitles yes VLC will probably work fine for you 99% of the time. But if you're in that 1% (and a lot of people are now) it will cause issues and no one producing such content will listen to your pleas to have it fixed. They will simply direct you to use mpv or something based upon it. Don't ask me why things are like this. It has been like this since the 90s. I don't know why a certain segment of multimedia producers/providers feel the need to continue using this horrible standard.
I do care about subtitles - and I do know that sometimes subtitles don't render great. But what I'm discovering is that it often boils down to file format and properly specifying how it gets rendered.

I've seen animes with pretty crappy-looking subtitles. They appear crappy no matter which player I use. And yes, I know the difference between hard (embedded) subtitles (like in .avi/mp4 files) and soft subs (like in .mkv files). I've been on the scene, learning to appreciate what makes good vs crappy subtitles for a while, since 2003. And things have improved for even real-time subtitling, and no, it doesn't take a very beefy machine any more.

Once again, if you think VLC doesn't support some kind of newer codec or renders some subtitles improperly - that's because your copy has been compiled without proper support for them. FreeBSD and other packagers tend to prepare pre-compiled stuff with very minimal options. I had problems with such conservative approaches on Linux, but only after coming to FreeBSD, was I able to turn on support for EVERYTHING, and have it work like a champ.

At this point, it's easier to continue this debate with screenshots of crappy sub rendering vs. good samples.
 
Every time I try Kodi on a crippled computer (Amazon Fire, Apple TV, Chromestick) I get video and audio out of sync. Not inspiring confidence.
Yeah, and that's why I stick with VLC no matter the platform (Apple, Win, Mac, whatever). VideoLAN devs seem to have figured something out, after all... 🤷‍♂️
 
my bad

the man page for vlc doesnt mention user-agent and referrer
but it is listed with the following command

Code:
vlc --longhelp --advanced

Code:
 HTTPS input (access)
      --http-continuous, --no-http-continuous
                                 Continuous stream
                                 (default disabled)
      --http-forward-cookies, --no-http-forward-cookies
                                 Cookies forwarding
                                 (default enabled)
      --http-referrer <string>   Referrer
      --http-user-agent <string> User agent

i used to used mpv and vlc as external players for kodi
and kodi has some urls that sometimes require a custom http header

vlc doesnt support custom http headers whereas mpv does
that was the issue

 
Every time I try Kodi on a crippled computer (Amazon Fire, Apple TV, Chromestick) I get video and audio out of sync. Not inspiring confidence.

You can set mpv to be the default player for kodi
for both local files and internet streams

not sure about set top boxes if you can install mpv,
but works with a regular computer or a raspberrry pi

create the playercorefactory.xml at this location

Code:
~/.kodi/userdata/playercorefactory.xml

with this code

Code:
<playercorefactory>
 <players>
   <player name="mpv" type="ExternalPlayer" audio="false" video="true">
    <filename>mpv</filename>
     <args>"{0}"</args>
     <hidexbmc>true</hidexbmc>
   </player>
 </players>
 <rules action="overwrite">
   <rule internetstream="true" player="mpv"></rule>
   <rule video="true" player="mpv"></rule>
 </rules>
</playercorefactory>

open a video file or link on kodi and it will play with mpv

my kodi videos which i had to take down from youtube

they kept getting removed 7 years after i uploaded them
and then youtube would give me a strike as well

 
On an Apple TV?
i was just re edit the post above, but you beat me to the punch
bit like the tyson fight

to say not sure about apple tv

another thing you can do is multicast a video from kodi to all the devices on your network


 
Back
Top