Help - 24PA, capturing full tape, wrong drop frames MID TAPE

S

stuntpeople

New member
Hello I recently shot a movie entirely in 24PA. I'm using Premier Pro 1.5. I set it up to capture 24PA, and I captured entire tapes this way. While watching them capture, the previewed footage looked fine.

However, I then open them in the 24PA project in Premier Pro 1.5. The first couple shots of the tape may be fine. But throughout the tape there are tons of shots that are choppy on the 24PA timeline, and it's because the project is dropping the wrong frame.

So rather than having ABBCD footage and dropping the B frame to make ABCD (proper 24PA footage), it's going ABBCD and dropping the A, C, or D frame. So you end up with like ABBC or BBCD and it looks terrible.

As I said, it does this for an entire shot, and then goes into a few consecutive shots after that. I have a feeling that during capturing that Premier Pro 1.5 was marking the wrong frame to be dropped. When I open the footage in an older program like Premier 6.5 the footage looks like it should at ABBCD, rendering all frames on the 30fps timeline.

So my first question: Is there any way to repair improperly marked drop-frames, MID TAPE?

Here's the second part. I didn't really care about editing this in true 24PA, so I thought I'd just do a 30fps timeline in Premier Pro and import the footage that way. But PPro STILL interprets the footage as 24PA, and it makes a mess of it by interlacing frames together, and every 1/6th of a second there's that annoying double-frame (BB or whatever) that is DEinterlaced.

Long story short, PPro 1.5 still looks at the footage I captured in Premier 6.5 as 24PA footage, and it has the exact same problem.

My second question: Is there any way to make Premier Pro 1.5 look at this footage captured in Premier 6.5 as just 30fps footage?

Thank you for your time.
Eric
 
If you want to edit 29.97 then you should be shooting 24p (not 24pa). 24pa isn't the smoothest at 29.97 and isn't meant to be viewed at that speed.
I don't use Premiere but in the future set it to stop if there's a timecode break or a cadence change. When shooting make sure to use the Rec Check button if you power off the camera or review a shot.
Search your Premiere help files for 24pa.
 
The 24PA footage looks ok on a 30fps timeline, really. It's just in Premier Pro it doesn't read it properly, and drops the wrong frame, be it A, B, C, OR D.

I'll remember that word, "Cadence".
 
This has been around the forums a couple of times. I remember hearing having "scene detect" on when capturing.
 
Scene Detect may fix the problem!? ... interesting. Why would that work? Doesn't it just cut the tape into shots (virtually)?
 
Scene detect might work because it seems you probably have time code breaks and that's liekly to cause the issues.

Note that if you're putting any 24p/24pa footage in a 29.97 timeline then pulldown shouldn't be removed at all. The camera automatically adds pulldown so it will play at 29.97 on normal video tape. If yo uremove pulldown then your system will have to insert true pulldown back in when placed in a 29.97 timeline. Most editing software just time stretches the frames to make it work. Unfortuantely the quality of this is poor compared to adding pulldown. Check your manual.
 
Time code breaks... even though the tape's time code goes from 0 to 60 minutes without 'breaking'? Or do you mean it breaks at the frame level?
 
Something is causign Premiere to be confused if it's not converting 24pa correctly.
If there's a break in the time code or cadence thsi will cause confusion for most editing software.
If it's a problem just in Premire then it coudl be somethign else.
But as noted before you shoudl set it NOT to do pulldown removal if you're editing at 29.97.
The problems you may be seeing may not be from the pulldown removal but the process of sticking it back into a 29.97 timeline.
 
I set it to non-pulldown, and it still has the same problem. Granted, it stops doing the frame drop, but it still 'virtually' drops the frame and interlaces the footage accordingly, which screws it up just as badly.

I'll try recapturing with scene detect and find out what happens.
 
You must log in or register to reply here.
Back
Top