So, to get those settings in MPEG Streamclip, you would load the video in Streamclip, then go to "File", "Export to MPEG-4"? And then in there, select the Compression as H.264, the Sound as MPEG-4 AAC, and then click on "iTunes", and select one of the four different "Apple TV" settings? Does that sound right?
You have it a bit backwards. As soon as you open the "MPEG-4 Exporter" window, immediately press the "iTunes" button and select one of the TV options. If you start my entereing settings and then selecting an TV preset, some of your settings may be changed. Whereas, if you select one of the TV options first, any changes you make will be the ones actually applied to the conversions.
As to which "iTunes" option to select, it depends on the source dimensions and aspect ratio, as well as, your actual target use for the output files. If you actually have an TV device, you would probably want your output to be compatible with it. This means that if your source file is 1280x720 or larger and was shot at 30 fps, you would limit your selection to 960x540 because the TV specs are limited to 960x540 at 30 fps but can play 1280x720 at 24/25 fps. On the other hand, if you have an iPad you can use the 1280x720 dimensions with the full 30 fps frame rate. (I.e., it is usually a good idea to avoid changing source frame rates and/or source interlacing if possible.)
When I select an "Apple TV" setting, it has the "Limit Data Rate:" check box checked, with the text box and pull-down menu next to it. This is what you are saying I should play with a little bit to see which I like the best?
The MPEG Streamclip TV preset limits the video data rate to 5 Mbps because that is the limit the TV device is supposed to handle. This data rate should be sufficient to provide commercial DVD at 720p dimensions downscaled from a 1080i/p source file. If you are not worried about mobile device compatibility, then you could use somethiong on the order of 8 Mpbs for for a full 1920x1080 movie and achieve about the same level of quality. Just remember, the larger the scale of your output, the longer the conversion will take. Further it is generally a waste of conversion time and storage space to upscale target files larger than the source file dimensions since you cannot "create" new data the would improve playback.
As to audio playback, if you are targeting a mobile device, MPEG Streamclip will automatically limit your AAC output to a max of 160 Kbps at 48 KHz even though the "box" says 256 Kbps since this is device limit.
And dimensions are the resolution settings?
The MPEG-4 Exporter window refers to them as the "frame size."
One more thing, the size that the file will be (the estimated one next to the pull-down menu), and the file size that it is after converting it doesn't affect how the video looks? It just affects the size of the clip? Just editing the size in the Data Rate box won't do anything to the quality?
As QTKirk indicated, "good" compression is an art. To be really good, the user must use all the tools available to meet the challenge of differents scene situations in your movie. As he further indicated, things like the rapidity of motion, the number and type of vesctors involved, the amount of light, the complexity of the graphics, etc. all have an effect on compression requirements (e.g., data rate rate to frame rate ratio, key frame rate to motion ratio, etc.). So yes, the data rate, frame rante, and display dimensions are important factors here. IF you reduce the display dimensions but hold the data rate constant, the quality tends to improve since the data to target pixel ratio increases. In a similar manner, if you reduce the frame rate using a blending rather than drop algorithm and again hold the data rate constant, once again you quality tends to improve since the data to frame (and thus, pixel) ratio again increases. However, if the data rate becomes to high for the viewing device, then you begin to defeat your purpose in increasing playback quality because the player then tend to "drop" frames during playback if it can't keep up with your data throughput. This is why there is not fixed answer her and why QTKirk advised that you make test conversion to better assess "quality" in the terms of your personal work flow and method of viewing the final product.
