Re: [hugin-ptx] How to create lens camera data file ( exif )?

[Carlos Eduardo G. Carvalho (Cartola)]

2013/8/8 Incony <inc...@incony.org>

i want to create the data file that hugin look for. for the camera... so it gets the info needed for remapped pics ( i.e downsized ) 

Hugin tries first to read it from the images, the exif information. Many programs can keep the original exif information when resizing images. On Windows a good free program to do that is XnView, which can work in batch processing as many images as you want at once. I usually recommend the portable version:

http://portableapps.com/apps/graphics_pictures/xnview_portable

Also GIMP and probably Photoshop and Lightroom will also keep exif data.

 

i know the lens data.. for the coolpix 30 m camera..  its 4.7 and 5.53   that info is as close as i can get.. else the fov info.. which is 32.9

#

i can make good pano`s using that info.. but hugin labours because it cant see the exif data... and i cant get hugin to see the camera and lens info before i ask it to make a pano from the downsized ( by half ) images of the originals..

win 7 can only use 3gb of memory  even though i have 5 on the pc..

Win 7 64bits can recognize more than 3GB of memory. Are you using the 32bits one?

 

so.. i cant use 20 pics of nearly 5 mp... hugin just goes awol..

i sue downsized pics,,, remapped pics..

but even though i tell it.. the data... it cycles a lot looking for exif data that i cant give..

how do i get the camera info.. into hugin..? to save me and it time?

Nikon Coolpix.. 20.1 mp camera as close as i can see is , is the s3400  mine says on the came lens - 4.7 - 32.9  and therefore 5.53 is the middle..

but.. what i need is the ability to have all the info available to hugin at start of  pano making..  downsized or not...

what do i do ? step by step?

When hugin doesn't find the info it opens a windows so that you can fill the necessary information, doesn't it? At that time you can either fill it manually or load a saved file. Well, it desn't seem to me that fill that manually takes more time than loading a file, but anyway... you can fill it manually, finish a panorama and save a lens file in the "Camera and Lens" tab by clicking over one image and pressing the corresponding button on the right side(?).

It is better, in my opinion, to save the file after optimizing, so the file will save the lens information already calibrated, but you can also save it right after filling the fields manually.

Another option is to edit the exif information of the files, but I don't know how to make it easily on windows. On Unix systems I could make a script to do that using some program like exiftools to copy the exif information from one file to many others at once. Maybe you can search for something like that for windows. Xnview itself can make many things in batch, maybe it is capable to solve it.

Good luck,

Carlos E G Carvalho (Cartola)
http://cartola.org/360
http://www.panoforum.com.br/

[Frederic Da Vitoria]

2013/8/9 Carlos Eduardo G. Carvalho (Cartola) <cart...@gmail.com>

Exiftools and exiv2 both exist on Windows, I use frequently. I'll post my command line to do just this this evening. The problem is that my command line copies everything, even the picture dimensions, which would be wrong after resizing and maybe would give problems to Hugin. . But I guess there exiftools or exiv2 offer a method to set those parameters correctly.

--
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org

[Frederic Da Vitoria]

2013/8/9 Frederic Da Vitoria <davi...@gmail.com>

Here is the command line I use : exiftool -F -tagsFromFile source_file_name destination_file_name

[Rogier Wolff]

On Fri, Aug 09, 2013 at 12:50:54PM -0300, Carlos Eduardo G. Carvalho (Cartola) wrote:
> 2013/8/8 Incony <inc...@incony.org>

> > win 7 can only use 3gb of memory even though i have 5 on the pc..
> >
>
> Win 7 64bits can recognize more than 3GB of memory. Are you using the
> 32bits one?

I'm not sure how much is true, but someone who knows more about
windows than me (doesn't take much), told me recently that Windows
still always has a 32-bit userspace with a 2G max available memory
for the application. I argued that windows copied the Linux tactic of
doing a 3G/1G split soon after we changed that in Linux.

Roger.


--
** R.E....@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.

[David W. Jones]

On 08/09/2013 07:31 PM, Rogier Wolff wrote:
> On Fri, Aug 09, 2013 at 12:50:54PM -0300, Carlos Eduardo G. Carvalho (Cartola) wrote:
>> 2013/8/8 Incony <inc...@incony.org>
>>> win 7 can only use 3gb of memory even though i have 5 on the pc..
>>
>> Win 7 64bits can recognize more than 3GB of memory. Are you using the
>> 32bits one?
>
> I'm not sure how much is true, but someone who knows more about
> windows than me (doesn't take much), told me recently that Windows
> still always has a 32-bit userspace with a 2G max available memory
> for the application. I argued that windows copied the Linux tactic of
> doing a 3G/1G split soon after we changed that in Linux.

The 32-bit Windows XP system at my office has 4GB memory, of which
~3.5GB is available for use. Has something to do with Windows setting
aside a range of memory for hardware, I think; IIRC, the reserved amount
may be larger, something to do with video hardware?

OP might have 32-bit Win7.

--
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/

[Incony]

Thanks for the replies. the PC is running  an X6800  2.93 dual chip, on 64 bit windows 7 ultimate. on start up the system info ( in the control panel ) window, shows the 5 gig of ram on the board as ok.. and says windows can only use 3  gig of it..  

i see from the web, that - that is a typical response.. for whatever reason i guess i will have to live with it..

i will try and see what i can do about the exif problem..   and how to get the lens info permanently available

 

[David W. Jones]

Good grief! You don't have to "live with it". My desktop (running 64-bit
Aptosid Linux) has 12GB of memory and sees all of it with no problems.

You've probably got enough disk space to install a good Linux distro
alongside your W7 setup, and make full use of the memory you have when
you need it just by booting into Linux instead of W7.

[Markku Kolkka]

10.8.2013 8:31, Rogier Wolff kirjoitti:
> I'm not sure how much is true, but someone who knows more about
> windows than me (doesn't take much), told me recently that Windows
> still always has a 32-bit userspace with a 2G max available memory
> for the application. I argued that windows copied the Linux tactic of
> doing a 3G/1G split soon after we changed that in Linux.

Windows 32-bit uses 2G/2G by default, but there's a switch to use 3G/1G:
http://blogs.technet.com/b/askperf/archive/2007/03/23/memory-management-demystifying-3gb.aspx
Applications need to be linked with a special flag to be able to use the
larger 3G user space.

--
Markku Kolkka
markku...@iki.fi

[Incony]

i have now been able to create the ini file. i used the parameters from the original pics..that have the exif data intact.   those are found in Hugin " Camera and Lens"  and can be saved by clicking save lens   and are then saved as an ini file   ( this was the kind of info i was posting about and wanted step by step info for  :)  )

that ini file can be opened then and edited and saved - so one can change the image size details ..... again the info i wanted to know..

so i now just need to be able to do the same with the image exif data...

ive tried exif.me and xnview... and they show me the exif data  but dont show me how to get that info into the resized images that dont have it... neither can hugin - that i can see..

and that is what hugin does... it says "unable to read exif data from image  blah blah... all the time its aligning the images, even if its got the lens data... 

so... if anyone can show me how to get the exif data, from the original image that i can see.. into the images that dont have it...

i would still like it...  :)

then i can make pano`s without watching hugin tell me line after line of info i already know... but cant change yet.

On Friday, August 9, 2013 4:50:54 PM UTC+1, Cartola wrote:

[Incony]

Photo me http://www.photome.de/home.html can load the exif data from an image and save it, as an exif file. i.e its called   yourimagename.exif.

one can then load an image like a downsized jg without any exif data in it, and then load that saved exif data...from the file  yourimagename.exif   and then save that image,,

it now has exif data on it.. that hugin can read..

its the solution i was looking for...  so now i can create a lens ini file i can use... and put exif data on images that dont have it..

Problem solved  :)   its a little slow to have to load and save the images one at a time.. because photo me cant batch process, but it made hugin faster at dealing with remapped images.

[Frederic Da Vitoria]

Did you try the exiftool command line I mentioned above? Or would you rather avoid command line tools entirely?

2013/8/10 Incony <inc...@incony.org>

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5e67d37b-d0ea-4c53-bd76-35647905c92e%40googlegroups.com?hl=en-US.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Incony]

Thanks Frederic... i am not as sharp with PC`s as i used to be.. i just couldnt see the right things to do.. :)

so.. when i could, using  photo me.. ( point and click ) and sort the lens data file using Hugin... ( point and click )   it was the means i was looking for..  so i havent tried the exiftool at all...

[Frederic Da Vitoria]

2013/8/11 Incony <inc...@incony.org>

OK. It's true I am so used to the command line that I often forget that some users feel quite uncomfortable with it. Plus I use Total Commander instead of the Windows Explorer, and TC allows to easily add any command (even command line) to a kind of contextual menu, which means I currently do this EXIF data copy in three steps: select source file, select destination file, invoke my user-defined command. The only thing I am missing and which I should correct is correcting the image dimensions. There must be an exiftool option to set those values to the actual values. But in your situation, this is unimportant since Hugin seems to work with a full EXIF copy.

[Incony]

I also found a batch resizer on CNET ( that doesnt make you load a mass of advertising gunk and tool bar changes )

http://download.cnet.com/Bulk-Image-Resize-Manager/3000-12511_4-10837108.html

in effect once i have changed the pic size and got the exif info then it gets easier still. since now i just need to put the exif data on each pic that doesnt have it.. 

for me thats about twenty pics for a complete 360 pano..

but i have to say.. Autostich does a very good job..

it made this..http://www.flickr.com/photos/54706462@N04/9486226415/sizes/o/in/photostream/

from the resized pics.. (50 percent resize)