Page 1 of 1

Compound clips not cached

PostPosted: Mon Jul 25, 2016 3:40 pm
by Nicolas Kick
It seems like compound clips are not cached even if the smart cache is enabled. In the main timeline, the orange bar gradually becomes blue for normal clips, but stays orange for compound clips. If I open a compound clip in a new timeline, it also stays orange.
I setup a small project to show the issue:
https://www.dropbox.com/s/6cclfansdgw478m/test.zip?dl=0

Re: Compound clips not cached

PostPosted: Sat Jan 21, 2017 12:04 am
by Nicolas Kick
This bug is really annoying, since compound clips always have to be exported in order to see them. Why does nobody care to solve this issue?

Re: Compound clips not cached

PostPosted: Sat Jan 21, 2017 11:23 am
by Peter Cordes
Did you already try "Render Cache Clip Output" ?

This is also the solution for rendering Fusion Connect Files.

Thanks
Peter

Re: Compound clips not cached

PostPosted: Sat Jan 21, 2017 5:58 pm
by Francois Dompierre
I agree, this bug is problematic. It's been driving me crazy. There's just no way to cache a compound clip (either a node, or with "Render Clip Output). I'm curious if the bug is Mac-specific or Windows too. Anyone on Windows able to cache those clips? This problem has been consistent for months, across several different projects.

It would also seem that NOISE REDUCTION doesn't work on compound clips, nor does it work on multicam clips (those imported from a final cut X xml at least). You can apply the effect (noise reduction) but it doesn't do anything on the clip. The noise reduction is not applied. For it to work you have to go "inside" the compound clip or multicam clip (by selecting "open in timeline") and apply the noise reduction directly on the master clip.

Re: Compound clips not cached

PostPosted: Sat Jan 21, 2017 8:23 pm
by John Paines
On Windows, a cache setting of "user" or "smart" will automatically render a compound clip, but there are portions which, as indicated by the red line, remain unrendered. With "none" selected, a cache output command won't initiate any action.

Re: Compound clips not cached

PostPosted: Mon Jan 23, 2017 1:13 pm
by Francois Dompierre
On Mac, neither smart or user (either with a node render setting to "on" or with "render clip output") makes a difference. Resolve doesn't render those clips.

Re: Compound clips not cached

PostPosted: Mon Jan 23, 2017 2:23 pm
by John Paines
Even when caching works, it's only good for one session -- the links are usually lost, the next time Resolve is loaded. Other problems, as well -- no difference between "user" and "smart", for one.

This feature would seem to be a work-in-progress....

Re: Compound clips not cached

PostPosted: Mon Jan 23, 2017 4:37 pm
by Francois Dompierre
How about noise reduction -- does it "take" on compound clips for you? Here it doesn't work at all on those clips. Same fo multicam clips. The noise reduction is not applied. I have to decompose the clips, and that brings its own set of problems (fades get removed etc). Anyone else with that problem? I've had to deal with this for several months on all my shows and it's quite time consuming.

Re: Compound clips not cached

PostPosted: Mon Jan 23, 2017 5:24 pm
by Jean Claude
I just made a test with a Compound clip: it is only OK with the spatial NR mode faster that it works (old algorithm). No indication of rendering (no red line) even with smart or user. Delivery is correct.
Spatial Better or Temporal NR = nop.

Re: Compound clips not cached

PostPosted: Wed Jan 25, 2017 3:24 am
by Francois Dompierre
Thanks Jean Claude! I guess it's a real bug, both on Mac and PC. Anyone at BlackMagic aware of this? Multicam clips behave the same way, which is a huge problem because a lot of TV shows are edited in multicam and then they remain that way when the sequence is brought into Resolve through xml export for online/grading/ finishing. The show I'm currently finishing has on average 900 edits/clips, and at least 70% of those are multicam, and I can't put any noise reduction on them because...it doesn't work... And theres's all sorts of issues/bug/limitations when I flatten a multicam clip (fades are removed, editorial reframes/repos are lost, and in about 10-20% of the cases the synch slips off by 1 frame), so I can't just flatten them all without double-checking the resulting synch and without copying/pasting the original multicam clip attributes. And a lot of the clips I'm working with need a light touch of noise reduction, so it's very frustrating and time consuming. This is a multi-million dollar show and the producers are not happy because of how much work ($$$) is involved in getting rid of the multicam clips only because there's a bug in Resolve.

Re: Compound clips not cached

PostPosted: Sat Feb 04, 2017 7:29 am
by Nicolas Kick
I tried changing every possible option I could think of but compound clips never got cached. What I observed is that sometimes the red line of a compound clip begins getting blue, and after a couple of seconds it turns red again. I'm using compound clips to apply some black borders to a sequence of clips, since currently there is no way of applying attributes to multiple clips at once (when selecting multiple clips, any changes are applied to the first clip only), and if there are some more advanced color corrections which make the preview slow, the only way of seeing the final result is exporting the compound clip each time a change is done. I'm experiencing this problem since the very first version of Resolve 12.

Re: Compound clips not cached

PostPosted: Sat Feb 04, 2017 5:03 pm
by waltervolpatto
i also stumbled on a cache shot from a compound that contained a random frame in it and there was no way to clear the cache and get rid of that.

no option or rebuild or clear.

i end up to export the compound clip timeline as dpx and be forced to ingest as normal clip.

Re: Compound clips not cached

PostPosted: Sat Feb 04, 2017 7:51 pm
by Mike C Bonner
One workaround that I've used is to make a Fusion Connect clip. Render the clip, just don't open it in Fusion.

Re: Compound clips not cached

PostPosted: Mon May 22, 2017 2:46 pm
by Adam Archer
Has anyone tested to see if this is still an issue in Resolve 14?

Seems like the best workaround is to render out the entire compound clip then use it as a source. Seems crazy when only small sections of the compound clip actually require cacheing.


Sent from my iPhone using Tapatalk

Re: Compound clips not cached

PostPosted: Wed May 22, 2019 7:14 pm
by Nicolas Kick
Anyone from the Blackmagic developer team caring to resolve bugs that make peoples' lives difficult?

Re: Compound clips not cached

PostPosted: Sat Jun 15, 2019 9:30 pm
by Nicolas Kick
Not a single one?