-
Why are timelines with 24p material sluggish, and 29.97 are fine.
I have been using the IO to remove the pulldown from BetaSP (Film originated footage). I have 23.98 clips on a 23.98 timeline. Everything works, however FCP has an extremely slow playback response time. From the time I hit play on the keyboard, it can sometimes take up to 3 full seconds before it starts to play. This is extremely annoying when trying to edit fast. I do not have this problem with ordinary 29.97 footage. Ideas anyone?
FCP 5.0.3
G5 Dual 2.7
AJA IO with v2.0 drivers
HUGE 4105 FCR RAID -
4 Replies
-
I wasn’t aware that the IO was capable of removing a pulldown. How does it do that?
-
Yes, with version 2.0, you can remove the 3:2 pulldown from tapes that have it. I use it with Film footage transferred to Digibeta and BetaSP. There are so many reasons to work in a 24p workflow I could go on and on. With version 2.0 drivers, AJA added a few new presets to accomodate this process, and it’s pretty easy. It’s not a perfect system however, I find that 1 out of 20 or 30 clips needs to be re-captured becuase it got the 3:2 cadence wrong, but when re-captured it was fine. Also, one MUST remember to log thier clips with a starting timecode that ends in either 0 or 5, this is known as the ‘A’ frame, and the IO must be told what the ‘A’ frame is in order to remove the pulldown properly.
The problem (that I’m refering to in this thread) is that FCP seems very sluggish in a 24p (23.98) timeline. There doesn’t even need to be any clips on the timeline. As an example, I placed some audio on the timeline first and FCP hung for about 1 to 2 seconds everytime I moved around the timeline or tried to open the audio clip in the viewer. Jumping back to a 29.97 project proved that the symptoms went away. I’m totally lost on this one.
-
This sounds like a job for AJA support. Give them a buzz.
jeremy
-
>Yes, with version 2.0, you can remove the 3:2 pulldown from tapes that have it.
Thanks, that’s good info.
Reply to this Discussion! Login or Sign Up