Sat Dec 04, 2021 6:44 am
It's not a bug as far as I'm aware. It's always done this as long as I've been using Resolve, when you drag an OFX as its own node - rather than onto an existing corrector:
I always figured that the extra two inputs are in case the OFX supports a second RGB and alpha input. For example, if it was a tracking/match move OFX, like Mocha Pro.
If the OFX you're adding doesn't need the second set of inputs, just don't use them.
Resolve Studio 17.4.3 and Fusion Studio 17.4.3 on macOS 11.6.1
Hackintosh:: X299, Intel i9-10980XE, 128GB DDR4, AMD 6900XT 16GB
Monitors: 1 x 3840x2160 & 3 x 1920x1200
Disk: 2TB NVMe + 4TB RAID0 NVMe; NAS: 36TB RAID6
BMD Speed Editor