A link to a zipped version of the fusion script here, to load it in the fusion panel do the following Go to the menu “File…” > “Import Fusion Composition..”, browse to the file you have downloaded and unzipped it will have a .comp extension.
For this project I received a clip of the dancer on a background of water and fountains. Normally I’d have to do at least a week of rotoscoping to get the subject separated from the background, but this time I used Rotobot and it processed the entire clip while I was asleep! I absolutely love this software and I’d recommend it to anyone who needs quick rotoscoping of human subjects. The generated matte was probably 95% accurate and I did some touch up in a couple of places but it was so much faster than manual rotoscoping, this video would not have been possible without your technology.
There are a few things you may need to adjust if you are not in ACEScc for the colour space you will need to update the OCIO Color Tranform Nodes away from the “From: linear” to from whatever space you are in, but to me Scene Linear makes sense.
Fill in the form below to get a copy of Rotobot 1.3.4 to test, mention your operating system, compositing package and if you have a CUDA card with driver 389 and above. Perhaps where you found out about Rotobot.
Sam Hodge from Kognat Software will be speaking about Kognat and Machine Learning in Media and Entertainment in Lot Fourteen as part of the Adelaide Fringe Festival. The conference showcases creative story telling using immersive media such as augmented reality, virtual reality, mixed reality and extended reality. Rotobot can be used in these media provided it can be calculated off line in advance.
The test above was part of testing the upcoming release on Blackmagic Fusion 16 and Blackmagic DaVinci Resolve 16 on Windows 10. There is a small technical glitch which results in a big crash. Kognat staff are very close to a fix.
Update the fix worked:
To see if macOS also suffered from the same issue an install of Rotobot was put onto the macOS 10.13.3 test box with NVIDIA CUDA 10 hardware and drivers installed and it worked flawlessly. So this confirms the problem was the small glitch on Windows and not a profound issue with Fusion.