[Ronny Courtens]

This requires a workaround. You can use Xto7 to get the FCPXML into FCP7 and in FCP7 send to Color.

But if Color is not absolutely necessary for you: get Davinci Resolve. It’s free, it’s good and you can open FCPXML straight in Resolve. No workarounds.

[Ronny Courtens]

Indeed.

Arrow = 1 px
Shift+Arrow = 10 px
Option+Arrow= 0.1 px

[Ronny Courtens]

As Mark says.

Highlight the parameter in the Inspector (click on its value) and use the Up and Down arrows to nudge.

OPTION+Up or Down arrows will increase or decrease the parameter by exactly 1 pixel.

[Ronny Courtens]

If you mean nudging in the Timeline:

Nudge 1 frame to the left: ,

Nudge 1 frame to the right: :

This is on a French keyboard.

[Ronny Courtens]

You will have to make sure the clip you are adding as an Audition has the same length as the original clip on the Timeline:

1. Select the clip on the Timeline and press CTRL+D.
This will show you the length of the clip in the time counter under the Viewer. Say the length shows 5:12

2. Select the clip you want to add as an Audition, set an In point and press CTRL+D. Then enter 512 on your numeric keypad and press Return.

3. Press SHIFT+Y to add the clip as an Audition.

When you open the Audition you will have two clips of exactly the same length and nothing will move on your Timeline when you switch from one clip to the other.

[Ronny Courtens]

Hi Sascha,

I usually don’t let FCPX analyze anything while importing. This takes extra time, and you can still do any analyzing on a clip by clip basis or on a group of clips anyway once you have imported the clips.

For your first questions, this might help:
https://help.apple.com/finalcutpro/mac/10.0/#verb6acc101

Auto balancing is what it says: it’s an automated feature that may (but not always) produce a proper color balanced shot. The analysis is non-destructive: you can always deselect it in the Inspector while you are editing (Video tab > Color: Balance). I rarely use this.

Analyze and fix audio problems:
https://help.apple.com/finalcutpro/mac/10.0/#verb6acaf60

You can always analyze and fix audio problems when you hear problems with imported clips. Again no real need to do this while importing. Select the clip in the Event Browser (or on the Timeline) and go to Inspector > Audio tab > Audio Enhancements. Click the little right arrow to reveal the Audio Enhancements window.

When you have stereo audio that you want to configure as dual mono channels you do this after importing: select all the stereo clips In the Event Browser (or on the Timeline) and in the Inspector > Audio tab > Channel Configuration change Stereo to Dual Mono.

Remove silent channels is one of the useful things you can do while importing. Although you can easily deselect silent tracks on the timeline or in the Events Browser as well.

[Ronny Courtens]

I can confirm that this export error is often related to corrupt or wrongly connected render files. Your workflow seems logical as it creates new render files for the problematic ones. Many times I delete all Project and Event render files before sharing a project. This does not affect export times.

[Ronny Courtens]

Broadcast dept. does TVC, trailers, episodic, long-form doc and narrative post for national broadcast. Plus a lot of in-depth sport and cultural programs (no news). Our other post dept. does subtitling and dubbing for the European market (cinema and television).

[Ronny Courtens]

Absolutely, Aindreas, but this is a debate forum after all (-:

[Ronny Courtens]

I’m in Brussels. I run a fairly large post house here and we also have an affiliate in Paris (15+ seats). We use FCPX exclusively, teamed with Resolve and Smoke. I see FCPX gradually being adopted in many larger facilities I know. Don’t know about Holland though, guess many are still on FCP7 or Avid there. But Media College Leiden now teach their film students FCPX, so does Broadcast College in Brussels. It is rapidly gaining ground. If you are a creative editor you will simply enjoy working with this app. I know I do.