[Jason Brown]

Great response and link!

I’m bookmarking this…I have several people who will run into this issue and come asking me whats up!

Thanks Alan!

-Jason

[Jason Brown]

I’m speaking a little out of turn here…my testing wasn’t scientific, but I think I can add some additional information in regards to VGA playback. There are a couple things I’ve run into:

-I don’t know that any video cards on a laptop support native playback through VGA at 1920×1080.
You’ll likely experience *computer* resolutions like 1024×768. (or the widescreen equivalent – 1366×768)

-Some video cards don’t even support widescreen dimensions so you’ll have black pillar bars on a widescreen TV (my tests are from a couple years ago, so that may have changed)

-If you are playing back at a supported resolution of the monitor and supported output of the video card and it fills the screen, it should be crisp…all my tests at different resolutions looked clean.

-Jason

[Jason Brown]

What are the reasons you’d want to use QT7 over QTX?

[Jason Brown]

What effect?

If you were using Text animation and the character count was the same, it would (should) look exactly the same.

-Jason

[Jason Brown]

Good point Walter…I created some basic text movement and image movement for a 24p project and was horrified to watch it back…you have to be VERY careful about movemement.

Have you ever used a media player box? We use WDTV boxes and I’ve done some render tests and that little box can play back some pretty impressive footage. I’ve loaded up h264 @ 1920×1080 with a bit rate comparable to bluray – 25-30Mbps VBR and that thing keeps up REALLY well…no skipping or hesitation. And all you do is throw it on a jump drive and it’s ready to go. HDMI interface…pushes audio and video

-Jason

[Jason Brown]

I think you’ll need to define HOW it’s hooked up to the TV. If you are using a VGA interface, then the monitor is basically an extension of the computer and any supported resolutions that the video card can push out will display appropriately. Then you’d use a video playback like VLC or Quicktime and go fullscreeen.

If you are using a video playback device, such as a Matrox box (I’ve used – with FCP) then I believe you’ll need to conform to the appropriate (I’m assuming NTSC) frame rate – 29.97. 24fps would be played back with a pulldown to 29.97 and would need to be sourced at 23.976. Your frame size would also need to be a NTSC compatible size – 1280×720 or 1920×1080.

I’ve only had personal experience using source footage @ 29.97 and a Matrox mini to output HDMI to a monitor…all this using Final Cut Pro.

HTH,
-Jason

[Jason Brown]

Dave,

Quick question…I’ve been dealing (more and more) with DVCPRO HD codecs. Are these the same intraframe codecs you are referring to? I know they are using PAR’s to lighten up the size…but I was just wondering if they were appropriate editing formats.

-Jason

[Jason Brown]

Thanks Kevin for the clarification.

[Kevin Camp] “but why not just work with a 59.94 frame rate comp to start with.”

I was pretty much asking that in the same terms of “why doesn’t adobe set the standard frame rate of the 720 template as 59.94”

Thanks again for the information. This makes MUCH more sense to me now.

-Jason

[Jason Brown]

Even though I probably won’t be using this 2 camera option anymore…I did get this working…once I collapse, it changes back to real time…sequence codec…full playback. I don’t know why it didn’t the other day. I restarted and it’s all working as you described Jeremy. Thanks!

-Jason

[Jason Brown]

Bouke –

I have a few tests I’ve ran…just sitting at a desk.

The tests I did were with the 7D at all 3 frame rate options. 23.98 – 29.97 at 1080 – and 59.94 recorded at 720.

I can post them somewhere if you want them:

jbtwist@gmail.com

-Jason

*they aren’t very scientific…no lighting…no specific framing or focusing…just simply a technical workflow test with on camera talking for sync*