Sounds like a good idea. There are a few things I would like to add: I'd prefer one common class/module for file IO and all the necessary conversions like millimeters <--> inches, focal length <--> horizontal view angle, picture ratio <--> film aperture, etc. so each application module can derive from this and stay as lightweight as possible.
Another module could handle the dialogs but if they're optional, it's easier to integrate the importer/exporter into a scripted pipeline or toolbars. Plugins could just use the correct application module but be separate files again so people don't have to use them. Also, to make it not just another almost-useful tool, don't forget less common properties like optical center shift etc. required by stereo setups, for example. As you already wrote in SPEC.txt, all expected units have to be defined. Michael On Wed, Jul 10, 2013 at 8:53 AM, Sandy Sutherland <sandy.mailli...@gmail.com > wrote: > Gene - this would be of huge interest I think - every studio I have been > at we have needed to do this, and have always fudged it - never had the > time to even start looking at creating a tool! > > So - a big yes from me! > > S. > > > On 2013/07/10 5:09 AM, Gene Crucean wrote: > > Hey folks, > > Who's in the mood for some open-source camera I/O code? I'm kind of > getting bummed out on having to write the same camera tools at every studio > just to get a simple, lightweight and most importantly reliable camera > pushed around from app to app. FBX does *not* cut it, not to mention it's > not available for all apps that could make use of it. So I thought I would > whip up a spec based on json and offer it up open source so anyone willing > to donate some time, could create some simple tools to import/export for > their favorite app. The spec is VERY lightweight and doesn't include some > things that I'm sure someone will want... but please let me know your > thoughts. > > I already have a Softimage plugin working (consider it alpha). At this > point it only has minor sanity checking and logic tests and I'm sure there > are a zillion ways to improve it. But it's a start. The goal is to at least > have plugins that all read and write the same spec from Houdini, Softimage, > Maya, Max, Blender, Nuke... and more. I've built the Soft one using PyQt > and it would be nice to maintain some consistency between apps, so I'm > hopeful that the other versions could be based off of the same .ui file. > > What do you guys think? Any interest in this? I know it's a simple thing > but I'm sure a lot of you also write these tools at studios quite a bit too > and could possibly be into something like this. > > Check out the spec and source, and if you have time, play with the Soft > plugin here: https://bitbucket.org/crewshin/json-cam > > > If you have completely zero interest in this... no worries. Thanks for > looking. > > > -- > -Gene > www.genecrucean.com > > >
