happy to report the NLE showing fix is in the latest 7.1 version of Titler Pro

https://newbluefx.com/totalfx/#pricing If you are considering New Blue...this is a good time.....

this shows WIN11 support https://borisfx.com/products/continuum/

is there a camera codec that the work avid has that this one does not? what sort of camera was it? Can you flip in the file in an encoder and get it to work or does the pixel error stay there?

...more notes....relaunching MC will allow the effects to be rendered.....it stays good for a time..... ...when it fails, everything NB FX fails...even FX that had rendered already.....This affects NB Elements, Essentials, Filters and Stylizers...nothing fixes it but a relaunch.... ....again, NB Transitions seem to be fine......Titler Pro 7 seems fine

Hello Marianna, This is being triggered by New Blue Effects but not Transitions, best i can tell. It was pronounced enough for a question about it to be raised on the New Blue beta testers site....and they couldn't reproduce it. It was also triggered by Boris 2019 BCC FX but not by the latest version. And not on the Mac side of New Blue. A clean

staying at multiples of 24 will help any artifacts.....many cameras can go to 48.....if its only B-roll then playing with higher frame rates and also adjusting shutter speeds can give you footage that will be most univerally useful in the future, if that is a goal.

what happens if you just bring the footage in to your project and let AVID adjust for the frame rate?

shoot as high a frame rate as your camera will allow.....AVID will adjust to it and higher frame rates make for smoother slow motion.

VideoEffectConsumer-unexpected status returned from Render Effect this is happening with New Blue FX and older boris FX