Streaming Media - June/July 2008 - (Page 72) Figure 4. Information available in the free version of QuickTime Player For the sake of completeness, I’ll mention Adobe’s own FLVCheck tool, which is a simple command-line tool that lets you verify that files conform to the Adobe FLV specification. This tool, now included with Adobe Flash servers, doesn’t disclose any file-based details, but can be invaluable if your files aren’t playing normally with the Flash Media Server. When viewing WMV files in Media Player, the Properties window (File > Properties) identifies the total bitrate, resolution, audio and video codecs, and audio bitrate (Figure 3), and you can get the playback frame rate in the Statistics screen by clicking View > Statistics during the video playback. In addition to this data, I need to know which SDK I’ve used during encoding, since SDK 11 delivers slightly better quality, even with the older WMV9 codec. When analyzing multiple bitrate files, I need to know the resolution, frame rate, and data rate parameters for each audio and video stream. If you’re a “tweaker,” whether via the Windows Media Power Toy, command-line encoding, or a tool that incorporates the SDK 11 tweaks, you’d also like as many of these tweaks as possible exposed in the file analysis, but don’t hold your breath, since none of the tools provide this information. MPEG-4 is a very complex algorithm with lots of configurable parameters. As you can see in Figure 4, the free QuickTime Player provides some of the basics, including audio and video codecs, resolution, data rate (in kilobytes/second) and frame rate. This information is available in the free QuickTime Player, with some critical information about hinted files available only in QuickTime Pro, which is the version I describe in Table 2 and below. Beyond this information, I’d love to know which H.264 codec was used to produce the file, since quality varies widely among them. I found no joy here, as no program identified the codec brand. You’ll have better luck identifying the codec (MPEG-4 versus AVC) and profile used to produce the file, which most programs reveal. If you experiment with lots of 72 STREAMING MEDIA June/July 2008 encoding parameters, you’d probably like to know the B-frame interval and whether CABAC or CAVLC was utilized, since both affect the horsepower required to play the file. When producing for a QuickTime server, you need to know if the file was hinted (i.e., whether control-data tracks were added), which QuickTime Pro can show you, and whether it was flattened (i.e., made accessible to multiple platforms) with a fast start header at the front of the movie. I found no tool that provided this last bit of data; the only piece of useful advice I found was to view the file header in a hex editor. If there’s an “mdat” string near the front of the file, it’s probably not a fast start; if there’s a “moov” string followed by an “mdat” string, it’s probably fast start. I also found a free tool called Lillipot that will add fast start headers to a batch of MOV, MP4, M4V, and M4A files, which you can find at www.qtbridge.com/ lillipot/lillipot.html. Now that we know what to look for, let’s have a look at the five tools I considered. under the hood QuickTime Pro QuickTime Player can open multiple instances on Mac and Windows, which makes it an essential playback tool for all QuickTime and H.264 producers. As a diagnostic tool, QuickTime Player is very limited, though if you upgrade to QuickTime Pro ($29.99), you can access unique data relating to hinted streaming files. QuickTime Pro has two diagnostic screens, Movie Inspector (Window > Show Movie Inspector), shown in Figure 4, and Movie Properties (Window > Show Movie Properties), shown in Figure 5. Movie Properties provides the best view of hinted streaming files that I’ve seen, identifying the streams and showing their respective data rates. Note that data rate is not one of the default columns; you have to right-click the window and choose it and other desired columns from the context menu. Information about the hinted tracks proved particularly useful when producing with Telestream Episode, since the program allocates a disproportionately high data rate to the Hinted video track—approximately 3–4 times higher than other encoders. For example, in Figure 5 you can see that the data rate for the hinted video track is higher than the actual streamed video. While this shouldn’t affect actual streaming bandwidth, since the hinted track never leaves the server, it does make the Figure 5. QuickTime Player’s Movie Properties window http://www.qtbridge.com/
For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.