Refresh Media

We need a feature in order to refresh the images / media in our project.

For example, I have several images in my current active project. Whie I'm working, I update the image using an external image editor.

How can I reflect this change in the project (timeline and media pool)?

Now, I close and (re)open the project but I find this tedious.

Steps to reproduce:

0. Create a new project
1. Import a short movie and an image (JPG). Let's say that the image represents a circle.
2. Drag the movie on the timeline
3. Drag the image above.
4. (optional) Play, render the project in order to see the image with the circle on it. Keep the project open.
5. Open the image in Paint (or in any other similar program)
6. Draw a rectangle in it (or alter it in some way)
7. Save the image.

Expected: „Press something” in order to have the changes of the image from the step 1 reflected in the project.

Actual: In daVinci Resolve the image imported at step 1 isn't updated. It has only the circle but not the rectangle.

Hint: It is - most probably - a cache problem. Please implement an option in RMB menu over the item in Media Pool in order to allow us to „Refresh” the item - that is, clear the cache + reload.

This is a long-standing problem that’s been discussed to death and slightly fixed a few versions ago. But as you see it persists.

Yes it’s a caching problem and hopefully they’ll fix it. Nobody knows when.

This is a long-standing problem that’s been discussed to death and slightly fixed a few versions ago. But as you see it persists.

Yes it’s a caching problem and hopefully they’ll fix it. Nobody knows when.

There are two variants here:

1. One which is „automatic” - based on „File Changed” signals from the Storage Layer. This is tricky because it needs good cache management in order to unload/reload only the changed item (the image in our discussion).

2. The second one is „manual” - my proposal. Because by clicking an option in a menu, the user takes a decisive action - it is ok(-ish) to clear all the cache in order to refresh the said item.

Just give us the possibility and we will pay the price. Anyways, it is better than what we have now.

I agree that good cache management can be tricky. It’s also required.

It’s much less tricky if everything is done with full use counting. Much like alloc/free. Hopefully that’s how they are - or will be - doing it. Then it’s not really tricky at all.

Once the cache management is fixed there’s no need for the command. Until the cache management is fixed we’ll have lots of cache bugs besides this one. As we do now.

I agree that good cache management can be tricky. It’s also required.

It’s much less tricky if everything is done with full use counting. Much like alloc/free. Hopefully that’s how they are - or will be - doing it. Then it’s not really tricky at all.

Once the cache management is fixed there’s no need for the command. Until the cache management is fixed we’ll have lots of cache bugs besides this one. As we do now.

Sure - but why don't they have reference counting? It is pretty old, straightforward and (at least in this case) a very good algorithm.

Now I suspect that they wait (forever?) to rewrite the cache engine and this can introduce (unwanted) delays.

However, even if the cache will work ok, then I suspect that this command is still needed if the media is on a (local) cloud because there, depending on the underlying storage subsystem, exists the possibility that a file change will be not signaled to the interested apps. I know that Windows till several years ago didn't support this on LAN.