…Through rich media! This is what I was writing about last week, and if you caught it – you saw a link to where it was used. If not – it’s time for you, the reader, to play catch up. Don’t worry, I’ll wait…
[Insert muzak here]
You back? Awesome! Pretty neat, huh? Now you might be wondering what do you need to put together submit to us, with your content, to exponentially increase the coolness factor to your content (as long as it’s relevant). This blog post will help with that.
What we'll need from you before we can embed any sort of rich media within any content on developerWorks is noted below. I will also probably add a wiki to the group, so I can post things like this and they can be easily found without digging through past blog posts.
We will be hosting all rich media content on the developerWorks' channel on YouTube, because currently developerWorks does not have any servers that are optimized for hosting/streaming rich media content. I should also mention, there are no future plans to ever obtain or optimize any current servers to handle this sort of thing, and really, when there is a site that does it so well, so easily – why would we need to? Moving on!
|Resolution||RECOMMENDED: Original resolution of your video – for HD is 1920x1080 (1080p) or 1280x720.|
|Bit rate||Because bit-rate is highly dependent on codec there is no recommend or minimum value. Videos should be optimized for resolution, aspect ration and frame rate rather than bit rate.|
|Frame rate||The frame rate of the original video should be maintained without re-sampling. In particular pulldown and other frame rate re-sampling techniques are strongly discouraged.|
|Codec||H.264 or MPEG-2 preferred.|
|FLV, MPEG-2, and MPEG-4|
|Codec||MP3 or AAC preferred|
|FLV, MPEG-2, and MPEG-4|
Now that you have that – what file types are accepted?
Here's the list of some well-known formats which YouTube supports:
- WebM files (Vp8 video codec and Vorbis Audio codec)
- .MPEG4, 3GPP and MOV files - (typically supporting h264 and mpeg4 video codecs and AAC audio codec)
- .AVI (Many cameras output this format - typically the video codec is MJPEG and audio is PCM)
- .MPEGPS (Typically supporting MPEG2 video codec and MP2 audio)
- .FLV (Adobe - FLV1 video codec, MP3 audio)
These are the specs from YouTube and should help you when putting together and creating an optimized file. The max file size that is accepted by YouTube is 2GB or 10 min in length. If you exceed either, I would suggest breaking it up into separate sections.
Since there is no facility to re-upload videos, it's important to test your audio and video quality and that they are satisfactory before you turn it over to developerWorks. The number of views, user ratings, user comments and other community data, cannot be transferred if another, higher quality version of the same video is uploaded. So make sure you get it right!
Closed captioning is mandatory to meet IBM accessibility guidelines if there are voice-overs. YouTube can caption your video from a text transcript we can upload of the spoken content in the video. A transcript is ALSO mandatory to meet IBM accessibility guidelines, but here’s the beauty of that – the transcript that you provide for the closed captioning? Can also be included as the transcript. wa-LA! This simple text file (.txt) should be included and submitted with your rich media file. We don’t have this simple document, we don’t embed. Simple as that.
If this is something you want, contact your editor to ask for the FTP log-in info so you can upload these big files to a secure server. At which point, we’ll download, review, and post to developerWorks’ channel on YouTube in time to be included with the publish of your content.