Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
(4) |
Jun
(8) |
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
(9) |
Dec
|
| 2005 |
Jan
(13) |
Feb
(3) |
Mar
(5) |
Apr
(12) |
May
(22) |
Jun
|
Jul
(10) |
Aug
(7) |
Sep
(3) |
Oct
(7) |
Nov
(10) |
Dec
(13) |
| 2006 |
Jan
(22) |
Feb
(20) |
Mar
(5) |
Apr
(50) |
May
(103) |
Jun
(98) |
Jul
(63) |
Aug
(35) |
Sep
(32) |
Oct
(149) |
Nov
(77) |
Dec
(113) |
| 2007 |
Jan
(145) |
Feb
(97) |
Mar
(109) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(2) |
Aug
(19) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2008 |
Jan
(5) |
Feb
(10) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(16) |
Sep
(2) |
Oct
|
Nov
|
Dec
(3) |
| 2009 |
Jan
(2) |
Feb
(2) |
Mar
(6) |
Apr
(5) |
May
(19) |
Jun
|
Jul
(5) |
Aug
(27) |
Sep
(188) |
Oct
(31) |
Nov
(23) |
Dec
(17) |
| 2010 |
Jan
(48) |
Feb
(14) |
Mar
(11) |
Apr
(3) |
May
(12) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(10) |
Oct
(6) |
Nov
|
Dec
|
| 2011 |
Jan
(51) |
Feb
(77) |
Mar
(39) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2012 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(7) |
Dec
|
| 2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
(4) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(11) |
| 2014 |
Jan
(14) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
|
2
(2) |
3
|
4
|
5
|
6
(2) |
7
|
|
8
|
9
(2) |
10
(2) |
11
(2) |
12
(4) |
13
(2) |
14
(4) |
|
15
(1) |
16
(1) |
17
(8) |
18
(5) |
19
(11) |
20
(3) |
21
(2) |
|
22
(7) |
23
(24) |
24
(15) |
25
(9) |
26
(14) |
27
(15) |
28
(8) |
|
29
|
30
(4) |
31
(2) |
|
|
|
|
|
From: Chris Erskine <stupid.tourist@gm...> - 2006-10-25 09:19:28
|
I've just recently got a perl camera control script running under linux (using gphoto) that i can take large hdr photos with. so I've now started looking into building a motorised panoramic rig that i can control with this same script. I'd like to use either 2 or 4 motors on it, with 4 would allow me to adjust the nodal point of the camera from the script. but then here is my problem, there is no point in adding the extra cost and weight of the extra motors unless i can automate the calibration. is it possible to get take 2 or more photos and have something say hugin to stitch the images and then if there are any parrallex errors it outputs a value that could be sent back to the script to adjust the position of the camera. then repeat the process until it stitches without any errors. thanks chris |
|
From: Daniel M. German <dmg@uv...> - 2006-10-25 00:30:12
|
Max Lyons twisted the bytes to say: >> > the binaries on my site are different from the=20 >> > "official" 2.8.4 release...in a good way! They >> > *are* binary compatible with PTStitcher and >> PTMender. >>=20 >>=20 >> Shouldn't these be the *official* 2.8.4 ? From a user >> perspective they definitely should be. >>=20 >> Could you provide me with the source? then I will >> compile them for >160=B0 and forward them to Jim for his >> site. This will feed the hungry users while 2.8.5 is >> being debugged. Max> The sources are whatever were in the source code repository on June= 11, 2006. =20 Max> I don't think I still have them lying around, but you should be abl= e to check=20 Max> our the code "as of" that date. Max, would it be possible to add a COPYING file to your bundle (see section 1 of the GPL). It is a requirement for any copies (binaries or sources) you make of the source code. You might also want to make explicit that PTstitcher is not covered under this license. -- daniel -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . =20 |
|
From: Max Lyons <max.lyons@ve...> - 2006-10-24 23:31:09
|
> Hi Max, > > Any chance you can contribute some of that code to panotoos? I'll > write the wrapper program around it. > I think I'm going to hold off on that. It is actually a stand alone C program, but this one was developed by my Tawbaware team (i.e. me), rather than my open source team (i.e. me)! The good news is that I'll be contributing another utility program shortly...PTFinalize. I'll have some more details later. Max |
|
From: Max Lyons <max.lyons@ve...> - 2006-10-24 23:31:08
|
> > the binaries on my site are different from the > > "official" 2.8.4 release...in a good way! They > > *are* binary compatible with PTStitcher and > PTMender. > > > Shouldn't these be the *official* 2.8.4 ? From a user > perspective they definitely should be. > > Could you provide me with the source? then I will > compile them for >160=B0 and forward them to Jim for his > site. This will feed the hungry users while 2.8.5 is > being debugged. The sources are whatever were in the source code repository on June 11, 20= 06. I don't think I still have them lying around, but you should be able to ch= eck our the code "as of" that date. > > In fact, my plan is not to provide compiled versions > > of pano13 at all. > > So what about the new features that will be added to > pano13? > They will all get compiled into PTMender...it is just that instead of havi= ng an executable (PTMender) and a library (Pano**dll), I'll roll up all of the c= ode into one executable (PTMender) without the library. > I love statically linked, self contained code. I do > not know yet how to compile the panotools statically > linked - any hint/help appreciated. Once you've built the library, you will have compiled all of the individua= l source files into *.o files. You can just add all of the these into the c= all to compile PTMender like this: gcc -o ptmender.exe ptmender.o ../filter.o ../parser.o ../queryfeature.o ../correct.o ../perspect.o (...and all the rest...) Don't forget to link with the image libraries (TIFF, PNG, JPEG, Z) as well= . Max |
|
From: Bruno Postle <bruno@po...> - 2006-10-24 22:59:52
|
On Thu 19-Oct-2006 at 19:02 +0200, Erik Krause wrote: > On Tuesday, October 17, 2006 at 20:00, Pablo d'Angelo wrote: > > > Ah, please let us know of the script/application, when its finished :-) > > Many thanks, Pablo and Rob! I have the solution so far. Currently it > is in an excel only, but I can provide it to anyone who wants. Thanks this is what I needed too. I've implemented it in the Panotools-Script perl module in panotools SVN. Basically, install the module (and Math::Matrix dependency) and you can rotate a PTStitcher or hugin .pto file on the command-line like so: transform-pano <roll> <pitch> <yaw> <input> <output> eg: $ transform-pano 15 90 -30 input.pto output.pto All the component image positions will then be transformed so the panorama as a whole is rotated. Tested on Linux, should be ok on windows with perl installed. -- Bruno |
|
From: Pablo d'Angelo <pablo.dangelo@we...> - 2006-10-24 20:04:51
|
Daniel M. German schrieb: > > JD> I suppose "do" -> "don't", but I thought PTBlender could handle > JD> cropped TIFF? > >> >> > >> >> Which version are you using? I fixed this bug few weeks ago. Try the > >> >> most current version (2.8.5.pre4 from the subversion pano13 branch). > >> > JD> The version at hugin.sf.org: 2.8.4 (from libpano12, compiled for Mac). > JD> Will libpano12 be obsoleted now that 13 is going strong? > >> > >> libpano12 is to be used with PTstitcher and other binaries for which > >> we do not have source code. > >> > >> For everything else pano13 is the way to go. It contains many features > >> not available in pano12. > > JD> What about Hugin/PTGui/PTAssembler/PTMac? Are they switching up to > JD> pano13? Since some of these still use PTStitcher, I supposer the > JD> upgrade path would be to drop that and use PTMender instead? > > Max (PTAssembler) and Pablo (Hugin) have been contributing to the > project, and they can share their thoughts and positions with respect > to PTmender. I plan to ship the next hugin version with pano13. The nice thing about pano13 is that now it is possible to implement stuff like TCA correction during remapping. Since I can't ship PTStitcher in the download from sourceforge anyway, I don't have a problem with a non working PTStitcher, however, I might for convinience add a compatible pano12.dll to the hugin windows package, so that people just need to drop the PTStitcher.exe into the hugin folder. I also have to add a new PTmender stitcher choice to hugin... > Also, we don't really have a pano13 build for Windows yet (problems > with the makefiles and the ./configure). I will build the windows binaries with MSVC, if required. I and Jim have been using MSVC project files for pano12. I remember that I made some updates to these in the pano12 branch, so I should probably update them in the pano13 branch too.. I also believe that its a lot easier to build using MSVC than mingw on windows. (I believe the version that can be downloaded at no cost from microsoft should also work well). ciao Pablo |
|
From: Bruno Postle <bruno@po...> - 2006-10-24 18:11:27
|
On Mon 23-Oct-2006 at 18:33 -0700, Yuval Levy wrote: > >I documented my experience with 2.8.4 and 2.8.5. It is >still very unfinished, though if the developers think >it is a good idea, i'll finish it and get it ready for >publication. > ><http://www.levy.ch/pt/ptwin.txt>; This bit doesn't make any sense: * copy makefile.win32 to source dir Makefile $ ./configure The 'configure' script will overwrite 'Makefile'. Basically the 'makefile.win32' is deprecated, it's only there if you can't get things to work any other way, so you can ignore it. Though I don't understand why you can't get it to compile using the Build_pano12_from_sourcecode wiki doc? > I am trying to set up a scripted system to do this > more or less automatically from the SVN repository. > How do I fetch a particular release from the SVN? Something like this, all on one line: svn co https://svn.sourceforge.net/svnroot/panotools/branches/pano12/libpano pano12 Should create a directory called 'pano12' containing the latest 'pano12' branch. The next problem you will find is that there is no 'configure' script in SVN... -- Bruno |
|
From: Daniel M. German <dmg@uv...> - 2006-10-24 16:55:14
|
Michal> PTblender in SVN is IMHO not working correctly. I had following problems: Michal> 1) When -c or -m is specified no image output is done and therefore it Michal> shouldn't be possible to specify -f too. Michal> 2) When -c is specified wrong index to array curveExtension is used. Michal> 3) Program tries to free already freed memory at the end. Michal> I made a patch for these bugs. If you find my patch acceptable, please Michal> apply it to SVN. Thanks Michal, I have committed this patch. I have to say that the curves output feature of PTblender is hardly tested. I still have to take care of the other patch. -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . |
|
From: Michal <michal@li...> - 2006-10-24 13:07:35
|
I just found out why my Photoshop can't load acv files generated with PTblender. Curves are generated wrong on little endian. Attached patch should fix this. Michal |
|
From: Michal <michal@li...> - 2006-10-24 12:10:05
|
PTblender in SVN is IMHO not working correctly. I had following problems: 1) When -c or -m is specified no image output is done and therefore it shouldn't be possible to specify -f too. 2) When -c is specified wrong index to array curveExtension is used. 3) Program tries to free already freed memory at the end. I made a patch for these bugs. If you find my patch acceptable, please apply it to SVN. FYI. photoshop CS2 complains "Could not load the curves because the file in not compatible with this version of Photoshop." when I'm trying to load ACV file. AMP files work good. Thanks Michal |
|
From: Daniel M. German <dmg@uv...> - 2006-10-24 02:45:30
|
yuval levy twisted the bytes to say:
yuval> Thank you Max - for sharing your thoughts, for the
yuval> ex-post permission to use your files for the test
yuval> installer, and for "saving" a binary-compatible 2.8.4.
yuval> Shouldn't these be the *official* 2.8.4 ? From a user
yuval> perspective they definitely should be.
They can become 2.8.6, but not 2.8.4. there is already an "official" 2.8.4
yuval> I have only marginally followed the discussion about
yuval> the code split and lack the technical expertise to
yuval> judge. As a user I must say that it is confusing, but
yuval> proper communication and support (which I am willing
yuval> to contribute) can linder the confusion. I am
yuval> collecting the thoughts I am reading here and putting
yuval> up an FAQ, though I doubt I'll finish it tonight and
yuval> tomorrow my working day starts at 7 AM...
Thanks Yuval, this is something that needs to be done, and we
appreciate your help.
>> I think that folks will need/use PTStitcher for some
>> time to come.
yuval> Indeed! Even if PTMender would be a perfect drop in
yuval> replacement for PTStitcher, users do not change their
yuval> setup as often as developers do.
>> In fact, my plan is not to provide compiled versions
>> of pano13 at all.
yuval> So what about the new features that will be added to
yuval> pano13?
>From the top of my head:
* PTmender supports:
- It maintains colour profiles and other metadata in TIFF and PSD
output.
- Colour correction (both colour and brightness) are fully
supported.
- Several bug fixes
* PTtiff2psd
- Supports stacking images
yuval> I love statically linked, self contained code. I do
yuval> not know yet how to compile the panotools statically
yuval> linked - any hint/help appreciated.
This is one of the great advantages of having the source code ;)
yuval> https://lists.sourceforge.net/lists/listinfo/panotools-devel
--
Daniel M. German "I'm crazy, but I'm not stupid"
Jackie Chan
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Daniel M. German <dmg@uv...> - 2006-10-24 02:39:40
|
yuval levy twisted the bytes to say:
yuval> --- "Daniel M. German" <dmg@...> wrote:
>> As time passes by, I think nona is the way to go.
yuval> so what exactly is the relationship between nona and
yuval> PTMender? I thought I read somewhere that both are
Like Juliet and Romeo, they love each other, and can't live
separated. But their families are on the way, and they might have to
kill each other to be together in the next life.
yuval> drop in replacements for PTstitcher?
yes
--
Daniel M. German "I come out of traditional mathematics
where we prove things,
but we don't charge people
Donald Knuth -> for using what we prove. "
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: yuval levy <yuval_levy@ya...> - 2006-10-24 02:34:42
|
--- "Daniel M. German" <dmg@...> wrote: > No, what I meant is, where is the source code of the > installer itself? The file I used to generate the installer will be contributed to the project (I guess we can add it to the SVN repository) once I get a better grasp of the file structure after compilation and don't have to manually move around the files. The installer itself is at <http://www.jrsoftware.org/isinfo.php>;, source code included. Yuv __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: yuval levy <yuval_levy@ya...> - 2006-10-24 02:31:31
|
--- "Daniel M. German" <dmg@...> wrote: > As time passes by, I think nona is the way to go. so what exactly is the relationship between nona and PTMender? I thought I read somewhere that both are drop in replacements for PTstitcher? Yuv __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: yuval levy <yuval_levy@ya...> - 2006-10-24 02:27:10
|
Thank you Max - for sharing your thoughts, for the ex-post permission to use your files for the test installer, and for "saving" a binary-compatible 2.8.4. > the binaries on my site are different from the > "official" 2.8.4 release...in a good way! They > *are* binary compatible with PTStitcher and PTMender. Shouldn't these be the *official* 2.8.4 ? From a user perspective they definitely should be. Could you provide me with the source? then I will compile them for >160° and forward them to Jim for his site. This will feed the hungry users while 2.8.5 is being debugged. > In fact, there isn't any technical reason why > PTMender, PTStitcher (and > friends) couldn't all work with a single pano12.dll. I have only marginally followed the discussion about the code split and lack the technical expertise to judge. As a user I must say that it is confusing, but proper communication and support (which I am willing to contribute) can linder the confusion. I am collecting the thoughts I am reading here and putting up an FAQ, though I doubt I'll finish it tonight and tomorrow my working day starts at 7 AM... > I think that folks will need/use PTStitcher for some > time to come. Indeed! Even if PTMender would be a perfect drop in replacement for PTStitcher, users do not change their setup as often as developers do. > In fact, my plan is not to provide compiled versions > of pano13 at all. So what about the new features that will be added to pano13? > I get enough e-mails from people who don't know how > to open a zip file, or who can't navigate the > directory structure on their file systems. sounds like you get e-mail from the real world :-) > So...my plan is to release versions of PTMender and > PTOptimizer that are statically linked. I love statically linked, self contained code. I do not know yet how to compile the panotools statically linked - any hint/help appreciated. Yuv __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: yuval levy <yuval_levy@ya...> - 2006-10-24 01:33:26
|
--- Jim Watters <jwatters@...> wrote: > I have never used autotools. I started to create a > document of how to create a build in windows. I documented my experience with 2.8.4 and 2.8.5. It is still very unfinished, though if the developers think it is a good idea, i'll finish it and get it ready for publication. <http://www.levy.ch/pt/ptwin.txt>; I am trying to set up a scripted system to do this more or less automatically from the SVN repository. How do I fetch a particular release from the SVN? Yuv __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Daniel M. German <dmg@uv...> - 2006-10-24 00:19:52
|
Pablo d'Angelo twisted the bytes to say:
Pablo> Hi Daniel,
Pablo> Daniel M. German schrieb:
>>
>> One of the things that I dislike about panotools is its desire to be
>> "symmetric" and to always put the point in front of the viewer in the
>> center of the image, even if the panorama only covers an area that
>> does not include it.
>>
>> For this reason I think it will be useful to be able to create some
>> command line commands that can analyze the TIFFs (cropped or
>> uncropped) to compute the true area of the panorama, and use this as
>> the basis for the cropping of the tiffs.
Pablo> I don't like the "symmetric" behaviour too, but I think it would be
Pablo> preferable to extend PTmender and nona to support cropping in the first
Pablo> place, with a new parameter in the "p" line, that specifies a subregion of
Pablo> the image:
Pablo> p f2 w3000 h1500 v360 bleft:top:right:bottom
Pablo> Then the user can decided what to render already while creating the
Pablo> panorama. Internally hugin and nona have support for that, I just haven't
Pablo> had the time to add it to parser and GUI yet.
I agree, this is something that will help a lot. Perhaps we should
also include two more options to output either:
* The bounding rectangle
or
* The inside rectangle.
This can accelerate processing (if the user wants to process only a
region of the pano) but I suspect that for the majority it will not
make a big difference (in processing speed) if the cropping happens
after the current remapped TIFFs are created.
We could then first implement it with a command line utility and then
embed it into PTmender or nona, if we feel it is worth the investment.
--
Daniel M. German "As De Gaulle used to say:
'Aim well, shoot fast
Henri Cartier Bresson -> and get the hell out.'"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Daniel M. German <dmg@uv...> - 2006-10-23 23:55:29
|
>> So I propose the creation of a pano cropping tool that takes as input
>> as set of TIFFs (cropped or uncropped) and generates as output a set
>> of cropped tiffs such that:
>>
>> a) Any edge of the total sum of all tiffs contains at least one "true"
>> pixel (a pixel with data from at least one pano).
>>
>> or
>>
>> b) Any edge of the total sum does not contain a single "black" pixel
>> (that is, a pixel with no information).
>>
Max> I've just finished coding something that does something similar to (b) that
Max> will be part of the next version of PTAssembler. It takes a final blended TIFF
Max> (e.g. the output from Enblend or Smartblend) and crops the image to remove all
Max> extra "black pixels" around the edge, leaving a finished, cropped image.
Max> It turned out to be more difficult than I had first guessed because what is
Max> really needed is to determine the rectangular region that encompasses the
Max> maximum area inside the image rather than look for rows or columns without
Max> black pixels at the edges.
Hi Max,
Any chance you can contribute some of that code to panotoos? I'll
write the wrapper program around it.
--
Daniel M. German "A person may cause evil to others
not only by his actions
but by his inaction,
and in neither case
he is justly accountable
John Stuart Mill -> to them for the injury."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Daniel M. German <dmg@uv...> - 2006-10-23 19:50:49
|
yuval levy twisted the bytes to say:
yuval> --- "Daniel M. German" <dmg@...> wrote:
>> Is the source code in your intall.exe program
>> available? It will have to be.
yuval> It is possible to put the source code in the
yuval> installer.
No, what I meant is, where is the source code of the installer itself?
--
Daniel M. German "Language alone protects us from the scariness
of things with no names.
Toni Morrison -> Language alone is meditation. "
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Daniel M. German <dmg@uv...> - 2006-10-23 19:49:34
|
Max Lyons twisted the bytes to say:
Max> Another idea might be to store the script inside the TIFF, after removing all
Max> the "o" (and perhaps "i" and "C") lines that correspond to other images in the
Max> project. That way, you'd have all the information necessary to recreate the
Max> image without carrying around the extra data for other images in the project.
Max> Max
hi Max,
I think this is a great idea.
The only disadvantage is what to do when we flatten the image. Perhaps
a better solution is to add:
* The entire script
* An indicator to which image number the current file corresponds to
(-1) if it is flatten.
I need to read the TIFF spec to see where we can add this extra
information.
dmg
--
Daniel M. German "As De Gaulle used to say:
'Aim well, shoot fast
Henri Cartier Bresson -> and get the hell out.'"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Daniel M. German <dmg@uv...> - 2006-10-23 19:46:21
|
Pablo dAngelo twisted the bytes to say:
Pablo> Hi all,
>> > Open Source is so driven by person needs of the
>> > developer. :)
>>
>> Does nona support fisheyes?
Pablo> Yes, I added support for fisheyes after I bought a Peleng fisheye lens :-)
I have been thinking about buying a Nikon 10.5, but I think I'll first
get a TS-E lens.
dmg
--
Daniel M. German "The greatest dangers to liberty
lurk in insidious encroachment
by men of zeal,
well-meaning
Louis Brandeis -> but without understanding."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Daniel M. German <dmg@uv...> - 2006-10-23 15:56:02
|
Pablo dAngelo twisted the bytes to say: Pablo> Hi all, >> > Open Source is so driven by person needs of the >> > developer. :) >> >> Does nona support fisheyes? Pablo> Yes, I added support for fisheyes after I bought a Peleng fisheye lens :-) As time passes by, I think nona is the way to go. That is one of the main reasons that I am concentrating in extracting functionality of PTstitcher into little command line utilities that can be used in combination with nona or PTmender. As far as I know, the only feature not supported by nona is morphing. dmg -- Daniel M. German "Speak not about what you have read, Azerbaijani Proverb -> but about what you have understood." http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . |
|
From: Daniel M. German <dmg@uv...> - 2006-10-23 15:55:59
|
Hi Max,
Max> That is fine with me. However, the binaries on my site are different from the
Max> "official" 2.8.4 release...in a good way! They *are* binary compatible with
Max> PTStitcher and PTMender. I know I'm contradicting the conventional wisdom
Max> here, but these versions of PTMender.exe and PTStitcher.exe both work with
Max> pano12.dll. How is this possible? It is because the change that "broke"
Max> binary compatibility happened just before 2.8.4 was released, and these files
Max> are from immediately prior to that change.
You have the right to distribute the code, but please don't call it
2.8.4. It is confusing. The official 2.8.4 is different than the one
you are distributing. Please call it something different. Perhaps
2.8.4m? It will avoid confusion with the users.
Max> I think that folks will need/use PTStitcher for some time to come. In addition
Max> to fisheye support which reportedely does not work (I haven't tested), PTMender
Max> still doesn't do feathering and crashes in a nasty way if fed some of the
Max> script parameters that work quite happily with PTStitcher (e.g.
Max> colour/brightness correction).
Version 2.4.5pre4 of pano13 supports all colour and brightness
corrections and should not crash under any circumstances.
Max> I use MingW, and I've never been able to build using the autotools either. It
Max> sounds like a good idea in the Unix world, but seems to cause problems in the
Max> the Windows world! Unfortunately, the test suite relies on this as well, so
Max> I'm not sure how much use of the test suite should be expected from Windows
Max> developers!
Look into Makefile.am in each of the tests directories. It is a very
simple process. Just run the script panoAutomateTest.pl with the name
of the script to test.
>> I think that pano12 is going to go into indefinite bugfix mode given
>> that maintaining this binary compatability is such a drag...pano13 is
>> the focus of development for PTmender etc... it will be numbered 3.0.0
>> or something to differentiate it from pano12.
Max> My guess is that pano12 will be more-or-less abandonned as developers make
Max> changes to the pano13 code, but not pano12. It is a shame because until/unless
Max> someone rewrites PTMorpher, PTInterpolate, PTStereo and all the other Panorama
Max> Tools programs, we'll still need to rely on pano12 for those to work.
Max> As for documentation, I think this would be an enormous help. I haven't looked
Max> recently, but last time I checked, the code was hard or impossible to find, and
Max> I found multiple versions of build instructions...none of which appeared to
Max> work!
I think you mean bild instructions under Windows. In the unix world
(both Linux and Mac OS) they are:
./boostrap
./configure
make
--
Daniel M. German "When asked whether or not we are
Marxists, our position is the same as
that of a physicist or a biologist who
is asked if he is a `Newtonian', or if
Che Guevara -> he is a `Pasteurian'"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
|
|
From: Pablo dAngelo <Pablo.dAngelo@we...> - 2006-10-23 14:53:49
|
Hi all, > > Open Source is so driven by person needs of the > > developer. :) > > Does nona support fisheyes? Yes, I added support for fisheyes after I bought a Peleng fisheye lens :-) ciao Pablo _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: Jim Watters <jwatters@ph...> - 2006-10-23 14:29:03
|
yuval levy wrote: >> I can add more binaries to my page if someone >> provides them to me. >> > > Let's work out what is required and work together to > reduce the load on your valuable time. > > Does it make sense to provide anything else but the > 2.8.0 currently on your site, or is it better to wait > for 2.8.5 before putting up new binaries at all? > I have been waiting for this but it sounds like Max has the build that can replace these. >> I am currently using 2.8.0 MSVC version. <snip/> >> The major increase in speed to me is well worth it. >> > > Then the key question is: is it worth it to keep an > MSVC *and* a MinGW distribution? Or said differently: > is there any chance that the latest MinGW has caught > up on the speed advantage? > Microsoft compiler does create faster code than that of MinGW. Once PTMender is a replacement for PTStitcher then it will not mater. The problem is MS compiler uses a different memory handling routine. For reading script files memory is allocated in pano12.dll and then destroyed in PTStitcher. > Would the free version of MSVC > <http://msdn.microsoft.com/vstudio/express/visualc/>; > be good enough to build panotools on Windows? If yes I > can put in the effort to learn it the same way I did > with minGW. > I don't see why it would not work. It is a newer version than I have at home currently I will try installing it on my new system when I get it. >> But I will continue to host binaries that are not >> restricted to 160 deg. >> > Let me know if you want to host them as an installer, > in which case I volunteer to package any binary > forwarded to me into an installer. > When you think you have the final version, email them directly to me, or let me know where to get them, and I will put them up. -- Jim Watters jwatters @ photocreations . ca http://photocreations.ca |