[John-michael Seng-wheeler]

Don’t forget I’m on CS6.
Tested on a PC. The options are exactly the same.

[John-michael Seng-wheeler]

Um… I added the comp to the render queue, clicked on the output module and changed the codec to H.264, render and done. This is on a Mac, perhaps that makes a diference.

In the output module settings there isn’t actually anything that sets the frame rate at all, it’s set in the render settings.

JM

[John-michael Seng-wheeler]

Ah, well, then that isn’t going to work. I did preface my original post by mentioning I was working in CS6.

CS6 can make H.264s in any frame rate you want… To test it I made one just now at 46.98fps, not standard in the slightest.

You can still edit this project with your current software, (though I have no way to test if Premiere CS4 will edit 48fps, you might have to do it all in AE or in Premiere at 24fps) and then download the trial of CS6 to do the render. Not that I like the idea of using a trial version for a paying project, but in this case if you can’t afford to upgrade you’re kinda stuck with using the trial.

JM

[John-michael Seng-wheeler]

What program is that screen shot from? I have no trouble making H.264s (ether in Quicktime or an MP4) in any frame rate in AE CS6…

JM

[John-michael Seng-wheeler]

[Noland Orozaco] “I need the final product to be a quicktime file”

Unfortunately that’s about as descriptive as saying “I need a package delivered to New York City”.

Quicktime is a container format, which can hold many codecs which often have many levels of compression.

That said, the reason that the files are so large and won’t play is probably because AE defaults to Animation as the codec, which is lossless and when applied to video results in files which are practically uncompressed. Understandably, these files do not play well.

H.264 or ProRes (or DNxHD) are probably your best bet but the choice depends on what you’re delivering to. You should ask your client/whomever is being given this file what codec they want. If all they say is “Quicktime” then clearly they don’t know all that much about codecs, in which case you should tell us what this file is being used for and then we can advise you on codecs and the settings for said codecs.

JM

[John-michael Seng-wheeler]

It’s quite simple in CS6, though be prepared for a few quirks. (Timecode doesn’t work at all for example.)

Just create a sequence and drop a 48fps clip into it. Premiere will ask if you want to change the sequence settings to match, and bingo, a 48Fps sequence.

If, like me, your footage was shot at 48fps but the camera doesn’t support 48 as a project timebase (resulting in shots that naturally play back in slo-mo, just interpret the footage as 48fps first before dropping it in the empty sequence.

Rending will have to be done with AfterEffects as Premiere doesn’t support rendering to 48fps.

Just import the Premiere Pro project into AfterEffects and then add the sequence to the render queue.

JM

[John-michael Seng-wheeler]

[Gerard Tay] “But for clips with effects added, and if you’re exporting to the same format as your preview format, there is no additional generation loss if “use preview files” is checked.”

I think we need to dig into this further:

Adobe them selves have appeared to state that there is a generation loss when “use previews” is selected.

Your test was done with ProRes, which is a special case since Premiere can’t encode or decode the file directly. Quicktime does the decode, and passes the frame to Premere. The reverse occurs on encode.

I can’t figure out how smart rending could occur in this situation unless Quicktime is doing it for premiere.

JM

[John-michael Seng-wheeler]

In the format drop-down, instead of Quicktime select H.264.

[John-michael Seng-wheeler]

My MBP doesn’t have little numbers on the keys but it does work.

typing fn +10 isn’t going to work… if you want ten frames you need to type fn+j (which will type a 1) and fn+m (the 0)

The first in each pair is the numpad key, the second is the key you hit alongside the fn key to produce it.

1=j 2=k 3=l
4=u 5=i 6=o
7=7 8=8 9=9
0=m +=/ -=;

Also, “=” is fn+-

[John-michael Seng-wheeler]

Tero is right, phones often record at weird frame rates which don’t stay constant.

One thing to try is to make a new sequence that matches the settings of the video:

Drag the video file from the Project panel onto the new item button at the bottom of the project panel.