As a tracker, this is one of my most used applications. it would be really handy to 'track' not just these files, but how file outputs from Syntheyes (or any other tracking app really) to maya, nuke and after effects.
Date
Votes
9 comments
-
Ryan Mayeda Hi Mike!
Thanks for bringing some community attention to SynthEyes! You're not the first person to ask about this and it's definitely on our radar. It looks like SynthEyes now has Python support, so that's an exciting (and new, I think) development!:
http://www.ssontech.com/python.htm
Previously they only had their Sizzle scripting language, which didn't have any sort of bridge into Python and thus couldn't communicate with Shotgun through the API. According to their site though, it looks like the Python integration isn't included by default and has an added cost (plus a license count minimum), so I wonder if we can expect all of our clients to be able to get access. Perhaps that is also something we can chat about with the SynthEyes team. In any case, with Siggraph coming up, that could be a great opportunity to meet in person. I will follow up on that and report back.
In the meantime, if there are any folks who have already looked at SynthEyes' SyPy, we'd love to hear more about your experience!
Ryan.
-
Michael Jackson This is a very exciting development! So this would enable a user to identify a plate to be tracked, launch a Syntheyes task, auto populate the shot with the plate, let the user do their thing, then run a python script to write the appropriate exports (to appropriate places) AND save the .sni file back to shotgun's folder structure.
Oh boy!
-
Marijn Eken Just yesterday the new version of Syntheyes was released (13.11). The Pro version now includes Python support as a standard. I guess they realized it was a bit silly to ask more money for that option.
I haven't looked at any of it yet, but I guess now it's more accessible by everyone. All the more reason to make an Engine for it! :)
-
Ryan Mayeda Hi Marijn.
I didn't realize SynthEyes now offers their Python support by default as opposed to having to make a deal with them for it. That's great news! Do you use SynthEyes a lot? I noticed you also posted in the other forums for camera tracking tools. I'm curious to know which one you think would be best to do first out of all of them?
Ryan.
-
Michael Jackson As Syntheyes is my primary tool, I am most interested in it. That said, I'm sure others would have other priorities.
Gimme, gimme, gimme.
-
Marijn Eken I'll just repeat here what I said in the 3D Equalizer Engine thread, so others can agree/disagree with me here as well! ;)
I think 3D Equalizer support should be higher on the list than Syntheyes. It's much more likely to be used in a situation where there's a proper pipeline.
Personally I use Syntheyes, but that's just because I occasionally do matchmoving (since I moved into compositing). A friend of mine, and professional matchmover, uses Syntheyes, PFTrack and 3D Equalizer, but pretty much swears by 3D Equalizer as having the best solver of them all.
-
James Cunningham You could argue that the people that use 3DE may be at a facility that have their own pipeline tool, rather than Shotgun.
-
Marijn Eken You could argue that, but I think there's also something to be said for facilities to try and adopt the Shotgun Pipeline tools. They're highly customizable, so that's no reason to stay away from it. Facilities might have their own pipeline tools, but that doesn't mean they are always the best, or well maintained.
Personally I'm very interested in using the Shotgun Pipeline Toolkit, mainly because it's too much work to create something like that myself. And at the same time, I'd like to use 3D Equalizer for the matchmoving. I think there might be more cases like this around.
And what you're saying about 3DE, could be said about a lot of the other Engines. A lot of those applications a fairly high end.
-
Sebastian Kral Hi everyone,
I sat down in some spare time and created a first working version of a SynthEyes Engine. I would like to give it to some testers to see if there are some bugs I can iron out before making it public.I didn't create a lot of documentation yet and was only able to test it under Windows.To run it you need a SynthEyes version with SyPy (2014 and above) and should probably know your way around Toolkit and Python a little bit.Looking forward to hearing from you.Cheers,Sebastian
Please sign in to leave a comment.