Wondering who else has this problem and if anyone has logged it allready as a defect as its very annoying:
i have a timeline with 2 layers, openclip on V1 and a logo on V2 , both are connected to other segements in different sequences, both segements are rendered
I update the V1 openclip with a new version from grade.
Randomly - in other timelines - where the clip was smart replaced (by versioning the openclip and there is also a layer above the replaced clip the render of the above logo does NOT get invalidated,.
We had this problem now on 2 larger jobs and its a absolute neck-braker
Current solution is to flush renders everytime before export which obviously is completely ridicolous.
So yea let me know, if nobody has submitted it as a bug - I will do it.
Flame 2025.2.1 , MacOS whatever , projectsever , central framestore.
I can confirm this has happened to me on many occasions but I usually fix it and move on and by the time I catch my breath I’ve forgotten that it happened. I haven’t had time to dig in to try to figure out a root cause but it would be a fun thing to investigate one day!
Loooong time thing… I tend to work with all segs unrendered bc of such. Anything that needs a rendered status to playback realtime, gets promoted to a comp. A logo w an Action and a Comp shouldnt need to be rendered.
Same. If I’ve got a bunch of timeline renders already done when I update openclips I tend to do it from inside format rather than at the fx ribbon at timeline level and toggle the color management to something else and then back to force invalidate the render.