urgent help:24fps footages and 25fps mixed in cs5

[m.lomibao]

hi,
im editting some 25fps footages on cs5 and ive got some 24fps footages that i need to mixed it with. As per general rule, when i create a new sequence on cs5, i have to match the setting of the original footages to begin with, im 80 almost finished with my 25fps sequences but now ive got some 24fps that i need to include in the same project. So how would the new 24fps footages affect the 25fps footages on the timeline? i mean, the project settings was matched to the 25fps ones...n now if i import n add the 25fps to the timeline, would that affect anything?

thanks

[Janke]

Dunnow... but I'd first convert that 24 stuff to 25, if technically possible, to avoid any jerkiness in the motion.

The slight pitch increase in sound would only be noticeable in song or music...

[Krane]

hi,
im editting some 25fps footages on cs5 and ive got some 24fps footages that i need to mixed it with. As per general rule, when i create a new sequence on cs5, i have to match the setting of the original footages to begin with, im 80 almost finished with my 25fps sequences but now ive got some 24fps that i need to include in the same project. So how would the new 24fps footages affect the 25fps footages on the timeline? i mean, the project settings was matched to the 25fps ones...n now if i import n add the 25fps to the timeline, would that affect anything?

thanks

I've never actually done it but the claim from Adobe is that you may mix and match to your hearts content. The adoption of the Mercury Engine makes all the worry a thing of the past.

[cgbier]

That mercury engine is more marketing than anything else.

[drapeama]

That mercury engine is more marketing than anything else.

More or less their own label for the use of CUDA acceleration. It is better/faster than Vegas in terms of previews during playback, but other than that...

[cgbier]

Exactly! If Vegas had something similar, they'd market it also as the egg of the Columbus. Motion had GPU acceleration from day one (2004) with a wider variety of cards. Untypical for Apple, they just never marketed it.

[m.lomibao]

I've been editing 25fps footages n yesterday I didn't realised that I filmed the remaining stuff in 24fps n now I can't re shoot them again ... What's my best solution on how to use them with the 25fps sequences in the timeline?

[cgbier]

I haven't mixed Pal and NTSC in Premiere yet, but in its cousin (FCP) it works without any issue. Just drop your footage into the timeline and see what happens.

[Rainer]

Just stick it onto the timeline. CS5 can handle the difference, including eliminating any pitch shift. I doubt you'll notice any difference when you play it back. What you want to do with the footage affects your project settings and how you render it. If you want a BRD you'll probably get a slightly better result setting your project and render to 24p.

[cgbier]

BTW: the old FCP had the nifty tool to convert 25p to 24p built in. As both, Premiere and FCP are basically the same, Premiere might have it also.

[Krane]

That mercury engine is more marketing than anything else.

Of course it's a marketing tool. Adobe like all the rest wants to sell software. Nevertheless, that doesn't mean it doesn't work as promised. The Mercury Engine is simply Adobe's way of indicating that they've done their homework and written and tested items that work seamlessly together.

These are: 1) A 64 bit OS, 2) A CUDA certified graphics card and, 3) a multi-core CPU. The Mercury Engine simply maximizes all of these together to give you maximum editing efficiency.

Just stick it onto the timeline. CS5 can handle the difference,

Provided the rest of your system is up to snuff. The software can only do so much with the hardware that it has to work with.

I've been editing 25fps footages n yesterday I didn't realised that I filmed the remaining stuff in 24fps n now I can't re shoot them again ... What's my best solution on how to use them with the 25fps sequences in the timeline?

Man you really have thrown a monkey wrench into your project. My advice is to find the best software and convert to one or the other before editing.

In the future double check your setting or get someone to do it for you. In a job, those mistakes can be unforgivable.

[Rainer]

Man you really have thrown a monkey wrench into your project.

Am I missing something here? I just don't get why this is a problem. You often - very often - have to work with different resolutions and framerates on the same timeline. With 24p and 25p it probably either drops or doubles a frame each second, depending on your project settings and how you want to render it, but you really are hard put to notice and surely most NLE's can handle it?

[m.lomibao]

Am I missing something here? I just don't get why this is a problem. You often - very often - have to work with different resolutions and framerates on the same timeline. With 24p and 25p it probably either drops or doubles a frame each second, depending on your project settings and how you want to render it, but you really are hard put to notice and surely most NLE's can handle it?

Oh alright, o thought u have to match the frame rate to the project settings ... Thanks for the clarification

[Krane]

Am I missing something here? I just don't get why this is a problem. You often - very often - have to work with different resolutions and framerates on the same timeline. With 24p and 25p it probably either drops or doubles a frame each second, depending on your project settings and how you want to render it, but you really are hard put to notice and surely most NLE's can handle it?

Yes, that old adage that, an ounce of prevention is worth a pound of cure. This was an error in preparation, not a necessary part of editing. If you were the employer, would you still be so understanding? In any event, that sentence was my "subtle" way of driving that point home.

[cgbier]

Uhm, Krane you know that there are editors who DON'T have control over the material they get onto their desk? Mixing 24 and 25p is no issue at all.

Create a timeline with the output bitrate, then dump everything in there. Premiere does the rest. I tested it meanwhile.

[EvilBastardProductions]

Yeah definitely no problem if they are progressive, though I'm not sure if interlaced would be a problem (never use it).
But with progressive footage, you just dump it in. You then have two options in "interpret footage"- either to interpret the 24p as 25p (so it will run slightly faster), or to leave as 24p, in which case it will just duplicate an extra frame every now and again to match it to 25p

[m.lomibao]

Yeah definitely no problem if they are progressive, though I'm not sure if interlaced would be a problem (never use it).
But with progressive footage, you just dump it in. You then have two options in "interpret footage"- either to interpret the 24p as 25p (so it will run slightly faster), or to leave as 24p, in which case it will just duplicate an extra frame every now and again to match it to 25p

Thanks mate ... I shall do that

[Krane]

Uhm, Krane you know that there are editors who DON'T have control over the material they get onto their desk?

Which does not dismiss the value of the adage.

Mixing 24 and 25p is no issue at all.

Create a timeline with the output bitrate, then dump everything in there. Premiere does the rest. I tested it meanwhile.

Maybe I'm being too subtle and thats why people aren't getting it? I know modern editors can handle mix/matched code, codeces, etc., but that wasn't my point. My point was to develop good habits of checking and double checking your settings. Or do you believe that isn't important?

Many things can be fixed with the right software and enough time, but I was speaking universally, well beyond this one particular event. Its good to develop these habits of checking those types of things again and again in the event it can't be "fixed in post"? Think about it for a moment, would you still be as liberal if you were the one writing the checks?