Harry, I have just checked ... I have more than 40 versions of Hugin on this machine! I tend to be cautious and keep the old version when I install a new one ... :-) By the look of it my last big clear out was March 2010!
So what I will do is install a fresh copy of your latest version on another Mac that I don't usually use for Hugin and then give that a try accessing the data and project files over the network. But it will be this evening or possible tomorrow before I will be able to do that. all the best George On Apr 22, 2:36 pm, Harry van der Wolf <[email protected]> wrote: > @George, > > Can you rename all Hugin.app and PTBatcherGui.app versions that you're not > using to something like .app.org. > Then start PTBatcherGui, leave it open, then start Hugin.app and do a > workflow? > > I have the vague idea that too many versions exist on your system and that > incompatible combinations are called. > > Harry > > Op 22 april 2012 14:43 schreef Rogier Wolff > <[email protected]>het volgende: > > > > > > > > > > > On Sat, Apr 21, 2012 at 02:46:32PM +0200, Harry van der Wolf wrote: > > > To be honest: I didn't know about the jpeg (IJG) and old-jpeg, but > > reading > > > that error it was the first thing I checked. When I started with Hugin > > on > > > OSX we were at jpeg6b from the IJG group and I'm still using that > > library, > > > now at version 8d. > > > All binaries and libraries are compiled against the same libtiff (and > > jpeg > > > and png for that matter), thereby using the same header files from the > > same > > > include path. I checked that with a.o. "otool -L ..." and especially > > > checked for files being "slipped in" from my macports: none at all. > > > My libtiff is compiled with both old-jpeg and jpeg support. > > > > If you have more suggestions on what went wrong, please let me know. > > > The big test is, can YOU run with LZW compression? (I expect: yes) If > > so, that is a strong hint that george is not using the same library > > binary as you are. > > > This could mean that on your system you are not using the tiff library > > you just built and include in the package, or the other way around, on > > george's system the hugin tools are not using the packaged libraries > > but the system ones. > > > Roger. > > > -- > > ** [email protected] **http://www.BitWizard.nl/** +31-15-2600998 ** > > ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** > > *-- BitWizard writes Linux device drivers for any device you may have! --* > > The plan was simple, like my brother-in-law Phil. But unlike > > Phil, this plan just might work. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Hugin and other free panoramic software" group. > > A list of frequently asked questions is available at: > >http://wiki.panotools.org/Hugin_FAQ > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/hugin-ptx > > -- > Hugin development bundles for Mac OS > X<http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin> > ImageFuser for Mac OS X <http://imagefuser.sourceforge.net/> > KImageFuser for > Linux<http://panorama.dyndns.org/index.php?lang=en&subject=KImageFuser&text...> -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
