[Jag Jagsson]

Thanks, will give it a try!

[Jag Jagsson]

Hmm, no, the multi processing doesn’t seem to cause the delay..

I have also checked that the project sample rate matches the audiofiles. The audio sound formats is ordinary wav or aiff – 24 and 16 bit.

Odd.

[Jag Jagsson]

Hmm,
Ok, you’re probably right, I’ll dig som more into the QT settings..

..but the the strange thing is that I’m able to watch all other clips encoded in animation. It’s just those specific clips I got problems with. Have they changed anything recently in the codec? New sound codecs etc.?

Are still able to watch the same clip (same hard drive) on a mac with fcp installed. In Quicktime media inspector it clearly says “using Animation codec”. Very odd.

There are also other quicktime formats that I can’t use, for example xdcam quicktime.

Prores 422 works brilliant.

I think there is time for Adobe and Apple to set up a meeting.

[Jag Jagsson]

Thanks Dave, but unfortunaly it did’t work.

What is it with fcp and their own quicktime codecs?
I don’t have fcp installed on my system and can therefore not read all quicktime files.

Do I need to buy a new computer and a fcp license or what is the deal?

High five.

[Jag Jagsson]

Kind of confused with the architecture of quicktime though. The timeline we worked with in fcp, is progressive. Also the files I rendered out. The meta data clearly says “25 fps, progressive, square pixels”. If I import it in AE, or Avid, the file displays just fine.

In THE SAME PROJECT in fcp, we imported both the HD1280 and the HD720. Fcp displays only the HD720 file as progressive. The other one as PAL with upper fields.

If I have the wrong settings in Fcp, where do I change this?

[Jag Jagsson]

Forgot to say that I’m using AE’s own Quicktime codec. Set to Millions of colors+, 25fps. Same aspect ratio as the project=square pixels, etc. Nothing strange. Got the same wierd result with PNG sequence.

HD720 works great every time though!

[Jag Jagsson]

Ok,
My project settings in AE is HDTV 1080 25fps. Progressive, square pixels. If I render a clip with the same settings (1920×1080, no fields, square pixels) in quicktime animation, FCP interperets the clip as odd/upper fields. Looks wrong, both on screen and monitor, just because the file has no fields. FCP simply looks at it the wrong way. This is what I call a bug.

If I do exactly the same thing with same settings, but stretching the file down to 1280×720, there is no problem in FCP!

Both files are looking good in quicktime (and in the movie inspector) and if I do a fresh import of the file in AE. Also looks good in Premiere, vcl and all my other video apps.

Read about other persons on the web that had the same problem, but I never saw a solution.

Why, why, why?

[Jag Jagsson]

Ye guys,
There’s loads of nice blurs out there – such as the built-in lens blur. I also find that lenscare and finalfocus looks very nice. But the problem consists..

Is it really impossible to link the camera DOF to a plugin with better blur??

Maybe there is an alternative type of camera layer/plugin to use somehow?

The built-in camera DOF blur is still a low res box blur (but yet very easy to control together with the camera movements.)

Generating depth maps to drive the blur is a dirty work that takes ages in complex scenes..

[Jag Jagsson]

True Ian. Lens distortion in “real” DOF has polygon shapes and also some displacement.. But AE DOF really looks like low quality box blur.

As far as I know this type of blur is commonly used for previews and are much faster than for example gaussian blur. You will see this if you are exaggerating the blur level from the cubic blur shapes that appears.

The reason I want gaussian blur in this scene, is that it would look much nicer with the animated graphics. But it would surely be cool to integrate and experiment with other types of blurs in the camera, such as lens blur (wich looks awesome in other cases) and gaussian..

Do you know a good way to export just the depht information in the scene to use for a plugin blur?

Tnx//Simon