OMFG - Loader node?? That's why my media is offline?

So after fighting with this BS for months, I finally find out about the "loader" node... which I guess loads media into your fusion composition. So that is why my media keeps going offline?

One question... Why even have a "media in" node? Why have two nodes that do almost the same thing, except one of them (media in) loses track of your goddamn media ever frigging time? Why does it even exist? Why not just make the "loader" be the default? You ALWAYS need to bring media in, you always need to keep track of your media... why have a f$%king node that can't keep track of your media? WHY?

Why make me waste hours and hours of my life? Why make me rebuild timelines over and over again? Why force me to spend days and days and days searching forums and tutorials? I am so f$%king pissed right now.

MediaIn is the connection between media in edit timeline and fusion comp, loader loads a set source file without Resolve side knowing anything about it. Why MediaIn goes offline when file is perfectly available, dunno, maybe BMD support knows.

What is ridiculous is that Fusion **defaults** to the mediaIn node. When you drag a piece of media from a bin into Fusion, it creates a mediaIn node. It should create a loader node. I could see if you are creating a fusion clip from the timeline, it defaulting to mediaIn (and even then I think it is stupid).

They are just setting people up to fail. I honestly just don't see why you would have a node that **can't keep track of media** . What is the point? Just have the loader node. And if you are going to insist on having a node that loses your media all the time - don't make it the DEFAULT.

I am months behind on my projects now because of this idiocy.

And also... this should be the FIRST thing mentioned during Fusion tutorials. I have watched about 100 tutorials, including some from BMD, and not a single one mentioned that the loader node even exists, let alone the difference between that and the MediaIn node. Or the vital - VITAL - piece of information that the MediaIn node has no idea what actual piece of media it is linked to.

God I can't even talk about this anymore, I'm gong to go punch some holes in my wall. And then go switch a few hundred MediaIn nodes over to loader nodes.

Want to be even more upset? The Loader node in Resolve can only read a sub-set of the file types that the Loader in standalone Fusion can read. It can only read image sequences for some reason.

I guess it lessens the prospect of what could become a temperal nightmare, if video of various frame rates go into Fusion and then on into a Resolve project of a certain other frame rate. It sounds like a lot of fun.

ultimately I think they're dumbing it down to keep stability in the Resolve timeline.