Encode H.264 (HTML5) video for iOS and Android, on a Mac

One would think after all these years encoding video for web playback would actually be more simple than it was in the 90’s. Sadly, it’s more complex than ever. Even though Google will be removing H.264 support in Chrome, it does still support H.264. So for now it can be used for both iOS and Android apps.

That said, there are many ways to encode H.264 video. Even if you use traditional encoding methods and stick to common tools like QuickTime 7 Pro, Adobe Media Encoder, Compressor… you will quickly notice creating one H.264 file that works in both iOS and Android is not very easy.

If you use QuickTime X and export for the iPhone – something that seems obvious – the file extension will end in .m4v which may cause playback issues in web browsers and non-iOS devices.

The solution?

Go ahead and use that Save As… iPhone option from QuickTime X. Then change the file extension to .mp4.

If you need something to help you embed the video in a webpage and help with delivering the right format to the right browser (egg Ogg to Firefox and Flash to IE8), give VideoJS a try.

WooThemes updates support forum, does things backwards

Support forums are nothing new. They exist for all sorts of projects, including just about every WordPress plugin. 99.9% of the time they are “users helping users” with the occasional response from a developer.

That’s how WooThemes handled their forum, until recently. Although their official responses were fairly common, users could still help users. Now WooThemes has overhauled their backend (dashboard), along with their support forum.

Users can no longer help users.

Why? Because WooThemes saw people were often posting to resolved threads trying to get answers. This is really common on forums. In fact, many forums will ban you if you start a new thread instead of reviving a recent one on the same topic. WooThemes thinks this doesn’t work well for them. (They also mentioned sometimes posts were creating confusion.)

WooThemes has gone and done two thing in opposition to the status quo. And you know what? It’s for the better.

Better WordPress Theme Support

The reason WooThemes has done this is because they want each and every forum question to get an official response. I don’t know of a single other product support forum that does this. Not even big companies like Intel offer this sort of support.

There are quite a few companies that promise quick response times from customer support. Really those are quite pointless. Often they’re canned responses that are sent simply to get back to you quickly. My least favorite are the one that ask you information you just provided them with like “What browser are you using?” And you already told them “Chrome 15.0.874.15, extensions off, cache flushed.”

WooThemes does things differently. Their responses are always useful. Sometimes they remind users they need more info, but sometimes that’s needed. They offer simply awesome support and not only that, but now they’ve streamlined it as well.

In the end my only complaint is that I can no longer give them a hand by answering questions or help confirm issues.

Front-end web development certification page from General Assembly has front-end development error

General Assembly (a campus for technology, design, and entrepreneurship) in New York is offering a certification course for front-end development. Their page promoting the certification program has an incredibly basic front-end development error.

Atop their page they have a link to the Schedule. The link is broken. It’s a target:

<a href="#SCHEDULE">SCHEDULE</a>

Later in the page we see:

<a id="Schedule and Application"></a>

Clearly that should be:

<a id="SCHEDULE"></a>

Website Uptime Monitoring

A year or so ago I did some research and testing of the variety of website uptime monitoring services out there. Sure any half-decent host does this as well, but sometimes a server only goes down externally and sometimes it doesn’t trigger their monitors. I also did this because I wanted to get a clear picture of just how much downtime a site might have.

Sites do go down, even if just for schedule maintenance. I wanted to see just how reliable my hosts were. Some of my hosting is supposed to be much more reliable than other hosts, and I wanted to see if I was getting what I was paying for.

When searching the first thing I realized were most all of the free or free trial offers were limited to the point of being useless. The next thing I noticed was that the paid options seemed rather expensive.

But then I came across Uptime Robot. They provided monitoring up to 50 sites – for free. They offer a number of configuration options, as well as uptime checking every five minutes which is much better than the 10-30 minutes other services offer. (I mean, really. If a service is only going to check every 30 minutes, that’s pretty much worthless. I’m going to have received a call by then.)

I’ve exchanged some emails with Uptime Robot. They helped me discover a problem with one host’s email, and they also implemented a feature I requested. They’ve been monitoring away on about a dozen sites of mine for about a year now, and they’ve done a very good job at it.

Open Pages (.pages) file without Pages

For a long time people would send Microsoft .doc files to users assuming the recipient could open the .doc file. Fast-forward ~15 years and that habit never went away, but technology adapted and many tools were created or modified to be able to open those Word Documents.

Of course, this problem repeated itself a few years ago when MS released it’s docx format. Sure it was supposed to be “open” but as many have pointed out, even MS didn’t follow their own standard. Not only that but the tools they released were flaky if not flat-out dysfunctional.

Apple has created a similar incompatibility with their Pages application. While you can “save as” a Word Document, if you make a change and hit save, it again saves it as a Pages document. Not only that, but without Pages nothing on a Mac (or PC) can even open the document.

The common “solution” suggested is to tell the user who sent you the file that they suck should send you the file as a PDF (or Save As… a .doc.) But they already have…

The Solution

  1. Take the .pages file and change the file extension to .zip – so if it was Document.pages rename it to Document.zip
  2. Now extract the file. On a Mac or in Windows, double-clicking the file should start the process
  3. Next, in the newly extracted folder (directory) locate the QuickLook directory and you will find Preview.pdf

With this PDF, you can open the doc and copy and paste the content into something more useful.