FORUMS: list search recent posts

Cache ... the never-ending story

COW Forums : DaVinci Resolve

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Sascha Haber
Cache ... the never-ending story
on Jan 20, 2014 at 12:07:26 pm

Hi guys,

I know I probably did post this request like 5 times since I started using Resolve professionally and I will not let go of this all time favourite.
let me spell it out :

WE NEED A WORKING CACHE SOLUTION !!!

Some scenarios.

1 . RED media.
Not all of us have a RED rocket card and in the future using the nMP even less people will.
I do not need 4K playback, but I would like to see full quality in 1920 and play that back without truncating.

2. CANON 300/500 media
...is a pain to work on and also benefits from caching

3. Temporal NR
My new best friend...this effectively frees me from using Smoke for NR and its sooo awesome to work with, but even on our beefed out 12 Core 3 GTX 680 system I get like 8fps on SD material.

4. Sapphires FX
As soon as people are getting their hands on those all RT playback is gone for good.

5. Using standard MACs for work
I had the pleasure to work in two shop without external cards and had to render everything that had more than 6 nodes.
Clients a thrilled to wait for that.


The cache system I would like to see is either ProRes4444 or even RAW based.
Disk speed is cheap now and a simple SSD or Dual Drive can play back uncompressed HD
Changing a shots length right now kills the whole cache...that is a total noGo
Closing the project right now kills the whole cache....another noGO
The system needs to create a folder for every shot and assign unique names to the cached frames.
A cached shot should just be colored golden and we should have the option to purge the cache for single shots , a selection of shots or the whole
timeline.

Oh, and i would be totally happy to call this a pro function and not include it into Resolve Lite
I bet the sales would honor it right away.

Nice regards
Sascha

A slice of color...

Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
http://vimeo.com/saschahaber


Return to posts index

Gabriele Turchi
Re: Cache ... the never-ending story
on Jan 20, 2014 at 2:58:20 pm

I agree completely

ALSO in my opinion could even be "TIMELINE RELATED" , so it cash things in the timeline such as sped changes and anything else that not effect the color tools

so

1 Global
1 for dissolves
1 for RAW based camera debayer
1 node specific
1 timeline (where applicable)

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX580+GTX5800+GTX580
24GB RAM
Panasonic 58PF Plasma
Panasonic BT300 Plasma
Ultrascope


Return to posts index

Margus Voll
Re: Cache ... the never-ending story
on Jan 20, 2014 at 8:35:42 pm

In theory it should be doable in tech sense ?

I mean in the same way like the compositing apps do it or they used to do it.

In combustion it was called similar like disk cache. And it had the option to
be rendered and played back from there or reverted to original i.e. like final render
in our case.

On paper seems simple to do.

--

Margus

http://iconstudios.eu
https://vimeo.com/iconstudioseu/videos

DaVinci 10, OSX 10.8.5
MacPro 5.1 2x2,93 24GB
GUI 4000 / GPU GTX 780
DL 4K
Eizo Color
Scope Box
Full Ligthspace CMS


Return to posts index


jake blackstone
Re: Cache ... the never-ending story
on Jan 21, 2014 at 12:02:25 am
Last Edited By jake blackstone on Jan 21, 2014 at 12:11:32 am

Couldn't agree more. Said that, I gave up waiting on a proper caching a while ago . I guess you're more persistent person or an eternal optimist:-)
Just a few posts about the same issue from the past, many including yours Sasha:-) Please note the quantity and how far this request dates back (almost 2.5 years).
http://forums.creativecow.net/readpost/277/27017
http://forums.creativecow.net/readpost/277/26720
http://forums.creativecow.net/readpost/277/25864
http://forums.creativecow.net/readpost/277/22361
http://forums.creativecow.net/readpost/277/18667
http://forums.creativecow.net/readpost/277/12523
http://forums.creativecow.net/readpost/277/9667
http://forums.creativecow.net/readpost/277/9667
http://www.reduser.net/forum/showthread.php?109756-How-many-GPUs-for-Resolv...
If you continue reading the last thread, you can see not everyone even convinced we really need proper caching in Resolve:-)
Finally, I had been told by people in the know, that the reason why it's difficult to implement the proper caching is the disc fragmentation, which I find odd. Isn't FCPX does background caching? Yes, it will increase fragmentation, but I never found that to be a problem. Once a week before i go home I hit de-frag utility on my PC and in the morning it's ready to go. Never had an issue. You can even set up a cron on a Mac to do that...


Return to posts index

Chris Hall
Re: Cache ... the never-ending story
on Jan 21, 2014 at 4:32:22 pm

well said, +1 here for FIXING the cache. I've never been able to see it work without lifting the black levels... EVER...

Chris Hall
Colorist - Prehistoric Digital
Santa Monica, CA


Return to posts index

Andy Winter
Re: Cache ... the never-ending story
on Jan 21, 2014 at 7:40:49 pm

+1!!!!!!

would love to have a number of nodes cache-function! so that for example i can use
noise suppression and some other stuff on the first two or three nodes and davinci
would treat it like the new original media and stays realtime until i edit those first
nodes!

i also love the new motion noise reduction!
(@sascha: it works for me in realtime unless i have too much nodes afterwards with blurs
and hsl qualifiers on my double titan setup)


Return to posts index


Robert Ruffo
Re: Cache ... the never-ending story
on Jan 21, 2014 at 11:38:30 pm

This is a great idea - like "cache to here" which would be a check box for every node, and would keep live anything after that. Since node order is not obvious in complex chains, it could be based on node number as assigned by Resolve to all nodes, and would include any nodes, even with later numbers, that feed into its inputs or the inputs of any nodes behind it.

It could also "grade over" the existing cache if we later choose a node further down the chain to make a new cache with more nodes, and so on. Cached nodes could be frozen/grayed out and we have to unfreeze them to change anything - this would be helpful if we don;t have time to loose a cached render, and help us decide to maybe add another node to make a desired color change rather than disturb one that would invalidate a cached render that took a long time.

But... would need to work in very high bit space in terms of the DPXs rendered, otherwise nodes after the clip point would clip and band.

The render page could even have a "use cache" option for quick previews sent as interim samples to clients during work in progress. Premiere has this (called "Use Previews") and it is very useful for this reason


Return to posts index

Lee Niederkofler
Re: Cache ... the never-ending story
on Jan 24, 2014 at 9:44:24 am

+1
Yes please!



Return to posts index

sean ross
Re: Cache ... the never-ending story
on Jan 24, 2014 at 4:15:58 pm

yes yes yes!!!! I would love a more robust cacheing scheme. Every upgrade I do a search in the release notes for the word "cache", and am eternally optimistic that the resolve team will sneak it in!!!


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2017 CreativeCOW.net All Rights Reserved
[TOP]