[Annaël Beauchemin]

I agree with all of this. AE’s time remap, even if it’s not doing an “optical flow”, is MUCH better than FCP’s time remap. FCP time remap gives all sorts of jitters and the GUI is horrible to use.

At least with twixtor you can now use FCP’s built-in time remap and render with Twixtor’s engine. This solves one of the problems…

[Annaël Beauchemin]

> I’d not shoot at 1/500th shutter unless you want that Gladiator battle high shutter speed look. I’d shoot with the standard,
> 1/48th I think for 24p, and either 1/60th or 1/120th for the slowmo stuff, based upon experimentation

This is interesting.

I’m not sure why the standard shutter speed would be better than a higher speed shutter for slowmo. In my experience, the motion blur of low shutter speed can create a randomly “throbbing” motion when slowed down. Sharp footage does also work way better with twixtor or the like.

But I do have less experience than you… so why do you recommend the standard shutter speed?

[Annaël Beauchemin]

you can disable field rendering by setting Field Domincance to None in the Sequence settings. This won’t deinterlace footage, but will prevent renders to be interlaced.

[Annaël Beauchemin]

I recently discovered this bug too. On my system it happens when I switch keyboard layout in the keyboard input menu.

I do this often when I work in AfterEffects in conjunction with FCP… I must use the US layout for aftereffects to use all the nice shortcuts. Flushing prefs doesn’t change anything.

[Annaël Beauchemin]

you can also select a clip, press ENTER or RETURN.

If a clip was previously open in the Filter tab, other clips will open in the Filter tab too. Unless you try to open it a second time.

[Annaël Beauchemin]

[justinheaney] “Is it possible for this FCP reference movie to embed the info of the sequence it came from, so that when it is opened, the original cuts will be there on the timeline?
“

No. For this you must export an EDL, a XML or an AAF if you have automatic duck.

The FCP quicktime movie will only embbed a video track, audio tracks and a timecode track.

[Annaël Beauchemin]

that was one very big smiley…

[Annaël Beauchemin]

[Le Coyote] “Avoid PNG, it will introduce a gamma shift when you’ll import back to FCP (or quicktime). Tiff is alright, PSD too.”

Actualy, if you export from FCP, retouch in PS, and then reimport in FCP it’s fine. But when you export to PNG from another app, FCP will screw it on import.

By the way, if anyone has an explanation on this…

[Annaël Beauchemin]

[Matte] “Step 3: Options… > Format: (choose PNG, PICT, TIFF or Photoshop) > OK “

Avoid PNG, it will introduce a gamma shift when you’ll import back to FCP (or quicktime). Tiff is alright, PSD too.

[Annaël Beauchemin]

[Graeme Nattress] “However, Apple can’t just stop at moving to Intel processors – we need PCI Express, better graphics cards with better GPUs etc. etc.
“

We’ll see PCI-E for sure, but i’m not sure about better graphics card except the usual consumer Nvidia or ATI cards. I remember having read a fxguide.com article where it was said they considered the OS X platform when they switched from SGI, but after some discussion with Apple they considered the platform not viable for one reason. Because of what? Because Apple *refused* to make room for higher end, professionnal video cards like Nividia Quadros or 3D labs wildcats.

to quote…: “It apears that there are two technical limitations that limit discreet’s use of an Apple solution, the first is the number of expansion slots and the second is Apple’s decisions on graphics cards. Discreet generally requires driver support for the highest-end graphics cards such as the NVIDIA 3000G and 4000SDI