Christopher Mcdonell
Forum Replies Created
-
Hey Magnus. Just to clarify, you can have both QT Pro 7.7 and QT X installed – there’s no need to uninstall X. A lot of people are keeping both because vs 7 is much better suited for the pro user. And if you haven’t seen any screen-tearing, you’re probably going to be fine. I just mentioned that because it’s something I get and I’ve read of a few others experiencing it as well. Cheers
-
I have the same camera. You meant Canon XH A1, right? If you shot at 25 fps, then it’s 25p (f), right? (unless there’s a 25i mode I don’t remember). So if it’s progressive, you don’t need to de-interlace. Also, if you transcoded to ProRes upon import, that’s not really downgrading. 1440×1080 are the same dimensions as HDV. But if you burn your video to a SD DVD, you’ll be downgrading big time so you don’t want to do that. Blu-Ray, different story.
If you can play off your own computer, and just wire it to a projector, then you could just play full-screen out of FCP as others have suggested. For me, using FCP 6 and OS X 10.8, I get the odd screen-tearing. So my preference would be to export a QT movie and play using QT Pro 7. Unless you have all your media handy (i.e. external harddrive), you’ll need to make it self-contained. I say QT Pro 7 because in Preferences you can Enable Final Cut Studio Color Compatibility so your picture looks the same as it did in FCP. QT X doesn’t offer this setting and if your picture looks wash-out, that’s why.
As far as I remember, if you make a self-contained QT file with FCP, it will only play on a computer that has FCP installed on it. So if you plan to play this off someone else’s computer, you may have to export a H.264 file and give the person that. If so, let us know and I’m sure someone here can help.
-
The way I see it, I can either change the timeline to progressive and de-interlace via FCP that way. Or I can roundtrip what needs to be interlaced using Compressor. Does that make sense? In truth, I haven’t done any tests yet because since I revisited this video, I’ve decided to clean a few things up. But from what I’ve read, Compressor is a far better tool for de-interlacing. I recently used it on another project and was actually pretty surprised with the results. Far better than how it looked in FCP in fact. So, to clarify, I’ve isolated all my graphics and text on specific layers. That way I can disable those layers in FCP, either by clicking the green button and making them invisible or disabling them by selecting Modify/Clip Enable. When I’m ready, I can then send the interlaced footage (minus graphics and text) to Compressor, change my FCP timeline to ProRes – progressive/no fields – and then bring the transcoded footage back (replacing that which was interlaced) and sync it up. Then, point 5, enable the disabled graphics/text clips (or make them visible), and RENDER ALL. Unless someone gives me a better idea (and no, I’m not trying to upres to HD)… that’s my plan. 😉
[Robert Withers] “Christopher, could you clarify something about your proposed process?
1) disable layers with text and graphics
2) send sequence to compressor and transcode to ProRes 422 using the de-interlacing filter with frame control settings
3) change fcp timeline settings to ProRes 422 progressive
4) import the de-interlaced video file and replace the old
5) render titles and graphics over the new footage and voila!I don’t understand 1) and 5). Do you mean leave the text and graphics interlaced? Are they in something like AE and not the FCP timeline? By what process do you “render them over the new footage”? Is text created in an interlaced FCP timeline not really interlaced?
Thanks,
Robert”To my knowledge, anything added to an interlaced timeline in FCP 6 gets interlaced in the process – text and graphics. So in DV NTSC, de-interlacing is essentially cutting 480 vertical lines down to 240 – not very pretty! – and then doubling them. As a result, text look even jaggier and rolling credits not so smooth.
-
Because I think the FCP de-interlacing will look like crap. I’ll run some tests over the weekend and report back. One thing I’m going to try is this:
1) disable layers with text and graphics
2) send sequence to compressor and transcode to ProRes 422 using the de-interlacing filter with frame control settings
3) change fcp timeline settings to ProRes 422 progressive
4) import the de-interlaced video file and replace the old
5) render titles and graphics over the new footage and voila!Unfortunately this means compressing the interlaced footage twice when it’s time to export for final output (mp4) but I think it might give me the best results.
-
Personally, I’m waiting to finish a project before upgrading to Mavericks. But what was your upgrade process? Did you install Mavericks over ML or do a clean install? If the latter, I assume you then installed Rosetta from SL so that you could install FCS 2? If the former, maybe consider doing the latter… But I’d wait and see what others say…
-
I wonder why you’re getting the crashes. I was cutting with fcp 6.0.6 on lion just fine. I’m now doing the same with ML. Occasionally I’ll get a crash… but very rarely.
You said you’re running fcp from an external drive? Hmm..
-
Wow, I’ve been putting up with this for so long I forgot it was a problem. I started a thread about it once, referring to my issue as screen tearing. I experienced it the same time I upgraded my computer (which came with lion) and changed displays, using a 27″ TBD. I thought it was the display and had some geniuses test it at the apple store but their display showed the same thing. I didn’t know it had anything to do with an OS X upgrade.
-
Did you lost QT Pro 7 along the way? Or is it installed too?
-
[Steve Walker] “It was worth downloading for the tagging in Finder. It seems pretty stable so far folks.”
Awesome news. Who wouldn’t want the latest OS to run their EDL of choice? For me, I can’t wait to finally have tabs in Finder. -
Thanks for starting this post, Jared, and Steve for responding as you did. My experience has been that if 7 works, so does 6. The only issue is installing 6, for which you need Rosetta. But when my G5 died, and my only other machine was a 2011 Macbook Air, people here said it wouldn’t work. You can’t edit on a Macbook Air, that’s crazy! But guess what, I installed on my Air and kept on cutting. Then Mountain Lion came out and people said don’t upgrade. It won’t work. I proved them wrong once again. Now I’m cutting with a rMBP. I’m still not interested in FCP X. And even Apple wouldn’t sell me an upgrade to vs 7 – only the full $1000 discs. So I bought SL for the sake of Rosetta, and in a couple weeks time, will test it out on my wife’s laptop which is now running Mavericks and report back here. But I’m optimistic. I’ve already read on other forums that it performs just fine. Till then, I’ll be following this thread.