Hi Toshiyuki,
On 8/7/06, Toshiyuki TAKAHEI <[EMAIL PROTECTED]> wrote:
Yes. ProjectionDesigner depends on Qt and DevIL library, so
I think it is easy to port it to Linux, Macintosh and other platforms.
But currently I don't have any proper PCs to work with,
so currently I have no plan to port it by myself.
If some of you could help me, highly welcome.
I'll put this project to the sourceforge soon.
I can't help out right now, but perhaps over the next few months I
might get an opportunity. I would hope it wouldn't require much more
than just adding a build system.
Before I began this project, I couldn't found any open source projects of
distortion correction for curved screens. Open Producer has powerful
solution for multi-pipe rendering, but it still lacks the non-linear
correction and edge blending. That's why I made this software.
Scratch the Itch!!
Its why the OSG and some much other open souce exists ;-)
ProjectionDesigner is useful tool for this purpose, but I think
more important thing is universal format of configuration files.
Set of distortion map, blend map and Producer's camera configuration file
will work for any shape of screen with any number of projectors.
Scalable realtime 3D framework such as OSG should support
this kind of universal output interface.
It'd be good to have standard display specification file format. It
may be what ever we can come up with can be put forward as a standard
once it stable and well tested across many display configurations.
In the future if you have a better setup tool than the ProjectionDesigner,
I hope it would export configuration files in the same format.
In Producer's .cfg file, I want to write like:
Camera "left"
{
Lens {
Frustum -0.0921693 0.0921693 -0.0624869 0.0624869 0.1 100;
}
Offset {
Rotate -45.0 1 0 0;
}
Distortion distortmap_left.png;
Blend blendmap_left.png;
}
With this modification, Producer's configuration file
would work for any kind of projection environments.
Current Producer may be terminated by the last two lines,
but at least I want Producer to just ignore the unknown tokens
and provide some functions to retrieve them.
Of course if you put these correction in OSG / Producer core,
it would be highly useful.
As a short-mid term solution this would be pretty reasonable. It
would be easy to add a couple of extra string fields to
Producer::Camera to store the file names. Producer doesn't have
support for reading imagery so would have to just carry these
passively, and let osgProducer add the implementation.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
