Robert Ruffo
Forum Replies Created
-
Not sure Cuda debayer will play nice with software like Resolve which is already taxing the GPU.
I would suggest a Freeze option – Freeze debayer, Freeze Until this Node, etc – would render DPZ of all until that time, and grey out the nodes that we require a re-render fi unfrozen. Would be great for OFX and noise reduction too – and we would learn the habit of noise reducing early in the chain.
A smart implementation would render out the alpha as well, but a reasonable restriction would be that alpha is unavailable until that node, and/or that the node chosen for “Freeze Until This Node” cannot contain an alpha output, just color. Freeze could also restrict to freezing everything (as last node output is color by definition) and it would save an alpha DPX seperately if “add alpha output” was present, and freeze both, to keep things simple, or maybe just Freeze doe snot work if “Add alpha output” has been used (still OK in most cases).
Then the user could add more nodes, and “grade over” the high bit DPXs, and only the changes within those nodes would need to operate in real time.
-
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
-
For that message to go away, the card, no matter how extraordinarily powerful, has to have no monitors attached to it – regardless of whether “Use GUI for Compute” is checked on or not – wee misjudgment in the warning system, or maybe it doesn’t see your checkbox yet at that stage of the load. Anyway, not a big thing to just press OK me thinks
-
Thanks Peter!
I’ll do that when I have a chance. I figured out that if I delete all the cache files the problem goes away, and that the problem only occurs when I use rendered previews of one or more clips. Problem being: That warning. Very slow loading of projects list upon opening. Very slow playback.
It would be great if
A) Resolve had a ‘Purge Cache” function, that could automatically purge upon quit of the user desires, and rendered clips were written over after a change (as it is now it tends to fill a hard drive…)
B) Rendered clips were persistent/reloaded between sessions. Not sure why that is not the case, or who would consider it better to re-render all previews every time they load a session. On a feature film it can become a big deal.
Another strange behavior is that of I use a GTX 570 for both GUI and render (as I will do if I am switching quickly between Resolve and Premiere) even if I check on “Use Gui For Compute” it gives me a non-realtime warning – even though in the end it works fine. (Second GUI card is tiny card only for Gui (Gt130)
-
Bit have no 3 too, and also have no idea why. Never saw that before… I also get black frames on Red Video. It seems to come and go with no rhyme or reason, as does very slow playback
-
Just add an alpha curves panel within or next to the existing curves pages.
“hue Vs alpha is self-evident if you understand what the existing curves do.
Combiner node having one more icon/node in the tree is not really adding complication either
-
Anyone agree?
-
4K is easy – work in 1/4 res in Premiere/DaVinci, (looks fine for working, paused res is full) render at 4K if needed.
This works like butter on 12 core Mac Pro. Same goes for full 5K. Day in, day out.
-
I think maybe your node order is wrong?
Your question might reveal a complete lack of knowledge of how to use DaVinci, or your system is acting up, so you should restart
-
No way to do that, but a good feature request over at Red if you feel like making it.