El domingo, 27 de junio de 2021 a las 11:10:35 UTC+2, [email protected] escribió:
> > There are three things you need to do: > > 1. Disable any photometric optimisation. Set all the photometric > parameters of all your input photos to zero, and the EV of the output > panorama to zero. This will prevent Hugin from trying to 'fix' the > exposure for you. > > 2. Disable blending between photos. In the Stitcher tab, set a blender > command-line option of '-l 0', or just use the 'built-in' blender > option with 'hard-seam' set. This will prevent mixing of colours from > adjacent photos. You will now see a hard-edge between photos in the > stitched output. > > 3. Disable interpolated sampling. In the stitcher tab, remapper > options, set the interpolator to 'Nearest neighbour'. Hugin is usually > averaging several adjacent input pixel values to generate an output > pixel, you don't want this 'anti-aliasing' behavior. The results will > not look as smooth, and arguably you are losing data with 'Nearest > Neighbour', but each output pixel will get its value from a single > input pixel. > > Hi Bruno, thanks you so much for the response! I tried your tips but with no results, hugin still modifying pixels in the false color panorama. Since I'm working without interface (i'm scripting in python through CLI commands) I found some issues: - Once I import any photo Er and Eb photometric parameters are set to 1 automatically. If I try to set it up to 0 with pto_var then nona throw the following exception: [image: 1.JPG] Variables will look like this in the .pto file: *#-hugin cropFactor=1* *i w640 h512 f0 v17 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er0 Eb0 r0 p-0.82153530183907 y-33.6586917800566 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 n"000_encoded.png"* There will be no problem with Er and Eb set to 1 so I think 0 is a not valid value. I'm not using any kind of automatic geometric or photometric optimization, I'm selecting the variables I want to opmitize through pto_var. Could this be causing problems? - I'm using the nona *'--seam=hard'* option in the CLI so I think tip nº2 its working fine. - About the interpolator choice: I can't select the interpolator in CLI command of nona: Even if I do this step in interface, pixels still beeing modified (maybe because of the issue with step 1). Let us know how you get on. When I was (briefly) surveying solar > arrays the drone was using a multi-spectral imaging camera, is your > data converted to RGB? Changing the Hugin stack to work with more than > three channels would be _very_ difficult. > > -- > Bruno Yes, I'm turning the thermal matrix from video frames of SEQ files (FLIR propietary thermal video files) into coded RGB images that i'm stitching. Once I stitch them I retrieve the thermal info back from coded pixels of the panorama. I know I'm losing thermal precision with this technique but its enough to do the job. Thanks in advance! Álvaro. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5a463ee8-5245-4e10-87ad-72adb1a60e42n%40googlegroups.com.
