Problem with the Loader Node

Hi everyone,

This is my first post on the forum. I'm not a native English speaker—hopefully you'll still be able to understand my message.

I have the following issue in Fusion: I've created a custom title graphic in Fusion that I intend to distribute to multiple users so they can use it on their own computers and make certain modifications. The title graphic includes, among other nodes, a Loader node that allows the end user to insert their own images into the title graphic based on the theme of their video, using files from their own storage drive.

In this title graphic, I've set a simple default .JPG image in the Loader node using the setting:\ path, so the end user can replace the default image with an image of their choice from their own drive.

Now, the problem arises when the end user tries to load their own image into the Loader node. When they are in the Inspector window and select the image they want to use via the "Browse" button, a following pop-up window immediately appears:

ss1.png (147.76 KiB) Viewed 1053 times

If the user clicks "No" or "Yes," Resolve crashes without warning. This is obviously a problem if the user's project hasn't been saved recently, as their work could be lost. If they click "Cancel," the pop-up disappears and the image loading is canceled.

I've also noticed that sometimes the pop-up doesn't appear at all when loading an image (.JPG or .PNG) from the Desktop or Downloads folder. However, when loading from the Documents folder, the issue occurs quite frequently. I'm not sure if this is relevant, as the pop-up refers to Trimming and Extend settings.

I'm wondering if there's a way to prevent this pop-up from appearing altogether. I'm also confused about the "Frames" values, since we're just replacing a simple static default image with another image—there are no GIFs or videos involved. Is it possible to configure the Loader node to accept images with different frame lengths? Could the issue be caused by replacing the default .JPG image with a .PNG image?

Crashes should never happen so I would advise creating a screen capture and then sending that and a Resolve Log to the Blackmagic support.

A workaround could be to use a switch node that enables another input on the template that would accept a different logo through a media in node.

Crashes should never happen so I would advise creating a screen capture and then sending that and a Resolve Log to the Blackmagic support.

A workaround could be to use a switch node that enables another input on the template that would accept a different logo through a media in node.

Thank you for your reply and your tips. I’ll definitely send a report to Blackmagic about this crashing issue.

That Switch node is not familiar to me, so I’ll need to look into it.

About the MediaIn node: I’ve understood that using a Loader node with the setting:\ file path is a more functional solution in cases where the template with different media files is intended to be distributed to other users.

Yes that is usually the right approach. But if I understand correctly the crash occurs when the customer is changing the path to a custom image. That’s why I would split it up. Keep the loader with the Setting: Path and allow the customer to switch to the custom input.

In theory you could also check if an input is connected using the switch node and an expression.
Then it would automatically switch to the custom image, but that expression in combination with the switch node has a project bricking bug as of the time I’m writing this.
It’s a bug that I have send to the support two months ago but unfortunately it hasn’t been fixed yet.

Yes that is usually the right approach. But if I understand correctly the crash occurs when the customer is changing the path to a custom image. That’s why I would split it up. Keep the loader with the Setting: Path and allow the customer to switch to the custom input.

In theory you could also check if an input is connected using the switch node and an expression.
Then it would automatically switch to the custom image, but that expression in combination with the switch node has a project bricking bug as of the time I’m writing this.
It’s a bug that I have send to the support two months ago but unfortunately it hasn’t been fixed yet.

Yes, the crash occurs specifically when the user tries to replace the setting:\ image with a custom image file from their local file path.

I'm going to try out this Switch node. Thanks again for your help!