Forum Replies Created

Page 6 of 9
  • Ben, I’ve been wondering the same thing. So far, there have been a lot of reports that the ATI Radeon HD 5770 works well.

    What other cards are people using?

  • Benjamin Reichman

    June 24, 2011 at 2:30 pm in reply to: Match frame: where is it?

    [Matt Callac] “I’ve been getting slight GUI interuptions too. Usually After I’m CMD+Tabbing back into FCPX. It always seems to be when I’m coming back from Firefox too.”

    Same here–it happens when I command-tab between FCP X and Firefox.

  • Benjamin Reichman

    June 24, 2011 at 12:53 am in reply to: Match frame: where is it?

    No, you’re not missing anything. I was. 😉 I pressed Shift-F, and then clicked in the Browser–which eliminated my In point before I even knew it was there. The filmstrip view is hard to get used to–I keep missing the Viewer. Maybe I’ll adapt after a few weeks.

    I just tried it again and the app worked a few times in a row, and then acted up. (It wreaked havoc with my graphics card a few minutes ago and smeared ghost images, etc. all over my monitor until it was very difficult to restart the Mac.)

  • David,

    Thanks–I know there’s no multicam editing, so it would be a manual process of cutting in part of the close-up, then part of the wide shot. And they’re OK with that. The real issue is replacing the DSLR audio with the good lav and boom tracks.

    I guess if I can use the auto-synching clips feature, and then use, um, Clip Connections? to make this work? Hmmm…I’ll experiment as soon as I have some time in a couple of hours and report back.

  • Benjamin Reichman

    June 22, 2011 at 2:48 pm in reply to: Apple’s Personal VISTA

    I agree with and understand the frustration and anger in this thread. I’m stunned. I was on a shoot when FCP X was released yesterday, so I didn’t go online, but today I feel like the COW is filled with the dazed survivors of a train crash… 😉

    However, if this is really is Apple’s Vista, there’s some hope.

    Remember that although Windows Vista was terrible, the low-level under-the-hood code, the real foundation of Windows, was revamped and remade in powerful ways. The problems were big, but they were largely with what was on TOP of that new, strong foundation.

    Then with Windows 7, they fixed all the top layers and tweaked the under-the-hood code in a few simple ways, and the result was what appeared to be a massive overhaul–a truly great operating system. But it wasn’t a big overhaul. It was simply Vista…finished.

    So if–and this is a big IF–FCP X is like Vista, a great foundation with junk on top, then Apple can in the next year or two turn it into the equivalent of Windows 7.

    Here’s hoping! And in the mean time: oy.

  • Benjamin Reichman

    June 22, 2011 at 3:44 am in reply to: Doesn’t look like Compressor 4 is 64-bit

    [Stepan Grasvenoff] “Is it still exceptionally laggy in the UI when doing large batches?”

    I’ll second Stepan’s question. This is by far the biggest complaint I have about Compressor, an app I really like in other ways.

  • Benjamin Reichman

    June 2, 2011 at 7:24 pm in reply to: What’s your FCPX plan?

    [Tom Wolsky] “Ah yes, we’ll just have to keep waiting around for the mythical June 31st to show up.”

    That’s the only day I’m confident FCP X will NOT be released. 😉

  • Benjamin Reichman

    May 12, 2011 at 10:15 pm in reply to: compressor

    Cody’s completely right: that’s what Compressor is supposed to do.

    I’ll add one more thought: if you have Final Cut Pro 7, you can use the Share function to burn a simple DVD more easily than in DVD Studio Pro. However, the Share function doesn’t give you much control at all over the look of the menu, etc.; it takes a long time; and in my experience, it’s pretty flaky.

    So I would recommend bringing the files you just made into DVD Studio Pro and creating a simple menu there. You can use the menu, buttons, etc.–or the whole project file–as a template for future DVDs.

  • Benjamin Reichman

    May 12, 2011 at 7:26 pm in reply to: compressor

    Tell us more: what codec/format did you start with, and what do you want to end with, and why?

  • Benjamin Reichman

    May 9, 2011 at 10:52 pm in reply to: Good work routines in FCP

    “5.) When using the ‘add default transition’ keyboard shortcut is seems that I can’t set all the parameters for the transition beforehand. For example the ‘Dip to color transition’ won’t save the color I choose when double clicking the transition in the effects browser and editing it. Very annoying to add 10 transition by one click and then STILL having to edit each one separately. Am I doing something wrong?”

    You can create ‘favorite’ transitions or filters and customize them. There are a number of different ways to do this, but one simple approach is to go into the Effects tab and drag “Dip to Color Dissolve” from the Video Transitions–>Dissolve bin into the Favorites bin. That will make a copy, which you can rename and change the settings of. Then right-click on it, and choose “Set Default Transition.”


    “8.) If I copy a clip from one place in the timeline or a whole other timeline it will paste into the track number correspondent to where it was placed before. This is very annoying since it will probably paste onto a clip that is already there. I tried moving the small a1/v1 sliders but they don’t seem to give me the chance to choose which tracks I want the pasted items to show up on. How is this done?”

    I don’t know how (or if) you can change the paste behavior, but if it’s a single clip, you can match frame (press F) and then insert directly into the other sequence. The correct In and Out points for the clip will be preserved.

    12.) Still question is maybe a bit too technical for this thread: I edit a lot of Canon 5D mkII H.264 clips and it’s not always that I have the time to spend a whole day converting all the footage to prores. So I edit sometimes the H.264 files directly. But when I export the timeline with the ‘current settings’ it gives lots of digital errors everywhere that I use effects (transitions/fades/etc). But if I export the timeline as ‘ProRes’ it renders perfectly. This is very annoying since it takes 20-30 times longer to export into prores instead of exporting in the format it’s already in… Any ideas why it doesn’t work?

    Final Cut Pro doesn’t handle H.264 clips well. I don’t know of any workarounds aside from converting to ProRes (or any other FCP-supported codec). Well, you could wait until June for Final Cut Pro X. 😉

Page 6 of 9

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy