gmane.comp.misc.ptx

Lens calibration for RAW with a JPEG reference

tosca — 2012-05-18T08:40:55

Hi,

I'm new to both the group and Hugin, just trying to calibrate the
'lenses' of a Canon Powershot S100 that are not yet in the LensFun
database; the JPEG files produced by the camera are OK (Canon's job!)
and I would like to use them as references to fix the RAW files
distortion.

I've shooted in RAW+JPEG, converted the RAW to a TIFF file, opened
both TIFF and JPEG files in Hugin, defined the JPEG as the reference
image. Apparently, Hugin automatically finds a lot of corresponding
points in the two images, and that seems fine.
From there, is there a way to tell 'him' to calculate the lens
distorsion parameters, instead of trying to assemble the two pictures
as a pano?

Thanks for your answer.

Something wrong with exif data processing

AlekseyM — 2012-05-18T12:12:26

I checked out Raw Photo Processor (RPP) recently and found that Hugin
cannot understand some of it's exif data. When I try to load the file,
produced by RPP (either tiff or jpeg) it always asks me to enter
multiplier, which on the Lens screen is called "crop factor". When I
convert the same image with Canon DPP, this does not happen. I tried
to evaluate the difference between exif data in the file, produced by
RPP and the one, produced by DPP and was not able to find any clue why
this may happen. There are some differences, but the data is
surprisingly similar. Yet, there is something wrong. I am starting to
think that the problem may be in the way Hugin treats exif data. Any
ideas? Where I can see how this data is processed by Hugin?

Re: Re: GUI overhaul

Drozilla — 2012-05-18T08:23:46

Thanks for pointing this out. That's fine with me. But I would then
completely remove the Optimizer Tab. Right now it seems to pop on and
off in my installation.

Also, there should be a preselection in the GUI, so I can just click
"Calculate".

We can never come up with a GUI that suites everybody. For GUI's it's
important that they remain stable, so people can stay in their workflow.
So we should create a useful GUI and then stick to it.

I'm all in favour of simple/advanced: Normaly I i want to get things
done quickly, and they work. In some occasions a Pano is difficult to
assemble, and then I need all the extra tweaking.

Cheers
Serge

Re: GUI overhaul

kfj — 2012-05-18T05:44:10


One situation where I find I have to work without exposure correction
(beyond merely reading the EXIF data) is when I do takes outdoors with
swiftly moving clouds. They can result in the photometric optimization
going wrong, because the assumption that the same spot in different
images is equally bright doesn't hold anymore. The blender will still
make a good panorama in the end, but with photometric optimization I
sometimes get overexposed bits with weird colours.

Kay

Re: Re: GUI overhaul

Thomas Pryds — 2012-05-18T04:46:24

2012/5/18 Monkey <davidhorman47< at >gmail.com>


I would imagine a number of checkbox switches, one for exposure correction,
one for stacks, one for HDR, etc., instead of the current checkboxes under
"Panorama Outputs" and "Remapped Images" in the Stitcher tab (current
layout; haven't seen the GUI overhaul) to be more intuitive. Just a thought.

Thomas

Re: Re: GUI overhaul

Bruno Postle — 2012-05-17T22:44:11

You don't have to set the Eev to 0, you can set it to 1 or 1000, so 
long as it is the same for all photos.  Eev is a log scale so '0' 
doesn't really mean 'off'.

What would be wrong with setting them to the EXIF exposure values 
rather than calculating them through optimisation?

Re: Re: GUI overhaul

Monkey — 2012-05-17T22:32:27

I shoot on manual and trust my blender to correct any other exposure 
difference (which should be very little), and I think having to reset all 
parameters to 0 to turn it "off" (when in fact it's still *on*, just at 0 
strength, as it were) is pretty convoluted.

A "no exposure correction" option seems very sensible to me - is this 
really something no-one else ever wanted? :S

David

On Thursday, May 17, 2012 11:08:34 PM UTC+1, Bruno Postle wrote:

Re: Re: GUI overhaul

Bruno Postle — 2012-05-17T22:08:34

At the moment you need to reset all photometric parameters in the 
Images tab, then stitch as normal.

What is your objection to the exposure correction?  You don't want 
any exposure correction, even from the EXIF data? or you don't like 
the values that the photometric optimisation comes up with?  
Sometimes the photometric optimiser doesn't work so well, especially 
if the geometric alignment hasn't found a good alignment first - but 
this could be fixed with an extra rule in the assistant.

Re: Re: GUI overhaul

Bruno Postle — 2012-05-17T22:08:28

XYZ is still very unstable, most of the time it goes and does 
something weird.  If you are careful you can get very good results, 
but this does make it 'expert' functionality.

RE: Re: GUI overhaul

Dale Beams — 2012-05-17T13:28:50

XYZ is in a universal language, that of experts, of mathematicians.  It is the language of XYZ that allows us to situate ourselves in a spatial 3d world.




Date: Wed, 16 May 2012 18:47:18 -0700
From: google< at >levy.ch
To: hugin-ptx< at >googlegroups.com
Subject: Re: [hugin-ptx] Re: GUI overhaul



On Tuesday, May 15, 2012 6:58:02 AM UTC-4, Jim Watters wrote:
  
    
  
  
    On 2012-05-14 7:45 PM, Margaret Wong wrote:
    
      
        
          Personally I think of the Assistant as 'beginner', and
          anything to do with bracketing or XYZ mosaics as 'expert',
          i.e. things that should be well hidden unless you go looking
          for them.  Everything else in the GUI is relevant to tweaking
          stuff that happens behind the scenes of the Assistant.
          
            

            
          
        
        

          As a relative beginner I do bracketing and mosaics and did those nearly from day one.  It took me ages to realise that an XYZ mosaic
          wasn't a pano in  str

Re: GUI overhaul

Monkey — 2012-05-17T10:54:12

Hi all,

There is one thing that always annoys me when I use Hugin, and it's this:

http://img716.imageshack.us/img716/9391/stitcher.png

On the stitcher tab, which panorama output option should I tick if I want a 
blended, *not* exposure corrected, low dynamic range panorama?

In fact I think many of these options are pretty confusing, especially to a 
beginner. I usually end up just using the "No exposure correction" for 
remapped images and blending them on the command line.

David

Re: GUI overhaul

Naked Robot — 2012-05-17T06:13:38

hi,

1) agree with jim. replace "beginner" with "simple". and probably 
"advanced" for the second mode, and don't have 3 modes.

2) the one most annoying thing about Hugin is still there: when I 
automatically align the images, it also does photometric correction, and 
then I don't know how to turn it off. With this new design i *really* don't 
know how to turn it off - beginner or advanced, whatever.



On Saturday, May 5, 2012 8:22:04 PM UTC+2, T. Modes wrote:

Re: Re: GUI overhaul

Yuv — 2012-05-17T01:47:18


On Tuesday, May 15, 2012 6:58:02 AM UTC-4, Jim Watters wrote:

I agree with both Margaret and Jim.  The current terminology reflects an 
inward view that has nothing to do with the level of proficiency of the 
user -- neither in terms of computing nor in terms of photography.  It 
draws an arbitrary line in the sand.  Why should XYZ be considered more 
advanced than bracketing?  only because it requires more parameters?  was 
added later?  Added technological complexity?

The current UI simplification is great from an expert perspective and I 
fully agree with Jim's view and support his terminology.  The 
beginner/advanced/expert terminology is misleading.  A real beginner is 
somebody who does not know the strict terms (to paraphrase Margaret) yet.  
For a beginner it does not matter whether the stitch was achieved with 
ypr/XYZ/morph-to-fit (BTW, good stuff, Bruno!) and whether visual 
uniformity was achieved with bracketing/exposure correction/blending.  
Without detracting from the current UI, which I

Re: Re: GUI overhaul

Bruno Postle — 2012-05-16T22:08:10

This is more-or-less how the current version of the gui_overhaul 
looks, though rather than a secondary set of tabs there are 'radio 
button widgets' for the various 'views' of columns.

Re: Panorama Viewer For Android

Bart van Andel — 2012-05-16T09:06:34

Hi Jorge,

I'm not sure why you haven't thought of this, but Flickr really is a good 
source if you need images to experiment with, for instance by searching for 
"equirectangular" (these are spherical images) [0].
Equirectangular images can be converted to cubic faces using e.g. Panotools 
Script [1]. For instructions see [2] (which mentions an older version but 
it still works the same).

Good luck and be sure to post back whenever you have a viewable result.

[0] http://www.flickr.com/search/?q=equirectangular
[1] http://search.cpan.org/~bpostle/Panotools-Script-0.26/
[2] 
http://vinayhacks.blogspot.com/2010/11/converting-equirectangular-panorama-to.html

--
Bart


On Wednesday, May 16, 2012 4:05:25 AM UTC+2, Jorge Luis Iten Júnior wrote:

Re: Re: GUI overhaul

Frederic Da Vitoria — 2012-05-16T09:05:58

2012/5/16 Gnome Nomad <gnomenomad< at >gmail.com>


First, what I am thinking may be completely wrong, I am on Windows, so I
did not see the new GUI.

Sorry, I was not clear, I did not mean tabs down the side (I think you
meant something like vertical :-/ ) I meant tabs within tabs. In the images
tab, on the left a single column list of image names, and in the right part
of the images tab add a sub-tab which would allow to choose the set of
colums. Either Camera and Lens sub-tabs or Camera, Lens and User (the user
could decide his columns in this last tab) When the user selects one (or
several) image name(s), the row(s) would be select in all the sub-tabs.
This way, the user could select on scroll to any image and easily switch
the different column sets.

I hope I am making myself clearer. If I don't, I'll try to draw a mock-up.

OTOH, a tab within a tab may be not quite user-friendly. For example, which
tab set should the Ctrl+Tab shortcut control?

Re: Re: GUI overhaul

Gnome Nomad — 2012-05-16T08:27:47

Well, if it makes sense to have image names on a tab, putting them in a 
column would be fine. I like the tabs across the top, personally, not 
down the side. Of course, that could a user configurable option.

Re: Panorama Viewer For Android

Jorge Luis Iten Júnior — 2012-05-16T02:05:25

Hi all,

Like I told you before, I am working at a panorama viewer for Android.
What I need now, is just a repository or web site where I can found
the images to project. I need cubic and spherycal images.

On 22 mar, 12:47, luca vascon <luca.vas...< at >gmail.com> wrote:

Re: GUI overhaul

Tduell — 2012-05-16T01:43:48


On May 16, 9:45 am, Tduell <tdu...< at >iinet.net.au> wrote:
[snip]

Found it! Photos tab, right click, context menu, Lens > ...

Cheers,
Terry

Re: GUI overhaul

Tduell — 2012-05-15T23:45:19


On May 15, 12:59 pm, Tduell <tdu...< at >iinet.net.au> wrote:
[snip]

This all seems to be working OK now with 5799:686e0c2aaa3e.

I can't find how to add local lens data or lensfun data in the new
gui.
Am I suffering from a form of 'domestic blindness' or is that function
not yet implemented?

Cheers,
Terry

Re: Feature suggestion: "Save Project" per Optimizer iteration

Carlos Eduardo G. Carvalho (Cartola — 2012-05-15T16:07:06

And/or an auto-save. There are some tools, like vi or even office editors
that have a swap file that stores every change. If the program crashes it
can recover from the swap file. Another way to implement would be an option
to save at each defined time, configurable by the user.

Cheers,

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



2012/5/15 Rich MacDonald <macdonald.rich< at >gmail.com>