puckhead193 said:i can't see anything, all i see are lines/boxes![]()
If you're on dial-up it takes about 4 or 5 minutes for all the images to load.
Was worth the wait.
puckhead193 said:i can't see anything, all i see are lines/boxes![]()
rdowns said:Very cool. I like the poster on the wall.
After a few hours debugging, it looks to be quite a serious problem.
It is associated with using "vecLib" - which is Apple's library of math function for using AltiVec (G4) acceleration to speed things up - in a CodeWarrior project, which is what the CubicConverter 2.x is. (v3.0 has moved to Xcode.)
I'm blaming Apple, of course, since it's their update that broke it! I've reported it as a bug, so we'll see what happens.
In the meantime I've created a temporary fix by disabling AltiVec. It is available here:
http://www.clickheredesign.com/downloads/
Feel free to pass this info on to anyone you know might be affected.
Regards,
Michael.
Cooknn said:Just found out - the OS X 10.4.6 update breaks CubicConverter. From Michael Bradshaw the developer...
iGary said:Well, imagine six of those taped images around OK?
Now with a 180 degree field of view. there is a bunch of overlap between each image. I'll let Q d the math.
So in PTMac, the program shows an image, and the one next to it (envision the picture above divided into six pieces). So say you have image 0 and image 1. Where those two meet (and all the others, too, there is an overlap area and you use the tape and corners to mark identical spots (control points) on each image, so the application knows what pixels "match," and where it should stitch them together.
You can see this below:
![]()
ChrisBrightwell said:Which camera and lens did you use?
I've wanted a quick solution for this sort of stuff for a while ... I have a 350D, but I'd need a lens to go with this thing. I've priced a few pano heads before, but none of them seem this well done.
$1000 is a lot, but you're right. That's pretty easily made up through local realtors and such.