CImg + Misc OFX crash Fusion 16 on startup
Opened this issue · 14 comments
Hi there,
when the Misc and CImg OFX are installed, Fusion 16 SAL crashes instantly; the splashscreen won't last a second.
There's a way to blacklist them so they won't be loaded on startup, then it will boot through.
Just in case someone needs to know :)
Best Regards
Hi there,
oh man I forgot all about bugtracking, didn't I :/
It's the packages that ship with Natron - so I didn't compile them myself and didn't install them directly, as they were already there.
I have Windows 10 Pro. Tomorrow I can check if the same happens on OSX!
I couldn't find any info on that, it seems to be not open; nothing in the manuals etc
But I found this: https://forum.blackmagicdesign.com/viewtopic.php?f=22&t=38699
It seems like the SDK is only available under NDA. Could we find the info we need in there?
Hi there,
I can't test it on OSX because my OS is too old to run Fusion 16 (needs at least 10.13), so I'm stuck to test it here :(
I'm in contact with support and will ask regarding the compiler etc, the Script Manual inside the Developer infos you get when installing is unfortunately not helpful either :(
hi devernay,
I now installed OSX 10.13.5 on my workmachine so I could check it out.
The issue is the same: as soon as Fusion hits the OFX while loading, it crashes. Does this rule out compiling-issues?
In the meantime I already contacted developer support for an SDK but had no answer so far.
best,
c
@CameraRick I'll try that at home. Is Fusion 16 for macOS free?
I tested Fusion 8.2.1 but it doesn't start on my Mac 10.14 (splash screen, then crash, even if I uninstall all OFX plugins). Is there a free version that runs on 10.14?
OK so Fusion 9 starts, but doesn't seem to support OFX plugins. I guess only the pay version (Fusion Studio) does?
Hi there devernay,
sorry for my late reply. It seems there is no SDK anymore, so that's an empty road unfortunately.
Fusion 16 needs a newer version of OSX unfortunately, also I think there is no free version anymore (as that one moved into Resolve). In the past, Fusion only supported OFX plugins in the paid versions.
Of course I'm happy to test anything on either OSX or Win10.
I fixed some stuff in NatronGitHub/openfx@3effa28 , so you can try the latest Appveyor build, or build your own plugins on OSX. It loads, and doesn't crash anymore, but strange things may happen (OFX support in Fusion and Resolve is not great)
Also improved Fusion compatibility in 8475347
Here are some caveats I found in Fusion's OFX support:
- kOfxPropAPIVersion kOfxPropVersionLabel kOfxImageEffectInstancePropSequentialRender are not set on the host
- unconnected clips have prop kOfxImageEffectPropPixelDepth=kOfxBitDepthNone
- when scrubbing parameters (changing values fast), the renderScale in the inArgs is 1/3. but the renderScale on images is 3.
Hi there deverney,
I tried the Appveyor-versions as I'm not capable of compiling anything myself :)
Fusion 16 (which is now released as stable btw) can not boot through, that is a win :) I can also load several plugins and many already work properly and as expected (as far as I can tell).
At least DenoiseSharpen, which I find is one of the most important plugins in the collection, does not work at all though.
The on-screen controls for the sample-region can not be used. When I use the coodinate-controls inside the tool I'm able to set up a region, but if I want to do anything (like analyzing it) nothing happens, so basically it stays still.
What would be needed to make this run properly in Fusion, the whole set? Is it something deep inside the code that must be altered in Fusion, or is it some info that is missing? From what I gathered from BMD, everything works according to the standard in their opinion
Hi there @devernay
I just got a mail from the Fusion guys, it seems they want to get in touch and ask me for an eMail-adress. Are you fine with this? I'd love to forward it to them. I don't know if GitHub has PMs, you can reach me through camerarick2k (a) gmail (dot) com