footofwrath wrote:Can we conclude though that it does employ CUDA in these tests though, and that therefore good scores are confirmation that CUDA is at least being used in this instance?
I believe CUDA has always been in operation in Resolve - you had it on Auto before, which should select CUDA, and now you have it specifically on CUDA.
That doesn't mean that the Spherical Stabilizer specifically is making good use of CUDA.
From my own test just now, it seems to use far more CPU than GPU. In fact it barely used any GPU at all, and the amount it did use could well be explained by Resolve decoding and debayering the source clip.
Spherical Stabilizer does have a GPU Acceleration on/off switch suggesting it should be GPU accelerated. But apparently in practice it's not doing much with it.
footofwrath wrote:OK so I'm guessing I'm not seeing the correct proxy res on the Fusion page. How do I fix that?
By making a Fusion Clip or Compound Clip and putting the Fusion comp on that.
However things are complicated by the fact that you want to render at 8k.
Things are also more complicated in this instance because the Spherical Stabilizer is a two-step process. First you have to track - and I assume that's what you're saying takes 9 hours? - and then you have to render.
I did my own test just now, with 8K BRAW media on 8K timeline. With Spherical Stabilizer at default settings, tracking proceeded at an average of 3.0 FPS, and then playback (once already tracked) was 3 - 6 FPS.
Given you want to render at 8K, it seems certain to me that you will always have a lengthy process at the end, of 5 - 9 hours.
However we may be able to improve the time it takes to track, by getting Fusion to stabilize based on the 1080p proxy image, and then applying that to the 8K image for rendering. In order for this to work, it's vital that the proxy is the same aspect ratio as the source clip. I think this is already the case - you mentioned your proxies are 1920x960 so presumably the source media is 7680x3840?
So these are the theoretical, untested steps.
Method one - creating 1/4 proxies and forcing Fusion to use them for tracking, but not for rendering:- Generate the 1/4 res proxies for your media, and make sure Playback -> Use Proxy Media is selected
- Create a 1080p timeline with the 8K media on it
- Select the clip(s), right-click, New Compound Clip
- Select the new Compound Clip, right-click, Open In Fusion page
- Look at the very top right of the Fusion viewer and confirm you see "1920x1080xfloat32"
- Add your Spherical Stabilizer, configure it, track it forward from frame 0.
- It'll take.. no idea how long. But less time than at 8K, hopefully a lot less
- When it's done and you are happy with the result, copy the Spherical Stabilizer node. Now paste it into a text file in Notepad or equivalent text editor. That's a backup so we can copy it back in a minute.
- Back in Resolve, go back to Edit.
- Right-click on the Compound Clip and Decompose In Place.
- Change the Timeline Settings to 8K.
- Right-click on the source media clip that's now visible again, and Open In Fusion Page
- You're now at a blank composition again. Select the MediaIn1 node.
- Go back to your text file, copy all the text (Control-A, Control-C), then back to the Fusion page, and with the MediaIn1 node still selected, paste.
- You'll get back your Spherical Stabilizer node again, which should be automatically connected between MediaIn1 and MediaOut.
- Check the output on a number of frames and confirm they look fine.
- Save the project, go to Deliver, make sure the Deliver option to use proxies is disabled, render at 8K.
- This will take.. no idea how long. Based on my own quick test, likely less time than it took you to track the stabilizer at 8K in past tests, so maybe 4.5 hours - 8 hours.
Method 2, passing Fusion the original source media but resizing it prior to stabilize tracking:- Create a 1080p timeline with 8K media on it. Don't bother with proxies.
- Go to the Fusion page
- After MediaIn1, first add a Resize node, set to 1920x960.
- Then add the SphericalStabilizer after that; configure it; track it forward from frame 0. Expect it to perform a little worse than method 1 (at a guess)
- When done, delete the Resize node, then check the output still looks right.
- Back to Edit, change Timeline Settings to 8K.
- Deliver: Set it to 8K, make sure the Deliver option to use Proxy Media is disabled, Deliver. This will take 6 - 9 hours I'd guess.
Method 2 is fewer steps but the performance might well be a bit worse than step 1 because Fusion is still seeing the 8K clip, which we're then resizing down to 1/4 before generating the track.
A variant could also be tried in standalone Fusion Studio (if you're a Resolve Studio owner). No timeline, just a Loader node. That Loader could either load the original source footage, and be followed by a Resize node as per method 2. Or it could load the 1920x960 proxy, in which case no Resize would be needed. If your footage is in a RAW format you'd first have to save out a version in ProRes or DNxHR for Fusion Studio to load (unless proxies were used which would already be in such a format). You would then do the tracking in Fusion Studio, and at the end could either copy the stabilizer node to Resolve (by copying and pasting the node as described in method 1). Or, if you loaded your original source footage in Fusion Studio, you could also do the rendering in Fusion Studio via a Saver.
I do not expect Fusion Studio to perform significantly quicker, if at all, than Resolve. But there might be a few % difference. And it might be less likely to crash or freeze during those lengthy track and render processes.
All of these theoretical methods assume that the Spherical Stabilizer track on 1/4 resolution files will be directly applicable to the full resolution. I don't know if this is the case.
It must be tested carefully. In theory it should work, because Fusion comps are resolution independent and all the keyframes stored by the Spherical Stabilizer are in a 0..1 scale. So 0.25 on an 8K image is the same place as 0.25 on a 1080p image.
However whether the stabilising job is as good when generated on 1/4 the number of pixels, I do not know. Whether there are side effects or artefacts, I do not know.
Re your questions on the Stabilizer - can't help there, never used it. Hopefully the others can.