Lens Distortion From Syntheyes
Posted 28 July 2012 - 12:45 PM
Posted 28 July 2012 - 08:16 PM
But I can't find a way to get an UV Distortion map out of Syntheye.
Posted 29 July 2012 - 01:22 AM
I hope Fusion gains Syntheyes support in the next version. After all, PFTrack has already been added. But maybe an email to requests@ eyeonline won't hurt :-)
I went the UV map route once as well. You need to create a UV map at the right size in Fusion and then replace your image sequence in Syntheyes with it. Export it as float and bring it back into Fusion... but it's a convoluted workflow, it needs the right settings for the Displace tool (which might break in proxy mode), needs special care if an undistorted image has a different size than the original plate et cetera...
Posted 29 July 2012 - 06:00 AM
Posted 29 July 2012 - 10:30 AM
Just sent my request to Eyeon about SynthEyes
BTW - DigitalTutors has a SynthEyes/Fusion course that I've just watched which is pretty useful for getting up to speed on SynthEyes/Fusion integration.
He didn't use Fusion's fog for the shot, but rather a 2D EXR sequence, which seemed to give him a lot of control, but ... I'd be curious about using the fog tool (as he had a depth pass).
Some of the course objects are in Modo format, but the author was nice enough to convert them to Lightwave for me, and I expect he'd do the same for OBJ/3ds/etc.
Posted 30 July 2012 - 05:13 AM
I normally had been using the syntheye workflow. But saving the undistorted image sequences and distort them after compositing, is something I would like to avoid!
It is better to all the distortion stuff in one compositing without an extra "generation" of the material.
Posted 30 December 2012 - 07:59 PM
Posted 31 December 2012 - 01:22 AM
Posted 31 December 2012 - 06:59 AM
Posted 31 December 2012 - 07:22 AM
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:/Users/Public/Documents/eyeon/Fusion/Scripts/Tool/LensDistort for Syntheyes.py", line 61
Posted 31 December 2012 - 09:39 AM
I'm running 2.7.1 myself. I have no idea what that error might indicate. There *might* be a warning about "import math" when you first start the script but that doesn't abort the script and it won't show up again when you run it again.
You could try to replace "print e" (almost the last line in the script) with the word "pass" and then see what happens.
Posted 31 December 2012 - 09:55 AM
If something like print e is an error it looks as if python 3.x is used as the print statement was replaced with a print function (which needs brackets).
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users