Scotty Why wrote:I have your solution: Loader Nodes
I had this same problem, it was driving me crazy. Just found out about Loader Nodes. So apparently, the ironically named "MediaIn" node has no idea what the actual media is, so if it is connected to a file, it loses track of it constantly. Loader nodes allow you to tell Fusion the specific file you are using.
This is the stupidest thing I have ever heard of - a media node that has no idea what media is, AND it is the default node. WTF Black Magic? Why isn't the loader the default? When I drag a file into Fusion why automatically create a node that is definitely, DEFINITELY, gong to lose track of my media? Do you hate us? I think you must hate us.
Are you copying Fusion compositions between different projects?
If so that would explain you constantly seeing MediaIn losing connection to your media, as the MediaIn node references media by a database ID unique to the current project.
If you're not copying comps between projects then this shouldn't be happening - in which case you should post more details of exactly what you're doing.
If you're referring to importable templates/bundles, then there's a way to reference media that comes with the template/bundle - see my response in your other thread regarding the Setting:\ pathmap.
Yes, Loader nodes are preferable whenever one is using still images, including footage saved as an image sequence (EXR, DPX, PNG, etc). It refers to media directly by its filename and path, so this always works for as long as the path is valid. It can also significantly increase performance in certain situations (more details here:
Fusion page: Major performance issue with MediaIn v Loader)
However the Resolve Loader node has been crippled such that it cannot open video footage (H264/ProRes/DNxHR etc). So one has to use MediaIn in that scenario. And to be fair that should work fine, so long as you remember how MediaIn nodes work and what exactly they're referring to.
MediaIn nodes are of course required in situations where one wants Fusion compositions to reference Edit media - which IMHO is the major benefit of Fusion's integration into Resolve.
Last year I wrote a length summary of the different kinds of Fusion compositions, how their MediaIn nodes access media, and how those compositions are stored within a Resolve project. You might find it useful:
viewtopic.php?f=22&t=120441#p662597