FORUMS: list search recent posts

render cache clip source -> tracking speed

COW Forums : DaVinci Resolve

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Andy Winter
render cache clip source -> tracking speed
on Sep 23, 2015 at 10:35:25 am

if i render cache clip source all of my 2,5k dpx-shots to prores4x4 and after that
want to eg stabilize the shot, it seems that the render cache gets thrown away and
davinci does take the 2,5dpx original shots as its basis for tracking.

this is kinda disappointing. if i generate dpx proxies via the proxy manager it works
well, but does use up a lot of hdd-space :(

it is a 16mm scan and therefore a stabilisation of nearly every shot will be needed to
compensate the little "shaking" introduced by the camera.

the caching system seems to fail to serve my demands.


Return to posts index

Andy Winter
Re: render cache clip source -> tracking speed
on Sep 23, 2015 at 10:41:10 am

ps: in case of dpx consolidate via the timeline doesn't seem to work either :(


Return to posts index

Sascha Haber
Re: render cache clip source -> tracking speed
on Sep 23, 2015 at 11:44:00 am

I strongly suggest using PFClean for those tasks..
Resolve is by no means up for this.
Not only due to the lack of a robust cache system, but also because you will into trouble with the sprocket wear data.
PFClean with perform that kind of stabilise by analysing the film wear and saving each frames offset in a data file.
I just cleaned a short movie with it and its just a different world.

Resolve 11.3 - Smoke 2015 EXT1 - Sapphire 8
Colorist / VFX Guru / Aerial footage nerd
http://vimeo.com/saschahaber
https://dk.linkedin.com/in/saschahaber


Return to posts index


Patrick Morgan
Re: render cache clip source -> tracking speed
on Sep 23, 2015 at 2:14:54 pm

PFC will do the job, but it is pricey, we have Phoenix, that will also fix splice jumps while we're
at it, but that is even more expensive ;-) (but really, really good - but then I would say so...)

Alternatively - download Fusion - it can help out a lot, depending on how the material was scanned
you may or may not have sprocket holes to help. Track the frame corners on one side.

If the film was a reprint, there is a chance that even using the sprockets won't work since the image
is moving relative to the actual film. As a last comment, if you are doing restoration, make sure you
stabilise the frame, you don't want to change the content of the film (unless required) by fixing the
camera movement.

Patrick
Digital Vision

Patrick Morgan
Product Marketing Manager
http://www.digitalvision.tv


Return to posts index

Joakim Ziegler
Re: render cache clip source -> tracking speed
on Sep 24, 2015 at 10:32:15 am

A matter of taste, I guess. I find pfClean's stabilize functionality to be so cumbersome to set up and use that it's almost useless, especially for stabilizing lots of shots.

Although, to be honest, the best solution to this is a scanner that does optical stabilization, which ours does, so the image is always rock steady, including eliminating splice jumps completely... That only leaves gate weave on opticals, which is easy to fix in Resolve.

--
Joakim Ziegler - Postproduction Supervisor


Return to posts index

Andy Winter
Re: render cache clip source -> tracking speed
on Sep 24, 2015 at 11:31:21 am

thanks for all the comments!

but my main question/comment was about the render cache.
i ended up freeing some diskspace on my fast raid and grade
from the dpx-sequences directly.

and the sabilization in davinci-resolve works great for that kind
of shots that i have (only tripod total shots, without panning or
tilting or zooming).

but yes, if i had to do with handheld-camera-work i would be
out of luck inside resolve i guess...


Return to posts index


Oyvind Stiauren
Re: render cache clip source -> tracking speed
on Sep 25, 2015 at 12:04:37 am

If I understand your problem correctly, I think there are two ways to do what you want:

1. If you are able to use Resolve 12 you can use the "Optimize Media" function. If correctly configured in the Settings, it will make proxy ProRes files in 1:1 resolution.

2. If you have to use Resolve 11, you can import the whole DPX file to Resolve, put it in a timeline and render to ProRes using the "Individual Source Clips" and "Render at source resolution" options in the Render Settings. Then use the ProRes files to work with and later re-connect the DPX files using the "Reconnect from bin(s)" option. This way is not as elegant as the first one, but it works. Getting "Reconnect from bin(s)" to do what you want it to do can be difficult. A good start is to make sure that the "Reel Name" on both the DPX and ProRes files are the same.

--
Oyvind Stiauren
Post production supervisor, Colorist
Terminal

Mexico City


Return to posts index

Andy Winter
Re: render cache clip source -> tracking speed
on Sep 25, 2015 at 9:05:23 pm

thanks Oyvind,

i am still on resolve 11 because of an unfinished project! but i could go
the other route you posted, and i really nearly did, but then i thought:
of course i can render my proxies manually, and later reconnect, but
shouldn't this be possible with the built-in render-cache automatically?

but thanks, this would be a great manual workaround.


Return to posts index

Oyvind Stiauren
Re: render cache clip source -> tracking speed
on Sep 25, 2015 at 10:58:19 pm

i am still on resolve 11 because of an unfinished project! but i could go
the other route you posted, and i really nearly did, but then i thought:
of course i can render my proxies manually, and later reconnect, but
shouldn't this be possible with the built-in render-cache automatically?


The problem with all the render cache options in Resolve 11 is that the caching is done in the current Timeline resolution, and not the original clip resolution. So you're left with the two options I mentioned before.

--
Oyvind Stiauren
Post production supervisor, Colorist
Terminal

Mexico City


Return to posts index

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