So, you've made a video recording of a lecture and you’re ready to show it to your students…
How do you make that happen?
First, you need to give it some place to live—a central location where it will be stored (and not lost!) and where your students can access it.
In other words, you need some kind of secure, internet-connected file server with a user interface you and your students can understand. You also need someone to make sure it runs, remains safeguarded from hackers, and has some way of backing up the important work you've stored on it.
So, you somehow get your video file on a server. Now your students want to watch it, but some have laptops, others have iPhones, and one of them even bought something called a Motorola XyBoard.
How will you make sure your video will play on all of those different devices?
You have to convert your video to multiple formats so that any device—iPads, mobile phones, PCs, etc.—can read it. Next, you have to create several different versions of each format with differing degrees of quality to account for the variations in data speed among those devices. This process is called encoding: it creates multiple formats and versions of your video to make sure that just about any internet-connected device can play it back.
So, you've managed to encode your lecture. Now your students with high-speed internet can watch a high-quality version of it, and students watching over a slower cell network can watch a compressed version that won't stall out for minutes at a time. Whatever device they have, whatever connection speed it’s running—your students can watch it.
That lecture is over an hour long. What if your students watched the first half yesterday and today they want to pick up in the middle?
You have two options: students can download the entire video and sit through the first half while they wait for the second half. Or, you can stream it to them—which lets them jump around within the video and watch what they need to watch. To stream the video, your device needs a way to tell the server “start playing at the 35-minute mark”. What’s more, because different devices stream video in different ways, your server needs to know what kind of device it's talking to.
So, you’ve set up a way for your server to talk to devices, know what kind of devices they are, send them the right files, and let them pick up where they left off—now your students can resume the lecture where they stopped watching yesterday.
What if you’re on the East Coast and you have distance students watching your video while sipping Kona coffee in a café in Hilo, Hawaii? And what if the server connection to the café’s wifi is slow as molasses?
Despite how little it seems physical matters affect the internet, if your video server is 6,500 miles away from your student, that will cause lags that result in delivery of a lower-quality video. If you want to your students to access the highest-quality video possible, you need a Content Delivery Network (CDN). A CDN maintains “edge” locations in multiple areas around the world. When a far-off somebody watches one of your videos, the CDN copies that particular file to the nearest edge location, allowing for a much swifter data transfer. And that lets your faraway distance students get a much quicker stream than if they were streaming it from your server.
So, you connect your file server setup to a CDN, ensuring the best connection between your students and your lecture. But what if... well, enough of that for now.
And that's how you make it happen. Your lecture is stored and backed-up, is encoded and optimized for streaming to multiple kinds of devices, and has the fleetness of a CDN to get it to your students regardless of their location. And all you needed...
- ...was a file server
- worthwhile encoding software
- a way to intelligently stream your videos
- a CDN to help get that lecture to everyone who wants to watch it
- oh, and IT staff to make the whole thing run like a top
Get your calculator.
You can also make it happen using Populi's built-in file storage and media streaming.
It handles everything mentioned above—and then some. With it, all you need to do is record your lecture, upload it, and start using it. We do everything else:
- Store your original file in the Amazon Cloud and back it up to the Rackspace Cloud
- Convert it to multiple formats so different devices can play it
- Make multiple copies in each format, each compressed to a different quality
- Configure everything for streaming so your students can skip around within the video
- Send all files through Amazon's CloudFront CDN
- Create an embed code so you can easily add it to your courses
Populi makes your audio and video files far more useful and accessible to your school for a fraction of the effort and—given the complexity of a home-grown setup—a fraction of the cost. Every pricing plan includes an allotment of file storage, and extra storage is available for
$2.50** $1 per GB per month. And since we've done all the hard, behind-the-scenes stuff***, there's no setup on your end whatosever—you can just start using it.
* Flash-enabled devices, for instance, use a protocol (a formally-defined language that lets computers talk to each other) called RMTP to tell the server, “start here.” iOS devices—iPhones, iPads, etc.—require that the video be split into dozens or hundreds of chunks; they then request the video start playing with the correct chunk (the one containing the 35-minute mark).
** Price per GB was changed as of July, 30 2012. Read more.
*** We even designed our own encoding software.