This entry was designed to act as the clarification of the codecs that are currently supported on this site. We feel it is necessary to break this off into its own individual entry similar to what we did for 7-Zip so that anyone who is new to our site can understand what is happening here.
So now it’s time for the state of the blog 2020 edition. Where we tell you some of the things that have been happening here at s-config.com and where we intend to move into the future here.
This quick guide goes through some of the details on how we convert some videos using FFmpeg. The video conversion is really important for those who are hosting their own files and not relying on a third-party site such as YouTube or Vimeo because you are looking for the most compatible video standards that offer the best quality at the lowest bandwidth so that not only your server is happy but the users that visit your site.
FFmpeg is awesome in respects that since it’s open-source it’s a binary that can be compiled on a remote server that you own and begin converting videos on the spot if necessary and if you have the CPU power to do it.
You could even run FFmpeg on a Raspberry Pi if you wanted to wait a few years for the results!
The real drawback is FFMpeg is a pure command line with no GUI which may scare some people away. But the fact that it’s not GUI also means that it can run on just about any modern OS in the world. We have other blog articles talking about GUI video conversion later on for those who are interested.
Since I did a blog about WebP minus well do one about WebM. As some of you may know that I run a hybrid video/regular blog we use WebM because it’s the latest and greatest. Back when I was running with the Angular theme that included its own version of MediaPlayer.js and all was good because the WebM files were being referenced first and foremost. That changed when I reverted back to a more standard WordPress theme that relied on the out-of-the-box MediaPlayer.js which is totally fine except for one problem.
Default WordPress HTML5 video player grabs MP4’s first. Not WebM.
The MP4 files issue goes into a licensing issue that prevented all of the codecs from being compiled into XBMC for ouya (Currently version 12.3 Frodo). Since version 13.x Gothan XBMC has changed its name over to the new platform KODI. If you point your Ouyas Browser over to the New Kodi homepage for downloads and select the Android ARM version. You can download the APK and side-load without the need of rooting your Ouya. The version direct from KODI will upgrade the player to version 14.x helix (At the time of this posting) and you will regain access back to playing videos upon it once again.
We are going to use the Razer Keyboard key-test movies as the test as they are the shortest and the the blog entry it pertains to has it streaming in multiple parts of the before and the after. All FooBox scripts are disabled on this page leaving only WordPress to handle everything here. This page serves as documentation of self-hosted video files and how a player should behave at its base level.
