Blackmagic Forum

Hello, absolute Fusion noob here.

When I select a clip from the timeline in Resolve, then click the fusion button, Fusion loads but the viewers are blank. I have tried toggling the rightview leftview dots, and split wipe... nothing.

Literally every tutorial just says put the playhead over the clip, then click Fusion button... but nothing displays in the viewers when I do this, and no amount of messing around changes this for me...

What am I doing wrong?

This is Resolve 15.2.4.006
on CentOS 7

Try selecting the MediaIn node then clicking 1

Alaz Soytemiz wrote:Try selecting the MediaIn node then clicking 1

Thanks, tried that, didn't work.

I also have tried opening new projects, and adding different clips.
I have also tried to drag the Mediain over to the viewer...ect.


These are all .mov files, does that make a difference?

joel383 wrote:

Alaz Soytemiz wrote:Try selecting the MediaIn node then clicking 1

Thanks, tried that, didn't work.

I also have tried opening new projects, and adding different clips.
I have also tried to drag the Mediain over to the viewer...ect.


These are all .mov files, does that make a difference?

Try starting out with a generator instead of a video clip, like a Solid Color Generator or a Fusion Comp Generator and see if they appear in the viewers.

xunile wrote:

joel383 wrote:

Alaz Soytemiz wrote:Try selecting the MediaIn node then clicking 1

Thanks, tried that, didn't work.

I also have tried opening new projects, and adding different clips.
I have also tried to drag the Mediain over to the viewer...ect.
These are all .mov files, does that make a difference?

Try starting out with a generator instead of a video clip, like a Solid Color Generator or a Fusion Comp Generator and see if they appear in the viewers.

This is actually what I tried first... as I was trying to make some animated text to overlay a clip. The text shows on the media timeline viewer, but not in Fusion viewers! frustrating.

I'm not finding much information on this problem... weird.
I wonder if it is because I have an older monitor? 1440x900
Resolve is oversized and is not scaling correctly to the screen. I have to hold alt+click to drag window to use some functions.

getting this odd message in the console"

MediaOut1 cannot get Parameter for Input at time 556
MediaOut1 cannot get Parameter for Input at time 556
Merge1 cannot get DoD for Foreground at time 0
MediaOut1 cannot get Parameter for Input at time 0
MediaOut1 failed at time 0

Also: check that your looking at the right 'time'. This happens to me when my red position-indicator is not 'inside' the timing of my fusion-clip.

Frank Feijen wrote:Also: check that your looking at the right 'time'. This happens to me when my red position-indicator is not 'inside' the timing of my fusion-clip.

Tried this too, thanks.

Update: I installed the standalone version of Fusion 9, and the viewers work.

Frustrating that I can't get it to work inside Resolve 15

Hello Joel:

Did you ever figure out what the issue was? I have a similar problem where the clips show in every tab except fusion. If I add a background I can see it in other tabs but not the fusion tab. I have in on 1 and out on two but they are just blank.

Like you I am on Centos 7 but I am using 16b3 studio.

Thanks

I also would like a solution to this. Both viewers don't show anything unless it's a background element. There's no checker pattern or anything. I've tried to get anything to show in fusion, and nothing works. I'm running the latest version of 15, whichever that is.

Are you running an AMD card? If so BMD support has told me they don't support AMD buy an NVidia card. As I had just bought a brand new card to get DR running I am not going out and buying another. I have been buying a new video card every 6 months or so for more than two years now and I am done. If it means I have to use some thing other that DR so be it.

Today I saw in one of Jayar's videos that there was a hardware guide for DR 15. I don't know if there is an updated one for 16.

We do support AMD cards so im not sure the context of your discussion with BMD about not supporting them. You need to install the correct drivers.

For those that have been having this issue. I was finally able to get this going today. What is working for me is Centos 7 KDE version patched up to latest.

After that I installed the ROCM drivers following this guide.
https://rocm-documentation.readthedocs. ... Guide.html

Then install the Studio 16.5 beta.

I have tried the amdgpu, amdgpupro & and ROCM drivers on the Gnome version and couldn't even get DR to launch. I had reinstalled many many times in the past with the ROCM drivers and various versions of DR both 15 & 16 on the KDE desktop and the viewers on the Fusion tab never worked before today. So I am not sure if it is some thing that has been updated in Centos, the ROCM driver or the new beta of DR. I am just so glad this is finally working.

Any update? I was having this issue with 16.1. Upgraded to 16.1.1 and it persists. I'm noticing that the node name isn't appearing at the top of the viewer even though the viewer's dot is selected in the node. I've tried loading footage and I've tried fusion comps. Nothing will show on either viewer. Loaded an old database from when fusion was working and it doesn't change anything.

If you are using an AMD card on Linux you need to either use the AMDGPUPro drivers or ROCM <12.1 I think it is. The Linux install thread will tell you which version. I would start there.

On NVidia and Win 10.

Same here.
Can't make it work, like all of you guys.

joel383 wrote:When I select a clip from the timeline in Resolve, then click the fusion button, Fusion loads but the viewers are blank. I have tried toggling the rightview leftview dots, and split wipe... nothing.

Clicking on a clip does nothing in terms of what appears in Fusion. You specify the clip in one of two ways:

1. The highest clip in the Edit Timeline that's UNDER the PLAYHEAD.

2. Right-click on the clip and choose Open in Fusion Page. (At least in v17, maybe not earlier.)

* Note: I experimented a little and if the playhead is actually over a gap, the playhead seems to jump towards the front of the timeline until it hits a clip and submits that clip to Fusion. (In version 17.) At least that's what I see in Fusion's Viewer and when I go back to Edit, the playhead has been moved.

So I think your playhead is over nothing but you click on a clip thinking it will direct it to Fusion, but instead you get nothing, based on where your playhead is. Other folks have talked about "the background" but perhaps the background extends farther than the clip they want to edit -- i.e. it's under the playhead -- so that's what they get.

I could be guessing wrong, but this is consistent with what you shared.

Me neither - doesn't work

wfolta wrote:

joel383 wrote:1. The highest clip in the Edit Timeline that's UNDER the PLAYHEAD.

Playhead is on the clip, the clip is selected: nothing in Fusion with 2 differents GPU and 2 versions of Resolve.
Maybe it's something with the hardware or somw Windows components.

Eddy Juillerat wrote:

wfolta wrote:

joel383 wrote:1. The highest clip in the Edit Timeline that's UNDER the PLAYHEAD.

Playhead is on the clip, the clip is selected: nothing in Fusion with 2 differents GPU and 2 versions of Resolve.
Maybe it's something with the hardware or somw Windows components.

Do you have the latest NVidia drivers?

Yes my GPU drivers are the latest, I just install it so it's fresh downloaded.
I updated my BIOS (it was way too old) and saw that on Asus Bios we can change the GPU PCIe port from 4x to 8x.
After reboot, Resolve have the same lag on ProRes LT clips.

(Now it's going far from the post subject)
So I check with Disk Speed Test from blackMagicDesign the SSD drive where Windows 10 is installed then...
Surprise: 1st attempts are regular around 430 MB/s write and 500 MB/s read but after 3 cycles, Write drops down in the middle of the cycle to 20 MB/s or 120 MB/s or even 0.5 MB/s (huge variations from one cycle to the next), the go back to a normal or max of 400 MB/s

So maybe my SSD is faulty.
Lucky me, I installed a second SSD for another partition for a Linux or something. this one is staying equal all the way through the cycles but a little slower.