Chris Coote
Forum Replies Created
-
Anyone?…I guess that’s a loud NO?
-
Let’s see…today FCP crashed at least 8 times. Motion crashed a couple of times. I am ready to throw the whole damn computer out the window pretty soon. I hve been editing for over 15 years but I am fairly new to FCP and have done several FCP NTSC projects without too many issues. Working in Prores HQ at 1080i seems to be very problematic, especially roundtripping with motion.
I don’t know if it’s a problem using that codec or if it has something to do with the terrablock partition I am using…I have to do a little more troubleshooting.
I posted another thread asking whether ANYONE is using this codec at this frame size without problems and so far no one has answered. -
The stuff was captured on our system using 6.01 back in the summer. The person doing the offline upgraded to 6.02 a couple of months ago and so did we.
-
Hi Michael
We are using standard house reference. I’m pretty sure you only need tri-level sync when working at 23.98 don’t you?
I’m not that concerned about the shots that need slipping…I figured I might have to do some of that since the original captures were being downconverted through the deck and the recaptures are going in through HDSDI through a Kona card. What I am more concerned about is the fact that some of the actual edit points are not matching between the timeline and the qt file. Never mind field issues…a cut at a certain frame on the timeline should be at the same location on the qt file that is made from that same timeline. I could understand if EVERY edit was a frame early but it is just some of them. We have been using a similar workflow for years using avid but have never had this happen. -
Ok, thanks everybody.
So I guess I can stick with the 3 way for most gamma and
white level adjustments, but if I really want to darken blacks
then I’m better off with Colorista. I guess I’ll just have to get used to the controls in Colorista…too bad, I really liked using the scroll wheel on the mouse to adjust levels. -
OK, thanks for all your suggestions.
I will do some tests today. -
OK, I will try the interpret footage – pulldown method…I don’t really know enough about expressions to make that skipping a frame thing work…unless you can give me the quick version on exactly how to do that. So I would interpret as 23.98 and not 25? I guess this avoids having to do time remapping? If all else fails I suppose I can always cut out every fifth frame manually in the avid (yikes).
thanks -
Wow, that makes fixing glitches a little tricky.
Ok, thanks. -
That’s strange, I was getting the opposite results.
I took a sequence into color (ProresHQ 1080i 29.97) and just used a simple primary contrast adjustment.
It took more than 3 times longer to render than a similar contrast adjustment in FCP 3 way
with a broadcast safe filter added on. I think this is because rendering in color can’t take advance of the 8 core processors? -
We have been testing Color along with the FCP 3 way CC to try and figure out a workflow for an upcoming series. I think we’ve decided not to use Color because of the long render times and bugginess. We’re not going to be doing any secondaries, mainly just contrast, legalizing and color cast fixes. We are also interested in trying out Colorista. How do the render times compare with the FCP 3 way? We will be using Prores HQ at 1080i 29.97 on an 8 core.