Archive for February, 2012
What is FFmpeg?
Chances are you’ve probably heard of FFmpeg already. It’s a set of tools dedicated to decoding, encoding and transcoding video and audio. FFmpeg is based on the popular
libavformat libraries that can be found in many other video conversion applications, like Handbrake.
So why would you need FFmpeg? Got a video in an obscure format that every other player couldn’t recognize? Transcode it with FFmpeg. Want to automate cutting video segments out of movies? Write a short batch script that uses FFmpeg. Where I work, I constantly have to encode and process video material, and I’d never want to go back to using a GUI tool for doing this.
This post is a follow-up on Video Conversion done right: Codecs and Software, where I discussed the various codecs and containers that you can find these days. For a quick overview, I’d suggest to read this one as well, because it covers some important basics.
Now, let’s dive into the more practical aspects.
I have been using the Windows 8 Developer Preview for about 5 months or so and in order to install it on my PC, I had to create a rather small partition on my primary hard drive consisting of only about 16GB. Thankfully, a clean install of Windows 8 will fit comfortably within that space and still provide enough room for some basic utilities and drivers (of course, I do have other secondary partitions that I use for installing applications).
During the installation of a particular application, the free disk space on the partition dropped to about 28MB. One of the users over in the Root Access chat room suggested that I try filling the disk until it is completely full and then blogging about what happens – hence this article. I was a bit reluctant at first since I didn’t want the hassle of reinstalling anything if it became corrupted somehow, but since I have up to date backups of everything, I decided to proceed anyway.
Some have heard about DNS and perhaps once configured in a router without knowing what it is or how it works. Others might know it, but haven’t considered to use another DNS server than the one of their ISP. This is what I will go through in this blog post.
DNS simply stands for Domain Name System, which is a hierarchy of Name Servers that have the intent to translate host names into IP addresses on a global scale. A name server hosts and/or caches these translations. In the case where they are at least hosted, the name server is often called a “DNS Server”. If you gave the host name
superuser.com to a DNS server, it would give you an IP back. In our case, that would be something like
Out of curiosity over a question I saw on Ask Different, I created a poll on web browsers for you. My main goal is to find out why people use one browser over another. Is it actually better, or do you just use it because it’s the default browser? The survey is for users of all OSes, including iOS and Android. We will come back in a couple of weeks to post the results from the survey.
Please feel free to take the survey multiple times if you regularly use multiple operating systems. You can visit my survey on Google Docs here.
You can take a look at the final results in this Google Docs spreadsheet.
Have you ever heard of a link like http://2915189091? Don’t worry, not a shock site…
While this does not always work in every browser (eg. some versions of Firefox), it does work in most browsers like MSIE and Google Chrome. It really depends on the implementation of how the URL is parsed, Firefox seems to not go beyond our usual ways to type a URL.
This is all about how the URL is stored. Many of you know that you can also access Google through their IP, eg. http://184.108.40.206. Now let’s see how much data storage that IP requires. As one character is 1 byte for ASCII, it takes 13 bytes to store the IP address. Or with Unicode (UTF-16) you will need the double, 26 bytes. Another way to store the IP is by taking each number and storing that apart, resulting in unsigned octets from 0 to 255 which each take a single byte, so that totals out at 4 bytes.
The purpose of the Super User Community Blog is to highlight what you want to see.
We are always excited to bring new writers and editors to the Super User Community Blog; so, if you are interested in contributing, please let us know! There are various ways in which you can contribute — ranging from your own stories to product reviews, tips and beyond. Don’t be afraid that you don’t come up with an idea because we already have some ready for you, but you are always welcome to share your own ideas…
Writing a blog post is simple:
- Register at Trello and leave us a message in the Super User Blog Editor Room with your Trello user name, we’ll set up access for you so that you can see our ideas and share your progress. Consider bookmarking both links for your convenience.
- You can start writing your post while you wait, we can later import it from any format into the WordPress Dashboard. Keep us up to date on your progress, so we can give you access to our WordPress Dashboard after you have shown a first draft, as well as proof-read and schedule your final version.
- The Blog Editor Room and Trello are our main communication points about the blog, feel free to share your progress in either. Remember that we are here to help you…
- Have fun! Enjoy expressing yourself, as well as being part of the Super User Community.
From idea to draft to finished post.
Blog posts mainly develop out of ideas and questions, for some you might have to do some research. From that point on you can think up the different paragraphs you will write in a draft, then it’s a matter of writing and rewriting them. Just writing one paragraph after another might not cut it for some…
Add some nice pictures for those that are easily distracted, get at least two other editors to proof read the blog post and we’ll schedule it for you. Please note that we don’t publish blog posts immediately, but intend to spread out the posts such that we regularly have new content and they are published at an optimal time. We’ll do this for you.