Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Crashing quite a bit

  • Crashing quite a bit

    Posted by Jeremy Garchow on July 8, 2011 at 5:28 pm

    Anyone else? Seems to be when I try and trim too much or too fast. 10.6.8, 64 bit, clean install.

    I can, however stack a crap load of effects to try and crash it, and it won’t.

    -The organization capability in FCPx is totally blowing me away. This is awesome. Seriously. Or perhaps awesomely serious, seriously awesome.

    -Also, if you at first bring in a clip without transcoding, and then decide to transcode it later, does it still show up as the original media in the browser for you?

    For example, bring in h264 clip natively, choose later to transcode through the right click drop down, the clip still shows h264 in list view, but if you reveal in finder it’s connected to the ProRes transcode. Makes things a bit confusing, considering there’s now 3 copies of the same file on my drive (the original, the original in the event, and the “High Quality” transcode in the event).

    -The handling of the media is not seriously awesomely serious awesome. Why do I need 3 copies of the same material? Seems like we are losing instead of gaining efficiency in this regard.

    -Once you break apart audio and video, is the only way to stitch them back through a compound clip?

    -Does bringing in P2 media result in some archaic naming scheme for you? Seems to be roughly tied to the creation date. I have throughly logged P2 footage using P2Flow, and NONE of that information gets passed over to FCPx. This is not real fun either.

    -One more thing, where does the “opacity” control show up in the inspector? Seems to only show up when hitting ‘y’. The manual seems to allude to that the compositing controls can show up in the inspector as well. What am I missing?

    Looking forward though, looking forward. If FCPx is allowed to get serious, this is going to be a blast.

    Jeremy Garchow replied 14 years, 11 months ago 3 Members · 6 Replies
  • 6 Replies
  • T. Payton

    July 8, 2011 at 5:44 pm

    What Mac are you on? My iMac at home crashes FCP X very often. MacBook Pro, crashes it seems like every other edit. MacPro, crashes only slightly more than occasionally.

    [Jeremy Garchow] “Also, if you at first bring in a clip without transcoding, and then decide to transcode it later, does it still show up as the original media in the browser for you?”

    It’s a “version” of the media. Very slick actually. You can see what versions you have by going to the inspector, info tab, clicking the gear and choosing “show file status”.

    [Jeremy Garchow] “The handling of the media is not seriously awesomely serious awesome. Why do I need 3 copies of the same material? Seems like we are losing instead of gaining efficiency in this regard”

    You don’t need 3 copies. You don’t need optimized media unless your system can’t handle the native stuff. Also sounds like you have the setting to copy the media to your event. Just deselect that in preferences.

    [Jeremy Garchow] “Once you break apart audio and video, is the only way to stitch them back through a compound clip?

    Yes. You are correct. It’s 1.0. (really should have been called a beta. If I would have beta tested this I would have found bugs from the first 10 minutes of using it.)

    ——
    T. Payton
    OneCreative, Albuquerque

  • Jeremy Garchow

    July 8, 2011 at 6:13 pm

    [Timothy Payton] “What Mac are you on?”

    MacPro 4,1 8 core ATI 4870. Fast Raid, my regular editing machine.

    [Timothy Payton] “It’s a “version” of the media. Very slick actually. You can see what versions you have by going to the inspector, info tab, clicking the gear and choosing “show file status”.”

    OK. Then the version that is listed in the browser is wrong. Under “Codecs” it says h264, when in the inspector it’s pointed to the ProRes file. And now that there’s at least 2, if not three copies of the media, then its’ confusing. Amright? Also, since I have three copies, it only shows 2.

    [Timothy Payton] “You don’t need 3 copies. “

    G.D. right I don’t. OK, let’s expand this further. I have also tried to use the link to original media as you suggest. For any other media that is not QT based, you have no less than three copies. For example, for P2 material, there’s the MXF original files (1). You import that material without the transcode pref, and FCPx creates an AVC-I QT movie (2), which is now a first copy, second “version” as you call it. Then you tell FCP to transcode, and it puts a lower file size ProRes movie in the “High Quality” folder (3). This is now a second copy of the media, third “version”. This seems way unnecessary and doesn’t tell me the truth about the origin of the media.

    [Timothy Payton] “Yes. You are correct. It’s 1.0. “

    I don’t really care, just asking. It kind of makes sense, but maybe it should be called a divorce and not a break up. As even though clips seem connected through the little connection marker, they operate in their own worlds. It’s kind of like they have children and need to communicate, but they are no longer living together and would rather live in different parts of the timeline sort of thing.

    Any ideas on where the “Compositing” tools end up? I can’t find them (besides hitting y), even though the manual says I should see them.

    Never mind, just found them. The clip has to be connected above a clip for compositing to work. It you want to keyframe opacity on a clip in the main storyline, then you must use the keyframe animation thingy by hitting control-v (not y as I said before).

    Jeremy

  • Michael Jasen

    July 8, 2011 at 11:52 pm

    I was having the same problem. I loaded up a bunch of h264 and eventually it was crashing on me every couple minutes. To its credit, I never lost any of my work.

    I fixed it by transcoding the h264 to 422.

    I understand it says h264 is native, but it doesnt appear to be functioning very well for me. (i’m on an imac i5)

  • Jeremy Garchow

    July 9, 2011 at 12:15 am

    Thanks, Michael.

    I thought about that and thats one of the reasons I transcoded everything to ProRes and found that it still lists everything as h264. I still had about 4 crashes in a few hours today.

    Perhaps I should start a new event and transcode immediately.

    Do your files say h264 in “codecs” field?

  • Michael Jasen

    July 9, 2011 at 1:53 am

    It does not say h264, but I also didn’t transcode it through fcpx.

    I was annoyed with all of the data it transfered over (the multiples copies of files things you mentioned above) so I just trashed the entire event and made a new one and imported all of the newly transcoded footage (I used compressor)

    Did you ever find out how to reattach a clip that you detached audio from? Compounding a clip doesn’t appear to just undo the detach. That one’s been bothering me…

  • Jeremy Garchow

    July 9, 2011 at 5:57 am

    [michael jasen] “(I used compressor)”

    Got ya.

    I don’t think there’s a way to get the a/v back together after the divorce without a compound clip.

    You would have to have really good reason to do it as there’s not a lot if use for it that I can think of for camera embedded audio.

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