I’ve always seen intermittent issues with dissolves since the earliest timelines. The most common is that it fails to clear its render cache when swapping the footage. Sometimes they just go black. In more recent versions I have seen unrendered ones do some really sketchy things like display frames from a completely different part of the timeline, until they are rendered, in which case they are fine.
I’ve always had issues (going back to the earliest of xml imports) with transitions wanting to start from black. I have to delete it and reapply a flame dissolve. This has bitten me many times over the years and I sometimes just go ahead and make an action with a surface transparency animation to avoid it.
This is why as soon as I see one transition has an issue… I switch to action transparency and sync everything using that method. You just have to manually delete all the transition effects. Hopefully I’ve caught it before the edits start multiplying.
I think it goes back to the fact that it comes from xml/aaf conform. The dev team would probably say ‘send us the files’ to investigate. But it’s so random for me that I can never repeat it consistently.
For me, the inability to clear the cache seems to come randomly with no history of an xml/aaf. The crazy shit tends to come from aafs. I also get crazy shit in the layers below when there is an action effect from xml/aaf.
such a basic thing.