Aspect Ratio & Progressive Scan

[Toshi.des]

Premiere CS4 has some limits with preview codecs, and so will Premiere CS5. I'm using beta CS4 on a 32bit OS so I have all codecs available for preview, but full version does seem to give the same issue on all 64bit OSes and some 32bit OSes "at random."
So basically, you're out of luck... AME is its own application for a reason - that is because premiere seems to have limits with some codecs the way it's built now (and this will especially be true with CS5, since it will be 64bit only and won't be able to use 32bit codecs), so they just have the dynamic linking between the premiere project and AME as a pipe of sorts, so AME can work fine with both 32bit and 64bit codecs without premiere needing to.
Basically, as far as preview codecs are concerned, you just have to bite the bullet and see which of those seems to work best for you. Alternatively, your PC seems to be strong enough to be able to playback most of your editing in real time without the need to preview at all. I know that I myself rarely preview within premiere despite having a broad list of codecs available, because premiere was optimized enough to let playback without rendering feasible. CS5 apparently will be able to let 6 720p tracks play in realtime without the need to render the scene to preview it...

How do I switch it to real time instead of using a codec?

what most of you aren't making clear is how important it is to maintain timecode. If anything is set to 30fps instead of 24, you might have to redo the timing for your whole amv to get it to render properly. Just a word of warning. Previewing in 24fps is also a good idea.

That is why I even looked at previewing information, I started to get concerned when it said 24p when I was editing a project for 30 FPS. Will any of the other codecs avoid this issue and preview with the FPS originally chosen? Whether it be 30 or 25 FPS?

You also mention that 24 fps is good to preview in, only for 24fps right? or did I get confused lol.

Thanks so much guys for the help!

[Kionon]

Don't listen to kickass. He's trolling.

[mirkosp]

While you edit, instead of hitting return and wait for it render, just hit the spacebar and it'll start playing from that point regardless.
And yeah, don't listen to kickass331... if you decided to edit at 29.97, your preview should be 29.97 too. Now, I don't know why you are doing 29.97, but if you decided so, it'd be a bad idea to preview based on 23.976.

[kickass331]

Don't listen to kickass. He's trolling.

no, 24 fps is the number of actual frames in ntsc. at 30fps interlaced, every 5th frame is interleaved. It is inserted to transition, if you understand what the process of telecining is, you'd understand why you want 24 fps for IVTC which you should always do to NTSC... follow the guides!

[mirkosp]

Don't listen to kickass. He's trolling.

no, 24 fps is the number of actual frames in ntsc. at 30fps interlaced, every 5th frame is interleaved. It is inserted to transition, if you understand what the process of telecining is, you'd understand why you want 24 fps for IVTC which you should always do to NTSC... follow the guides!

This is based on the assumption that he has telecined material or that he isn't required to have some other fps settings due to some situation (ie: con requirements). Which could be very well wrong.
Also, you likely meant that every 5th frame is a duplicate, since the amount of interlaced frame in every set of 5 in a 3:2 pulldown is 2.

[kickass331]

Don't listen to kickass. He's trolling.

no, 24 fps is the number of actual frames in ntsc. at 30fps interlaced, every 5th frame is interleaved. It is inserted to transition, if you understand what the process of telecining is, you'd understand why you want 24 fps for IVTC which you should always do to NTSC... follow the guides!

This is based on the assumption that he has telecined material or that he isn't required to have some other fps settings due to some situation (ie: con requirements). Which could be very well wrong.
Also, you likely meant that every 5th frame is a duplicate, since the amount of interlaced frame in every set of 5 in a 3:2 pulldown is 2.

no, I was trying to state how every 5th frame pulls 2 half frames from the b frames which represents one frame since interlace represents half interpolated fields.

[Kionon]

Don't listen to kickass. He's trolling.

no, 24 fps is the number of actual frames in ntsc. at 30fps interlaced, every 5th frame is interleaved. It is inserted to transition, if you understand what the process of telecining is, you'd understand why you want 24 fps for IVTC which you should always do to NTSC... follow the guides!

I wrote one of the guides.

Telecining

NTSC Film runs at a speed of 24 frames per second (fps). NTSC Video runs at a speed of 30fps. These frames are usually interlaced as well. Showing a film in video requires adding extra frames- 6 for every second. Or for every four frames, add one. Simply removing interlacing from NTSC material will produce an effect where two frames appear to be overlaid, creating an effect known as “ghosting”. If you have deinterlaced, and you get ghosting, then your footage is a prime candidate for inverse telecining, which undoes the telecine process and produces footage that looks right.

Interlacing

Quite literally, interlacing was created to update the image twice as often, but only send half the content. Originally designed to compress video inside radio waves for broadcast television, interlacing only looks right on an old cathode ray tube television. On LCD or plasma monitors/TVs, interlaced content appears as lines where the two half images meet and alternate. Deinterlacing determines how to put the lines in the proper order, creating a sustained clear picture.