Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

FCPX hiccups during transitions - help!

Please have a look at this movie - http://vimeo.com/34601706


First, you must know I am a complete novice and am fairly sure this problem is with me not doing something right.


This was created in my trial version of FCPX. Every place there is a transition, the movie gets hung up. This is apparently not a Vimeo problem because the exact same thing happens when I burn the movie to a DVD (which is how I initially found the problem). Here is what I am doing:


  1. Bring clips in (via FCP import) directly from my XA10 to an event
  2. Create a new project, link it to the event and let FCP decide the format based on the format of the first video clip brought into the timeline (1080i, 60i - FCP converts 60 to 29.97 and I would love to know just how it does this and what the ramifications are)
  3. Drag in my clips and transitions, and bring in a music track
  4. Render the entire thing (which seems redundant because FCP seems to begin rendering automatically whenever I make a change in the timeline)
  5. Play the timeline from beginning to end within FCP, and note that it runs perfectly
  6. Then, using the "share" pulldown, either send it to Vimeo (as 1080i, 29.97) or burn to DVD (automatic settings)
  7. See that the exact same problem occurs with each one


OK, where am I going wrong? If you need more info, just ask for it. I am not sure what you might want to know, so I am being lazy and not listing every detail I can think of. Thanks a bunch for your time considering this.

MacBook Air, Mac OS X (10.7.2)

Posted on Jan 5, 2012 11:08 AM

Reply
18 replies

Jan 5, 2012 2:50 PM in response to Whiteshirt

Whiteshirt wrote:


  1. Bring clips in (via FCP import) directly from my XA10 to an event
  2. Create a new project, link it to the event and let FCP decide the format based on the format of the first video clip brought into the timeline (1080i, 60i - FCP converts 60 to 29.97 and I would love to know just how it does this and what the ramifications are)
  3. Drag in my clips and transitions, and bring in a music track
  4. Render the entire thing (which seems redundant because FCP seems to begin rendering automatically whenever I make a change in the timeline)
  5. Play the timeline from beginning to end within FCP, and note that it runs perfectly
  6. Then, using the "share" pulldown, either send it to Vimeo (as 1080i, 29.97) or burn to DVD (automatic settings)
  7. See that the exact same problem occurs with each one


  • 1 Select the option, optimize media when importing
  • 2 Don't let FCPX choose the project setting, try setting it manually by selecting the custom option
  • 3 Is your video siiting in the primary storyline? can you upload a screen grab of your timeline?
  • 4 Switch rendering off in your preferences. You really don't need to render, I find it a waste of time
  • 6 Try not sending it directly to vimeo, instead share your project, and choose the export media option. Once exported, bring the file back into a new project, then choose share - vimeo option.


Tony

Jan 5, 2012 3:48 PM in response to Whiteshirt

Forgot to mention, you can optimize your current media in your event by selecting all your video clips, right mouse clicking and choosing Transcode Media. Tick the Create Optimized Media, and let FCPX transcode. Once the transcoding is done, FCPX will automatically connect the media in your event to the new optimized files.


I keep saying this in all my posts, BUT THAT I LOVE ABOUT FCPX 😉

Jan 5, 2012 3:55 PM in response to blimpmedia

Newbie question for you - what does optimizing the media do for me? It might help to add that at this point I am interested in the highest quality video and audio (or at least that is what I am trying to work towards, hence the abandoning of iMovie).


I would love an explanation of what optimizing actually does and the pros and cons of it.


Thanks!!

Jan 5, 2012 4:29 PM in response to Whiteshirt

Whiteshirt wrote:


I would love an explanation of what optimizing actually does and the pros and cons of it.


Pros: The Optimized Media option is a Apple ProRes 422 codec. 422 is a uncompressed codec which makes it easier for your CPU to work with, as opposed to the native codec like H.264, AVCHD etc...


From what I've been noticing in this discussion group, a lot of the problems people are experiencing is that there trying to work with native formats, which seems to be causing havoc. I strongly suggest for the time been you work with Optimized AKA: ProRes 422 till Apple iron these minor issues out.


Cons: Unfortunately the down side to ProRe is that it ends up being double the file size when transcoded too, which means larger HD, and the time it takes to transcode. Apart from that, personally I don't believe there are any other downsides, more positives than negatives 😉

Jan 6, 2012 2:42 PM in response to blimpmedia

Thanks for all the helpful information folks. I messed around with this last night and will have to mess around more tomorrow. It seems that if I switch out of the H264 codec and into the Apple codec, a noticeable bit of resolution is lost. But by now I may have royally screwed everything up, so tomorrow I will start this all over from scratch, following your suggestions and see what happens.


Here is my thought that goes against the concept of optimizing (if I have things right). The native codec of the XA10 is H264, which FCP seems to import unchanged (is that right?). Vimeo, for example, asks for uploads to be in H264 format, and so I would think sticking with H264 throughout the life of the project from import to export would be least likely to be buggy, drop frames and/or lose resolution. But again, I am an amateur, so please school me on this. I am drooling to learn this stuff and learn it the right way. I want to make nice clear movies - bottm line.


Oh one more thing, the footage I am using from the camera is actually 60i, but FCP is stating it is 29.97. Somewhere along the line I read an explanation of this (although the explanation was unsuitably terse), but would love it if you guys could touch on this concept as well.


Thanks again! This place is quite helpful.

Jan 6, 2012 3:22 PM in response to Tom Wolsky

Tom, thanks - I was hoping you'd chime in. This is where I get confused. I *thought* 60i meant 60 frames, even though they are incomplete frames. That is, e.g., Frame 1 contains lines 1, 3, 5, etc. and Frame 2 contains lines 2, 4, 6 etc. If I am correct, then deinterlacing I assume would yield 30 (or actually 29.97 as you point out). So in reality, 60i means 30 "complete" frames, but isn't the rate still 60 fps? What is FCP doing to make the rate 29.97? Or am I just thinking about this all wrong?


Thanks again - I would love to know how this works.

FCPX hiccups during transitions - help!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.