[Andy Smith]

Yeah, but our case we have a home grown programme and won’t be using EditShare. Many ingress and egress systems involved and it’s crafted around the organisations needs so it doesn’t help when it looks like if anything Apple might end up doing some form of MAM that is created around FCPX behaviour rather than something more traditional.

Don’t get me wrong, we have various things that don’t fit the traditional mould such as frame based systems as well as numerous file based NLE but they have their own place and they have long since been considered.

[Andy Smith]

Wow, I didn’t notice you could do that. Ah well, that will save me a lot of time, thanks again Mark!

[Andy Smith]

Yep, and get this, it doesn’t actually work at all if you use ProRes with Interlaced video.

If you change the Field Dominance to Progressive PRIOR to analysing (I’m from the UK that’s not a typo :)) then it does stabilise but you seem to need to apply maxed out rolling shutter correction to cope with warping effects.

If you forgot to set the Field Dominance then your only choice seems to be to throw the media away and delete it completely from FCPX and reimport it. I tried a lot of things and couldn’t do anything that would make it go through that ‘Dominant Motion Analysis’ again once it thought it had done it :S

Oh yeah, but if for some reason your media is in it’s native format (first time I tried it I forgot to import with Convert to High Quality media turned on) then it DOES seem to work.. figure that one out 😮

Reaaally hoping they sort out the Motion 5 round trip soon, that’s the proper way to go.

[Andy Smith]

Thanks Mark, I’ll need to dig around at that end a little further then.

I have let FCPX analyse stabilisation but it’s crude and it’s not having any noticeable effect on this clip so I though that nailing some tracking points in Motion would be the best approach. The stabilisation in FCPX seems to be based on automated Dominant Motion analysis that you can’t do much with to customise (as far as I can see).

The only thing I can really think of as the best solution for this is to output as a separate clip directly from Motion, bring it back into the events in FCPX and add it to the project again. This isn’t really how I want to work and it’s going to use a lot of disk space doing this kind of thing.

I’m just wondering if the integration will arrive when Lion launches…?

[Andy Smith]

Cheers Tony,

I suspected that might be the answer. Ah well, hopefully in the patch :p

[Andy Smith]

Never mind, I found it.

Select a range with the range selection tool, turn on looping and hit / to play region. I was hitting the play button on the Viewer so it was ignoring the range.

[Andy Smith]

Sorry for the typo, the last one should have read…

x64 Kernel

[Andy Smith]

Hi, first post here btw.

I was lucky to be able to download FCPX (well some might disagree) with my iMac 7,1 which has one of the unsupported Radeon HD 2600s. It works fine, it’s a little sluggish at render and very sluggish at image stabilisation but to be honest my MacBook that does have a supported NVidia card in it is almost as slow.

I did a good deal of digging around on OpenCL today and it seems that OpenCL on Snow Leopard has 4 Kernels

An AMD, one which is restricted to running on the ‘compute shader’ of the AMD chipsets that support it and doesn’t support the ‘vector shader’ of the chipsets (which all the cards have, only 4xxx+ series have a compute shader).

A PTX kernel which is used for NVidia cards

A 32 bit x86 Kernel (why???)

An x86 Kernel

It looks like for some tasks (and I didn’t pull the OpenCL samples apart too much) that a GPU based Kernel is absolutely required, if the Kernel is then going on to manipulate the graphics directly.

In the case of FCPX though I’m guessing this doesn’t happen and the x64 Kernel may be the one that’s ‘unofficially’ supporting the product on unsupported machines.

The downside is that Apple could, in one line of code, specifically request the GPU type of OpenCL Kernel only. It would be extremely petty to do that though since performance levels are bearable for some folks on a tight budget and it would stop the product running on a Machine that the App Store already OK’d for the product to be installed on.

This site has some background on the ATI cards https://netkas.org/?p=182

Sadly the option strings in the part of the framework that are mentioned have been now removed so it looks like somebody decided to tighten up the ATI OpenCL codebase.

Regards,

Andy