problem monitoring 24pn footage

take2visualmedia

Well-known member
Footage that is at 23.98 on my FCP timeline, shot at 24pn won't play through to my CRT monitor. The monitor just shows the single frame that the timeline started on. Other footage on a different timeline shot at 1080i or 720p (both 30p not 24) plays fine.

I monitor by sending the firewire to a Canopus ADVC 110 that is an SD D/A and the S-video is looped through my Beta deck to the monitor. I have checked the sequence settings, did a command-F12 to show all frames and still nothing. Any ideas? Thanks.
 
Last edited:
Check to see that the RT button has add 3.2 pulldown.

Not sure if that will fix it... but give it a try.

CaptM
 
That hardware ain't going to cut it. If you want motion playback you'll need something like a Blackmagic or AJA Kona card.

Noah
 
Thanks for the fast reply Capt. Under RT I don't see any 3:2 option, just "safe" "Unlimited", etc.

You must have your deck on and selected in the View video OUT... and ALL FRAMES selected...

THEN you will see that the pulldown can be added out.

BUT as noah says, not sure why the other HD material is flowing out via the canopus... don't think it should.

Odd.

CaptM
 
Some hardware doesn't support pN frame rates. They can support anything over 60, but native won't cut it.

I believe the Intensity is one example
 
re

re

I was looking to buy an Blackmagic Intensity Pro. That should fix this problem you thing? I'm still going to be monitoring on an SD CRT for a month or so so I will be using the analog s-video to monitor until I get an HDMI monitor.
 
which mac? if your computer is too slow to insert pulldown in realtime then single frame is all you will get for 23.98 timelines.

i don't stream hd via firewire but i remember this same problem a couple years ago when my mac was too slow to insert pulldown into my 23.98 dv footage. i was going firewire out thru a dv cam and to a tv. my solution at that point was to drop the footage on a 29.97 timeline and render. then it streamed just fine.

new computer eventually fixed the problem.
 
just thought of this as well. you might try trashing your fcp prefs. when you run it for the first time it analyzes your system and decides what it can and can't do as far as realtime processing. if you add ram or other upgrades, it doesn't automatically update. trashing prefs forces it to re-evaluate your computer...

shot in the dark but may help...
 
Back
Top