Re: What does PTmender mean to hugin?

 Ippei UKAI twisted the bytes to say:

>> 
 >> I think they can co-exist. Command line tools are good for testing and
 >> batch processing.

 Ippei> I see. It sounds like libpano is going to gain the new functionality  
 Ippei> currently in PTcommon.c. That means hugin can directly benefit from  
 Ippei> it then. Do you think this is going to happen before 0.6 release?

 Ippei> Ippei

I just inspected the code.

The main function that does the work in PTmender is CreatePanorama: 

int CreatePanorama(fullPath ptrImageFileNames[], int counterImageFiles, fullPath *panoFileName,
fullPath *scriptFileName)

It is not that different from running PTmender from the command
line. At this point the parameters have been supposed to have been
verified, and the script parsed and checked for consistency. 

I think that is all that is needed by hugin (plus the callback to the
Progress function, I think the code for that is already in
panotools). The script will determine the type of processing expected,
and the format of the output.

By the way, CreatePanorama is not reentrant (in its current

Re: [PTBeta] Testing pano12 2.8.1rc1

On Thu 04-May-2006 at 10:39 +0200, Serge Maandag wrote:

> Retry, the message did not seem to get through

Odd, I got both.

> > I've uploaded a 'release candidate' of libpano12-2.8.1 for testing
> > here:

> > http://panotools.sourceforge.net/snapshots/

> I just downloaded the windows binaries. Where they compiled with mingw or
> with msvs?

The windows binary is compiled with mingw/gcc (I don't have access 
to msvc).

> In the latter case, I'll have to use ptmender. I have som questions about it:
> 
> Is it command line compatible with ptstitcher so I can rename it and use
> it in ptgui?

It should be a drop in replacement, though it isn't 100% complete.  
Notably it doesn't do fisheye input images.  It also has some useful 
new functionality such as cropped-tiff and LZW compression.

> The README file says:
>
> TODO:
>   * Recreate the following functions:

def files, which one is the one to modify?

Hi everybody, 

I am in the process of moving some of the PTmender (and friends)
functions into the libpano library.

I have seen there are 4 def files (libpano12.def, pano12.def,
pano12vc.def, pano12vcd.def). Which one is the right one to modify?
Or should I modify them all?

I'll probably rewrite clens to take advantage of the new functions in
the library (and to test them). 

thanks!

daniel

--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with  <at>  and (dot) with .

Changes to the library

Hi everybody,

I moved the CreatePanorama function (and all that are needed by it)
into the libpano library. This will make it possible for programs to
directly interact with it rather than using PTmender.

The function's prototype is:

int CreatePanorama(fullPath ptrImageFileNames[], int counterImageFiles, fullPath *panoFileName,
fullPath *scriptFileName);

that means that it is still necessary to create the script file. We
could potentially get rid of the need for the script file but I think
it is easier to use than filling a complex data structure (and less
error prone).

I some of you could:

* download the latest version (2.8.2)
* Compile it
* Try PTmender and hugin on it

I would appreciate it. It is working for me (OS X) 

I am going to start modifying clens to take advantage of it.

dmg

--

Re: Changes to the library

Le Samedi 6 Mai 2006 22:20, dmg a écrit :
> Hi everybody,
>
> I moved the CreatePanorama function (and all that are needed by it)
> into the libpano library. This will make it possible for programs to
> directly interact with it rather than using PTmender.
>
> The function's prototype is:
>
> int CreatePanorama(fullPath ptrImageFileNames[], int counterImageFiles,
> fullPath *panoFileName, fullPath *scriptFileName);
>
> that means that it is still necessary to create the script file. We
> could potentially get rid of the need for the script file but I think
> it is easier to use than filling a complex data structure (and less
> error prone).
[...]

Maybe is it time to increase shared library version ?
It should normaly be increased each time a change is made to exported 
functions and data elements.

--

-- 
Florent

support for 16 bits in PTmender

Hi everybody,

I just completed full support for 16 bit images in PTmender. 

In the process I updated libpano version to 2.8.3

--
Daniel M. German                  "For indeed who is there alive
                                   that will not be swayed by his
                                   bias and partiality to
    Jonathan Swift ->              the place of his birth?"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with  <at>  and (dot) with .

libpano12-2.8.1 released

Version 2.8.1 of libpano12 has been released:

http://sourceforge.net/project/showfiles.php?group_id=96188&package_id=132440

This release contains many small bugfixes and a number of useful new 
features.

Changes since 2.8.0
===================

Four new projection types have been added (Pablo d'Angelo)

* Stereographic (use f4 in the 'p-line')

* Mercator (use f5 in the 'p-line')

* Transverse mercator (use f6 in the 'p-line')

* Sinusoidal (use f7 in the 'p-line')

http://www.panotools.info/mediawiki/index.php?title=Projections

These work with existing versions of PTStitcher, PTmender and the
upcoming hugin-0.6.

Support for radiance 32bit float .hdr files (Thomas Rauscher)

A new API allows application developers to optionally supply their 
own callback functions for error and progress reporting (Pablo
d'Angelo).

Re: [PanoTools] libpano12-2.8.1 released

On Mon 08-May-2006 at 17:33 -0000, John Houghton wrote:
> --- In PanoTools@..., "Fernando Chaves" <fernchaves <at> ...> 
> wrote:
> > I've just tried pano12 2.8.1 on winxp sp2 with Ptgui 5.8.2.
> > When press "Preview" button I got the message:...impossible to find 
> > entrance point to TIFFClose process in pano12.dll.
> 
> I get the same message: "The procedure entry point TIFFClose could not 
> be located in the link library pano12.dll".  This is output when 
> PTStitcher is run, whether it's the final panorama or the preview.

Thanks for the report, this seem to be the same bug encountered by 
Manfred Kröger (libpano12.def doesn't export the same symbols as 
pano12.def).

Hmm, this file was created specifically _not_ to export the TIFFxxxx 
symbols.  It's confusing that this release fails when 2.8.0 which 
was built against the same library versions is apparently ok (unless 
nobody bothered to report that).

I won't have access to a windows machine again until the end of the 
week, but I'm not really the right person to investigate this 
anyway.  I'll delete the windows binaries from sourceforge unless 
somebody else finds that they are working for them.

--

-- 
Bruno

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?

Fwd: [PanoTools] Building the pano12.dll? Not again!

Forwarded from the panotools list.

-- 
Bruno

From: Manfred Kröger <Manfred_Kroeger@...>
Subject: [PanoTools] Building the pano12.dll? Not again!
Date: 2006-05-08 19:58:34 GMT

Hi!

If I would have known what a pain in the a.. building the dll would be I 
wouldn't have tried it. It seems there are two ways to build the dll:
http://www.panotools.info/mediawiki/index.php?title=Build_pano12_from_sourcecode
and
http://sourceforge.net/docman/display_doc.php?docid=20557&group_id=96188

Both descriptions are not really accurate and neither one of them works. 
Here are some hints for people who try to build the lib from what was 
available as the 2.7.0.14 release's source code. It seems the 
documentation on panotools.info is the better one so you should follow 
it - more or less.

1. Download and install MinGW and make sure you also install the Java 

Re: [PanoTools] libpano12-2.8.1 released

Thanks for announcing this new release.  I'm looking forward to trying out the 
new projections!

Im having a little problem with it, however.  PTOptimizer runs correctly with 
this new version, but when I try and run PTStitcher, I see a window with the 
following message (see attached screenshot):

"The procedure entry point TIFFClose could not be located in the dynamic link 
library pano12.dll".

I've tried this on two machines (Windows XP SP1, and Windows XP SP2) with the 
same result...Anyone have any thoughts on what might be causing this?

Thanks,

Max

> Version 2.8.1 of libpano12 has been released:
> 
> http://sourceforge.net/project/showfiles.php?group_id=96188&package_id=132440
> 
> This release contains many small bugfixes and a number of useful new 
> features.
> 
> Changes since 2.8.0
> ===================
> 
> Four new projection types have been added (Pablo d'Angelo)
> 
> * Stereographic (use f4 in the 'p-line')