VideoEffectConsumer-unexpected status returned from Render Effect

this is happening with New Blue FX and older boris FX

Hi there

Possible that you have a corrupted render file for a specific effect....   

Can you load the sequence with the video monitor icon turned off, so no video is displayed?  What happens?

Once you do that then mark the whole timeline in and out with all tracks active, and from the clip menu choose "clear renders" and then re-render the timeline and see where you go from there. 

When you get the error screen, you can always start with "continue", but if the problem persists, exit the application and relaunch. 

MM

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 install of WIN11 and AVID and New Blue, basically to get rid of Quicktime for sure, made the problem much harder to replicate (a good thing) but stacking a bunch of New Blue FX and adding them to other clips and then rendering will very often trigger it now.

The message is about rendering...what triggers that message in your system?  Any tips to pass on to NB to make this problem go away completely....?

...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....

...for sure, the WIN11/AVID/New Blue rebuild created new projects, users, site settings, etc...then testing took place.....with the multiple stacking triggering the error....

I am having the same problem, the issue has persisted for over a year on two different crates - both windows 11. Did you find a resolution? It's driving me nuts!

start by getting rid of quicktime...that helped for sure.....but the issue is still there.....

Both AVID and NB are aware of the problem but its new to them....its a good thing you spoke up....

Thanks. I reported the bug to NewBlue in Feb 2023. This was a proposed fix they sent me at the time. It seem'd to do the trick on my old crate, but now I have upgraded, the problem has returned and the following steps now appear ineffective. They seem to think it's a conflict with Titler Pro 7 .

1. Reboot the system
2. Uninstall Titler Pro
3. Delete Titler from C:\Program Files\NewBlueFX
4. Delete any folders referencing "Titler" from C:\Program Files\Avid\AVX2_Plug-ins\NewBlue
5. Delete Titler from C:\Program Files\Avid\AVX2_Plug-ins\NewBlueFX
6. Reboot your system
7. Click Start and type Regedit, then run the app
8. Within Regedit, look under HKEY_CURRENT_USER > SOFTWARE, right-click NewBlue and select Delete
9. Next look under HKEY_LOCAL_MACHINE > SOFTWARE, right click NewBlue and select Delete
10. Re-install Titler Pro

happy to report this is apparently fixed in the latest beta....tested here and it worked fine....maybe NB will release this soon?

Hey!!   Everyone here is in the Thu, Oct 13 2005 crew.....

I will ask if you can get the beta version with the fix......easy enough.....but, no idea what the legal stuff is, etc.....

check for an email, Tim.....New Blue said it was OK to share the beta with the render fix....