Jason Levy
Forum Replies Created
-
Sync cable was bad. No sync was getting to Decklink. New cable fixed it.
-
That worked. Thanks.
It’s all there in the FCS manual of course.. (except for the bit about the restart…) I wonder why I didn’t have the reflex to search there… I checked the whole rest of the internet.
j.
-
Hi Kristian. Thanks. Yes I understood that but was having no luck understanding how to do that. I finally got it figured out: I had to create a new FCP capture setting (not easy setting.. that comes later) by duplicating and editing that.. thanks..
jason
-
Card is a decklink HD extreme. BTW.
-
Hi Arnie,
We have done them in the past.. but suddenly it’s not working properly. And I can’t figure out why. It actually is doing inserts no problem. just that the last frame is black.
The deck does have the flying erase heads, etc.
tanks
-
It’s a subtle point. One has to look at the difference between framerate and timecode rate. Two different things.
There is a big difference between framerates of 24 and 23.98.. yes. But if you are talking about timecode there is no such thing as 23.98 TIMECODE. There are exactly 24 frames for every time the second digit ticks over regardless of whether the framerate is 24 or 23.98. That is why when when you go to the timecode menu I mentioned there is no way to select 23.98… just 24.
Still don’t get why or how the material was ingested with a frame rate of 23.98 and a timecode rate of 30 fps. That is what caused FCP to play it back improperly. Fixing the timecode rate got it working properly again.
thanks for taking the time to discuss this. It’s appreciated.
jason
-
Already did the hokey pokey earlier. Can you recommend some other dance? 😉
thanks Shane.
-
Made a copy of the media and then used FCP to change the timecode (not the frame rate) to 24 (menu-> modify -> timecode – rate)
Very weird. Seemed to be a 23.97 quicktime with 30 fps timecode and that seemed to be confusing FCP. Changed the timecode to 24 (there is no option for 23.98 of course) and it’s normal.
Thanks for helping out guys..
jason
-
In the 23.98 sequence its native – no colored render line at all.. in the 29.97 sequence where it plays normally it shows the dark green line.. ie converting on the fly. Converting 23.98 to 29.97. the audio is not asking for a render in either timeline.
-
720p… I didn’t shoot it so I don’t know the answer to that question.