[hugin-ptx] Re: Problem at the time of assembly

[Bruno Postle]

On Mon 12-Jan-2009 at 10:00 -0800, dyge wrote:

>enblend  -f3000x2455 -o JardinNeige.jpg JardinNeige.tif JardinNeige0001.tif
>enblend: error opening output file "JardinNeige.jpg":
>Precondition violation!
>did not find a matching codec for the given file extension

>Is this a known problem, yt is the solution ...

Hi, your enblend is compiled without JPEG support.

You can either choose a different output format such as PNG or TIFF, 
or you can recompile enblend after installing a 'libjpeg devel' 
package.

-- 
Bruno

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Image geometry data into EXIF?

[Klaus]

Hello,

When I wrote my suggestion, I thought about my usual workflow of
stitching and then cropping to rectangular shape, whatever the output
projection. And I had realised the advantage of a proper panorama
viewer over Preview/IrvanView/xv.

Although I did not ask for it, there may indeed be a point in
providing information on image data area inside an image file
(although within TIFFs the mask could prevent the viewer from
venturing into directions without image content). But that is image
content, not projection geometry.

So for a viewer to interpret the projection correctly, for rectilinear
(and fisheye) one needs to tell where the optical axis is in the image
(expressed as a fraction of image width/height from the left/top), and
in some way the focal length (measured in image diagonal length
units). If this info is invariant to image scaling, even better (so it
is). For cylindrical and equirectangular it is about hfov (degrees,
rad, gon?) and the position of the horizon line in the image (from the
top in units of height). In other words, just the info to allow
mapping of the image back onto the panosphere.

Cheers

Klaus
--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Image geometry data into EXIF?

[Bruno Postle]

On Mon 12-Jan-2009 at 15:51 -0500, Daniel M. German wrote:
>
> Bruno> PTmender sort-of does what you want, it puts a full copy of the 
> Bruno> stitching script in the exif data.  We could modify the hugin 
> Bruno> exiftool command to do the same, but currently no tools are able to 
> Bruno> make use of it.
>
>In my opinion the entire script is the best solution with respect to
>embedding information about how the stitch is done.

One problem is that the script is usually very compact unless it 
has thousands of lines of control points - These are of no interest 
in the output image metadata.

-- 
Bruno

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Problem at the time of assembly

[dyge]

Hello,
Sorry for my English but I can not control the language too.
I have an installation of logicile (hugin 7) and I wanted to make a
first overview of two photos.
It did not work and I had this message:
--
nona -z PACKBITS  -r ldr -m TIFF_m -o JardinNeige -i 0 /tmp/
huginpto_AtbLMu
nona -z PACKBITS  -r ldr -m TIFF_m -o JardinNeige -i 1 /tmp/
huginpto_AtbLMu
enblend  -f3000x2455 -o JardinNeige.jpg JardinNeige.tif
JardinNeige0001.tif

enblend: error opening output file "JardinNeige.jpg":

Precondition violation!
did not find a matching codec for the given file extension

make: *** [JardinNeige.jpg] Erreur 1
--
Is this a known problem, yt is the solution ...
Pending a response, thank you in advance.
Yann.

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Exposure correction for time lapse

[Andrew Kreps]

On Mon, Jan 12, 2009 at 12:46 PM, Daniel M German  wrote:
>
>
> Why don't you use PTblender? it is very good dealing with only 2
> images at a time.
>


Wow, that's even more perfect.  Thank you!

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Image geometry data into EXIF?

[Daniel M German]

 Klaus  twisted the bytes to say:


 >> it puts a full copy of the stitching script in the exif data.

 Klaus> This is more than I thought of, fine by me. However, having followed
 Klaus> the story of some proprietary entries by camera makers a few months
 Klaus> ago, I'd suggest that at least within the panoramic software community
 Klaus> one agrees on some kind of standard.

PTstitcher input format is sort of an standard.

But I agree, having a universal format would be good. Another  question is,
where do we put it? PT put it in the TIFF comment field, and
they do not output JPGs. 

---dmg

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Image geometry data into EXIF?

[Daniel M German]

 Bruno Postle twisted the bytes to say:

 Bruno> On Sat 10-Jan-2009 at 10:09 -0800, Klaus wrote:
 >> 
 >> As I do see a vast majority of panoramic images not being of the 4\pi
 >> or 360 degrees type, information like hfov, projection type, position
 >> of horizon line should allow viewer programmes to properly display the
 >> hugin/enblend output.
 >> 
 >> Is there maybe even a standard way of including such info into EXIF?

 Bruno> Only for rectilinear images, we could add fake focal length and 
 Bruno> sensor size info, but this would be wrong if the image is cropped.

 Bruno> PTmender sort-of does what you want, it puts a full copy of the 
 Bruno> stitching script in the exif data.  We could modify the hugin 
 Bruno> exiftool command to do the same, but currently no tools are able to 
 Bruno> make use of it.

In my opinion the entire script is the best solution with respect to
embedding information about how the stitch is done.

Each of the images that is output by PTmender have this information in
an TIFF field (I don't recall which one, I think it is the TIFF
comment field). The TIFF field that indicates the "page number" and
"total pages" have the corresponding image number from the script. So
you can easily lookup the "i" line that generated that image.

All PT keep the script in the file. This data is lost in JPegs.

--dmg



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Image geometry data into EXIF?

[Daniel M German]

 Klaus  twisted the bytes to say:



 Klaus> Hello all,

 Klaus> With crop lines available in the Stitcher tab making cropping in gimp
 Klaus> less urgent, and EXIF being ported as default from original images, I
 Klaus> want to propose to add image geometry info into the image output as
 Klaus> well.

One thing I have wanted to implement in PTcrop is the ability to
automatically crop the image to remove any area that has no
information. I think Max's PTstitcher implements it already.

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


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Exposure correction for time lapse

[Daniel M German]

 Andrew Kreps twisted the bytes to say:



 Andrew> On Wed, Jan 7, 2009 at 4:28 AM, Bruno Postle  wrote:
 >>> What about the exposure correction available in hugin 0.7? This would do
 >>> just that
 >> 
 >> This also has an equivalent command-line tool called vig_optimize.
 >> 

 Andrew> That sounds very cool, I'll check it out.  I'm guessing hugin would
 Andrew> choke with my dataset as I'm at 28,000 frames currently, and I'm
 Andrew> generating about 1,500 per week.

 Andrew> Thanks again, this list is invaluable!

Why don't you use PTblender? it is very good dealing with only 2
images at a time.


--dmg
 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: segmentation fault when stitching

[Felix Hagemann]

2009/1/12 Lukáš Jirkovský :
> Fortunately someone did more testing on the gcc side
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38625) and the cause was
> found. I'm attaching small patch to configure.in against newest cvs
> which adds necessary flag to CXXFLAGS when compiler is GCC.
> Can someone test it? It's still a little bit hackish, but it works for me.

Works for me. A test case that was segfaulting reproducibly when
compiling without debugging symbols now completes. And four to fives
times faster as well, finallz  making pano stitching and blending fun
again!

Thanks for sorting this out,
Felix

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Community Funding (was Re: *Your* Opinion is requested about Google Summer of Code 2009 and "Community Funding")

[J. Schneider]

Yuval Levy schrieb:
> Hi all again, and thanks for the feedback about this subject.
> 
> First of all thanks to the Mac and Linux users for their display of 
> generosity. Did I miss something, or Windows users were conspicuously 
> absent? with the exception of
So far I was only reading. But not conspicuously.

One thing is that I would happily donate. And if I get a download link 
as "thank you", that's OK for me. On the other hand: If I knew I would 
never get a windows build anymore without donation, it would actually be 
buying, not donating. Nevertheless, for me it's worth it.

A completely different thing is that this is an open source project 
driven by volunteers and volunteers do the work that they choose, of 
course. And if there is no volunteer do to the windows work, then it is 
not done. It's as simple as that. I would find it a pity but I could not 
complain.
Then there is commercial software development and why shouldn't somebody 
do this work for money alongside with all other work he does for a 
living? There is nothing wrong about that.

The arguments Rich brought have to be considered by you developers but 
if you choose to loose some windows users as a trade-off for not having 
to do this particularly complicated and unappealing work, that's your 
decision. And a decision I can understand.
(My guess is that in the long run some windows user who is able to do 
that will step in as it happened with PPC.)

regards
Joachim

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: 0.61 update of Panini perspective tool available

[Bart.van.Andel]

> Aaaarghh!  Mac users are reporting all sorts of problems with cubic
> format, you are not alone...

> But why only on Macs?  And with 3 different video systems at least?

For the record, I don't have a Mac (I only wish I had one, haha). I'm
running WinXP SP3 and just updated my graphic card drivers (ATI Radeon
9600SE) to the newest version. I just installed the drivers, not that
piece of memory consuming bloatware called Catalyst.


> I wouldn't have
> any idea how to set up mapping of multiple texture images onto one
> surface.  If you do know, please tell me.

Well, basically they're just 6 rectangular projections 90 degrees
apart, which shouldn't be too difficult to backproject onto the
panosphere. I guess you're already doing the same thing when loading a
rectangular image?


> Am I safe in assuming that you can display the non-cubic formats OK?

Correct. Only trouble with cubics.


> > I'll see if I can figure out more details later.
>
> Any help you can give would be most welcome.  I am not a Mac developer
> and have no Mac to test on.

Me neither, unfortunately. I've read through the source code a bit and
couldn't find anything wrong there. Moreover, I compared your code to
some of the code available on other websites (by googling), and if not
pretty much an exact copy, it's still fairly the same amount and order
of operations. Strange.

If you look closer at the picture I linked to in my previous post,
it's not only that the same image is shown on every face. It's shown
with a *different* error on every face. The images are shifted in both
X and Y directions (in texture coordinates), and have border issues
which differ from face to face. It popped into my mind that something
might be wrong with texture coordinate generation internally, but this
does not quite explain the cloning behavior.

By the way this is the first time I dive into OpenGL, so don't expect
me doing wonders just yet ;)

Cheers,
Bart
--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: GSoC 2009 (was: *Your* Opinion is requested about Google Summer of Code 2009 and "Community Funding")

[prokoudine]

On Jan 11, 6:20 pm, Yuval Levy  wrote:

> 2007 I was admin and you (Alexandre) were backup admin. 2008 we inverted
> roles. My wish for 2009 is to bring in fresh people. If you want to back
>   the new admin up, I'll gladly take a further step back. I can always
> mentor a student. We need to spread the know-how in the community so
> that others can continue after us.

Well, whatever comes, you can rely on me as either primary or backup
admin.

> I've a son now and I hope he will be applying as a student in 2027 ;-)

:-)

Alexandre
--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: segmentation fault when stitching

[Alex Romosan]

"Lukáš Jirkovský"  writes:

> Fortunately someone did more testing on the gcc side
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38625) and the cause
> was found. I'm attaching small patch to configure.in against newest
> cvs which adds necessary flag to CXXFLAGS when compiler is GCC. Can
> someone test it? It's still a little bit hackish, but it works for
> me.

adding --param inline-unit-growth=60 to g++ compile flags makes
enblend work fine without debugging symbols. thanks for finding this.

--alex--

-- 
| I believe the moment is at hand when, by a paranoiac and active |
|  advance of the mind, it will be possible (simultaneously with  |
|  automatism and other passive states) to systematize confusion  |
|  and thus to help to discredit completely the world of reality. |

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: segmentation fault when stitching

[Kornel Benko]

Am Monday 12 January 2009 schrieb Lukáš Jirkovský:
> Fortunately someone did more testing on the gcc side
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38625) and the cause was
> found. I'm attaching small patch to configure.in against newest cvs
> which adds necessary flag to CXXFLAGS when compiler is GCC.
> Can someone test it? It's still a little bit hackish, but it works for me.


Yes, but it works. I tried some projects, and it did not crash.

Very "nice" bug indeed.

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: segmentation fault when stitching

[Lukáš Jirkovský]

Fortunately someone did more testing on the gcc side
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38625) and the cause was
found. I'm attaching small patch to configure.in against newest cvs
which adds necessary flag to CXXFLAGS when compiler is GCC.
Can someone test it? It's still a little bit hackish, but it works for me.

Regards
Lukas "stativ" Jirkovsky

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

diff -rup -x CVS enblend/configure.in enblend-new/configure.in
--- enblend/configure.in	2008-09-09 07:33:07.0 +0200
+++ enblend-new/configure.in	2009-01-12 11:54:19.0 +0100
@@ -35,6 +35,11 @@ LIBS="${OPENEXR_LIBS} $LIBS"
 CFLAGS="${OPENEXR_CFLAGS} $CFLAGS"
 CXXFLAGS="${OPENEXR_CFLAGS} $CXXFLAGS"
 
+# Add --param inline-unit-growth=60 because otherwise enblend can segfault when compiled with newer gcc versions
+if test "$GXX" = yes ; then
+ CXXFLAGS="--param inline-unit-growth=60 $CXXFLAGS"
+fi
+
 
 # Replaced with custom M4 macros, JD Smith, June, 2007
 #AC_CHECK_LIB(glut,glutInitDisplayMode,,AC_MSG_WARN([GLUT is required to compile enblend.]),[-lGL -lGLU])

[hugin-ptx] Re: Community Funding (was Re: *Your* Opinion is requested about Google Summer of Code 2009 and "Community Funding")

[Rich]

On 2009.01.12. 07:57, Yuval Levy wrote:
...
>  > charging for a new version and keeping the previous one free is not a
>  > good choice, as it would simply slow down the upgrading in the user
>  > community.
> 
> So what? If users are happy with the old version, why waste resources on 
> providing/supporting the new one?

because for an opensource project your users are your only wealth.
project needs users at least as much as users need the project.
users mean testing, marketing, new developers...
having more users on the bleeding edge is best a project can hope for - 
other projects employ various strategies (even trick) to get more 
testing for new versions. working against this will only do harm for the 
project.
that's the broad look on the project. individual contributors can be 
motivated by many different factors.

> Bruno Postle wrote:
>  > I have no objection, supporting Windows is a lot of work.
> 
> Indeed supporting Windows is a lot of work. More ranting on this below.

that's another question. if you feel that your work should be paid for, 
it's your choice.
...
>  > Windows users are also accustomed to get stuff for free
> 
> you mean they don't pay a license fee for Windows?

i'll bite - yes, 95% of them ;>
...
> been there, done that. Click on the thumbnail at 
> 
> 
> This part of the deal was never explicit, but I am sure it helped to get 
> more Ninjas to dole out to every participant to GSoC 2008 (as opposed to 
> just the students and assigned mentors like the previous year). Up to 
> you and the other recipients of Nodal Ninjas to tell if this has been 
> motivation to contribute.

that's very cool. too bad canon, nikon and others aren't following the 
suit (yet) :)
...
> Maintaining Windows or anything for it is no longer fun for me. 
> Especially since I can run all Windows applications I need with Wine. 
> I've done this to learn and understand, and I am ready to move to 
> something else.

i don't think anybody would blame you for stopping this maintenance 
then. it's your time, your call. maybe somebody else just needs the push 
to help in this area :)
...
> Then it is a clear message that there is no need to support Windows. 
> Remember the users' outcry when I questioned whether PowerPC Mac should 
> be maintained? PPC users stepped up to the task and helped themselves.

which would be awesome to happen in this case as well :)
...
> Yuv
-- 
  Rich

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---