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

[Jaroslav.Beran]

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 when
> building hugin.
>
> - Gerry
>
>
>
> On Tue, Oct 7, 2008 at 5:46 PM, Yuval Levy <[EMAIL PROTECTED]> wrote:
>
> > 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 read them - I've tried to open the
> > files you posted earlier and it prompts me to enter HFOV and Focal
> > Length as well.
>
> > Yuv- Skrýt citovaný text -
>
> - Zobrazit citovaný text -
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

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

[Jaroslav.Beran]

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 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 read them - I've tried to open the
> files you posted earlier and it prompts me to enter HFOV and Focal
> Length as well.
>
> Yuv
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

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

[Gerry Patterson]

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 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 read them - I've tried to open the
> files you posted earlier and it prompts me to enter HFOV and Focal
> Length as well.
>
> Yuv
>
> >
>

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.7.0 released

[Yuval Levy]

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 
> early merge of the gsoc integration branch into the trunk. Once the 
> remaining projects are ready for a merge, they can be merged into the 
> trunk directly.

each project's circumstances are unique, waiting for all of them to be 
ready for a big bang is IMO not very sensible.

let's release every time a bunch of features becomes somewhat usable / 
integrated so to get more user feedback on the way to robustness.

specifically, the fast preview and the batch processor have already been 
integrated in gsoc2008_integration, and will go into 0.8.0alpha1 if 
nobody disagrees.

Celeste is next in line. Tim has been working hard hard lately with help 
from Harry, trying to fix a weird behavior in OSX GUI.

for the last two projects I have not seen much from Fahim and Onur after 
GSoC ended. The circumstances are different too.

Fahim / Masking in GUI: we need to think how it will fit in the overall 
hugin process, while Fahim's project still need some fine tuning too 
according to him.

Onur / Feature Matching is a quite complex project. the parts need to be 
pulled together with Zoran's last year project. still a lot of work 
before anything can be integrated.

Yuv


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.7.0 released

[Yuval Levy]

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 conflicts.

done (on my local machine for now - I am testing the build before 
committing).

there was only one file with a conflict, an xrc file (sorry I no longer 
recall which, but if it is important I'll grab that piece of information).

will commit later if the build does not return strange things.

Yuv



--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

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

[Yuval Levy]

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
> there was a pre-release "translation freeze" in effect.  So it has
> only been tested on Win32, but as it works just like several other
> options I would expect no platform dependence.
> 
> I suppose applying that patch to 0.7.0 would be violating some other
> release regulation; but I am going to do it for my personal builds
> (both Windows and Linux) because I have little use or admiration for
> exiftool.

now that 0.7.0 is released, trunk is in a state of flux again. I'd say:
go ahead and commit the patch.

also for the future I would suggest branching out release branches (like
has been done now with release-0.7.0) rather than freezing trunk. Trunk
should live on.

Yuv

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

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

[Yuval Levy]

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 read them - I've tried to open the 
files you posted earlier and it prompts me to enter HFOV and Focal 
Length as well.

Yuv

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: license of m4 files

[Bruno Postle]

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 in the next enblend release.

>[1] http://code.google.com/p/autoconf-gl-macros/

Hi Sebastian, can you add this to the enblend tracker on 
sourceforge?

http://sourceforge.net/projects/enblend

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.7.0 released

[Bruno Postle]

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/final.  I didn't copy the trunk as there have 
been some (minor) changes to the trunk since the rc6/final release.

>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 conflicts.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.7.0 released

[Pablo d'Angelo]

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 objections?
> 
> ciao
>   Pablo
> 
> 
> 
> Hi all,
> 
> I haven't been watching the GSOC integration branch very much.  Have all 
> of the projects been merged in?

No, only the OpenGL preview and the batch stitching functionality is in 
the GSOC integration branch.

>  At one point I thought the plan was to 
> merge all of the projects into a single branch, get everything (or most 
> everything) working then merge it wholesale into the trunk.

The most important reason was that integration could start while the 
last changes for the 0.7 release were made. Having all projects in there 
before the next release series 0.8 would be one possibility, but I fear 
it would introduce some delays.

 > 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 
early merge of the gsoc integration branch into the trunk. Once the 
remaining projects are ready for a merge, they can be merged into the 
trunk directly.

ciao
   Pablo

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.7.0 released

[Gerry Patterson]

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 GSOC integration branch very much.  Have all of
the projects been merged in?  At one point I thought the plan was to merge
all of the projects into a single branch, get everything (or most
everything) working then merge it wholesale into the trunk.  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.

Best Regards,

- Gerry

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.7.0 released

[Pablo d'Angelo]

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, so 
I didn't have the time to really contribute to hugins development lately.

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.

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

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: license of m4 files

[Sebastian Harl]

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
>   @license AllPermissive
> 
> Could you please clarify the license of those files? Currently, they are
> non-redistributable, as that right is not explicitly granted to the user
> ("AllPermissive" could be basically anything). If you don't really care
> about any specific license, please use any of the well known and GPL
> compatible licenses like LGPL, GPL or the (three clause) BSD license to
> avoid license conflicts.

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 in the next enblend release.

TIA,
Sebastian

[1] http://code.google.com/p/autoconf-gl-macros/

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature

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

[Sebastian Harl]

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 enblend is released under the GNU Free
Documentation License (without invariant sections - which is an
important detail in Debian as it would else be considered non-free). I'd
assume that enfuse-focus-stacking is supposed to be released under that
license as well but this has to be specified in the .text / .info files.
I'd really appreciate if you would clarify that.

Thanks a lot in advance!

Cheers,
Sebastian

PS: As a side-note: To cleanly apply the GNU FDL to some piece of text,
the license requires you to add a copyright and license notice as
specified in section "How to use this License for your documents" of
the license. When you're at it, it would be nice if you'd add that
as well.

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature

[hugin-ptx] license of m4 files

[Sebastian Harl]

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, they are
non-redistributable, as that right is not explicitly granted to the user
("AllPermissive" could be basically anything). If you don't really care
about any specific license, please use any of the well known and GPL
compatible licenses like LGPL, GPL or the (three clause) BSD license to
avoid license conflicts.

See m4/acx_pthread.m4 for a nice example.

Thanks a lot in advance!

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature

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

[alexpg]

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-12, at 12:18, [EMAIL PROTECTED] wrote:
>
>
>
> > Harry,
>
> > I get the wxExecute Error message when running the Create Control  
> > points with RC5. Looking back, RC4 works for me.  All three of the  
> > selected control point plug-ins appear to go through their paces but  
> > result in this same error. The error message pops up when they are  
> > complete. I notice the following console log messages appear just  
> > after pressing the Create control points button:
>
> > ERROR: 22:04:32.284773 (/Users/Shared/development/hugin_related/
> > hugin/mac/../src/hugin1/base_wx/platform.cpp:214)  
> > MacGetPathToBundledExecutableFile(): Mac: Cannot locate the file in  
> > the bundle.
> > ERROR: 22:04:32.285338 (/Users/Shared/development/hugin_related/
> > hugin/mac/../src/hugin1/base_wx/platform.cpp:179)  
> > MacGetPathToBundledResourceFile(): Mac: Cannot locate the file in  
> > bundle.
> > ERROR: 22:04:32.286057 (/Users/Shared/development/hugin_related/
> > hugin/mac/../src/hugin1/base_wx/platform.cpp:179)  
> > MacGetPathToBundledResourceFile(): Mac: Cannot locate the file in  
> > bundle.
>
> > I assume this is related. The /Users/Shared/development/
> > hugin_related/ folder is not present on my machine. I suspect  
> > something is hard coded to this path on your machine.
>
> > Allan
>
> > On Sep 6, 2008, at 6:25 AM, Harry van der Wolf wrote:
>
> >> Hi Mac users,
>
> >> I just published the RC5plus bundle. I named it RC5 plus as it  
> >> contains an extra patch. wxMac on PPC somehow fails to notify  the  
> >> end of the launched stitcher process. Ippei programmed a workaround  
> >> for that. It is currently really a workaround as it now only checks  
> >> whether the process has finished. It doesn't check whether it was  
> >> successful or not.
>
> >> Information and binaries via my website
> >>  >> >.
> >> (The binaries itself are, as always, served from  
> >> hugin.panotools.org who kindly provide the disk space and bandwidth).
>
> >> Hoi Harry
>
> --
>   ->> 鵜飼 一平  (UKAI Ippei) -
>MSN & AIM: [EMAIL PROTECTED]   Skype: ippei_ukai
>Homepage:  http://homepage.mac.com/ippei_ukai/

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---