Blackmagic Forum

Hi, is this a secret update? Resolve seems to now automatically reload/refresh a changed image sequence.

It's extremely proactive about it too, updating the images as they are rendered out nearly instantly.

This is a massive upgrade for me, so thank you very much for finally addressing this issue!

Have you been able to confirm this? How do you trigger the update? I do a lot of CG and this would be great. For me it doesnt seem to update unless I delete the cache and let it rebuild

vfxwolf wrote:Have you been able to confirm this? How do you trigger the update? I do a lot of CG and this would be great. For me it doesnt seem to update unless I delete the cache and let it rebuild

There's nothing to trigger. It just works now. This had been a huge pain point for me, so I'm very happy to see it finally working. Here is a demo of how instant it is with the updating (I start with some red-coloured footage already imported into Resolve, that I re-render from Ae as blue):

vfxwolf wrote:it doesnt seem to update unless I delete the cache and let it rebuild

That's to be expected, when Cache is involved. Current Cache won't be invalidated because the Source changed.

Which sounds like a bug in the reloading implementation. As in I'd say that's very much not expected or acceptable behavior.


Sent from my iPhone using Tapatalk

Jim Simon wrote:

vfxwolf wrote:it doesnt seem to update unless I delete the cache and let it rebuild

That's to be expected, when Cache is involved. Current Cache won't be invalidated because the Source changed.

Joe Shapiro wrote:Which sounds like a bug in the reloading implementation. As in I'd say that's very much not expected or acceptable behavior.

I agree. If the timestamps on the source footage change, then any cached copies should be invalidated to force the source to be re-loaded and re-cached.

You guys know what to do.

viewforum.php?f=33

Yes. File a bug report right here like we did. This isn't a feature request.

You sure about that? You know for certain that the software is actually programmed to operate as you wish?

There's a difference between implementation and intent.

I am very certain that the intent is to read the updated file in all cases - not just those where no cached version exists.
It appears that it hasn't yet been coded that way. I call that a bug.

Joe Shapiro wrote:I am very certain that the intent is to read the updated file in all cases - not just those where no cached version exists. It appears that it hasn't yet been coded that way. I call that a bug.

Just you wait. They'll "fix" this problem and then someone will inevitably complain that Resolve deleted cached file that they were depending on to recover from some stupid mistake. And it didn't even warn them!

Doesn't seem to be working for changed audio files....

ironlion37 wrote:Doesn't seem to be working for changed audio files....

I may have jumped the gun with my enthusiasm. Right now it works best with image sequences and (mostly) with still images. For some reason Resolve now hard locks a video file so that it cannot be overwritten at all while that project is loaded, mandating a necessary restart of Resolve.

Sigh...so close, but still so terrible.