Autodesk Matchmover freezing
Posted in: Matchmoving Softwareis anyone else having this problem and does anyone know a solution? i have my images cached. but im thinking that maybe my image sequence is just to big for matchmover to cope. 🙁
is anyone else having this problem and does anyone know a solution? i have my images cached. but im thinking that maybe my image sequence is just to big for matchmover to cope. 🙁
:thanks:
MatG
It turned out that our new lens distortion models, recently introduced with 3DE4 r1b10, are much more powerful than our "vintage" classic one.
To make them even more powerful, in terms of integration into production pipelines, our friends at Weta Digital developed a Nuke node infrastructure which is based on our lens distortion SDK (LDPK).
The cool thing is, they released their work as open source:
Nuke nodes for 3D Equalizer lens distortion plugin kit
In addition, there is a 3DE4 Python script which allows to create a Nuke 3DE distortion node (.nk), compatible to the currently selected camera (incl. dynamic lens distortion):
Export Nuke Distortion Nodes v1.2
Many thanks to Peter Hillman, Wolfgang Niedermeier and Lee Bramwell!
Cheers,
Rolf
www.3dequalizer.com /devblog
Does anyone have another solution?
For example, I’m using a canon 60D (1.6 crop) with a 50mm prime lens. Do I tell PfTrack I’m using a 50mm lens or an 80mm lens?
(50mm X 1.6 crop = 80mm)
Pftrack approximates the lens at 35mm, which is not even close. Syntheyes approximates the lens at 50mm, which sounds right, but I’m not sure if it’s correct.
I’m getting a solid track regardless, but I’m just wondering…