Here is a little more info from the header file in the ACF SDK... /*! \remarks A hidden parameter that indicates whether or not an effect internally uses an accumulation buffer so that the results of one frame depend on the results of previous frames. A True value signifies that the effect must always be fully rendered in one atomic operation, while

[quote user="jef"] I checked it in draft, 8bit and 10bit. [/quote] Hmmm, I'm not sure then - if you want to send me a small sample clip, I'll take a look at it. Is the transcoded material also 2K like the original ARRI or was it resized to HD? Is there a spatial adapter (FrameFlex) on the clip in the HDi project? [quote user="jef"

Hi Jef, I'm curious if were you stepping through in draft mode? (The motion effect is somewhat limited in draft mode, which might explain that cadence.) If so, how does it look in full quality mode instead? Render always operates in full quality mode, which might explain why the precompute looks ok. Thanks, Bruce

[quote user="usatraveler"] Does this also mean that DNxHR becomes available in 8.4 in all project types, in order to provide that rate/resolution independence? [/quote] In legacy SD/HD projects, it's only for transcode in v8.4.

[quote user="Eric Hill"] Why on earth it's only available when your project is set to greater than HD resolutions is beyond me as it's completely capable of transcoding to 1920x1080. [/quote] That restriction will be lifted in v8.4. Thanks, Bruce

[quote user="jdrouette"] Here's hoping for the next patch. [/quote] Hey guys, We made what we hope are some improvements to the handling of field topness with respect to FrameFlex. The intention is for the functionality to be comparable to the old converters. These changes will be available in the upcoming MC v8.4 release. Please try them

[quote user="jef"] I have a 1920x1080 sequence. I have a 1280x720p shot in the sequence. This shot shows a motion adapter, but not the Frameflex adapter on the clip in the sequence. [/quote] Hi Jef, MC decided not to apply a FrameFlex in this case. Since HD 720 & HD 1080 have the same aspect ratio (16:9) and bounds boxes (1600.0*900.0

Hey guys! Initially, I was skeptical about the claim that the FrameFlex resizer was faulty, since it actually uses the exact same scaler and interpolation method as the old implicit converter that was used before MC7. However, after digging into it a little further, I discovered that there is indeed a subtle problem with how FrameFlex processes a change

That setting was introduced in v7.0.3. Your system specs said v8.1, so I had assumed you would have it...

How about disabling Settings->Render->Use frame blending in Motion Adapters? Note you'll need to reload the clip into the source monitor and reedit it into the sequence.