Bugs shouldn't be present on the 19.0.1

Here below some very annoying bugs. Typical bugs of an Alpha or Beta. But they shouldn't be there in a final release.

Ah: you can complete the list into the comments.

Compound Clip: FX in original clip aren't into the compound, when that compound is inside a Multicam Timeline.

viewtopic.php?f=21&t=208338


Imported pictures are not updated
viewtopic.php?f=21&t=208406&p=1081917#p1081917

Imported pictures are not updated

I think that might be a design issue. Resolve has been this way for years.

I'm guessing some sort of Caching goes on for imported images, so that when the file on the drive is changed, you're still looking at the Cache.

This makes me wonder if there would be some kind of performance issue were Resolve to read those in real time, every time, so that changes showed up immediately.

Imported pictures are not updated

I think that might be a design issue. Resolve has been this way for years.

I'm guessing some sort of Caching goes on for imported images, so that when the file on the drive is changed, you're still looking at the Cache.

This makes me wonder if there would be some kind of performance issue were Resolve to read those in real time, every time, so that changes showed up immediately.

Well when the md5 of a file changes, it means the file isn't more as before, DaVinci must re-cache it. Hower Not only I deleted any cache, it was also deactivated but still the issue up and running for no reason

when the md5 of a file changes

I don't know that Resolve looks at that. I don't know that any NLE does.

when the md5 of a file changes

I don't know that Resolve looks at that. I don't know that any NLE does.

I was just assuming that. Not clue what it does.

Well when the md5 of a file changes, it means the file isn't more as before, DaVinci must re-cache it. Hower Not only I deleted any cache, it was also deactivated but still the issue up and running for no reason

Do you really want Resolve churning through every byte of every asset in your entire project to recalculate MD5 hashes? It would be bad enough to do this when you open a project, let alone doing it while you're working on the project just so that it could pick up a change in one image file somewhere.

I do agree that Resolve should flush its caches when the file metadata (i.e., file creation, modification time or size) changes. But I'd understand if it would require closing and reopening the project to pick these up. Otherwise it would take a lot of continuous file system monitoring to catch changes.

Well when the md5 of a file changes, it means the file isn't more as before, DaVinci must re-cache it. Hower Not only I deleted any cache, it was also deactivated but still the issue up and running for no reason

Do you really want Resolve churning through every byte of every asset in your entire project to recalculate MD5 hashes? It would be bad enough to do this when you open a project, let alone doing it while you're working on the project just so that it could pick up a change in one image file somewhere.

I do agree that Resolve should flush its caches when the file metadata (i.e., file creation, modification time or size) changes. But I'd understand if it would require closing and reopening the project to pick these up. Otherwise it would take a lot of continuous file system monitoring to catch changes.

Like any other video/audio software does and no one is dying for this. DRS MUST update the mediafiles as soon as they are modified.
I told about md5 because I was assuming it was checking this. Not clue what it does. I'm not developer. So far it does nothing

This (spending time and energy looking for changed files) is a problem that was solved decades ago.

There’s a system call in every OS Resolve is on that tells the program when a file it’s interested in changes. No cost.

This (spending time and energy looking for changed files) is a problem that was solved decades ago.

There’s a system call in every OS Resolve is on that tells the program when a file it’s interested in changes. No cost.

Ok it means tha DRS is very buggy then.


Sent from my iPad using Tapatalk

it means tha DRS is very buggy then.

Not necessarily. I think Joe was just pointing out a way BMD might change this behavior without too much performance cost.

it means tha DRS is very buggy then.

Not necessarily. I think Joe was just pointing out a way BMD might change the code to give you what you want without too much performance cost.

Well I think they should know ... so it remains a kind of bug.


Sent from my iPad using Tapatalk

There’s a system call in every OS Resolve is on that tells the program when a file it’s interested in changes. No cost.

True, but as a developer myself I don't imagine it would be all that easy to implement in Resolve. It's an asynchronous call from the OS to the application, and given that there are many Resolve "pages" that are involved, all of which I suspect are separate processes which would have to be independently notified, it might need a fair bit of work and validation to get running properly. With asynchronous notification there are all kinds of edge cases you have to deal with - for example what happens if an asset changes just as you're rendering it? Changes can be trivial or very consequential, such as changed resolution. And there might still be some limitations where assets are stored on remote computers for the purposes of sharing.

I'd be happy with a check against the project assets that's done when the project is loaded. That would require the project to be closed/opened, but IMHO that's still miles ahead of what I have to do right now, which is to create a new version of the changed asset with a different name (I use a "_V1", "_V2" etc. suffix) and then go into the media pool to relink to it.

But hey, if they want to invest in the effort to "do it right" then more power to them!

The easy way is : add in a dropdown menu the voice “reload”… in media pool or in timeline.
Media pool select all, right click, find reload, done.
It’s like work in After effects from decades and was accepted.


Inviato dal mio iPhone utilizzando Tapatalk

The easy way is : add in a dropdown menu the voice “reload”… in media pool or in timeline.
Media pool select all, right click, find reload, done.
It’s like work in After effects from decades and was accepted.


Inviato dal mio iPhone utilizzando Tapatalk

Bravissimo! It's what I was thinking and writing as well. You anticipated me.

Wondering why programmers are not implementing such stuff instead. It looks like "we can't" instead of "we can do it, however it will take some time"

The easy way is : add in a dropdown menu the voice “reload”… in media pool or in timeline.
Media pool select all, right click, find reload, done.
It’s like work in After effects from decades and was accepted.

Yeah, that would be a great way to do it!

The easy way is : add in a dropdown menu the voice “reload”… in media pool or in timeline.
Media pool select all, right click, find reload, done.
It’s like work in After effects from decades and was accepted.


Inviato dal mio iPhone utilizzando Tapatalk

+1 for this.

This would be a perfectly acceptable short term solution.
I still hope they "do it right" with the system call approach.
As to the complexity of dealing with asynchronous notification - I can be 99+% sure that Resolve is already handling such things. It's multi-threaded and talks over the net to databases for instance. Getting "file has changed" callbacks is easy peasy compared to that.