viewer one problem in fusion

hello guys,
I'm a new member, I got my first two certificates online but when working on fusion training it seems to have a problem with viewer 1 sometimes: after working on a fusion project for a while, viewer 1 seem to not work when you select a node and choose to view it there, and that happens with whatever node you choose, even MediaIn,
I love this product and want to be a professional
thanks in advance

I get the same thing sometimes, and restarting Fusion is the only solution. I think it's been happening for a long time, but I don't know what triggers it.

@HASNAOUI seems to be on the fusion page of resolve, while I am on the Studio version.

Thanks for your answer,
yes I am on davinci resolve 17, but in contrast of what you said, restarting davinci doesn't correct that in my case, and it's distracting

I've been noticing the same thing in fu studio 17.4.1 - either viewer will freeze and you cannot load a new node into it without restarting fusion. This seems to happen fairly regularly (at least 3 or 4 times a day) in 17.4.1 and I don't remember ever seeing it fu9 studio.

When this happens, try to add a Loader node. If the file browser does not appear, then I suspect the composition has been locked somehow. This may happen if certain scripts terminate before they're finished running. If that's the case, then opening the Console and typing comp:Unlock() may clear the condition. Also, if this is happening, it will lock all image views, not just one of them.

Another possibility is that you've accidentally locked the Viewer with the Ctrl+L hotkey. If so, when you right-click anywhere in the Viewer to get the context menu, you'll see the checkmark next to "Lock Display."

Untitled.png (11.28 KiB) Viewed 1773 times

If neither of those things is true, then we might be looking at a new bug.

I'm using 17.3.1. All views will be unresponsive, not just viewer 1. I don't remember v9, but it may have been v16 as well. It seems to be happening even after changing the GPU hardware and drivers.

This is a very rare phenomenon, so it may simply be that Fusion is crashing internally.

to make things clearer,
the viewer turns white when you select viewing a node there but is not frozen
when you unassign the node, it turns black,
so the viewer seems to be ready and interacts with content, but doesn't display it well

Again, a locked comp due to premature termination of a script is the most likely culprit. Now that I stop to think about it, I actually have a little script that might help if that's the case:

Code: Select all

print("Unlock Comp")

-- ===========================================================================
-- globals
-- ===========================================================================
_fusion = nil
_comp = nil
ui = nil
disp = nil

--==============================================================
-- Main()
--
-- Typical set-up for a script developed in an IDE. Sets globals
-- and connects to the active comp. Initializes UI Manger.
--==============================================================

function main()
   -- get fusion instance
   _fusion = getFusion()

   -- ensure a fusion instance was retrieved
   if not _fusion then
      error("Please open the Fusion GUI before running this tool.")
   end

   -- Set up aliases to the UI Manager framework
   ui = _fusion.UIManager
   disp = bmd.UIDispatcher(ui)
   
   -- get composition
   _comp = _fusion.CurrentComp
   SetActiveComp(_comp)

   unlockComp(_comp)

   -- ensure a composition is active
   if not _comp then
      error("Please open a composition before running this tool.")
   end

   dprint("\nActive comp is ".._comp:GetAttrs().COMPS_Name)

end

--======================== ENVIRONMENT SETUP ============================--

------------------------------------------------------------------------
-- getFusion()
--
-- check if global fusion is set, meaning this script is being
-- executed from within fusion
--
-- Arguments: None
-- Returns: handle to the Fusion instance
------------------------------------------------------------------------
function getFusion()
   if fusion == nil then
      -- remotely get the fusion ui instance
      fusion = bmd.scriptapp("Fusion", "localhost")
   end
   return fusion
end -- end of getFusion()

-- Unlocks the comp
function unlockComp(c)
   if c:GetAttrs().COMPB_Locked == false then lockComp(c) end
   while c:GetAttrs().COMPB_Locked == true do
      c:Unlock()
   end
end

-- Locks the comp
function lockComp(c)
   if c:GetAttrs().COMPB_Locked == true then unlockComp(c) end
   while c:GetAttrs().COMPB_Locked == false do
      c:Lock()
   end
end


--========================== DEBUGGING ============================--


---------------------------------------------------------------------
-- dprint(string, suppressNewline)
--
-- Prints debugging information to the console when DEBUG flag is set
--
-- Arguments:
--      string, string, a message for the console
--      suppressNewline, boolean, do not start a new line
---------------------------------------------------------------------
function dprint(string, suppressNewline)
   local newline = "\n"
   if suppressNewline then newline = '' end
   if DEBUG then _comp:Print(string..newline) end
end -- dprint()

main()


Save that as unlockComp.lua in your Scripts/Comp folder.

This is a little more complex than the single-line thing I recommended earlier. The reason is because a comp's lock state can actually be nested. So if it's been locked four times, unlocking it just once won't do. And weirdly, a comp can be unlocked multiple times, too. So this detects the lock state and ensures that it's Unlocked exactly one time, no matter how many times the script gets run. This is the first thing I try whenever Fusion seems to have hung.

ok Bryan, thanks
I'll give that a try if it happens again, because it didn't happen since I asked this question which is good

@Bryan

I don't know if my phenomenon is the same as yours, but I will try.

Thank you!

to make things clearer,
the viewer turns white when you select viewing a node there but is not frozen
when you unassign the node, it turns black,
so the viewer seems to be ready and interacts with content, but doesn't display it well

For some reason, this post hadn't appeared when I was responding before, even though it's time-stamped way earlier. Weird.

This definitely sounds like a display bug of some kind, not just a locked comp. It's not one that I've seen before, but since it affects only image views, my guess would be a problem with the video card or driver. Only advice I can give is to make sure your drivers are up to date. If that doesn't solve it, then you may need to contact Support.

Fusion is sensitive to the driver. The latest drivers are often the cause of problems for Fusion. I try to choose the latest one before the release of Fusion that I am using.

I've been having trouble with DeckLink lately (from around 17.2~3) because of its delicate compatibility.

I just experienced this in the Fusion page of Resolve Studio 17.4.1. Here's a screenshot of a crashed viewer:



Completely black, with no node name shown at the top, and the Gain/Gamma sliders have also gone blank.

When this happened I was viewing the alpha of a DeltaKeyer, playing with the Threshold and Clean Background settings, with Gamma at max, and I started to get some weird results. I increased the Threshold to remove some white spots on the background, then I lowered the Threshold to try Clean Background instead, but saw no change in the image when I did so. Then I raised the Threshold back to where it had been 30 seconds earlier, but still saw no effect. So now the image was effectively frozen, not being affected by any parameters.

Confused, I tried changing what image was active in the viewer, and that's when it went completely black and I had to restart Resolve.