Editing 24pa footage in a FCP HD 23.97 timeline - G5 needed?

dignan00

Member
Hello,

I recently aquired an XL2 and plan to shoot a project soon in some form of 24p, but I'm trying to figure out my best workflow. I'd like to have the OPTION to transfer the project to film - but, that may never happen, and in the meantime, I will DEFINITELY need to make a gazillion decent looking "screener" copies on standard NTSC VHS or DVD to pass around.

The best way to approach this that I can decipher is to shoot with 2:3:3:2 added on the XL2 (advanced), and then capture in FCP HD with the 2:3:3:2 removal capture setting. Then I should be able to edit the resulting footage in an NTSC DV 23.97 timeline, right? Then just have FCP HD send back to tape, re-adding the 2:3:3:2 for NTSC, or, stay in true 23.98 for any potential film transfers. Well, is this possible to edit in a 23.97 timeline on my G4 1.25 GHZ machine with 1 GIG of RAM with 10.3.8? Or is it really in G5 turf?

I'm just not having any luck doing the above workflow on my system. For some reason when I try this workflow, the playback of my 23.97 timeline is horribly stroby and sluggish, and FCP HD becomes mega unstable and often times just leaves me in the dark (ie, unexpectedly quits). I'm assuming I just have an inadequate machine for such an undertaking? It's just strange that it works so well for standard 29.97 timelines - even if I throw a 23.98 clip or two on there. What in the world is the processor doing to slow it down so much in my 23.98 timeline? Adding back the pulldown in real time? Even if I drop the sequence RT settings to lowest of the low, it's totally unusable. Is there any way to make this workable on my machine?

I'm hoping perhaps I have some magical setting wrong - but after hours (days) of searching and trial after trial I can't find any such magic setting.

If it is my system, I suppose the alternative would be to shoot in 24p normal and import it as regular ol' 29.97. But I'm afraid of this mainly cause I hear that if you desire a film transfer this way, you must be careful to not disturb the 5-frame cadence to ever hope to bring it down to true 24 fps. It just seems so unnecessarily hard for me this way, especially since I have an NLE capable of handling 24pa footage.

Argh. I suppose I'm looking at a costly system upgrade. Any advice?
 
When you send back to tape set it to 2:3:2:3 for viewing. Only dump it to 2:3:3:2 if you want to recapture with advanced pulldown.

Are you viewing this on the computer or on a video monitor by way of firewire? There's some overhead involved in outputting to firewire.
Quit any other applications and turn off any background applications. Go into Activity monitor and check the different applications. If you have a number of background tasks or widgets (palm sync, etc) you coudl be gettign drain from these.
Make sure you have at least 1g disk space. Ideally several gigs.
Run repair permissions to make sure you don't have other problems.
Are you using an external firewire drive for the footage? try the internal drive.
 
Thanks for the reply Scott...

This behavior seems to happen with or without a video monitor/camera attached via firewire. Even if I remove those and open FCP HD, it still has the issues. I certainly have no other apps open, activity monitor says. I have 35 gigs of HD space and it's all on the 7200 RPM internal drive. Seems like I should be okay right? Really beats me. I'll run repair permissions just in case. If you think of anything else let me know. I'm running out of ideas.

Thanks again.
 
You might try posting to 2-pop.com since there are many FCP experts there.

Otherthing to make sure is NOT to have Norton utilities/anti-virus installed.
 
I used a 1.25ghz emac with 512mb of RAM and have no problem exporting with 3:2 pulldown (well, except when I'm ultra low on disk space). It sounds a software problem, or you could try a faster external drive.
 
I'll try removing Norton. Policar: the sluggishness comes when I'm just cutting a project on a 23.97 timeline and playing it back within FCP HD in the canvas. I'm assuming your 1.25 ghz Emac didn't have this issue?
 
Back
Top