[Paul Dougherty]

Thanks Steve. Does that greater risk of artifacts or stutter in the video playback in the canvas display?

[Paul Dougherty]

Yes, thanks I tried this but found it pretty ineffective for removing a color cast.

[Paul Dougherty]

Thanks Brad, that close to what I’m doing. I’d prefer 29.97 but as I mentioned Seq setting but is set or locked at 30 (Editing Time Base) and provides no way I see to chg it to 29.97

Paul

[Paul Dougherty]

Thanks Alan – I will go ProRes & 48k with everything

It’s a tangent but does anyone have an answer to why has this usually reliable prompt gone away? “Change sequence settings to match clip settings?” 

Best,

Paul

[Paul Dougherty]

Yes thanks Alan, I started doing that. I should mention more problems seem to arise working with Vimeo clips. However using 3.5 when I take a Vimeo h.264 clip and drop it into Compressor, all’s well with the first clip but the 2nd appears in Compressor with “jobaction” in the corner and the system goes nuts with long delays. The workaround is a new batch for each clip, silly but it seems to work.

[Paul Dougherty]

correction I’m working in FCP6 but *could* move up to 7

[Paul Dougherty]

“Are you just keyframing position in the Motion tab?”

Yes. Applying Strobe to that clip with position keyframes doesn’t do anything in my tests. (my strobe needs are uniform, no keyframes there)

Thanks

Paul

[Paul Dougherty]

Yes I had Googled that a bunch, to little avail. Just did it again. You get little other than Alex’s free ripple transition, that while better than the standard, it has a very hard edge that I don’t like. cgm has a slightly better version that’s part of a bundle of 33 filters for $184. If the ripple was perfect I might buy it but… while the ripples are softer in the middle of the transition, they start out hard in spite of adjusting the blur radius.

Maybe displacement with a moov is the way to go, but I need help with that.

[Paul Dougherty]

Thanks Mark, I’m more of an AE guy for the hi-end efx and was hoping to do this in FCP proper.

-P

[Paul Dougherty]

Thanks. I’ll suggest the viz code route to my client but on a job with *volume* the FCP render time for generating the viz introduces a lot of overhead. Makes me wonder if there is something in Quicktime that can dynamically generate a viz display that has more permanence (works in regular Qt player) ie. can be saved (Save As) with the viz display. (This being faster than setting up as FCP Seq with viz and then exporting).

-P