NEED movie to iPad export in Q.T. Pro

Question

Quick Time Pro desperately NEEDS to add an export format:
     "Movie to iPad"

Answer 1

As far as the "in touch programer" goes.......I still believe someone would see this problem and within QT Pro create a link from .Mov to iPad only whereby the source file is somehow popped up to the higher dimensions so the output on the iPad is clear and not distorted.
A 320x240 display might be referred to as a 240p or 240i 4:3 aspect ratio frame containing 76,800 pixels.
A 640x480 display might be referred to as a 480p or 480i 4:3 aspect ratio frame containing 307,200 pixels.
A 960x720 display might be referred to as a 720p or 720i 4:3 aspect ratio frame containing 691,200 pixels.
As you can see from this progression, linear increases in the display dimensions increases the number of pixels (data) exponentially. That is, doubling the dimensions increases the number of pixels by a factor of 4, tripling the dimensions increases the number of pixels by a factor of 9, etc. Therefore, magnifying the 320x240 file to 640x480 pixels, means the encoding application must come up with 230,400 pixels from nowhere. Similarly, to increase the dimensions from 320x240 to 960x720, the encoding application must "manufacture" 614,400 pixels to "fill in" the display. Most applications simply replicate the original source pixels for scaled encoding or scaled display use. I.e., 640x480 encode or display would simply use 4 pixels arranged in a 2x2 matrix to represent each of the originally decoded source pixels in the new file or display or 9 pixels in a 3x3 matrix to represent the scaled encode/display for 960x720 target dimensions.
As an example, here is a sample 320x240 display which contains a reasonable amount of detail.
If you click on the above imaage, I believe you will see the 640x480 rendering. (If I have this figured out correctly.) In any case, this image is beginning to lose detail and texture. While the encoding of data at one set of dimensioins and displaying at another is a frequently used trick to save bandwidth, most users stick to a 2x limit.
Hopefully, clicking on this image will display what the original 320x240 file would look like encoded/displayed at 3x the original dimensions. If you look closely at the frames on the eyeglases shirt edges, you may note some pixellation along with a loss/smearing in details and textures.
In any case, Apple has a long standing tradition of not allowing most "presets" to upscale clips larger than their source dimensions since this work flow can greatly increase file size without producing better quality than the built-in player-device scaling feature. Still this is easly gotten around by merely performing a manual encode using QT 7 Pro or GarageBand. In fact, the manual encode would allow you to access the "Sharpen" feature which might be useful.
My little Nikon would NOT take videos at those size dimensions.  I knew when I was taking the demo, it made funny sounds.  When I loaded it on my computer, it was NOT a video but still frames that skipped mightily.  So, that camera was out as far as larger size.
Our big Canon digital did take a video.  It was larger when viewed in QT and nice and clear.  BUT when I went to QT and exported to Movie for Apple TV,  the output was BLANK.  TWICE with 2 different demos.
Can't help you here without additional information. As previously stated, MOV merely refers to the container—not the data contained in the file. Different digital cameras recoderd using different compression formats which may or may not be stored in an MOV file container. Further, some digital cameras may use different compression formats for different recording modes. A "muxed" MPEG-1 file conversion would normally lose the audio using QT conversions. Many Lion users are complaining that Motion JPEG clip convert with a "black" display screen which may be the result of a lack of native support for this video format as indicated on the Apple web site.