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

I tried to find a file "exiv*.*" on my computer, but there is none... Jarda On 8 Říj, 05:50, "Gerry Patterson" <[EMAIL PROTECTED]> wrote: > Hello, > > I haven't looked yet, but it may be a lack of support in the metadata > handling library: exiv2.  I am not sure what version people are using whe

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

Yes, but to enter these values, I have to open the images first :/ Really looks like some important component (dll or something) is missing... Jarda On 8 Říj, 00:46, Yuval Levy <[EMAIL PROTECTED]> wrote: > Jaroslav.Beran wrote: > > Well, here is exiftool output for the first image > > thanks. It

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

Hello, I haven't looked yet, but it may be a lack of support in the metadata handling library: exiv2. I am not sure what version people are using when building hugin. - Gerry On Tue, Oct 7, 2008 at 5:46 PM, Yuval Levy <[EMAIL PROTECTED]> wrote: > > Jaroslav.Beran wrote: > > Well, here is exif

[hugin-ptx] Re: hugin-0.7.0 released

Pablo d'Angelo wrote: > > It does not >> matter much to me if the GSOC projects are brought now or when the >> integration branch is finished. I just don't want to lose track of >> where the up to date changes are. > > To avoid delays and expose the new functionality earlier, I'd favor an >

[hugin-ptx] Re: hugin-0.7.0 released

Bruno Postle wrote: > On Tue 07-Oct-2008 at 20:54 +0200, Pablo d'Angelo wrote: >> We could then merge the gsoc_integration branch into the trunk and >> contine developing the new functionality for the 0.8 release. > > Makes sense to me, who wants to do this? Probably there will be > some confl

[hugin-ptx] exiftool option (was Re: [hugin-ptx] Re: hugin-0.7.0 released)

Tom Sharpless wrote: > One way to deal with exiftool problems is to not use exiftool. > > Some time ago I put a patch on the hugin tracker that makes running > exiftool an option in the preferences tab. I was told I couldn't > commit because it would introduce a UI label needing translation, and

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

Jaroslav.Beran wrote: > Well, here is exiftool output for the first image thanks. It looks OK. > 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. I am puzzled as to why hugin can't

[hugin-ptx] Re: license of m4 files

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 acx_pthread.m4). It would be nice if you >would include the new versions

[hugin-ptx] Re: hugin-0.7.0 released

On Tue 07-Oct-2008 at 20:54 +0200, Pablo d'Angelo wrote: > >As for the further development, I agree with Garry that we should do an >svn cp hutin/trunk hugin/branches/release-0.7.0 >to create a stable branch, which could be used for urgent bugfixes, >should the need occur. Ok, done based on rc6/

[hugin-ptx] Re: hugin-0.7.0 released

Gerry Patterson wrote: > On Tue, Oct 7, 2008 at 1:54 PM, Pablo d'Angelo <[EMAIL PROTECTED] > > wrote: > > > > > We could then merge the gsoc_integration branch into the trunk and > contine developing the new functionality for the 0.8 release. > > Any obj

[hugin-ptx] Re: hugin-0.7.0 released

On Tue, Oct 7, 2008 at 1:54 PM, Pablo d'Angelo <[EMAIL PROTECTED]> wrote: > > > > We could then merge the gsoc_integration branch into the trunk and > contine developing the new functionality for the 0.8 release. > > Any objections? > > ciao >Pablo > > > Hi all, I haven't been watching the GS

[hugin-ptx] Re: hugin-0.7.0 released

Hi Bruno, Bruno Postle wrote: > Congratulations to everyone responsible for this release! Thanks a lot for doing the final hard work for making the release possible. Also thanks to all other developers who made this happen. I have been very busy with day time work and other commitments lately

[hugin-ptx] Re: license of m4 files

Hi again, On Tue, Oct 07, 2008 at 02:47:01PM +0200, Sebastian Harl wrote: > Some of the m4 files shipped with enblend (e.g. m4/ax_check_gl.m4) are > shipped with a note like this: > > @category InstalledPackages > @author Braden McDaniel <[EMAIL PROTECTED]> > @version 2004-11-15 > @licens

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

Hi again, 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, etc. All other documentation in enble

[hugin-ptx] license of m4 files

Hi, Some of the m4 files shipped with enblend (e.g. m4/ax_check_gl.m4) are shipped with a note like this: @category InstalledPackages @author Braden McDaniel <[EMAIL PROTECTED]> @version 2004-11-15 @license AllPermissive Could you please clarify the license of those files? Currently, the

[hugin-ptx] wxExecute Error at Create Control Points 0.7.0

I'm getting errors too. http://aglassman.com/hugin/ and click on the jpgs. On Sep 12, 6:22 am, Ippei UKAI <[EMAIL PROTECTED]> wrote: > Those 'error' messages probably have nothing to do with the problem. > Those are debug messages wrongly tagged as error. I'll fix that. > > Ippei > > On 2008-09-1