[hugin-ptx] Re: Could not decode image (JPEG)

Just curious, and trying to pinpoint the problem. Could you try saving/ converting those images as TIFF first, before loading them in Hugin? As you mentioned, there might be something wrong with loading JPGs with Hugin on your computer, but does loading TIFF work? If not, Exif might not be the pro

[hugin-ptx] autopano maxdim setting

i have done a small bit of playing around with the maxdim value of autopano in the past. it seems this has an effect on not just the amount of time it takes to load images and complete control point creation, but also on the quality of the stitching, sometimes adversely. is there there an 'optim

[hugin-ptx] Re: Request For Comments: hugin 0.8.0 release cycle

On Wed, Oct 8, 2008 at 7:13 PM, Yuval Levy <[EMAIL PROTECTED]> wrote: > > EXPERIMENTAL FEATURE RELEASES > > I intend to release a windows binary installer of the > gsoc2008_integration branch soon. If there are no objections I'll call > it 0.8.0alpha1. > > in its current state it includes fast pre

[hugin-ptx] Request For Comments: hugin 0.8.0 release cycle

there have been some off-list mails about the next releases going around. My reply to those mails was to lay down my intentions - something I do here publicly with a request for comments. I would like to see the hugin project move to frequent incremental releases. I would like to see the new f

[hugin-ptx] Re: Could not decode image (JPEG)

I'd like to use the workaround > Field Of View : 47.3 deg > Focal Length: 6.8 mm (35 mm equivalent: 41.1 mm) as a work around, enter these values when asked. but as I can't open the images (Hugin just says "Could not decode image"), I have no chance to enter

[hugin-ptx] Re: Could not decode image (JPEG)

Jaroslav.Beran wrote: > Am I doing it the wrong way? no, you are doing it the same way I do that with the images you posted a couple of days ago, with the same version of hugin you are using. I am at loss explaining what is specifically wrong in the chain of events on your computer. on my com

[hugin-ptx] Re: Could not decode image (JPEG)

Yuv, on the first tab of new project (called "Assistant") there is a button "Load images..." I click the button, select images, click "Open", and then the message "Could not decode image" appears. Am I doing it the wrong way? Jarda On 9 Říj, 00:03, Yuval Levy <[EMAIL PROTECTED]> wrote: > Jarosl

[hugin-ptx] Re: Could not decode image (JPEG)

Jaroslav.Beran wrote: > but as I can't open the images (Hugin just says "Could not decode > image"), I have no chance to enter the values :( note that hugin *opens* project files, not images. Images are added to a project. what are you doing to "open" the images? Yuv --~--~-~--~~--

[hugin-ptx] Re: Could not decode image (JPEG)

Jaroslav.Beran wrote: > But it is obvious from the mere fact, that on Linux and > Apple the files can be opened, that the problem is system dependent. > But that's everything I can deduce. So if any more experienced user > can get closer to the solution, I will be very glad... I could open the fi

[hugin-ptx] Re: Smartblend: Potential use with Hugin

I just adapted Bob's bash script into a Windows batch file, for usage with Windows 2000 and up. Save the script at the end of this post to a file named "smartblend-hugin.bat" and store it in the folder where smartblend was installed. Usage: 1. Start Hugin. 2. Open File -> preferences. 3. Sw

[hugin-ptx] nona -r hdr creates INF pixels

Hi, [ Andrew, I'm Ccing you because I don't know if you're on the list ] first of all, thanks for the great tool (hugin). But I've run into a problem I can't solve. When I try to create hdr panorama with hugin, some areas looks like [1]. The red areas actually represents pixels with infinite val

[hugin-ptx] Re: hugin-0.7.0 released

PS having generated control points with an earlier version of Hugin I was able to save the project file and then open it in the current, released version. It then performed a stitch as expected producing a resulting file that I was happy with.However ... it ended the stitching process with

[hugin-ptx] Re: Could not decode image (JPEG)

Yes, I know - Field of view can me computed from chip diagonal and focus length. But I think, that this is not the case. If Hugin can't decode image, it can't recognize it as JPEG (but other apps do). So - there must be something wrong with HUGIN installation (missing component or premise). Logica

[hugin-ptx] Re: hugin-0.7.0 released

Ippei, Harry, I have just tried Ippei's new release. I installed it on my PowerMac G5 machine. I also installed your new Autopano-SIFT-C plug-in replacing the previous one in "Application Support" I opened a recent project and tried using Autopano-SIFT-C to generate a few control points ... th

[hugin-ptx] Re: gsoc2008_integration merged into trunk

Pablo dAngelo wrote: > Hi all, > > I have just merged the gsoc2008_integration branch into the trunk. thanks. this is where I left it yesterday. I took a larger chunk to bite than I can chew :-) Yuv --~--~-~--~~~-

[hugin-ptx] gsoc2008_integration merged into trunk

Hi all, I have just merged the gsoc2008_integration branch into the trunk. This means that: * OpenGL Preview and Batch Processor are in the trunk * The gsoc2008_integration branch is obselete, and should not be used for future development. * The Sky identification, control point matching and m

[hugin-ptx] Re: Could not decode image (JPEG)

> I tried to find a file "exiv*.*" on my computer, but there is none... You won't find or need such a file unless you are building from source. Upon compiling, it is integrated into the program. "FieldOfView" doesn't seem to be a real tag in the Exif specification by the way; it can't be found i

[hugin-ptx] Re: license of enfuse-focus-stacking.{texi,info}

Hi Chris, On Wed, Oct 08, 2008 at 12:25:48AM -0700, cspiel wrote: > Sebastian Harl wrote: > The file will (probably) be superseded in the next version of > Enblend/Enfuse by a complete rewrite of the Enblend and Enfuse > manual pages. In fact, there will be a "Reference- and User-Guide" >

[hugin-ptx] Re: license of m4 files

Hi, On Tue, Oct 07, 2008 at 11:06:25PM +0100, Bruno Postle wrote: > On Tue 07-Oct-2008 at 18:40 +0200, Sebastian Harl wrote: > >In a private response, Braden pointed me to [1] which includes new > >versions of those macros that are licensed under the GPL2 + autoconf > >macro exception (just like a

[hugin-ptx] Re: hugin-0.7.0 released

Deal all, now that we have a release, I would like to express my sincere thanks to Pablo and the team for making it all possible. Hugin is an integral part of my photography now; I couldn't do without it. As my contribution, I have now published a sequence of articles in a Royal Photog

[hugin-ptx] Control Points between Images of Various Resolution

Hi, first of all I am working on stitching together a very huge piece of image (20-30 pieces of ranging resolution images up to 3000x2500). When setting control points manually, I realize that it would be much more accurate if one could zoom in on only a single image and set the control point. The

[hugin-ptx] Control Points between Images of Various Resolution

Hi, first of all I am working on stitching together a very huge piece of image (20-30 pieces of ranging resolution images up to 3000x2500). When setting control points manually, I realize that it would be much more accurate if one could zoom in on only a single image and set the control point. The

[hugin-ptx] Control points for different image resolutions

Hi, first of all I am working on stitching together a very huge piece of image (20-30 pieces of ranging resolution images up to 3000x2500). When setting control points manually, I realize that it would be much more accurate if one could zoom in on only a single image and set the control point. The

[hugin-ptx] Control Points: Various resolutions

Hi, first of all I am working on stitching together a very huge piece of image (20-30 pieces of ranging resolution images up to 3000x2500). When setting control points manually, I realize that it would be much more accurate if one could zoom in on only a single image and set the control point. The

[hugin-ptx] Re: license of enfuse-focus-stacking.{texi,info}

Sebastian - Sebastian Harl wrote: > The files doc/enfuse-focus-stacking.{texi,info} in enblend do not > contain any license information but a copyright holder > (Dr. Christoph L. Spiel) only. This, again, makes enblend > non-redistributable as we're missing any terms of use, > redistribution, et