[hugin-ptx] Source: the problem that causes endless filenames

[Abrimaal]

fused_layers.executor 
Line 24:
Result=%prefix%_blended_fused.tif

blended_stacks.executor
Line 24:
Result=%prefix%_fused.tif

Could you change these lines to single letter _b and _f
Result=%prefix%_b.tif
Result=%prefix%_f.tif 

or allow user defined suffixes (as variables).
When merging images muliple times, to get the best results, we get such 
names as

20231204_0749_blended_fused_blended_fused_fused_fused_blended_fused 

I used Bulk Rename Utility command line, 
to shorten _blended_fused to _b and _fused to _f, but passing through all 
drives and folders could take weeks. 
and it did not change the filenames in .pto files.
Better to correct this in the source.

Thanks in advance

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e07be008-7cc8-462e-a818-91e3f748f4c4n%40googlegroups.com.

[hugin-ptx] Shorten filenames generated by Hugin and its components

[Abrimaal]

If replacing _blended_fused and _fused to _b and _f is impossible in the 
software code,
I am trying to write a command line cleaner for Hugin files.
Go from the base folder, through all subfolders,
1. Delete all *.mk and *.log files
2. Rename all _blended_fused in filenames to _b
3. Rename all _fused in filenames to _f

The start folder is E:\foto

:STARTER
E:
set folder=foto
set foldercurrent=%folder%

:MAINLOOP
CD foldercurrent

goto SUBFOLDERCHECK

:CLEANER
if exist *.mk del *.mk
if exist *.log del *.log

:FINDER
if exist *.jpg CALL :RENAMER
if exist *.png CALL :RENAMER
if exist *.tif CALL :RENAMER
if exist *.pto CALL :RENAMER & CALL :INFILEREPLACE
REM rename other software files corresponding with images, one example below
if exist *.mch CALL :RENAMER

GOTO MAINLOOP

REM  subs =

:SUBFOLDERCHECK
REM find the deepest subfolder
? if subfolder not exists goto :CLEANER
? set subfolder=subfolder name
cd subfolder
set foldercurrent=%foldercurrent%\%subfolder%
REM I completely do not know how to write this part
REM if there are many nested subfolders
REM after getting to the deepest subfolder
goto CLEANER
REM then move back to the base folder
REM and open the next subfolder
REM to check if all folders were processed, then exit the script
cls & echo ALL FILES PROCESSED & pause & exit /b


:RENAMER
set filename=%~nI
? if %filename% contains _blended_fused replace with _b
? if %filename% contains _fused replace with _f
REM by the way replace Windows file numbering 
[space][bracket]number[bracket] with _number
? if %filename% contains characters %20( replace with _
? if %filename% contains character ) remove from filename
REM replace unwanted characters
? if %filename% contains character . replace with _
? if %filename% contains character ~ replace with -
? if %filename% contains UTF character replace with basic letter
? build a filenamenew
ren filename filenamenew
exit /b

:INFILEREPLACE
REM panoramas may be built from other panoramas
notepad.exe filename
? if not exist _blended_fused in pto file exit /b
? if not exist _fused in pto file exit /b
? replace all _blended_fused with _b
? replace all _fused with _f
exit /b

--

Variant 2 - use Windows search in the base folder
call Windows Search for *_blended_fused and rename the first file,
call Search again, if no more *_blended_fused, search for *_fused and rename
?

---
Variant 3 - use an external batch rename app and in-file word replace, 
called with parameters from command line
?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/fb06f1bc-2e27-4617-ac6e-02f4cd45427dn%40googlegroups.com.

[hugin-ptx] Re: Hugin 2021.0.0 released

[Abrimaal]

Thanks a lot for the option to 
*Ignore the color spaces* (profiles)
The ICC profiles were relicts of misunderstanding between human eyes 
(everyone sees different colors) 
and imperfections of machine sensors.
This useful option will save a lot of time, drive space and abusing inhuman 
words. 

Thanks for horizontal line detector, as well.

Happy New Year :)

[image: Commodore64_palette.png]

On Thursday, December 30, 2021 at 10:42:13 AM UTC+1 T. Modes wrote:

> Hi all,
>
> today we are releasing Hugin 2021.0.0 
>
> Source tarball can be downloaded
> at sourceforge: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2021.0/hugin-2021.0.0.tar.bz2/download
>
> Verify its checksums:
> md5:
> 166a8e795548cec566a06db38f0ed664  hugin-2021.0.0.tar.bz2
> sha1:
> bd0ffdd70d47ae6c6723c5b3225ddce56595ebc1  hugin-2021.0.0.tar.bz2
>
> This is a source code release. 
> Users communities produce executables for their respective platforms. 
> Please announce them here.
>
> (The 2021.0 release correspond to changeset 52df0f76c700 in our 
> repository, which is also tagged as 2021.0.0).
>
> Changes since 2021.0 rc1
> * Only the release date has been updated in the appdata files
> * No changes to source code or build system.
>
> Changes since 2021.0 beta 1
> * Updates several translations
> * Fixes possible crash in autocrop algorithm when using extreme large 
> canvas size
>
> Changes since 2020.0
> * Fast preview window can be panned in zoomed state with middle mouse 
> button.
> * New overview mode: inside panorama sphere (similar to a interactive 
> panorama viewer)
> * Updated build system for OpenEXR3.
> * Several bug fixes.
>
> Upgrading from previous versions of Hugin should be seamless. If you do 
> have problems with old settings, these can be reset in the Preferences 
> window by clicking 'Load defaults'.
>
> Please test and report bug/issues to mailing list or bug tracker 
> https://bugs.launchpad.net/hugin 
>
> The release notes can now also be found at http://hugin.sourceforge.net/
> releases/2021.0.0/
>
> Windows binaries (64 bit) can be found at sourceforge: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2021.0/Hugin-2021.0.0-win64.msi/download
> (It contains also libpano13-2.9.21, which was released today)
>
> MD5 checksum
> 1c79c2a20cf427d1153788c7012aa77e *Hugin-2021.0.0-win64.msi
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4fd5a421-d120-4f5b-b76e-2a44cbeaec4bn%40googlegroups.com.

[hugin-ptx] Inaccurate cropping. Request for planar mode and keyboard shortcut.

[Abrimaal]

Selective blending of variants of the same image. All images are the same 
size.

I do:
Load images, set projection to reclilinear, reset positions.
No control points, no calculations, no alignment.
Selective masking out and in.
Saving new versions by blending stacks.
Stitcher -> Calculate size -> Calculate crop -> Save a few new variants.

Then again, blending the best version with the base image (or another 
version)
I want to change lens, all images to Lens 0
Hugin says:* impossible*!
Why?
The saved image is 1 pixel taller than the original.

How could it happen?
Hugin as panorama maker, calculates everything, angles, field of view, 
automatic crop, instead just reading the data, when no transformations, 
remapping was done.
Hugin doesn't know if we loaded partial images to make a panorama
or variants of the same image for selective blending.

This is my request, because Hugin is a multipurpose tool for almost all 
transformations of graphics.
Could you introduce a *Keyboard shortcut* for planar mode?
For example *R *or Ctrl+R or a definable key.

Pressing the key will do:

Projection = rectilinear
Reset positions (center all images)
Reset lenses and photometric parameters (optionally, because sometimes we 
change the parameters manually, especially exposure for better results)
Ignore field of view
Ignore color profiles
Image size to save is not calculated, it is exactly the size of the image 
selected as 
*position anchor*or if undefined, the output size is the size of the 
largest image.

Now what if? The images differ by size, but all are the same area (field of 
view), because these are variants of the same).
I often use mobile photo enhancers such as Colorize, Remini, FaceApp to 
improve images.
Sometimes the images are saved with different sizes - Remini upsizes to 
enhance details, some other apps may downsize a little. 
Sometimes they are saved (without asking the user) with different color 
profiles.

This is why the planar mode will ignore lenses, sizes, color profiles.
This improvement will open new horizons.

A few years I requested *single image straightening*, 
you introduced it and it works perfectly.



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6dcf5c96-8d99-4ac4-8299-7e85581cbd3dn%40googlegroups.com.

Re: [hugin-ptx] Re: Errors building latest hugin default source

[Abrimaal]

Hi Luís Henrique,

It is possible in Hugin to merge (overlay, collage) various image formats 
(jpg, png, tif...), various sizes and even various origins (digital photo + 
scanned negative + screenshot + rendered graphics).
It seems almost impossible to hear, like adding centimeters to inches, 
euros to dollars, water to oil... and this is possible in Hugin.
Color spaces / profiles are just special effects, like adding milimeters to 
kilometers, seconds to days. These milimeters change statistics, but are 
invisible for someone who runs long distance (long time) projects.

I consider this as the main error in the program, that there is no *ignore 
*button 
when opening (or *ignore color profiles *option in settings).
Image editing software often apply color profiles without asking. Even the 
developers are not aware of this, when using ready libraries. 
It refers mainly to mobile apps, but not only. I use Machinery HDR Editor 
for improving image quality. It applies an exotic "Black scaled" color 
profile, without asking.
Images processed (protected?) this way cannot be merged with other images 
in Hugin. 
The original photo + processed photo cannot be opened by Hugin for 
selective blending of both.
More... even when two editors are using *different versions* of the same 
color profile, Hugin GUI does not allow to open them.
More... even when the version number in one image is *2.1* and in another 
image is *2_1* they cannot be opened.
This is like adding lightyears to milimeters (converting thousands of 
images, video frames and screenshots may take longer than blending them).

And the second place is (the main error no 2):
After "Image was not found, please manually select the correct image" and 
pressing Cancel or [X]
the project is *closed* automatically.
The missing image was deleted years ago, because of low quality.
I need to open the project with all remaining images.
After deleting the line in a text editor, that refers to the missing image, 
Hugin opens the project and *everything is working*. :)

[image: hugin_expects_to_convert_almost_a_million_images.png]


On Saturday, April 3, 2021 at 5:10:34 PM UTC+2 Luís Henrique Camargo Quiroz 
wrote:

>
>Hi Abrimaal,
>
>Just to tell that I use a color calibrated monitor, and also have 
> calibrated a few other monitors (none of them CTRs), and I know by 
> experience that color management *and* color profiles do make a big 
> difference!
>Some pointers: hardware like the Datacolor Spyder5EXPRESS 
> <https://www.amazon.com/Datacolor-Spyder5EXPRESS-Designed-Hobbyist-Photographers/dp/B00UBSL2TO/ref=sr_1_8?crid=2KJZ29NDJAWOF=1=spyder+5+express=1617461371=spyder+5%2Caps%2C305=8-8>,
>  
> and software as DisplayCAL <https://displaycal.net/> and ArgyllCMS 
> <https://www.argyllcms.com/>. Even my former (satellite) TV provider 
> offered, as a paid service, the color calibration of digital TV sets. 
>
>And now I have found some links which I will see myself in order to 
> better understand all this :)  
>
> https://www.khanacademy.org/computing/pixar/color/color-101/v/color-science-1
>https://en.wikipedia.org/wiki/Color_management
>
>   
>
>
>
>
>
> Em sex., 2 de abr. de 2021 às 19:07, Abrimaal  escreveu:
>
>> Color profiles "I will not pass" - it seems to be a cardinal error. Now 
>> not only in .jpg, it also appears in .tif images.
>> All these color profiles were developed in the times of CRT monitors and 
>> early digital cameras, that had problems with displaying proper colours, 
>> especially blue tones.
>> Today all images can be stitched, taking no care for the profiles, just 
>> ignoring them. 
>> There is no difference if we disable color management in the monitors, 
>> graphic cards and applications. We see the real colors as the camera 
>> registered them.
>>
>> Hugin may display a warning and continue to work ignoring these profiles.
>> The simplest way will be to disable profile detection when loading images 
>> (activate the warning at user`s request and risk).
>> On Monday, March 8, 2021 at 11:06:15 PM UTC+1 Tduell wrote:
>>
>>> On Mon, 2021-03-08 at 08:31 -0800, T. Modes wrote: 
>>> > 
>>> > Tduell schrieb am Montag, 8. März 2021 um 03:43:25 UTC+1: 
>>> > > Attached is a partial listing of the rpmbuild output showing the 
>>> initial 
>>> > > error 
>>> > > messages. 
>>> > 
>>> > This is a bug in wxWidgets, which is already fixed: 
>>> > 
>>> https://github.com/wxWidgets/wxWidgets/commit/b4aaa1003247535675f21b69cf800353012ca81c
>>>  
>>> > I pushed a workaround to the repository. 
>>> > 
>>>
>>> Thank y

Re: [hugin-ptx] Re: Errors building latest hugin default source

[Abrimaal]

Color profiles "I will not pass" - it seems to be a cardinal error. Now not 
only in .jpg, it also appears in .tif images.
All these color profiles were developed in the times of CRT monitors and 
early digital cameras, that had problems with displaying proper colours, 
especially blue tones.
Today all images can be stitched, taking no care for the profiles, just 
ignoring them. 
There is no difference if we disable color management in the monitors, 
graphic cards and applications. We see the real colors as the camera 
registered them.

Hugin may display a warning and continue to work ignoring these profiles.
The simplest way will be to disable profile detection when loading images 
(activate the warning at user`s request and risk).
On Monday, March 8, 2021 at 11:06:15 PM UTC+1 Tduell wrote:

> On Mon, 2021-03-08 at 08:31 -0800, T. Modes wrote:
> > 
> > Tduell schrieb am Montag, 8. März 2021 um 03:43:25 UTC+1:
> > > Attached is a partial listing of the rpmbuild output showing the 
> initial
> > > error
> > > messages.
> > 
> > This is a bug in wxWidgets, which is already fixed: 
> > 
> https://github.com/wxWidgets/wxWidgets/commit/b4aaa1003247535675f21b69cf800353012ca81c
> > I pushed a workaround to the repository.
> > 
>
> Thank you Thomas.
> It builds OK now.
>
> Cheers,
> -- 
> Terry Duell 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4027abf1-10d9-4507-b576-d1ad31653604n%40googlegroups.com.

Re: [hugin-ptx] Exposure anchor - how to work with it?

[Abrimaal]

"Edit message?" option unavailable. 
I finally forgot to ask:
When making panoramas from stacks of HDR images 
should I use exposure correction or reset all photometric parameters before 
stitching?
because after exposure correction all images look the same.



On Saturday, February 27, 2021 at 4:24:22 PM UTC+1 Abrimaal wrote:

> I think I understand it, although not everything.
> Sometimes panoramas (especially taken in HDR - stacks of 3 photos with 
> various exposures) look like this - there are lighter and darker areas in 
> the sky at the stitching edges.
> I think it may be a result of taking HDR photos from the hand, every photo 
> is a little moved. (I use don't align stacks).
> But the same panorama from the basic photos (the first exposure only, 
> without the stacks) looks a lot better.
>
>  [image: 20180406_1028_c0274-ph-12_fd-sma.jpg]
>
> On Saturday, February 13, 2021 at 10:00:37 AM UTC+1 bruno...@gmail.com 
> wrote:
>
>>
>>
>> On 13 February 2021 00:28:54 GMT, Abrimaal wrote: 
>> >I have made thousands of panoramas and I still don't understand how the 
>> > 
>> >selector "anchor this image for exposure" works. 
>>
>> The anchor image retains the Ev exposure value during optimisation. A 
>> good anchor image has few 'blown-out' overexposed areas. 
>>
>> What you are noticing is that Hugin also has a project-wide Ev setting, 
>> which the assistant automatically sets to the average of all the photos in 
>> the project, so your anchor image may look different in the output because 
>> this average looks at all photos together. 
>>
>> You can change this global Ev in the panorama tab of the fast preview: 
>> set it to the same value as the anchor, and the anchor will have no 
>> exposure adjustment; there is also a reset to average button; and + - 
>> buttons that raise lower the global Ev by ⅓ of a stop to brighten/darken 
>> your final panorama. 
>>
>> -- 
>> Bruno 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ca3f33b4-fd69-4586-af05-3f8cd770a249n%40googlegroups.com.

[hugin-ptx] Remove color ICC profile info from .jpg files (batch edit)

[Abrimaal]

Recently I was editing EXIF data of a .jpg file for the first time, because 
I had to change the date.
If Hugin still takes so much care for color space and it will not pass, 
even if I beg (there is no "open anyway").
I think about batch removing the color space from a few hundred thousands 
of .jpg files. 
Does any software exist?

I think the info is stored in this line, but not all images contain it. 

[image: ICC_profile.png]

Who created these profiles that all refer to camera errors? The only 
acceptable color profile is "reality", all the other profiles are based on 
camera misintepretation of real world colors.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/661a73ed-4688-45a4-aae6-e6fff85c5d62n%40googlegroups.com.

Re: [hugin-ptx] [Request]: Resolve confusion between "Distance" and "Correlation"

[Abrimaal]

"Fine tune all points" is usable. I often make two versions of the same 
panorama, with and without Fine tune.
It is often visible on the preview, that the panorama layout changes after 
fine tuning.
When adding control points manually, a human selects the most sharp edges 
and the highest contrasts.
The detector (I think) compares blocks X × Y pixels, this is why these 
points look misplaced.
The similarity is very low.

The image is an example, that points 5, 7, 8, 10, 11 are auto-detected, 
where a human would never place control points.
Points 9, 12, 13 are added manually and fine tuned.
After deletion of the misplaced points 5, 7, 8 the final result may be much 
better.
It would be much better if "Fine tune all points" automatically removed 
points with low correlation.
Correlation is similarity, and it is not related to distance (in pixels).

By the way, this is an analogue scan, the result may differ from digital 
photos.
The points could be placed on dust :)
[image: misplaced control points.jpg] 





On Tuesday, February 9, 2021 at 5:11:31 AM UTC+1 Groogle wrote:

> On Monday, 8 February 2021 at 21:28:45 -0600, dgjohnston wrote:
> > Before I use hugin I usually use DxO PhotoLab to correct for lens
> > and camera body distortion.
>
> Yes, I do that too.
>
> > Does anyone know if DxO uses the Brown-Conrady lens model for their
> > routines or anything similar?
>
> The DxO developers will know. Why don't you ask a question of
> support?
>
> Greg
> --
> Sent from my desktop computer.
> Finger groo...@gmail.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/945f95c1-1922-4281-bc79-4b6dbc8fad01n%40googlegroups.com.

Re: [hugin-ptx] [Feature request]: Circle brush eraser for control points

[Abrimaal]

Yes, we the photographers and graphic artist work and think in graphic 
mode, while the programmers work with numbers.
This causes a lot of misunderstanding between the developers "it is 
working" and the users "it is missing".
Initially Hugin was intended to be a graphic editor, dedicated for 
photographers. 
Now, if you want to create a perfect panorama, you need to type a lot of 
numbers. 
For people who work with graphics, even such option as "rotate by 270°" may 
be not understood. 
We rotate left or right moving the cursor. (this applies to a different 
editor).

How many years I am begging for introducing graphic sliders to correct 
vertical and horizontal compression 
of the panorama previews. 
Or just dark editor background than makes possible to work with night 
photos. 
"For you can work with numbers" - this is the usual response.
So, we can forget about a graphic eraser and similar improvements,
such as exposure and color correction using sliders, scale and rotate 
images in graphic mode.
Numeric values may be used for very precise work, with single pixels.
Am I right or wrong?
Masks are the best example how simple is the work in graphic mode. 
I understand that it was not easy for the programmer.



On Monday, February 1, 2021 at 2:41:02 AM UTC+1 ChameleonScales wrote:

> I've only done python code so far and have zero C++ knowledge.
> But if someone knows how to do it but needs the funding I can help with 
> that.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5a41d1c9-5771-4378-9e4a-8fa1245b0120n%40googlegroups.com.

Re: [hugin-ptx] Does anyone have any image sets, particularly ones that don't blend well, that they could share for testing purposes?

[Abrimaal]

Yes, sure. These are only 3 images. You are great if you find control 
points on the *white background* *of Hugin*.
Normally, when viewing in full screen I see where I should add the points. 

https://www.mediafire.com/file/j6q7l01z8gb3d7g/20210127+fullmoon.7z/file
On Tuesday, January 26, 2021 at 3:48:49 PM UTC+1 Monkey wrote:

> Hi Laurent,
>
> Those sound ideal, especially if they exhibit change in lighting or 
> exposure. Loss of contrast is one of my remaining problems with Multiblend 
> so even well-matched images will be useful for that, and if the panos are 
> big that will help test caching.
>
> On Tuesday, 26 January 2021 at 04:47:43 UTC Laurent E wrote:
>
>> Hi Monkey,
>> I'm finishing a virtual tour that includes 8 street-art flat panoramas. 
>> Some are 30 meters wide.
>> Is it the kind of pano you're looking for?
>>
>> On Tuesday, January 26, 2021 at 5:13:22 AM UTC+7 Monkey wrote:
>>
>>> Perfect, thanks!
>>>
>>> On Monday, 25 January 2021 at 20:35:45 UTC Donald Johnston wrote:
>>>
 Hi Monkey … these are links to some file sets I have on Sync.com.  Let 
 me know if they are useful.

 https://ln2.sync.com/dl/f27685a80/392a24qm-7uudw2mp-4vzsr5eg-qaj852qx
 https://ln2.sync.com/dl/310817b80/vxegvztw-7ixx2fqu-8q5h6kr8-8g7789m8
 https://ln2.sync.com/dl/380fc1290/x63ceeax-pnft3mpd-fhub63bd-gcasikxn
 https://ln2.sync.com/dl/b7d757380/68iyddwc-puc3yr7d-exqjavjv-mpmg4rnh

 Don Johnston


 On Jan 25, 2021, at 12:08 PM, Monkey  wrote:

 I'm making a new version of Multiblend but I don't have a lot of 
 panoramas/mosaics to test it with. Does anyone have any image sets they 
 could share, perhaps via Google Drive, particularly ones which have proven 
 problematic to blend together?

 360s x 180s, gigapixels, planar mosaics and such would also all be 
 good, but I'm mainly looking for the kind of "Automatic" mosaics that show 
 wide variations in white balance, exposure, and focus, or ones where there 
 is minimal overlap between images.

 I just need JPEG sets, plus a PTO file if you happen to have one.

 I won't share results with anyone except the uploader, unless 
 explicitly given permission to do so.

 Thanks in advance!

 -- 
 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/28763516-6521-4f7a-890e-5f3392eb846an%40googlegroups.com
  
 
 .




-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ce80d423-bc15-4c06-8dfe-057baa51ada5n%40googlegroups.com.

Re: [hugin-ptx] Hugin 2020.0 beta 1 release

[Abrimaal]

No changes since 2017. I am so sorry. I see it will be easier for me to buy 
5 new hard drives, convert about a million photos to .png and continue the 
work.
What does the sequence -ca-pah-2s_fd-cp-ph2c_bf-h-mk-b mean?
This is the order of edits of a single photo. The photo has been processed 
in various software, Hugin, android apps, PC apps.
If a photo is bad, no color space can help. Who cares of color space? 

On Sunday, November 1, 2020 at 3:04:43 AM UTC+1 Groogle wrote:

> On Sunday, 25 October 2020 at 1:58:55 -0700, T. Modes wrote:
> > Hi all,
> >
> > today we are releasing beta 1 of Hugin 2020.0.0
> >
> > Source tarball can be downloaded
> > at sourceforge:
> > 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2020.0/hugin-2020.0_beta1.tar.bz2/download
> > or at launchpad:
> > 
> https://launchpad.net/hugin/2020.0/2020.0beta1/+download/hugin-2020.0_beta1.tar.bz2
>
> A FreeBSD package is available at
> http://www.lemis.com/pkg/hugin-2020.0.txz . I won't be committing the
> port to the repository, because it will go away "soon".
>
> Greg
> --
> Sent from my desktop computer.
> Finger groo...@gmail.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/835689af-b292-4323-a745-86d6346ccb70n%40googlegroups.com.

Re: [hugin-ptx] Unsupported file format | Could not decode image

[Abrimaal]

 It was strange that Windows (or any other system) allowed to use "*" in a 
folder name. Even if the folder was imported from a 1980s computer ;) 
Well, work with a computer is not writing poetry.
The best to use only the standarized 26 letters and digits. We really do 
not need any other characters than a-z, A-Z, 0-9 and separators - _
Do not use C:\Users for any important files, such as program configuration 
settings. 
The user folder is a system workspace, where everything can be modified, 
overwritten or deleted by Windows. 
Much better to save program configurations in the program main folder. 
This way we can use more than one instances of the same program, each of 
them configured for different tasks.



On Saturday, November 28, 2020 at 3:13:28 PM UTC+1 colou...@gmail.com wrote:

> Thank you Gunter, yes i figured it out, the folder name had an '*' , 
> removed it and i was able to import them.
>
> Problem solved, i am trying to change the subject line.
>
> Regards,
> Anoop
> On Saturday, 28 November, 2020 at 7:14:20 pm UTC+5:30 
> gunter.ko...@gmail.com wrote:
>
>> If you are using windows you might be in that weird situation that you 
>> don't see non-ascii characters in the path to your files: "Documents" for 
>> example is shorthand for "C:\users\(your username)\(the translation of " 
>> documents" into your system language).
>> Also the temp directory temporary files are stored in might be in a 
>> similar path - even if that pathname is never shown.
>>
>> Might that be the case, this time?
>>
>> Kind regards,
>>
>> Gunter.
>>
>>
>> On November 28, 2020 1:03:49 PM GMT+01:00, Anoop Bhaskar <
>> colou...@gmail.com> wrote:
>>>
>>> Greetings all,
>>>
>>> I am really new with Hugin.
>>>
>>> I want to stitch 26 images to form a 360 panorama or an equirectangular 
>>> image, but i am not able to load the images as it is not able to decode.
>>>
>>> When googled it said that it might be because of non latin characters, 
>>> but all the files are in latin script. 
>>>
>>> The images are from DJI, i have edited them on lightroom and converted 
>>> them to jpg.
>>>
>>> Has anyone faced a similar issue?
>>>
>>> Thank you,
>>> Anoop
>>>
>>>
>> -- 
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/bca25f7f-3e3e-48fc-afbf-d928e5cf539cn%40googlegroups.com.

[hugin-ptx] Re: Greetings and hello!

[Abrimaal]

Yes, you can, but the problem is in projections. 
Instead of such presets as "equirectangular, architectural, mercator, 
cylindrical" I would make two sliders for proportional vertical 
compression. 
One slider for tops, the other one for bottoms, with "stop" points at these 
presets.

The cylindrical projection uses no vertical compression, the other 
projections bend the tops and bottoms, proportionally,  but often one 
projection is "too much" while the other is "too little" compressed.
This reply is rather to the developers, to allow to modify the vertical and 
horizontal compression in graphic mode.
It can be useful also for art creators, to extend the compression sliders 
beyond the natural limits of cylindrical projection -  to stretch the sky 
or ground and create an impression of distance.

On Thursday, November 12, 2020 at 8:55:14 PM UTC+1 1sold...@gmail.com wrote:

> Is there a way to stitch together vertical panoramas using hugin? I've 
> checked out other applications that can do so, Lightroom, etc., but can't 
> seem to find any helpful information regarding hugin. Also, I'm using 
> Darktable 3.0.
>
> Thanks for any assistance.
> ~
> EM
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/69895fd6-cf26-428d-a8ca-68b3fdd10af6n%40googlegroups.com.

[hugin-ptx] Re: Fixing seams with control points

[Abrimaal]

This is common with multiplane panoramas. You can delete control points at 
the bottom and optimize (or align) again. 
The objects closer to the camera are sharper, this is why the detector 
mainly places control points on the objects near you. 
No worries, you can delete all points on trees and rocks. Even if they are 
not aligned, the stitcher will blend them. Nobody will count leaves on 
trees and cracks on the rocks :)
For you the most important is the horizon and the objects in the middle. 

If you want to make your work easier, add exclude masks on the bottoms 
before searching for control points, 
Then select "remove control points in masks", and remove the masks.
You should see if there are any important objects at the bottom - 
buildings, towers etc.  that could be duplicated or hidden on the panorama. 
For these objects, add one or two control points manually. 

Take care to rotate the camera only around its axis, this is very important 
for multiplane panoramas. 

 [image: multiplane.jpg]



On Wednesday, November 11, 2020 at 7:38:13 PM UTC+1 Peter wrote:

> Hello! I'm new to Hugin so apologies if I'm missing something obvious. I 
> also searched around the group here but couldn't find a post covering this 
> issue, but may have missed it.
>
> I'm trying to fix a seam in one of my panoramas. While the foreground and 
> background generally seem to line up, there is a bridge in the middle that 
> always seems to be misaligned. I've tried adding more and more control 
> points along the bridge, as well as running and not running the various 
> stitch and align commands in the program incase I was accidentally 
> overwriting something, but while the bridge seam has changed a little bit 
> with each run, it still doesn't seem to be any closer to lining up. Perhaps 
> there is some obvious step I am missing? I was also wondering if there is a 
> way to give certain control points more priority or weight? Or should I be 
> removing some of the automatically generated ones to compensate? Thank you!
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f7ebe225-245d-4b94-be0e-29cf5cd949b9n%40googlegroups.com.

[hugin-ptx] Re: Shorten filename suffixes without recompiling Hugin

[Abrimaal]

No, certainly not this way. Simple replacing *blended_fused* and 
*fused_blended* to *bf* and *fd* 
and adding 11 random characters does nothing, the output suffixes are still 
the same.
So, temporarily I give in searching for another method.

[image: output_bf_bitmap12345678901.png]
[image: output_bf12345678901.png]
On Tuesday, October 13, 2020 at 6:10:31 AM UTC+2 Abrimaal wrote:

> First maybe without the source code if I need to install almost a new 
> system to change one constant.
>
> I have searched for "_blended_fused" string in the *hugin_version_number\bin 
> *folder
> It occurs only twice in *hugin.exe*, in lines 9757 and 9759. No 
> occurences in other files. (if not encoded in UTF-16, because I have no 
> editor to search for text in UTF-16) 
> *output_blended_fused_bitmap* and a sequence of NUL (zeros)
> The same for _fused, two occurences in the same lines, but it is not just 
> _*fused 
> *but *_fused_blended*
> *output_fused_blended_bitmap* and a sequence of zeros.
>
> Now I am unsure if these strings are responsible for generating filenames
> or they are parts of GUI, the displayed text in menu
> or they are internal labels of the program. 
>
> *blended_fused* contains 13 characters. If I replace them with two 
> character *bf* and add 11 zeros after 
> *_bitmap *to preserve relative offsets and the total length of the file 
> will remain unchanged.
> Is there a chance to work?
> This way I modified displayed text in games and other .exe files and they 
> work. 
>
> I used the alternative that you suggested, to rename files after the fact. 
> Using 
> *Bulk Rename Utility *that changed thousands of _blended_fused and _fused 
> suffiixed to _bf and _fd, but...
> these files are often included in projects, such as video slideshows, 
> batch photo post-processing
> or just refining the panorama in Hugin by masking and merging both images 
> into one.
> The filenames remain in projects and the project files become useless 
> after renaming.
>
> I am interested how to customize the executor. In Hugin settings there is 
> no such option. I can define only the main filename, not suffixes.
>
> On Friday, October 9, 2020 at 11:45:40 PM UTC+2 Anaglyphic wrote:
>
>> Hi. COVID sucks, I have a half hour to kill. Here's a small novel.
>> 
>>
>> Yes. Both. Yes. Sure, skip down / skim, or just read it.
>>
>> Assuming you extracted the hugin source thusly?
>>
>> D:\code\hugin\hugin-2019.2.0> grep -RHEn "(_blended_fused|_fused)" * 
>>
>> StitchingExecutor.cpp:697:const wxString 
>> fusedExposureLayersFilename(prefix + wxT("_blended_fused.") + 
>> opts.outputImageType);
>> StitchingExecutor.cpp:738:const wxString 
>> fusedStacksFilename(prefix + wxT("_fused.") + opts.outputImageType);
>>
>> Just change the text in the quotes to "_bf" and "_fd" and compile. Doing 
>> it this way will change it so any reference by any of the multiple programs 
>> that make up hugin will use your truncated names, and nothing will break or 
>> require hand-editing to fix. (Note this is not what you should be doing, 
>> but that is what you asked for.) You'll need to install a LOT of tools, 
>> first of all even grep is not part of Windows by default. There's no unix 
>> dev environment by default. You can enable the Windows Subsystem for Linux 
>> (WSL) if you want to get that going, but you'll still need a full GNU dev 
>> environment and all the prerequisites installed and properly configured.
>>
>> Don't take this the wrong way, you were trying to hexedit the precompiled 
>> binary of an open-source project to change it, so this is might be a long 
>> road for you for something simple.
>>
>> I'd suggest 2 alternatives. 1) Just write a batch file to rename the 
>> files after-the-fact, or 2) customize an executor so you can make your own 
>> output filenames, that's what most of us do.
>>
>> Let me outline an example:
>>
>> Go into Program Files\Hugin\share\hugin\data, pick the one you have the 
>> problem with _blended_fused, which is fused_layers.executor. Copy that to 
>> something else, abri_fused_layers.executor then edit it. (use something 
>> that understands unix line endings like notepad++ / bluefish / brackets / 
>> even wordpad) Change the Description= and Help= lines, to make it something 
>> unique, now go down to the Result line and change it to read something like 
>> Result=%prefix%_bf.tif
>>
>> That's it. Save and exit. Now load up an already-optimized and 
>> ready-to-stitch .pto file in hugin gui, click Output / User

[hugin-ptx] Re: Shorten filename suffixes without recompiling Hugin

[Abrimaal]

First maybe without the source code if I need to install almost a new 
system to change one constant.

I have searched for "_blended_fused" string in the *hugin_version_number\bin 
*folder
It occurs only twice in *hugin.exe*, in lines 9757 and 9759. No occurences 
in other files. (if not encoded in UTF-16, because I have no editor to 
search for text in UTF-16) 
*output_blended_fused_bitmap* and a sequence of NUL (zeros)
The same for _fused, two occurences in the same lines, but it is not just 
_*fused 
*but *_fused_blended*
*output_fused_blended_bitmap* and a sequence of zeros.

Now I am unsure if these strings are responsible for generating filenames
or they are parts of GUI, the displayed text in menu
or they are internal labels of the program. 

*blended_fused* contains 13 characters. If I replace them with two 
character *bf* and add 11 zeros after 
*_bitmap *to preserve relative offsets and the total length of the file 
will remain unchanged.
Is there a chance to work?
This way I modified displayed text in games and other .exe files and they 
work. 

I used the alternative that you suggested, to rename files after the fact. 
Using 
*Bulk Rename Utility *that changed thousands of _blended_fused and _fused 
suffiixed to _bf and _fd, but...
these files are often included in projects, such as video slideshows, batch 
photo post-processing
or just refining the panorama in Hugin by masking and merging both images 
into one.
The filenames remain in projects and the project files become useless after 
renaming.

I am interested how to customize the executor. In Hugin settings there is 
no such option. I can define only the main filename, not suffixes.

On Friday, October 9, 2020 at 11:45:40 PM UTC+2 Anaglyphic wrote:

> Hi. COVID sucks, I have a half hour to kill. Here's a small novel.
> 
>
> Yes. Both. Yes. Sure, skip down / skim, or just read it.
>
> Assuming you extracted the hugin source thusly?
>
> D:\code\hugin\hugin-2019.2.0> grep -RHEn "(_blended_fused|_fused)" * 
>
> StitchingExecutor.cpp:697:const wxString 
> fusedExposureLayersFilename(prefix + wxT("_blended_fused.") + 
> opts.outputImageType);
> StitchingExecutor.cpp:738:const wxString 
> fusedStacksFilename(prefix + wxT("_fused.") + opts.outputImageType);
>
> Just change the text in the quotes to "_bf" and "_fd" and compile. Doing 
> it this way will change it so any reference by any of the multiple programs 
> that make up hugin will use your truncated names, and nothing will break or 
> require hand-editing to fix. (Note this is not what you should be doing, 
> but that is what you asked for.) You'll need to install a LOT of tools, 
> first of all even grep is not part of Windows by default. There's no unix 
> dev environment by default. You can enable the Windows Subsystem for Linux 
> (WSL) if you want to get that going, but you'll still need a full GNU dev 
> environment and all the prerequisites installed and properly configured.
>
> Don't take this the wrong way, you were trying to hexedit the precompiled 
> binary of an open-source project to change it, so this is might be a long 
> road for you for something simple.
>
> I'd suggest 2 alternatives. 1) Just write a batch file to rename the files 
> after-the-fact, or 2) customize an executor so you can make your own output 
> filenames, that's what most of us do.
>
> Let me outline an example:
>
> Go into Program Files\Hugin\share\hugin\data, pick the one you have the 
> problem with _blended_fused, which is fused_layers.executor. Copy that to 
> something else, abri_fused_layers.executor then edit it. (use something 
> that understands unix line endings like notepad++ / bluefish / brackets / 
> even wordpad) Change the Description= and Help= lines, to make it something 
> unique, now go down to the Result line and change it to read something like 
> Result=%prefix%_bf.tif
>
> That's it. Save and exit. Now load up an already-optimized and 
> ready-to-stitch .pto file in hugin gui, click Output / User defined output 
> sequences / and the Description you chose. Boom, there it goes. And there 
> goes your intermediate files being named what you wanted. You can make as 
> many of these as you need, every scenario every file type, there's enough 
> examples in that directory for you to customize anything you want, and 
> again, no recompiling required. You could make your own assistant if you 
> chose to.
>
> I'm not sure if there's a default one that you can change the executor of 
> that will change the hugin GUI so that when clicking the Stitch! button 
> with fused and blend settings, it'll use your modified version, or if 
> you'll need to recompile for that. But this here will get you going.
>
> Have a great day.

[hugin-ptx] Re: The math is perfect ...

[Abrimaal]

> Can Hugin’s GUI style be influenced by your operating 
system’s settings? 
No, the Windows colour scheme is set to dark. Dark grey, with white text. 
Hugin UI remains white. 
I was searching in Windows settings and asked the Windows help community 
(waiting for response)
if I can force-apply the system colour scheme to software that don't follow 
the system settings.



On Monday, October 5, 2020 at 9:08:13 AM UTC+2 Torsten Bronger wrote:

> Hallöchen!
>
> Abrimaal writes:
>
> > [...]
> >
> > The dark background is just a modification of the image above, but
> > we really need it to be introduced. Those who work in an office
> > will never understand it.
>
> [To those who didn’t get it like me at first: The problem discussed
> by the Abrimaal is the difficulty to set control points if the GUI
> is bright and the image is dark.]
>
> @Abrimaal: Can Hugin’s GUI style be influenced by your operating
> system’s settings?
>
> Tschö,
> Torsten.
>
> -- 
> Torsten Bronger
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8efbbcb1-7340-4a9d-b685-13948f00d57dn%40googlegroups.com.

Re: [hugin-ptx] Making panoramas in Pano Editor instead of Align button

[Abrimaal]

Edit: 
*Straighten *adjusts the positions to "as taken with camera", not to the 
vertical lines
*Optimize *after Straighten restores the geometry based on vertical lines - 
but not always it works. I think the optimizer at the first run does not 
know what to optimize. First it must be selected what - positions only, 
positions and view, barrel, etc.
*Align *button builds the panorama again. I think it doesn't add new 
control points and lines, but it changes photometric parameters.
In settings there are optional steps what should be done. There is no 
"adjust photometry" or "skip photometry adjustment". I think it should be 
included in Optional Steps.
So, only *Reset photometric* parameters or* Reset user defined* (exposure 
and/or color) is usable.

On Sunday, October 4, 2020 at 4:41:32 PM UTC+2 Abrimaal wrote:

> Yes. *Straighten* adjusts the vertical geometry. *Optimize* not always. 
>
> One more question related to the position:
> If I select "align this image for position", does it mean that
> - the selected image is centered (y,p,r = 0) before all calculations?
> or
> - the selected image position is random, as loaded and the position must 
> be reset manually?
> On Wednesday, September 16, 2020 at 6:19:01 AM UTC+2 GnomeNomad wrote:
>
>> On 9/15/20 12:11 PM, Abrimaal wrote: 
>> > I always pressed "Align" after loading all images. Align also affects 
>> > photometrics, so I try to make a panorama using the Editor only. 
>>
>> Hmm, I presume you're talking about the button in the Assistant? You 
>> could still use Align there, then reset the photometric optimizations in 
>> the main Hugin window. 
>>
>> > What step have I skipped? 
>> > 
>> > 1. Mark the middle image "for position" 
>> > 2. Find control points + Celeste and vertical lines 
>> > 3. Fine tune all points 
>> > 4. Calculate and optimize 
>> > a. positions from anchor 
>> > b. positions and view 
>> > c. everything 
>> > 
>> > The image is still not straight. 
>> > I checked all vertical lines, removed the short and misplaced lines, 
>> > added a few new. 
>> > I clicked "reset positions" and "optimize" again and the result is the 
>> same. 
>>
>> In the Fast Preview window, under the Move/Drag tab, there's a 
>> Straighten button. Does that help? 
>>
>> > What step of "Align" have I skipped that the vertical geometry is not 
>> > optimized? 
>>
>> Only thing I see missing from the above is to clean control points? Not 
>> remove them, clean them. That always helps mine by removing ones that 
>> seem to be way off or mismatched. I do that step after optimizing 
>> positions from anchor (your 4.a). Or is that what you mean by "Fine tune 
>> all points". 
>>
>> And as someone else on the list asked, what projection are you using? 
>>
>> -- 
>> David W. Jones 
>> gnome...@gmail.com 
>> wandering the landscape of god 
>> http://dancingtreefrog.com 
>> My password is the last 8 digits of π. 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d4ad23e9-7df0-4354-add9-f398d75cf4bcn%40googlegroups.com.

Re: [hugin-ptx] Making panoramas in Pano Editor instead of Align button

[Abrimaal]

Yes. *Straighten* adjusts the vertical geometry. *Optimize* not always. 

One more question related to the position:
If I select "align this image for position", does it mean that
- the selected image is centered (y,p,r = 0) before all calculations?
or
- the selected image position is random, as loaded and the position must be 
reset manually?
On Wednesday, September 16, 2020 at 6:19:01 AM UTC+2 GnomeNomad wrote:

> On 9/15/20 12:11 PM, Abrimaal wrote:
> > I always pressed "Align" after loading all images. Align also affects 
> > photometrics, so I try to make a panorama using the Editor only.
>
> Hmm, I presume you're talking about the button in the Assistant? You 
> could still use Align there, then reset the photometric optimizations in 
> the main Hugin window.
>
> > What step have I skipped?
> > 
> > 1. Mark the middle image "for position"
> > 2. Find control points + Celeste and vertical lines
> > 3. Fine tune all points
> > 4. Calculate and optimize
> > a. positions from anchor
> > b. positions and view
> > c. everything
> > 
> > The image is still not straight.
> > I checked all vertical lines, removed the short and misplaced lines, 
> > added a few new.
> > I clicked "reset positions" and "optimize" again and the result is the 
> same.
>
> In the Fast Preview window, under the Move/Drag tab, there's a 
> Straighten button. Does that help?
>
> > What step of "Align" have I skipped that the vertical geometry is not 
> > optimized?
>
> Only thing I see missing from the above is to clean control points? Not 
> remove them, clean them. That always helps mine by removing ones that 
> seem to be way off or mismatched. I do that step after optimizing 
> positions from anchor (your 4.a). Or is that what you mean by "Fine tune 
> all points".
>
> And as someone else on the list asked, what projection are you using?
>
> -- 
> David W. Jones
> gnome...@gmail.com
> wandering the landscape of god
> http://dancingtreefrog.com
> My password is the last 8 digits of π.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9599d523-7943-47b7-ae62-508738361c8cn%40googlegroups.com.

[hugin-ptx] Making panoramas in Pano Editor instead of Align button

[Abrimaal]

I always pressed "Align" after loading all images. Align also affects 
photometrics, so I try to make a panorama using the Editor only.

What step have I skipped?

1. Mark the middle image "for position"
2. Find control points + Celeste and vertical lines
3. Fine tune all points
4. Calculate and optimize
a. positions from anchor
b. positions and view
c. everything

The image is still not straight. 
I checked all vertical lines, removed the short and misplaced lines, added 
a few new. 
I clicked "reset positions" and "optimize" again and the result is the same.

What step of "Align" have I skipped that the vertical geometry is not 
optimized? 

[image: 202009_stough_using_pano_editor_instead_of_align.jpg] 







-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3edf8242-0efd-4e54-8b0f-5194910ea938n%40googlegroups.com.

[hugin-ptx] Re: Shorten filename suffixes without recompiling Hugin

[Abrimaal]

Are the suffixes generated by hugin.exe or one of the co-apps?
I could try to recomplile from source, just tell me in which file are the 
suffixes defined.

On Thursday, September 10, 2020 at 12:46:40 AM UTC+2 Abrimaal wrote:

> What files should I modify to shorten the _blended_fused and _fused 
> suffixes to *_bf *and *_fd* ? 
> Multiple stitching of panoramas and making collages creates extremely long 
> filenames. 
>
> Then automatic renaming that obviously doesn't rename contents of .pto 
> files, if a file with _blended_fused suffix is added to a new .pto project 
> file
>
> I already tried, but there are too many blended_fused strings only in the 
> main .exe file.
> So I don't know which of them are responsible for filename suffixes, which 
> of them may be labels, variables or commands.
>
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2bdf82ad-f723-4119-98bf-7ac6f81b7b9fn%40googlegroups.com.

[hugin-ptx] Shorten filename suffixes without recompiling Hugin

[Abrimaal]

What files should I modify to shorten the _blended_fused and _fused 
suffixes to *_bf *and *_fd* ? 
Multiple stitching of panoramas and making collages creates extremely long 
filenames. 

Then automatic renaming that obviously doesn't rename contents of .pto 
files, if a file with _blended_fused suffix is added to a new .pto project 
file

I already tried, but there are too many blended_fused strings only in the 
main .exe file.
So I don't know which of them are responsible for filename suffixes, which 
of them may be labels, variables or commands.



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0c03f635-fba5-4e29-beaa-86441605357fn%40googlegroups.com.

Re: [hugin-ptx] Is there a technical term for a tilt all around the panorama?

[Abrimaal]

Some 3D objects editors use both X,Y,Z translation and X,Y,Z rotation. 
Translation is by pixels, cm or other units, rotation is by degrees.

On Monday, May 25, 2020 at 4:39:53 PM UTC+2, Donald Johnston wrote:
>
> X Y Z is just translation without any pitch, roll, yaw. After a 
> translation the camera is still pointing along the same parallel path. 
>
> D Johnston
> On May 25, 2020, at 2:25 a.m., Abrimaal > 
> wrote:
>>
>> Why not X,Y,Z? Before using Hugin I did not know what yawn meant.
>>
>> On Monday, May 25, 2020 at 6:54:01 AM UTC+2, GnomeNomad wrote:
>>>
>>> In the "yaw, pitch, roll" world, wouldn't this be pitch? 
>>>
>>> On 5/24/20 4:59 PM, Donald Johnston wrote: 
>>> > Vertical shift sounds more like what a camera on an elevator would do. 
>>> > 
>>> > On May 24, 2020, at 5:26 p.m., Bruno Postle wrote: 
>>> > 
>>> > I think we would call this vertical shift. 
>>>
>>>
>>> -- 
>>> David W. Jones 
>>> gnome...@gmail.com 
>>> wandering the landscape of god 
>>> http://dancingtreefrog.com 
>>> My password is the last 8 digits of π. 
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9ac73fa8-4f85-444c-8ae7-d997c220f51co%40googlegroups.com.

[hugin-ptx] Operations with masks and image stacks - selective video stabilization

[Abrimaal]

I am trying to *stabilize* short video sequences to the *moving object*. 
Trying to stabilize video this way, that the *moving object* is always *in 
the middle* of the video - it can be a human, a car, anything in distance. 
This method ignores the background by *exclude masks *and/or finds control 
points only in the moving object using 

*include masks.*The image stacks are video frames.
I experiment with masking, removing control points in masks or outside 
masks, then removing masks. 

Other tests *exclude* all moving objects, to stabilize video *to the 
background*. 
Even if the moving objects are close, they are masked out.

I have found in *Hugin menu *only "*remove all control points in masks*" - 
it is very usable, 
but I am not sure if it removes points in* include masks too*?

It takes long hours to work with masks even with 100 frames. 

Are there any *batch operations on masks* available?


I am looking how to make the work simpler, it means:

- *add the same mask *to* all images* (to ignore logo or other overlay)
- *delete all masks *from* all images*
- *toggle all masks* from* exclude to include* and vice versa
- *inverse all masks* (what was masked becomes unmasked)
- find *control points* only in* include masks*

Are the features available in the *Advanced mode*
or by modifying *.pto *files in a* text editor* (Notepad++)?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/dab612d8-e7b9-4fe6-b8b1-ec23e541ae5fo%40googlegroups.com.

Re: [hugin-ptx] Is there a technical term for a tilt all around the panorama?

[Abrimaal]

Why not X,Y,Z? Before using Hugin I did not know what yawn meant.

On Monday, May 25, 2020 at 6:54:01 AM UTC+2, GnomeNomad wrote:
>
> In the "yaw, pitch, roll" world, wouldn't this be pitch? 
>
> On 5/24/20 4:59 PM, Donald Johnston wrote: 
> > Vertical shift sounds more like what a camera on an elevator would do. 
> > 
> > On May 24, 2020, at 5:26 p.m., Bruno Postle wrote: 
> > 
> > I think we would call this vertical shift. 
>
>
> -- 
> David W. Jones 
> gnome...@gmail.com  
> wandering the landscape of god 
> http://dancingtreefrog.com 
> My password is the last 8 digits of π. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4b6505c3-2ba0-4650-a07c-c32d633877bc%40googlegroups.com.

Re: [hugin-ptx] Hugin is driving me crazy

[Abrimaal]

PT Batcher is freezing not only your Mac, it makes Windows inoperable too. 
With every new task the PT Batcher icon pops the taskbar up, and I cannot 
access the tools at the bottom of the screen. When working with many 
programs at once it becomes a horror, to click and hide the terrible icon 
every time.
You may change in Preferences>Stitching>Processor the PT Batcher to 
Hugin_stitch_project 
but remember to save project after every change.


On Saturday, May 23, 2020 at 4:08:17 PM UTC+2, Stanley Green wrote:
>
> Thank you for your response.
> This morning, before I received your email, I deleted Hugin, restarted my 
> Mac and then reloaded Hugin.
> I may have had a corrupted app, because now Hugin seems to be functioning 
> ok.
> “Images are connected by 137 control points.  Mean error after 
> optimization: 1.6 pixel, max:3.9”
> Unfortunately, I did not retain a copy of the prior CP data
>
>
> My only problem now is how best to get the finished pano back into C1. 
> Ideally I’d like it to be in the same catalog that contains the raw images. 
>  But, from what I have read on various forums, that is a lost cause.
> Thank you  again,
> Stan 
>
> On May 23, 2020, at 9:29 AM, Luís Henrique Camargo Quiroz <
> lui...@gmail.com > wrote:
>
>
>   Hi,
>
>   I think that automatic control point detection is to blame here. Have 
> you checked if the control points are right? 
>   What are the CP errors values?
>
>   
>
>
> Em sex., 22 de mai. de 2020 às 22:50, 'Stanley Green' via hugin and other 
> free panoramic software > escreveu:
>
>> please accept my apology re: file size. I will be more concerned in the 
>> future
>>
>> Do you have any advice regarding the problem that I am experiencing
>>
>> Sent from my iPhone
>>
>> > On May 22, 2020, at 8:34 PM, Terry Duell > > wrote:
>> > 
>> > On Sat, 23 May 2020 00:40:51 +1000, 'Stanley Green' via hugin and 
>> other free panoramic software > 
>> wrote:
>> > 
>> > 
>> > [snip]
>> > 
>> >> As can be seen below the resulting pano is less than satisfactory.
>> > 
>> > Surely it isn't necessary to have images comprising 6.3MB to convey 
>> your story.
>> > It is not good etiquette to add large attachments to mailing list posts.
>> > Not all members will wish to see them, and if the images can't be 
>> suitably downsized they should be available via a link.
>> > 
>> > Cheers,
>> > -- 
>> > Regards,
>> > Terry Duell
>> > 
>> > -- 
>> > 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 hugi...@googlegroups.com .
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/hugin-ptx/op.0k1h7gulrs0ygh%40localhost
>> .
>>
>> -- 
>> 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 hugi...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/hugin-ptx/CDEC2CD6-3BC6-4605-A49F-4A9D89B90106%40verizon.net
>> .
>>
>
>
> -- 
> -- 
> Luis Henrique Camargo Quiroz
> http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
> http://panoramaslh.net/
>
> -- 
> 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 hugi...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/hugin-ptx/CAEKSoZYuMi7ZEUM7G88WC5y0gdbXqGwVzV5NhbrLezUrug6sjQ%40mail.gmail.com
>  
> 
> .
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/376873dc-4faf-4157-87f3-c08b4231a723%40googlegroups.com.

[hugin-ptx] Re: Hugin is driving me crazy

[Abrimaal]

About the panorama example:

Yes, the control points at the horizon are most important here. The 
detector finds control points on the ground, because the details are sharp 
and high contrast.
Before running the detector, mask out (exclude) the bottom parts 
(especially the tree). You can leave only the horizon unmasked.
run the detector and optimize.
Now remove masks. 

When the horizon is done, you may add manually some points at the bottom 
and see, compare if it looks better.

I think the 1st example is cylindrical and the 2nd is rectilinear. 

On Friday, May 22, 2020 at 4:41:22 PM UTC+2, Stanley Green wrote:
>
> In the past I used Hugin to make simple panos and then I stopped making 
> panos.  I recently decided to teach my granddaughter how to shoot and 
> stitch panos so I loaded Hugin onto my Mac. (Hugin 2019.2.0, iMac 2019, 
> Catalina).  When I first downloaded Hugin, I had a problem with 
> PTBatcherGUI freezing my Mac.  Thanks to advice that I received from the 
> user forum, that is no longer an issue.
>
> I have a set of four images that I took from the South Rim of the Grand 
> Canyon.  This not a particularly exciting scene, but I already have the 
> images. I first tried generating the pano with Hugin. As can be seen below 
> the resulting pano is less than satisfactory.  
>
> Hugin Pano Rectilinear
>
> Then I tried Hugin Cylindrical (Better than Rectilinear, but still not 
> very good)
>
> I then tried generating the pano using Affinity Photo.  The Affinity pano 
> has some minor artifacts at the horizon where the images are merged, but it 
> stitched successfully. And, from my prospectives, looks considerably 
> better than either of the Hugin panos
>
> Affinity Photo Pano
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d45ed0fe-33af-4b4f-95be-9d0451d93942%40googlegroups.com.

[hugin-ptx] Re: Default file locations for Add Images, Open Project File and Save Project dialog boxes

[Abrimaal]

The temporary folder is emptied at exit, you can change its location in 
Preferences -> Filenames -> Temporary dir

Saving projects in the same folder as the images is the best option ever. 
Believe me, if you had one folder for projects, after creating 5000 
projects you would never find it.

On Tuesday, May 19, 2020 at 1:09:52 AM UTC+2, Stan Tess wrote:
>
> *Hi,*
>
>  
>
> *I am new to Hugin and I could use some help.  I’ve noticed that both the 
> Add Images dialog box and the Open Project File dialog box open to the last 
> used folder by default.  I have also notice the Save Project File opens to 
> User\AppData\Local\Temp by default.  I would like to change these 
> locations. Where are these default folder locations stored?  I open Hugin 
> with a win batch file so I would probably change the default folder 
> locations in the batch file as needed.  I found a couple of entries in the 
> registry but changing these folder locations didn’t change the default 
> locations when I opened any of the three dialog boxes so I assume the 
> folder location is probably stored in a file somewhere.*
>
>  
>
> *Thanks and best regards,*
>
> *Stan Tess*
>
>  
>
>  
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8a24175f-4b47-40f9-abd8-879e216ec4e4%40googlegroups.com.

[hugin-ptx] Auto crop inaccuracy

[Abrimaal]

Today not about panoramas. About blending various versions of the same 
photo.

I open 3 versions of the same photo - all of them are the same size, for 
example 3000x2000 px
I reset positions and use inclusive masks to select the best parts of each 
version.
There are no control points, because all photos are the same size an 
position (0,0,0) 

Then Stitcher tab - calculate size and crop. 
The cropper often sets the size to 3000x2001 or 3001x1999 or 2998x2000 when 
the images have exactly the same size, position and lens. 
I can correct it manually, but why this inaccuracy?

Maybe you will ask me why I blend 3 versions of the same photo.
A human portrait - one image (the softest version goes for face), version 2 
is body with more contrasts and detail, version 3 is clothes with high HDR 
effect. There can be one more photo for blurred background. 
For architecture and landscape - the sky should be soft and highly 
denoised, the grass and trees should be intermediate, and the bricks with 
high detail. 


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ab3f1ca8-4fd2-41b9-af06-e8565b64b2e5%40googlegroups.com.

[hugin-ptx] Re: Scale panorama FOV

[Abrimaal]

Maybe it will be useful to do it in two steps.
Load the final panorama to Hugin (as a single image) and change the field 
of view.
This is a 360° panorama with HFOV changed to 20° I think it will work in 
both ways.



On Tuesday, March 10, 2020 at 12:00:10 PM UTC+1, ChameleonScales wrote:
>
> I have a panorama that is sewed correctly except the entire panorama 
> covers a field of view that I know is too small.
>
> How would I go about scaling the entire thing up or down, that is, change 
> the field of view of the whole panorama, effectively changing all the y,p,r 
> and distortion parameters of each photo so that the panorama looks the same 
> except bigger on the sphere ?
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f1dc5814-2a06-49f9-9936-d5e1ca4b1ead%40googlegroups.com.

Re: [hugin-ptx] Discard JPG color profiles - interpret them as simple RGB

[Abrimaal]

Ad GIMP and other external converters: time counts. Often we have to 
prepare a photo document to publish it the same day, and we want to have 
good photos for future projects. 

One more possible solution. Hugin work files are in .tif format. 
While opening (with the option discard color profiles selected), all .jpg 
images are saved temporarily as .tif. 
The panorama is stitched from these .tif files. Original .jpg files are not 
used.  

On Friday, March 20, 2020 at 8:07:54 AM UTC+1, Bruno Postle wrote:
>
> I open them all in GIMP and convert to sRGB, but this isn't something we 
> can expect all users to find obvious. 
>
> Possible solutions are: 
> 1. Transparently convert everything to a single profile when remapping. 
> 2. Discard profiles for all images but the 'anchor', and let the Hugin 
> photometric optimiser sort out the rest. 
>
> I have no idea how hard 1 is, and 2 would need some testing to see how 
> viable it is. 
>
> -- 
> Bruno 
>
>
> On 19 March 2020 23:20:07 GMT, Abrimaal wrote: 
> >Once there was only RGB, CMYK and grayscale and nobody took care about 
> >color spaces and profiles. What happened that today we have so many color 
> >profiles, and they apply only to .jpg format? 
> >I process photos in various editors, each of them saves .jpg with a color 
> >profile. Some editors, especially mobile apps even don't inform the user 
> >that they change the original profile and apply another. 
> >I often stitch together the same image processed in various editors, 
> >because the sky looks great in one version. 
> >In another version of the same photo the shadows look the best, in 
> another 
> >there is a detail that I want to expose. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/72297ad2-b4cb-49de-95b4-27183ed769e8%40googlegroups.com.

[hugin-ptx] Select all vertical lines and change to horizontal at once - it this possible?

[Abrimaal]

This is an example of straightening a single photo (but it also refers to a 
sequence of images and there are more lines)

I open an image. 
Rotate it 90°
Run vertical line detector to detect horizontal lines. 

All the horizontal lines are detected as vertical lines, what is correct.

*Now I would like to select all lines and change the value to horizontal - 
but select all does not work here. *
I rotate the image back to 0°, the detected lines are still listed as 
vertical.

When loading 3 exposures, there are already 15 lines to correct. 
*Is there any simpler method to change all vertical lines to horizontal*, 
than click on any of the 15 lines and change each?

I run again the line detector - this time it detects vertical lines.
Optimise and save.





-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/917c0d1c-cdad-4433-aa4f-b247f9216c85%40googlegroups.com.

[hugin-ptx] Discard JPG color profiles - interpret them as simple RGB

[Abrimaal]

Once there was only RGB, CMYK and grayscale and nobody took care about 
color spaces and profiles. What happened that today we have so many color 
profiles, and they apply only to .jpg format?
I process photos in various editors, each of them saves .jpg with a color 
profile. Some editors, especially mobile apps even don't inform the user 
that they change the original profile and apply another.
I often stitch together the same image processed in various editors, 
because the sky looks great in one version. 
In another version of the same photo the shadows look the best, in another 
there is a detail that I want to expose. 

Using include / exclude masks, Hugin blends the images and creates a 
perfect photo from all the versions. 
Even without finding control points. I just reset positions and stitch - 
they are the same size.

Often the creation of a perfect photo or a collage ends while opening the 
images. 
If at least one of images uses a different color profile, it cannot be 
loaded, even by force (by changing filename in .pto file). 
I don't know any profile converter, so I save all photos to .png or .tif. 
The color profiles are discarded, Hugin opens them all and the difference 
is almost invisible. 

Can I ask for enabling such dialog while opening: Discard the color 
profiles? 
Or such a checkbox in settings 
[ v ] Discard .jpg color profiles if they are different. 


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5bad23f9-a98b-47d4-9579-9cbeb4c92390%40googlegroups.com.

[hugin-ptx] Re: Hugin 2019.2.0 released

[Abrimaal]

Thanks a lot for "check if still exist and delete again" temporary .tif 
files, when the same folder was open in another image viewer.
Will it be difficult to add "Open file location" to the batch processor 
right-click menu? When right clicking on a project from the task list, the 
folder with the project will be opened. 
"Open file location" is in Windows shell, I think. 

On Monday, December 30, 2019 at 10:31:31 AM UTC+1, T. Modes wrote:
>
> Hi all,
>
> today we are releasing Hugin 2019.2.0 
>
> Source tarball can be downloaded
> at sourceforge: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2019.2/hugin-2019.2.0.tar.bz2/download
> or at launchpad: 
> https://launchpad.net/hugin/2019.2/2019.2.0/+download/hugin-2019.2.0.tar.bz2
>
> Verify its checksums:
> md5:
> 3409c3a84e1881145b5b556df63de73c  hugin-2019.2.0.tar.bz2
> sha1:
> e91bfbb286d0d5f40cd93ecb961eb55a37f3f5bb  hugin-2019.2.0.tar.bz2
>
> This is a source code release. 
> Users communities produce executables for their respective platforms. 
> Please announce them here.
>
> Currently binaries are available
> for Windows 64 bit: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2019.2/Hugin-2019.2.0-win64.msi/download
> MD5 checksum: 0703e31a08f2db5076823648c9805de0
> and MacOS: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2019.2/Hugin-2019.2.0.dmg/download
> MD5 checksum: 8d0f93542297ab5404e17255cfb682ca
>
>
> (This release correspond to changeset b690aa0334b5 in our repository, 
> which is also tagged as 2019.2.0.
> It is identical to RC3.)
>
> Changes since 2019.0
> * Mainly a bug fix release.
> * Fixes raw import on Mac OS.
> * Fixes bugs in verdandi/internal blender.
> * Scripting interface needs now Python3.
> * Improvements for high dpi displays (Windows, GTK+3).
>
> Upgrading from previous versions of Hugin should be seamless. If you do 
> have problems with old settings, these can be reset in the Preferences 
> window by clicking 'Load defaults'.
>
> Please test and report bug/issues to mailing list or bug tracker 
> https://bugs.launchpad.net/hugin
>
> The release notes can now also be found at 
> http://hugin.sourceforge.net/releases/2019.2.0/
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1185f732-d403-4931-b30c-65e1fe8409ec%40googlegroups.com.

Re: [hugin-ptx] Can you calculate position and FOV of cameras using Hugin for 3dsmax?

[Abrimaal]

A little offtopic, but I am interested. I downloaded Meshroom. What can I 
do in this? 
Can I load a series of photos to create a 3D model?
I tried everything, nothing worked. Started from loading a photo.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/db0f056d-6aa6-4999-a74d-56a33624597e%40googlegroups.com.

[hugin-ptx] Re: Meaning of Verticle/Horizontal control point distances

[Abrimaal]

The vertical and horizontal lines are used for calculating a good looking 
panorama. The distance is important to avoid errors in calculations. 

The V lines should be distant as far as possible, at least two near the 
edges of a panorama, to calculate and straighten the view.
When there are lines only at one side, the other side of the panorama may 
be curved up or down (for example when there is only one straight object 
near the left or right edge, the rest is landscape). 
It is better to add a horizontal line to compensate the curved horizon (or 
a vertical line on an object that should be straight, for example a tall 
tree).
When the panorama is a landscape only, the detector may place vertical 
lines on trees, grass and other objects. If it looks good, leave as it is, 
but try also the [Straighten] button to compare how it looks without the 
detected lines.

Why the distance is important: to avoid statistic errors. The detector may 
place 5 vertical lines on the same traffic sign or electric pole that is 
not straight (and repeat the error on objects arranged at similar angle).
The best to place vertical lines only on firm straight objects, such as 
buildings, windows in buildings etc. The detector finds high contrasts, but 
it does not recognize if this is a building, a tree or a human leg.

What are horizontal lines for: when you work (for example) with front views 
of architecture, they are used to optimize the left-right position and 
barrel distortion. They are not detected, not introduced yet. Finding them 
is the same work for the detector, it is equally simple. It's hard to say 
why the developers did not introduce this yet. 

The distance between the horizontal lines is the answer for "what you want 
to straighten". If you want to straighten the whole image, they should be 
as far as possible. If you want to straighten a specific object, a front 
view of a building, a photographed picture, a single window, the lines 
should be placed only on this object, the rest is not important.
"a photographed picture" refers not only to a single photo of a picture on 
a wall or a banner on a street that you want to use, 
it refers also to panoramas of maps and other large sheets, scanned or 
photographed. 

The horizontal lines are also useful and the only way to straighten the 
horizon when you work with landscapes or waterscapes (and there are no 
human-built objects). 




On Wednesday, January 8, 2020 at 8:38:26 PM UTC+1, Judson Fisher wrote:
>
> Hi,
>
> I'm enjoying very much getting to learn about how Hugin works, one thing 
> that has not been clear to me is:  What is the significance of control 
> point distance in regards to horizontal and vertical control points?
>
> Thanks,
> /Jud
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/19c0b70e-a7d8-454b-ac6d-8bb83ea66f86%40googlegroups.com.

Re: [hugin-ptx] Re: Aligning images of different dimensions

[Abrimaal]

Do not use HDR autocrop - it crops to the smallest common area. Normal 
autocrop crops to the largest area.
You may also skip autocrop and draw the rectangle with borders. Save as png 
or tif - then the outlying border will be transparent.

On Wednesday, December 11, 2019 at 8:02:18 PM UTC+1, Judson Fisher wrote:
>
> Thank you all who replied, what a responsive community!
> I tried the process again. I was using all manual control points, but I 
> don't believe I was setting the crop and view properly. Using fit and auto 
> crop HDR in the quick preview window and not using the crop button in the 
> stitch tab seems to have made the process work. 
> Sorry if I'm mistaking the function names, I'm new to Huggin and I'm not 
> in front of the computer at the moment.
> I have many more questions but I think I should start a new topic for that.
> Thanks,
> /Jud
>
>
>
>
> On Wed, Dec 11, 2019, 10:27 AM Abrimaal > 
> wrote:
>
>> 1. Check the control points, any image with any. The detector often fails 
>> with scanned images. Check the vertical lines, they are often added on the 
>> edges of photos. The best to add all control points manually.
>> 2. Set a different lens number to every image - 0,1,2,3...
>> 3. Mask out (exclude) the image borders, if they are white, black or 
>> uneven.
>> 4. Reset photometric parameters if the images are similar exposure (I 
>> think the images are black and white). 
>> 5. Optimize positions and view - it will adjust image sizes. It may 
>> result a very small field of view, so try to crop the images manually. 
>>
>> On Tuesday, December 10, 2019 at 5:40:23 PM UTC+1, Judson Fisher wrote:
>>>
>>> Hello,
>>> I am trying to align a stack of historical aerial photos using their 
>>> fiducial marks.  The images are photos of photos and were taken such that 
>>> the images sizes are inconsistent, varying by up  to 40 pixels.  I've made 
>>> control points between a base image and the rest but when I attempt to 
>>> stitch them the batch processor returns an error regarding the inconsistent 
>>> image size.  Do i need to use other software to make my image size 
>>> consistent, or can Hugin help me with this?
>>> thanks,
>>> /Jud
>>>
>> -- 
>> A list of frequently asked questions is available at: 
>> http://wiki.panotools.org/Hugin_FAQ
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "hugin and other free panoramic software" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/hugin-ptx/RLXtgTdmagk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> hugi...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/hugin-ptx/1424c334-b001-4048-8929-0ae0bab508d4%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/hugin-ptx/1424c334-b001-4048-8929-0ae0bab508d4%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2db45032-e608-4282-863d-0f322bb0451a%40googlegroups.com.

[hugin-ptx] Re: Aligning images of different dimensions

[Abrimaal]

1. Check the control points, any image with any. The detector often fails 
with scanned images. Check the vertical lines, they are often added on the 
edges of photos. The best to add all control points manually.
2. Set a different lens number to every image - 0,1,2,3...
3. Mask out (exclude) the image borders, if they are white, black or uneven.
4. Reset photometric parameters if the images are similar exposure (I think 
the images are black and white). 
5. Optimize positions and view - it will adjust image sizes. It may result 
a very small field of view, so try to crop the images manually. 

On Tuesday, December 10, 2019 at 5:40:23 PM UTC+1, Judson Fisher wrote:
>
> Hello,
> I am trying to align a stack of historical aerial photos using their 
> fiducial marks.  The images are photos of photos and were taken such that 
> the images sizes are inconsistent, varying by up  to 40 pixels.  I've made 
> control points between a base image and the rest but when I attempt to 
> stitch them the batch processor returns an error regarding the inconsistent 
> image size.  Do i need to use other software to make my image size 
> consistent, or can Hugin help me with this?
> thanks,
> /Jud
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1424c334-b001-4048-8929-0ae0bab508d4%40googlegroups.com.

[hugin-ptx] Re: Hugin 2019.2.0 rc1 released

[Abrimaal]

I see no differences.
Not much has changed in the new versions (Windows) since 2016, when 
straightening single photos was introduced (thankful I am for this mode, 
the only introduced feature from my suggestions).
Thanks also for enabling image preview in "Open"
Thanks for "Cancel" when calculating crop takes too long. Usually it caused 
crash.

The installer still deletes the previous, stable version - it must be 
backed up before installing (no portable archive to unzip).

The background is still white what makes the work with night photos 
impossible.

Horizontal lines are not detected.

If the panorama editor is already open, clicking "View / Panorama editor" 
does not switch to panorama editor. I suggested to add Panorama editor as a 
tab of the simple interface (after Crop).

Batch processor still blocks the taskbar from auto-hiding. Even if 
auto-hide is enabled in the system settings, it is overriden by Batch 
processor. The visible taskbar makes the lower part of the screen 
unaccessible (until a "confirm click" on the icon every time a new task is 
added to the processor).

Filename suffixes "blended_fused" and "fused" are not shortened to "bf" and 
"fd". Who knows how long the process of photo editing can be. Such names as 
"Original_filename_2bf_2fd_bf2a_mk3c_e2a_acr_hue_hdr2b_mx" are normal in 
the process of photo editing. The filename suffix must be short, especially 
when working on Windows and Android with the same images (Android apps 
usually do not care for filenames). 
Indeed, final panoramas are loaded multiple times to Hugin, often 
"blended_fused" is stitched together with "fused", then again 
"blended_fused_fused" with another panorama that is 
"blended_fused_blended_fused" - it outputs extremely long filenames. 
"blended_fused" and "fused" may be shortened by renaming software, what 
does not change names in the project files.

It is possible to load (.jpg +.png) (.png + .bmp) (.jpg + .tif + .png + 
other supported formats) at once, but (.jpg + .jpg) images cannot be 
stitched if they differ only by ICC profile. Simply, a dialog to discard 
color space could appear while loading. Or by default the profile discarded 
in settings. 

There is no option to define the minimal distance between lines for the 
line detector, to avoid placing lines on the same tree or traffic sign that 
are never straight.

Why I am writing about the same again? This cannot be a war between a 
developer and a user who "dreams" of a collab, not ignoring each other.

New proposals to introduce
 
To extend the compression sliders in Panini general to negative values. The 
value 0 (rectilinear) is sometimes not enough, especially when correcting 
cylindrical panoramas taken with a mobile device. Adding horizontal lines 
and de-barrelizing takes a lot of time. Typing numbers by guessing is just 
guessing. This is the main difference between being a programmer and a 
photographer. The first one depends on numbers, the other on visuals - this 
is why I always use the simple interface, even with advanced work.
To extend the preview sliders to smaller angles in rectilinear and panini 
general. The image preview is sometimes 2x2 mm on the screen.

"Darker color priority" mode. The standard stitching mode (both by enblend 
and enfuse) includes all photography errors, such as sun flares, 
reflections (if they are not masked) in panoramas, because it bases on 
"brighter color priority".

"Open project location" from the batch processor right-click menu.





On Saturday, November 23, 2019 at 12:34:30 PM UTC+1, T. Modes wrote:
>
> Hi all,
>
> today we are releasing release candidate 1 of Hugin 2019.2. 
>
> Source tarball can be downloaded
> at sourceforge: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2019.2/hugin-2019.2.0-rc1.tar.bz2/download
> or at launchpad: 
> https://launchpad.net/hugin/2019.2/2019.2rc1/+download/hugin-2019.2.0-rc1.tar.bz2
>
> Verify its checksums:
> md5:
> ed8a602894dcbbe5c96ec0e265a70c9f  hugin-2019.2.0-rc1.tar.bz2
> sha1: 
> b6818e7eb32475826d67982871168ae059b730df  hugin-2019.2.0-rc1.tar.bz2
>
> This is a source code release. 
> Users communities produce executables for their respective platforms. 
> Please announce them here.
>
> (The rc1 correspond to changeset 6c8394bb3ce7 in our repository, which is 
> also tagged as 2019.2rc1).
>
> Changes since 2019.0
> * Mainly a bug fix release.
> * Fixes raw import on Mac OS.
> * Fixes bugs in verdandi/internal blender.
> * Scripting interface needs now Python3.
> * Improvements for high dpi displays (Windows, GTK+3).
>
> Upgrading from previous versions of Hugin should be seamless. If you do 
> have problems with old settings, these can be reset in the Preferences 
> window by clicking 'Load defaults'.
>
> Please test and report bug/issues to mailing list or bug tracker 
> https://bugs.launchpad.net/hugin
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message 

Re: [hugin-ptx] Stitching scanned images

[Abrimaal]

It's simpler to use Include masks. 
Include the whole text of the left page on the left image 
and the whole text of the right page on the right image. 

| [ text text text  ] | [part of
| [ include mask] | [right page
| [ on whole text   ] | [no need to
| [ of  left page   ] | [exclude

No need to exclude mask on the right side, because the right page is 
included on the 2nd image.




On Friday, November 8, 2019 at 2:02:23 AM UTC+1, aks wrote:
>
> Yes, use masks. On image A you mask off the part of image B you do not 
> want to come from image A. On image B you mask off the part of image A you 
> do not want to come from image B. By the way, if you had multiple image As 
> and image Bs where each is a stack of the same image at different exposures 
> then you would need to use the exact same mask for the As and the exact 
> same mask for the Bs. That is when the mask copy paste ability comes in 
> handy.
>
> Regarding the sentence, depending on how many of these you need to do and 
> also how well produced the finished product needs to look, I would add in 
> the sentence with another application. The sentence text can be added with 
> an opaque background so that the new text covers up the poorly stitched 
> sentence.
>
> On Nov 7, 2019, at 4:44 PM, 'Chris H' via hugin and other free panoramic 
> software > wrote:
>
> Hi,
>
> My first post here so hello to all!
> I have a question regarding stitching scanned images. 
> So I am scanning a book that is slightly wider than A4 so I end up with 
> two scans for every page, the left and the right scans that need to be 
> stitched.
> I came across this tutorial 
> http://hugin.sourceforge.net/tutorials/scans/en.shtml and am almost 
> there, the only problem is Hugin by default seems to be overlapping those 
> two images, so as a result if the right edge of the left scan has some 
> imperfections resulting from for example that scan not being firmly pressed 
> into the scanner along that edge, they will be reflected in the resulting 
> panorama image, obviously same thing happens if there are some 
> imperfections with the left edge of the right scan.
> But more importantly what I am scanning is a book so the written sentences 
> from both left and right image are also stitched with some kind of 
> overlapping, but after that's done the edges of the letters on the 
> resulting panorama are far from being as smooth as they are if you look at 
> each image separately.
>
> So the question... Is there a way to configure the stitcher so that 
> everything to the left of the "stitching line" would come from the left 
> image only and similarly everything to the right of the stitching line from 
> the right image only?
>
> Thanks in advance for any suggestions!
> Chris
>
> -- 
> 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 hugi...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/hugin-ptx/86994b19-d5d6-46b9-8598-9923015f7617%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9f06e6f6-edb2-41ee-94bb-91d3236ef91d%40googlegroups.com.

[hugin-ptx] Re: Find control points only for the added image

[Abrimaal]

Yes, I selected only the neighbouring images. This is an example of adding 
2 images to a 29 image panorama that had a "black hole" inside. 
These 2 added images were from a different photo sequence and they covered 
the black hole.
Finding points for all images would take hours. Thanks for explaining how 
the selection works.

Maybe the points are not duplicated pixel to pixel, but most of these are 
in the same places. When deleting one point, there is usually another one 
below. 
Finding points only for selected images will prevent this. 

[image: hugin find controlpoints only for selected images.png]
  



On Wednesday, September 11, 2019 at 12:39:56 AM UTC+2, Erik Krause wrote:
>
> Am 10.09.2019 um 03:16 schrieb Abrimaal: 
>
> > I selected image 6 to find points between image 6 and ALL the rest 
> > 6+0, 6+1, 6+2, 6+3, 6+4, 6+5 but NOT between 1+2, 1+3... ... 4+5 
>
> If you have a panorama with aligned images and you add another image it 
> usually is sufficient to create control points between this image and 
> one or two other images. However, it is good practice to add all images 
> to a project, then specify which of those should be treated specially, 
> (f.e. by viewpoint correction), then press Align. 
>
> > Duplicated control points are not a problem, they don't change geometry, 
> > but it takes a lot of time to calculate. 
>
> PTGui doesn't create duplicate points, it always creates additional ones. 
>
> -- 
> Erik Krause 
> http://www.erik-krause.de 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/359fe2fc-788a-4133-8181-149083c4be6b%40googlegroups.com.

Re: [hugin-ptx] Find control points only for the added image

[Abrimaal]

“None means all” - this is perfectly logical and intuitive, 
I selected image 6 to find points between image 6 and ALL the rest 6+0, 
6+1, 6+2, 6+3, 6+4, 6+5
but NOT between 1+2, 1+3... ... 4+5
Duplicated control points are not a problem, they don't change geometry, 
but it takes a lot of time to calculate. 
(and when you don't have to remove more control points manually). 

Maybe I should try to select 6+0 and "Find control points", then 6+1 and 
find and repeat the step until 6+5.
I will try next time, maybe this will avoid duplicates between images 
connected before.


On Monday, September 9, 2019 at 6:53:59 PM UTC+2, aks wrote:
>
> “Find control points” operates on the selected images. It assumes you want 
> the operation to apply to all the images when no images are selected 
> because “none means all” makes perfect sense most of the time in most 
> workflows.
>
> In your case when you add image 6 and for example you only want to find 
> control points between image 6, image 5 and image 1, then select only those 
> images in the image list prior to invoking the “Find control points” 
> operation. Control points will be found between only the selected images.
>
> I don’t know if there is a delete duplicate control points command. I’ve 
> made the same mistake and also wanted to delete duplicate control points. 
> You can view the control points as a list table (F3 is the short cut). 
> There are sorting features in that table that can help you to identify the 
> duplicate points. Deleting points is easy to do within the table view. The 
> control points list goes way back in the Hugin interface but it almost 
> seems ignored in the current menu structure. With its sorting features one 
> could easily spot the zinger control point that should not be or edge 
> matchings that would skew a stitch.
>
> On Sep 9, 2019, at 10:32 AM, Abrimaal > wrote:
>
> I added one more image to an existing panorama. Now I want to find control 
> points only for this image (no. 6) , it means
> 6 and 0
> 6 and 1
> 6 and 2
> 6 and 3
> 6 and 4
> 6 and 5
> vertical line detection only for image 6
>
> When I select image 6 and right click, there is no "Find control points" 
> for this image only.
> So I use "Find control points" with only image 6 selected.
>
> 
>
>
> The detector starts the search once again for all images 0 and 1, 0 and 2 
> and so on.
>
> To avoid duplication of existing control points, I want to skip finding 
> control points for images that are already connected, only for the added 
> image.
>
>
> Can I do this?
>
> Comparing the stats, we see that all points for already connected images 
> have been duplicated.
>
> 
>
>
>
> -- 
> 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 hugi...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/hugin-ptx/ee72a266-1598-4db1-beb5-5f3205b3af7a%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/hugin-ptx/ee72a266-1598-4db1-beb5-5f3205b3af7a%40googlegroups.com?utm_medium=email_source=footer>
> .
>  duplicated.png>
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/440bc81f-7561-4fb0-b0ad-3ae676dd9dff%40googlegroups.com.

[hugin-ptx] Find control points only for the added image

[Abrimaal]

I added one more image to an existing panorama. Now I want to find control 
points only for this image (no. 6) , it means
6 and 0
6 and 1
6 and 2
6 and 3
6 and 4
6 and 5
vertical line detection only for image 6

When I select image 6 and right click, there is no "Find control points" 
for this image only.
So I use "Find control points" with only image 6 selected.

[image: hugin how to find control points for added img.png]


The detector starts the search once again for all images 0 and 1, 0 and 2 
and so on.

To avoid duplication of existing control points, I want to skip finding 
control points for images that are already connected, only for the added 
image.


Can I do this?

Comparing the stats, we see that all points for already connected images 
have been duplicated.

[image: hugin control points duplicated.png]


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ee72a266-1598-4db1-beb5-5f3205b3af7a%40googlegroups.com.

[hugin-ptx] Batch processor unknown error - empty window that could not be closed.

[Abrimaal]

I think it was a Batch Processor error, because I could save a project and 
close Hugin, but could not close BP. 
The message window was empty and not responsive to clicks. I closed BP with 
Task manager.
When I opened the saved project in Hugin again, the panorama was stitched 
normally.

[image: Clipboard01.jpg]






-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/90d10e79-2272-4b1d-9c6b-f64a79ab61c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<>

[hugin-ptx] Re: stitching cylindrical pano from rectilinear images results in vertical mismatch at ends

[Abrimaal]

> 1. I Load Images (easy), then set Projection to Cylindrical.
> 2. I run Align;
Hugin will not remember the selected projection when you click [ Align ], 
because the simple Align automatically selects projection, based on the 
field of view. 
You might not notice this, because cylindrical is the default projection 
for long panoramas.
But if you select Panini, Mercator or a different projection, and click 
Align, it will be automatically changed to cylindrical. You may always 
change the projection after alignment... 
or use Panorama editor (find control points, vertical lines if you need, 
optimize positions, optionally adjust the exposures/white balance) and 
return to the simple preview. This sequence works the same as [ Align ] 
button without changing the pre-selected projection.

> This barfed earlier today for some reason in the batch processor, but now 
seems to work fine.
I don't know how the batch processor behaves under OS X, but under Windows 
it is very annoying, especially when you have sooo many panoramas to make.
With every added task, the icon of the batch processor is popping up the 
taskbar blocking the bottom of the screen. Until you click on the icon. I 
reported this bug many times, because it slows down the work, especially 
when there are many panoramas to stitch. 


On Tuesday, April 30, 2019 at 5:07:35 PM UTC+2, James Proctor wrote:
>
> Thanks again for your help, Groogle & Erik. I'm now learning a few things 
> that may differentiate my outcome from yours, and that may've resulted in 
> some confusion:
>
>- I'm running the Simple interface. (I've played with the Advanced 
>interface, but issues with PTBatcherGUI took me back to Simple...possibly 
>due to version noted below?).
>- I'm running the Mac OS version of Hugin (2019.0.0 on OS X latest).
>- I'm running cpFind as the default control point detector as set in 
>Prefs.
>
> With Simple interface the three-step process seemed buggy when testing 
> this AM, but now works:
>
>1. I Load Images (easy), then set Projection to Cylindrical.
>2. I run Align; this now works in establishing control points btw my 
>first and last image. I typically end up with ~550 automatic control 
> points.
>3. I then run Create Panorama. This barfed earlier today for some 
>reason in the batch processor, but now seems to work fine. 
>
> I realize I'm doing the very simple/uncorrected approach here, but it now 
> seems to work fine. I have on order a half dozen other historical (2000-01) 
> panos to stitch similarly, which I'll do, and report issues to this thread 
> as relevant.
>
> I want to thank you all for your great help. If questions re. above, feel 
> free to ask.
>
> Regards,
>
> Jim P. 
>
> On Sunday, April 28, 2019 at 10:40:58 PM UTC-7, James Proctor wrote:
>>
>> Greetings -- I'm using Hugin to stitch together some old digital images 
>> taken from a Nikon Coolpix atop a tripod/pano mount (14 total per pano). 
>> There was plenty of overlap btw all images, including the first and last 
>> image. The stitching process seems to work great, but when I export and 
>> view the pano the vertical position of elements at the left and right ends 
>> is off, resulting in a jagged transition...see e.g. attached. 
>>
>> The settings I used are as follows:
>>
>>1. Load Images: Lens type rectilinear, 3.8mm/13.7 multiplier 
>>(automatically detected?)
>>2. Projection switched from default Rectilinear to Cylindrical
>>3. I've played a bit with Center/Fit/Straighten buttons, but they 
>>don't seem to do the trick
>>
>> There must be an easy explanation as to why the stitching process doesn't 
>> align the two ends of the pano, given the original images overlap 
>> substantially. It just doesn't seem to recognize that these 14 images are 
>> from a quasi-cylindrical (vs. e.g. planar) source.
>>
>> If you could please point me to a ready solution I'd sure appreciate! The 
>> app is proving useful for me to re-stitch circa 2000 digital panos 
>> previously saved in now-extinct QTVR format.
>>
>> Regards,
>>
>> Jim Proctor
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5615b36d-9df0-4d6b-8404-b44e705c31f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: stitching cylindrical pano from rectilinear images results in vertical mismatch at ends

[Abrimaal]

The horizon looks very good, the trees are straight and the hills naturally 
curved. 
I see that the sky colors don't look natural. 
This has been caused by the automatic exposure and white balance 
correction. 
When you use "Align" button, the exposures and WB are adjusted, but they 
rather adjust the dark tones - this is why the ground looks very good.
Try to reset the photometric parameters in the Panorama editor and save a 
new panorama.
The new panorama may have differences in the exposures of the ground, but 
the sky will look good.

Then load both panoramas into Hugin, set rectilinear projection,
Edit image variables: set yaw, pitch, roll to 0 (this will overlay both 
panoramas)
Now use masks - include mask for this part of image where the ground looks 
good, and other include mask where the sky looks good... and save a new 
panorama from stacks using the Stitcher.





On Monday, April 29, 2019 at 7:40:58 AM UTC+2, James Proctor wrote:
>
> Greetings -- I'm using Hugin to stitch together some old digital images 
> taken from a Nikon Coolpix atop a tripod/pano mount (14 total per pano). 
> There was plenty of overlap btw all images, including the first and last 
> image. The stitching process seems to work great, but when I export and 
> view the pano the vertical position of elements at the left and right ends 
> is off, resulting in a jagged transition...see e.g. attached. 
>
> The settings I used are as follows:
>
>1. Load Images: Lens type rectilinear, 3.8mm/13.7 multiplier 
>(automatically detected?)
>2. Projection switched from default Rectilinear to Cylindrical
>3. I've played a bit with Center/Fit/Straighten buttons, but they 
>don't seem to do the trick
>
> There must be an easy explanation as to why the stitching process doesn't 
> align the two ends of the pano, given the original images overlap 
> substantially. It just doesn't seem to recognize that these 14 images are 
> from a quasi-cylindrical (vs. e.g. planar) source.
>
> If you could please point me to a ready solution I'd sure appreciate! The 
> app is proving useful for me to re-stitch circa 2000 digital panos 
> previously saved in now-extinct QTVR format.
>
> Regards,
>
> Jim Proctor
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/bc76df60-8bb9-4e03-8e6e-a7d6216f6429%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: CPFind images as command line parameter

[Abrimaal]

They are selected images from the Explorer, dragged and dropped from 
Explorer to Hugin, or sent to Hugin from Windows Explorer or other 
application. (for Windows).
Btw: the component applications of Hugin can be run from command line with 
parameters. I am also interested where to find the list of parameters, so I 
subscribe to this topic.
.


On Thursday, March 21, 2019 at 4:31:35 PM UTC+1, Caetano Veyssières wrote:
>
> What do you mean by "marking the images"?
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/de65a55f-48e8-4582-964b-6326b4361cf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

Excellent. I always forget that I can manually modify X Y Z positions.

On Monday, March 18, 2019 at 8:14:41 AM UTC+1, Bruno Postle wrote:
>
>
>
> On 17 March 2019 19:35:01 GMT, Abrimaal wrote: 
> > 
> >Creating a multiview pano is possible on a 2D screen, but except a lot of 
> masking, 
> >it would require a rectangular (planar) projection to be introduced, such 
> >as is used for stitching maps and flat documents. 
>
> You can absolutely stitch these street elevations in Hugin, this picture 
> (attached) is created in Hugin without using any other tools. 
>
> I used saved lens parameters, optimised X,Y positions, then added r,p 
> rotation. This is a lot of parameters, so the optimisation can get 
> unstable, but with practice, by introducing one parameter at a time, it 
> works well. 
>
> I also find that I get better results if I don't shoot the photos straight 
> on, for the buildings on the left I turn the camera slightly to the left, 
> then gradually turn to the right for the rest. 
>
> -- 
> Bruno

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0ee03aa7-fa54-4791-b080-0dd5f968a383%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

Theory, raw theory. When stitching 40 panoramas daily, every second counts. 
"Add images" already opens Windows explorer, a second Explorer window will only 
take space on the screen and it will not follow the current work folder. 

I started to write a command line script to get filenames from .pto files, to 
be interpreted as images, but as I see, it will certainly fail. Command line is 
tough for multiple file operations and loops (and extremely slow) (and I don't 
know any other language). 
The initial goal is only to get filenames from .pto files and load these images 
to Hugin. All the parameters may be added later. 

Why it is so important to me: I have already photographed almost the whole town 
in panoramas, from 3 to 20 photos. Then gradually merge one pano with another, 
to create a street, then a street with another street and so on...

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b97e2f9f-63ce-47f4-a244-97030bb0ab1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

>But this DOES NOT turn a PTO magically into an image, so it cannot be 
opened as an image, because it isn't an image. 
Yes, I know. I use Load images button to preview how the panorama looks. 
(right click -> open in a default viewer) 
The .pto file is saved just before the panorama in the same folder.
If the panorama requires corrections, then right click .pto -> Send to -> 
Hugin. 
Now it became impossible. When there are a few hundreds partial images in a 
folder, it is not easy to find the proper .pto file from the standard menu 
File -> Open.

On Monday, February 25, 2019 at 10:51:32 PM UTC+1, Bart van Andel wrote:
>
> Abrimaal wrote:
>>
>> It does not work in the 2019 beta 2 version, because the filter "All 
>> files" has been changed to "All images".
>>
>
> Sorry, apparently I missed this. BTW I think 2018 version had both
>  
>
>> I typed:
>> *
>> "*"
>> *.*
>> "*.*"
>> in the filename field.
>> .pto files are among the images, but not accessible.
>>
>
> Just * works for me to show all files. But this DOES NOT turn a PTO 
> magically into an image, so it cannot be opened as an image, because it 
> isn't an image. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ea7223fa-859d-44f1-b449-803fc1bb2211%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

[image: file-filter-all-images-instead-of-all-files-pto-not-accessible.png]


On Monday, February 25, 2019 at 6:06:29 PM UTC+1, Bart van Andel wrote:
>
> All the things you want are basically the job of a file manager. It isn't 
> reasonable to assume that all tools should be able to perform file manager 
> things. If you have images with a wrong extension, rename them.
>
> Having said that, if you want to show all files in any regular "Open File" 
> or "Save File" dialog in Windows, you can usually just enter "*" in the 
> "File name" field and hit enter. Just verified, this works in Hugin too. 
> Actually the drop down to the right of this file field already contains an 
> option for showing "All files (*)", both in Hugin 2018.0.0 and the current 
> 2019.0.0. I think we can conclude you've been served already a while ago ;-)
>
> On Thursday, 21 February 2019 17:56:51 UTC+1, Abrimaal wrote:
>>
>> Please at least allow to display All files in the Load images window. 
>> This way panoramas that must be quickly corrected can be sent to another 
>> instance of Hugin
>> Right click .pto file -> Send to -> Hugin.
>>
>> Btw. filtering images by extension is not the best method, it excludes 
>> images without extension, or with extensions such as .jpg.bk
>> that could be created in mobile apps or other systems, and they are 
>> normal .jpg or .png files.
>> Take a look at the file header and the file type, for .jpg this is:
>> ÿØÿà JFIF 
>> The Windows command Findstr may be used to determine the file type.
>>
>> On Thursday, February 21, 2019 at 5:04:14 PM UTC+1, T. Modes wrote:
>>>
>>>
>>> @Bart
>>> Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel:
>>>>
>>>> What you're asking is (correct me if I'm wrong) the ability to import 
>>>> images from one project into another one. That is currently not supported 
>>>> without scripting I think. Still not the same as treating the PTO as an 
>>>> image though.
>>>>
>>> This is already possible (without scripting): in panorame editor: 
>>> File>Merge project
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/76a846cc-6fa7-41c1-b3c6-cbbe660cd69f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

It does not work in the 2019 beta 2 version, because the filter "All files" 
has been changed to "All images".
I typed:
*
"*"
*.*
"*.*"
in the filename field.
.pto files are among the images, but not accessible.



On Monday, February 25, 2019 at 6:06:29 PM UTC+1, Bart van Andel wrote:
>
> All the things you want are basically the job of a file manager. It isn't 
> reasonable to assume that all tools should be able to perform file manager 
> things. If you have images with a wrong extension, rename them.
>
> Having said that, if you want to show all files in any regular "Open File" 
> or "Save File" dialog in Windows, you can usually just enter "*" in the 
> "File name" field and hit enter. Just verified, this works in Hugin too. 
> Actually the drop down to the right of this file field already contains an 
> option for showing "All files (*)", both in Hugin 2018.0.0 and the current 
> 2019.0.0. I think we can conclude you've been served already a while ago ;-)
>
> On Thursday, 21 February 2019 17:56:51 UTC+1, Abrimaal wrote:
>>
>> Please at least allow to display All files in the Load images window. 
>> This way panoramas that must be quickly corrected can be sent to another 
>> instance of Hugin
>> Right click .pto file -> Send to -> Hugin.
>>
>> Btw. filtering images by extension is not the best method, it excludes 
>> images without extension, or with extensions such as .jpg.bk
>> that could be created in mobile apps or other systems, and they are 
>> normal .jpg or .png files.
>> Take a look at the file header and the file type, for .jpg this is:
>> ÿØÿà JFIF 
>> The Windows command Findstr may be used to determine the file type.
>>
>> On Thursday, February 21, 2019 at 5:04:14 PM UTC+1, T. Modes wrote:
>>>
>>>
>>> @Bart
>>> Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel:
>>>>
>>>> What you're asking is (correct me if I'm wrong) the ability to import 
>>>> images from one project into another one. That is currently not supported 
>>>> without scripting I think. Still not the same as treating the PTO as an 
>>>> image though.
>>>>
>>> This is already possible (without scripting): in panorame editor: 
>>> File>Merge project
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c5685424-cb01-4197-aa0d-dd5831064e37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

Please at least allow to display All files in the Load images window. 
This way panoramas that must be quickly corrected can be sent to another 
instance of Hugin
Right click .pto file -> Send to -> Hugin.

Btw. filtering images by extension is not the best method, it excludes 
images without extension, or with extensions such as .jpg.bk
that could be created in mobile apps or other systems, and they are normal 
.jpg or .png files.
Take a look at the file header and the file type, for .jpg this is:
ÿØÿà  JFIF 
The Windows command Findstr may be used to determine the file type.

On Thursday, February 21, 2019 at 5:04:14 PM UTC+1, T. Modes wrote:
>
>
> @Bart
> Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel:
>>
>> What you're asking is (correct me if I'm wrong) the ability to import 
>> images from one project into another one. That is currently not supported 
>> without scripting I think. Still not the same as treating the PTO as an 
>> image though.
>>
> This is already possible (without scripting): in panorame editor: 
> File>Merge project
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4412c0d6-1ca0-4933-8e1f-f4b0e34fedfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

[Abrimaal]

*In beta2 Pre-Release 2019.0.0.75168618c648 the problem has grown.*

There is no "All Files" filter in "Add Images". It means that it became 
impossible to right click a .pto file and open it in another instance of 
Hugin.
"Add Images" window is the fastest method for quick preview of a finished 
panorama, because it opens the folder, where the panoramas and .pto files 
are saved.
If the panorama did not look perfectly, it was very simple to send the .pto 
file to another Hugin instance and work on it without running around drives 
and folders.







On Monday, February 4, 2019 at 3:48:33 PM UTC+1, Abrimaal wrote:
>
> [image: hugin-could-not-decode-image-from-pto-file.png]
> While loading images from a .pto file, this error message is displayed.
> The images have not been moved, not renamed, the are still in the same 
> folder as the .pto file.
> The filenames and paths to images stored in the .pto file did not change.
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/fef6ba57-ecea-4837-af66-e4a95fc10ff4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Installed hugin now what?

[Abrimaal]

Although the default installation folder in Windows is "C:\Program Files", 
it is not recommended to install any third party software on C:, except 
drivers, codecs, fonts and other shared files.
Files on C: are often protected by Windows in various ways, 
Better to install software on a different hard drive or partition. The user 
can access all files, the system is more efficient and easier to manage.

When Hugin starts, it displays useful hints, leave them active.

On Wednesday, February 6, 2019 at 8:44:32 AM UTC+1, David Reichard wrote:
>
> I a new user and just installed 2018.0.0. But:
>
>1. How do I start it? I type "hugin" in windows search bar and only 
>the installer shows up. I go to C:\Program Files\Hugin\bin and try to 
> guess 
>which exe to run:
>   1. hugin.exe: I get hugin splash screen then a "Debug report 
>   "hugin"" screen. No error message. I close the Debug screen and the 
> splash 
>   screen goes away leaving nothing.
>   2. hugin_stich_project.exe: screen asks me to browse the to 
>   location of Project Files. But I haven't started a project or even the 
>   hugin program so I don't think I have any project files yet.
>   3. PTBatcherGUI.exe: Opens nice Batch Processor GUI but I have no 
>   idea what to do. 
>2. Is there a very basic tutorial for Windows? Like which exe to run 
>and what to do next?
>3. Is this the best place for questions like this?
>
> Thanks in advance.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b1801a7f-4f10-410e-8ade-3a6e80f5df28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Could not decode image error in 2019.0 beta 1

[Abrimaal]

Well, a .doc file is formatted for printing, but it's a shame that 
Photoshop cannot open a plain .txt file and display the text, to copy and 
paste to an image.
.pto files are also plain text files and they can be simply opened by "Add 
images" button.
The same way images can be opened with File/Open menu. Reading a file 
header, the program will distinguish the file type.

This is not new behavior of this version, but it is definitely an 
unexploited potential worth introducing,
just like a few other features and repeating bugs I described here:
https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/hugin-ptx/eMSGRxdrpjM

Using the new version for a few days I haven't noticed any progress 
comparing to the 2018 release.
.jpg images with different color profiles still cannot be stitched, 
the batch processor icon still locks the taskbar,
horizontal lines are not detected,
.tif workfiles are not cleaned at exit if they could not be deleted after 
finishing a panorama,
the editor background is white, what makes manual work with night scenes 
impossible,

Zoom in the mask editor has been introduced,* thanks a lot* for the useful 
feature.  
How could it be improved? Zooming by mouse wheel is what the intuition 
suggests.

A new behavior I noticed in the 2019 beta, that "Don't save project" is not 
working until we select "New"
For example when we open an incorrect image and we don't want to save this 
project.

[image: dont-save-not-working-hugin-2019-0-beta.png]





On Wednesday, February 6, 2019 at 2:02:33 PM UTC+1, zarl wrote:
>
> The subject suggests that this is a new behaviour in the latest version, 
> so did you try that earlier and what happend with earlier versions of hugin?
>
> From what you write I get the feeling that you want to merge projects, or 
> what do you try to do? 
>
> Carl
>
> ps.
> A .pto is a project file and thus not digested via an "add image(s)" 
> command. Try opening a .doc (containing image names) in Photoshop...
>
> On Monday, February 4, 2019 at 7:27:47 PM UTC+1, Abrimaal wrote:
>>
>> PTO files contain names and paths of images. This is all what is needed 
>> to open images.
>> With one click multiple images can be opened to:
>> correct a panorama
>> add images to these already open, to create a new panorama.
>>
>> File paths and names are everything what is needed to merge images+pto or 
>> pto+pto+pto...
>> The rest of .pto file, projection, exposure data may be discarded.
>>
>>
>> On Monday, February 4, 2019 at 4:14:08 PM UTC+1, Luís Henrique Camargo 
>> Quiroz wrote:
>>>
>>>
>>>   By the message I understand that Hugin is trying to open an image file 
>>> named 20180317_1735_c26-3s.pto  
>>>   Please check if the project file is not included as image. The 
>>> extension, ".pto", does not correspond to an image file ;)
>>>
>>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/dbf1878a-0910-4aca-b073-45673eb691b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Could not decode image error in 2019.0 beta 1

[Abrimaal]

PTO files contain names and paths of images. This is all what is needed to 
open images.
With one click multiple images can be opened to:
correct a panorama
add images to these already open, to create a new panorama.

File paths and names are everything what is needed to merge images+pto or 
pto+pto+pto...
The rest of .pto file, projection, exposure data may be discarded.


On Monday, February 4, 2019 at 4:14:08 PM UTC+1, Luís Henrique Camargo 
Quiroz wrote:
>
>
>   By the message I understand that Hugin is trying to open an image file 
> named 20180317_1735_c26-3s.pto  
>   Please check if the project file is not included as image. The 
> extension, ".pto", does not correspond to an image file ;)
>
>  
>
> Em seg, 4 de fev de 2019 às 12:48, Abrimaal > 
> escreveu:
>
>> [image: hugin-could-not-decode-image-from-pto-file.png]
>> While loading images from a .pto file, this error message is displayed.
>> The images have not been moved, not renamed, the are still in the same 
>> folder as the .pto file.
>> The filenames and paths to images stored in the .pto file did not change.
>>
>>
>> -- 
>> 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/af55809f-cb74-4342-9b72-b3e684514a76%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/hugin-ptx/af55809f-cb74-4342-9b72-b3e684514a76%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> -- 
> Luis Henrique Camargo Quiroz
> http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
> http://panoramaslh.net/
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e8a214f7-42b5-4c87-af65-88383ecee0fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Could not decode image error in 2019.0 beta 1

[Abrimaal]

[image: hugin-could-not-decode-image-from-pto-file.png]
While loading images from a .pto file, this error message is displayed.
The images have not been moved, not renamed, the are still in the same 
folder as the .pto file.
The filenames and paths to images stored in the .pto file did not change.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/af55809f-cb74-4342-9b72-b3e684514a76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: How to stitch a map divided into 32 scans...

[Abrimaal]

The problem is that there is no rectangular (planar) projection available 
in Hugin. 
It is different from rectilinear.
Rectilinear projection preserves straight lines, but does not preserve 
straight angles.
Rectangular does not preserve areas, but preserves straight lines and 
angles.
The adjustment of partial images is based on control points, as always, 
but it is done by rotating and resizing images. 
Field of view is discarded because scans may have different pixel size and 
they are not related to any lens field of view.

If you have an Android device, you may try Bimostitch or Mapstitch, that 
use the planar (rectangular) projection.
Bimostitch is better because it does not blend images (you can select 
between matching or blending).

For Windows you may try ArcSoft Scan-n-Stitch Deluxe, but it is very 
limited and outdated.
All images must be the same pixel sizes and it often fails even with 2 rows 
map, because correction of misplaced control points is not available in 
this software.


On Friday, December 14, 2018 at 11:15:02 AM UTC+1, Edward Carnby wrote:
>
> Hi all,
> I've used Hugin for some time and I encounter no problem stitching old 
> maps I scanned from libraries. They usually were divided into four or six 
> parts. I have now to stitch a very large map of Italy divided into 32 scans 
> (eight rows, four columns). I followed the tutorial (stitching flat scanned 
> images) but I wasn't able to achieve a decent result. The optimizer always 
> stitch it in a bad way. I tried to stitch some parts and than stitch them 
> again with others but the result was pretty unacceptable because of bad 
> alignment. Besides I have a Win 64 system and cannot install autopano sift 
> C. Hints are appreciated.
> Best regards.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c194acad-6521-422d-a096-8c2fa8fa36b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Dark UI for Hugin / skins

[Abrimaal]

I have just read the topic on aligning stars. I sometimes work with night 
panoramas, where the I add and adjust control points and masks manually.
Changing the whole Windows theme is uncomfortable, when working with other 
applications at once (image viewer, Windows explorer...)
Is it easy to create a dark skin interface for Hugin? In what software 
could I try doing this?
or maybe such skins already exist?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/bf2199c6-1874-40a0-960f-f2d306ebbb23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Skins for Hugin / dark background

[Abrimaal]

I have just read the topic on aligning stars. I sometimes work with night 
panoramas, where the I add and adjust control points and masks manually.
Changing the whole Windows theme is uncomfortable, when working with other 
applications at once (image viewer, Windows explorer...)
Is it easy to create a dark skin interface for Hugin? In what software 
could I try doing this?


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/13c78b45-1ec8-49f5-886a-ffceb4f3d009%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Adaptive adjustment of image sizes

[Abrimaal]

 Should I exclude the 1st image in the simple mode and optimize? How? I 
cannot find in the menu how to adjust dimensions (field of view) of the 2nd 
image.

> You need to optimize hfov of the second image only in this case. 
>
So use user defined optimization and optimize v,y,p,r of second image only.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d8081843-528a-4f88-b3c4-7ce5807e1008%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Adaptive adjustment of image sizes

[Abrimaal]

I was trying to stitch two photos of the same object. One image was large 
about 5000x3200 px, the other one was smaller 1200x800. 
The first one conatined lens data, the other did not.

The detector did not find any control points, so I placed them manually 
where they should be.

After optimization (y,v,p,r) the 2nd image was still much smaller. So I 
copied the field of view from the 1st image to the 2nd.
However they still varied in size, so there were many attempts to put a 
correct value there.
Finally the panorama was rendered correctly.

Another example - one image is original from a camera, the other one is 
cropped from the original, both with EXIF data.
The field of view is of both images is set to the same value, but the 
cropped image is much larger.

Now questions:

Is there a way to calculate the field of view by comparing the distance 
between control points? (rectilinear projection with position anchor, 
centered)
Just as one of images can be set as anchor for position and exposure, to 
set one of images as the base for field of view?
Can the control point detector (temporarily, optionally, if CPs not found) 
resize all images to the same size to find control points?

I can add that a mobile app can stitch images of various size and aspect if 
it only finds common points. I use this for merging two or more exposures 
or applied filters.
Even if images vary in size, they are almost perfectly stitched, the 
blurred (overlaid) details can be corrected in Hugin by masking.



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/751bd003-a587-4e52-a610-cbd837a13197%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Hugin expects... Discard color ICC profiles

[Abrimaal]

Image editors save files with various color profiles, black-scaled or so... 
Are the images loaded to Hugin converted to bitmaps (or .tif) for 
processing?
If yes, there should be no problem to stitch images even in different 
formats - jpg + png, jpg + bmp, jpg + tif, any that Hugin can open. Not to 
mention .jpg + .jpg (any colour profile). 
Even if there are slight differences in colours in various color profiles, 
they can be simply discarded. Hugin can blend them perfectly.

First is to define the base profile, how the images are converted to 
bitmaps, then it will be possible to work with all supported image formats, 
discarding the color profiles.

It resembles work with Virtual Dub, a simple, but powerful video editor. 
When trying to merge two or more video files into one, and videos framerate 
differ by .1s from the same camera, one file cannot be appended to the 
other. User converts and tries again. Now the audio streams are different. 
128 vs 256 kb/s. VDub will not pass. Ok, user converts. Third attempt. One 
stream is variable bitrate, the other is constant. Will not pass. And so, a 
simple operation that can be done in 15 minutes extends to long hours. Not 
to mention, it works only with .avi and all frames must be the same size, 
the same color profile and cannot contain EXIF data. :( 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b42536d9-cd36-4fde-a68c-ebe7b92d126e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Settings: Line detector: Minimal distance between vertical lines

[Abrimaal]

The line detector often places multiple vertical lines on traffic signs, 
antennas, trees, because they are straight, but very rarely vertical.
They are easy to detect because of high contrast and they are usually 
detected as the first lines.
To minimize the risk of multiplication of the same error, placing lines on 
objects arranged at similar angle as the first detected line, 

I suggest introducing a used-defined minimal distance between two lines, in 
the application settings. 
The distance could be defined relatively, as a percentage of a single image 
width.
I think 5 - 10% will be good not to place vertical lines on the same thin 
object. 

Repeating "Add vertical lines" from the panorama editor does not skip 
already existing lines, just duplicates them on the same objects. 

If any way to define the distance already exists, could you tell me what 
parameter to use?

Below two examples of vertical lines placed on the same object, vertical or 
not

Example 1: 
The detector placed the first line on the building edge and 4 lines on the 
same window. 
It did not detect the second edge, because of bricks, what is obvious. The 
individual bricks are short. All together form a long straight line,
If the distance threshold was introduced, it would search for lines in the 
darker side of the building. 

Image 2: 
The detector placed 3 lines on the same antenna that is never vertical and 
two lines in the dark part of the building.
it did not detect the other high contrast building on the other side of the 
street. Because it was not parallel to the antenna?
It did not also detect the chimney that is a vertical object and very high 
contrast, because it already detected 5 lines.
In 60% the straightened image will be not straight. 
If the distance is introduced, the probability of error will go down to 20% 
(1 line on the antenna). Easy to delete manually.




-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/66888aa8-5357-4cea-9415-46135d47edb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: if ... then ... Opening projects and images from Windows Explorer

[Abrimaal]

if (if ... then) failed else
Two big buttons one above the other

[ Open files ] = opens images and projects
[ Add images ] = add images to a blank or an existing project

On Tuesday, January 30, 2018 at 11:18:37 PM UTC+1, GnomeNomad wrote:
>
>
>
> On January 30, 2018 12:14:56 PM HST, Frederic Da Vitoria <
> davi...@gmail.com > wrote: 
> >2018-01-30 21:09 GMT+01:00 Abrimaal <abri...@wp.pl >: 
> > 
> >> Yes, after some work I also think that the rearrangement would make 
> >too 
> >> much mess. At least opening projects from the main button could open 
> >them 
> >> (instead of displaying error) when "all file types are selected". 
> >> 
> >> On Monday, January 29, 2018 at 8:28:44 PM UTC+1, T. Modes wrote: 
> >>> 
> >>> Sorry, but I find this too confusing. You are mixing loading project 
> >and 
> >>> adding images/other projects to open projects. These are 2 different 
> >things 
> >>> and should be separated. 
> >>> 
> >> 
> > ... or the "All files" option could be entirely removed. Or is there a 
> > situation where it would be useful? 
>
> Is there any other Hugin project file format, or can Hugin open projects 
> from other panorama generators? If no to either, I vote to remove the 'All 
> files' option. 
>
> David W. Jones 
> gnome...@gmail.com  
> wandering the landscape of god 
> http://dancingtreefrog.com 
>
> Sent from my Android device with K-9 Mail. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b20b47f4-04af-4c61-8237-e2f6f3f509c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: if ... then ... Opening projects and images from Windows Explorer

[Abrimaal]

Yes, after some work I also think that the rearrangement would make too 
much mess. At least opening projects from the main button could open them 
(instead of displaying error) when "all file types are selected". 

On Monday, January 29, 2018 at 8:28:44 PM UTC+1, T. Modes wrote:
>
>
>
> Am Samstag, 27. Januar 2018 18:58:51 UTC+1 schrieb Abrimaal:
>>
>> How to distinguish between Open project and Merge / Add images to project:
>>
>> On a blank screen, big button clicked:
>> - Selecting a single .pto file does NEW, Open Project
>> - Selecting more than one .pto files does NEW,  Open and merge projects
>> - Selecting a .pto file and images does NEW, Open project, add images to 
>> project
>> - Selecting images only may Add images as it works currently or do NEW, 
>> Open images. Decision belongs to you. 
>>
> Sorry, but I find this too confusing. You are mixing loading project and 
> adding images/other projects to open projects. These are 2 different things 
> and should be separated.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/71a95a17-8835-40c7--7bd65a8c51a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: if ... then ... Opening projects and images from Windows Explorer

[Abrimaal]

Opinions are various. At least allowing Hugin to load projects with the big 
button will simplify the work.

How to distinguish between Open project and Merge / Add images to project:

On a blank screen, big button clicked:
- Selecting a single .pto file does NEW, Open Project
- Selecting more than one .pto files does NEW,  Open and merge projects
- Selecting a .pto file and images does NEW, Open project, add images to 
project
- Selecting images only may Add images as it works currently or do NEW, 
Open images. Decision belongs to you. 

While work, selection from menu:
Selecting from menu File/Add (not using the big button) will not do New, 
but it will allow to add images and projects to the currently open project.



On Saturday, January 27, 2018 at 9:11:15 AM UTC+1, T. Modes wrote:
>
>
>
> Am Samstag, 27. Januar 2018 07:03:48 UTC+1 schrieb Abrimaal:
>>
>> When we click [ Add Images ] button in the simple interface, we can see 
>> both images and .pto projects,
>> but we cannot open a project from here, because an error "Could not 
>> decode image" is displayed. (attachment 1)
>>
>> When we want to open an existing project from the menu [ Open ], you 
>> don't see what you open, because images are not displayed. (attachment 2)
>> (let's assume that images and projects are in the same folder)
>>
> If Hugin displays .pto projects in Add images, why not to open projects 
>> from here and rename the button to [ Open files ] or [ Load files ]
>> It looks simple to detect the header '# hugin project file' and jump to 
>> project opening routine. At least simple compared to all calculations 
>> performed by Hugin :)
>>
>
> This happens only because you set the file filter in the add images dialog 
> to "all files" instead of the default "all image file". (But you didn't 
> this in the load project.)
>
> It will allow the user to start a new project, load images, open projects, 
>> add images to a project and merge projects with a single button.
>>
> How do you want then to distinguish between open project and merge 
> project? And how should a new project started in this context?
> Sorry, but this is more then confuse.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a245d758-6691-4fee-b135-1276f99d59f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin 2018.0 beta1

[Abrimaal]

Thanks. I'm testing it right now. What features are new in the 2018 beta to 
be tested?
The Windows installer does not contain enblend and enfuse, fortunately I 
made a backup of the 2017 version, that was removed during the installation 
(it should never be removed, I still keep the 2014 beta version, because it 
detects horizontal lines :) ).
I have reported a new bug. When Windows search box was used to find an 
image, the Assistant wants to save in search results, not in the folder. 


On Tuesday, December 19, 2017 at 8:27:06 AM UTC+1, Giulio wrote:
>
> Il giorno lunedì 18 dicembre 2017 20:09:56 UTC+1, T. Modes ha scritto:
>>
>> Hi Giulio,
>>
>> Am Montag, 18. Dezember 2017 17:48:36 UTC+1 schrieb Giulio:
>>>
>>> I have a little feature suggestion: could you please change in 
>>> hugin1/hugin/config_defaults.h , line "%firstimage - %lastimage" , with a 
>>> default file name without the space in the middle? "%firstimage-%lastimage"
>>>
>> This setting can already be changed in the preferences. No need to change 
>> this in the source.
>>
>
> Thank you, yes i know but i thought that without space it could be a 
> better default.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/99e8d550-000e-467f-9020-dcf9b99821f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin halves my DPI from 300 to 150 causing loss of quality. How do I change this?

[Abrimaal]

Do it only once and forever. In File / Preferences / Assistant / 
Downscale final pano [ 100 ] percent of the max width. 
The panoramas will never downsized again (until you don't want to).

On Tuesday, May 13, 2014 at 6:57:53 AM UTC+2, tda...@gmail.com wrote:
>
> I scanned an A2 sized electrical schematic with an A4 scanner in 12 
> pieces, and tried out Hugin to stitch them together. The result is very 
> promising but there is one problem - the DPI has been changed from 300dpi 
> to 150dpi resulting in a smaller image and some loss of quality.
>
> Of course I have read http://hugin.sourceforge.net/docs/manual/PPI.html 
> but before anyone starts telling me how this does not affect image quality 
> etc please view the attached files and see for yourself how the quality has 
> been degraded.
>
> I did try changing the DPI setting of the file back to 300dpi using Gimp 
> but this made no difference.
>
> How can I tell Hugin (or its processor program) NOT to change the 
> resolution down to 150dpi and rather keep it at 300dpi?
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a0f8b640-df44-4344-a8cc-4d15c9e940a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Partial Stitching

[Abrimaal]

I am not sure if I understood your question. You want to replace two photos 
and save a new 62 image panorama.

First Save as a new project. Very important. 

Go to the Editor, remove the 2 photos you don't need.
Add the new 2 photos
Control points: for two photos you can add them manually (and fine tune). 
Running a detector will duplicate already existing points.

Now you can do it in a few ways

1. Full Align - it will change the final image proportions, exposures, 
possibly even the projection.
2. Optimize positions - the new images will take the place of these 
removed. The exposures and projection will remain unchanged. But the final 
image may be different.
3. Stitch the previous 62-image panorama with the 2 new photos. Mask the 
areas where the previous two images were. 
For this operation, the 62 image panorama must be saved in 100% size.  
4. If the 62 image panorama was resized to X percent of the original, 
resize the two photos to the same percentage.

There are many more possibilities. 
For example you can open the .pto file in a text editor, replace the 
filenames of these 2 photos, save as a new project and open it in Hugin.
Now you should only adjust the control points, optimize and stitch a new 
panorama.



On Saturday, December 23, 2017 at 12:50:56 AM UTC+1, Martí Mendez wrote:
>
> Dear friends,
>
> Is it possible to send commands to stich one single image in a large 
> panorama?. I have a 62 images panorama and I want to replace 2 of the 
> images with new ones, I want to know if is possible launch a partial 
> process to stich this 2 images instead to launch the whole process again.
>
> Regards
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9b1effc0-dcff-4ca8-b6dc-3d184b6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Hugin - Build for android ndk

[Abrimaal]

If ever it happens. Maybe a marginal detail, but very important when working 
with photos on Android and PC.
Please respect the filenames when saving. The most of Android apps save files 
with random names. There are only a few exceptions that append a suffix to the 
original filename.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/24fd890f-6fdf-4a98-b4a0-2b5b93492846%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Problem with deformation when stitching several scanned images

[Abrimaal]

The problem is that Hugin does not offer undistorted projection, suitable 
for scanned documents. 
Thy this: 
00. Before all, note down the dimensions in pixels of each partial image.
01. Load all images to Hugin
02. Set the projection to rectilinear 
03. Go to Panorama Editor, Control Points tab
04. Open the same images in both view panels
05. Add two horizontal and two vertical lines. Click near the top left in 
the first panel and near the top right in the 2nd panel. 
06. Now you have the first horizontal line. Correct the numeric values to 
x=0, y=0 and x=0, y=image width.
07. Do the same for the 2nd horizontal line at the bottom and two vertical 
lines. Then repeat the steps for all images.
08. Go to Photos tab, create control points using the Hugin CPFind.
09. Go back to the main window, save the project. This is important is 
something goes wrong, you can always go back (you can use Undo too, but 
saving is safer)
10. Back to the Editor. There are several metods of optimizing the 
geometrics. Try the first one (positions, incremental). If it looks not 
perfectly, undo and try another method. 
11. You can save every method as a panorama, then compare the images. I 
recommend this to compare the images in full screen viewer.
11. Optimizing photometrics is optional, usable only when the images were 
scanned with auto exposition, auto fix, auto contrast etc. 

This way I stitched some maps, but it took a lot of time and work. Easier 
to go to a printing service, they have A0 scanners there. 


On Saturday, August 5, 2017 at 8:00:58 AM UTC+2, abou...@eng.ucsd.edu wrote:
>
> Hi, 
>
> I have downloaded Hugin cause I try to find an equivalent of the Photoshop 
> Automate --> Automerge option to stitch several scanned images together, 
> but when I am doing it with Hugin, the final image is deformed (as it was 
> flatten see the comparison with Photoshop below), I searched a little but I 
> didn't find how to correct that (sorry I am also a beginner). If someone 
> has an idea, suggestion or the answer that would help me a lot thank you! 
>
> Here are the final images created with Hugin (first one) and Photoshop 
> (second one) to see the point: 
>
>
> 
>
>
> 
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ab0abbdd-6648-4b59-80ac-335585fcf5c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Hugin 2017.0 released

[Abrimaal]

It is possible that the image viewer (FastStone or Machinery Explorer) is 
reading the file and creating a thumbnail in the same time. The .tif file 
can be easily deleted after it is displayed it the viewer. They .tif file 
must be deleted manually, if the user forgets, about 50 MB file remains in 
the folder. 
The files/folders are not connected to dropbox.
 
>If the problem is that the image viewer prevents the file from being 
>deleted for a fraction of a second - and by reading the file triggers 
>the virus scanner and the automatic indexing service which prevent a 
>deletion of the file. Or if the problem is that dropbox hinders the file 
>from being deleted while it is uploaded the following can be done: 

On Tuesday, July 4, 2017 at 7:36:03 AM UTC+2, Gunter Königsmann wrote:
>
>
>
> On 03.07.2017 23:45, Abrimaal wrote: 
> > First of all, thanks a lot for single photo straightening mode. It saves 
> > a lot of time and manual work. 
> > There is a small problem that can grow into gigabytes. (Windows) 
> > The batch processor does not remove temporary .tif files from single 
> > photos, but successfully removes them when stitching a multi-file 
> panorama. 
> > It happens only when the folder with photos is open in another image 
> > viewer (it is always open in another image viewer, because everybody 
> > knows how little a user can do in Windows Explorer). 
> > 
> If the problem is that the image viewer prevents the file from being 
> deleted for a fraction of a second - and by reading the file triggers 
> the virus scanner and the automatic indexing service which prevent a 
> deletion of the file. Or if the problem is that dropbox hinders the file 
> from being deleted while it is uploaded the following can be done: 
>
>   - try to delete the file 
>   - look if it is actually deleted 
>   - if not: wait a second, try to delete it again and if that fails 
> another time: give up. 
>
> TortoiseSVN and wxMaxima do so in a few places. 
>
> If the image viewer keeps the files open indefinitely I don't think 
> hugin can work around this: For some reason windows doesn't let you 
> delete mark files that are currently open in any application as deleted 
> (which prevents a cleanup in this case). On Linux, Android and Mac Os 
> you can ask the operating system to delete opened files instead: They 
> will instantly disappear from the directory, but the disk space they 
> occupy will only be unallocated when the file is closed by all 
> applications. 
>
> In theory on windows one could tell hugin to retry deleting all 
> no-more-used files every few seconds until that try succeeds and to stay 
> open as long as there still are temporary files left. But no other 
> application I know does do that. 
>
> Kind regards, 
>
>Gunter. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/dcdb699a-22ac-4b28-a786-3de2f385354c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin 2017.0 released

[Abrimaal]

First of all, thanks a lot for single photo straightening mode. It saves a 
lot of time and manual work. 
There is a small problem that can grow into gigabytes. (Windows)
The batch processor does not remove temporary .tif files from single 
photos, but successfully removes them when stitching a multi-file panorama. 
It happens only when the folder with photos is open in another image viewer 
(it is always open in another image viewer, because everybody knows how 
little a user can do in Windows Explorer). 


On Saturday, July 1, 2017 at 8:49:08 AM UTC+2, T. Modes wrote:
>
> Hi all,
>
> today we are releasing Hugin 2017.0.
>
> Changes since 2016.2.0
> The version 2017.0 is mainly a bug fix release. The biggest fixes regard:
> * Several fixes for working with HDR images (display in GUI, photometric 
> optimizer, handling of under/over exposured pixels in merging code).
> * Fixes handling of masks in cpfind when images needs remapping for cp 
> finding.
> * Sometimes unsaved changes were disregarded without asking the user (e.g. 
> when loading a project via the recently used projects list). Unsaved 
> changes should now always require user confirmation.
>
> Besides the bug fixes some smaller improvements have been implemented.
> * Optimizer tabs uses now checkboxes instead of bold underlined font for 
> marking of variables to be optimized.
> * Use wxWidgets help windows instead of default browser (Linux only, 
> this provides table of content, index and full text search in help files).
> * Added special assistant variant for single image projects.
> * Display of final panorama dimensions on stitcher tab.
> * Extended the user defined output sequences:
>** The shipped user defined output sequences are exposed in the GUI as 
> own sub-menu.
>** Added some more user defined output sequences (layered TIFF, cube 
> faces).
>** Added new placeholder %sourceimage% to user defined output sequence.
>
> Source tarball can be downloaded
> at sourceforge: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/hugin-2017.0.tar.bz2/download
> or at launchpad: 
> https://launchpad.net/hugin/2017.0/2017.0/+download/hugin-2017.0.tar.bz2
>
> Verify its checksums:
> md5: 3b49a905da8ee395774347ee6b3903b0  hugin-2017.0.tar.bz2
> sha1: 4ba7f5bf5afdadbea9cf10d15aa14e644ef94ed3  hugin-2017.0.tar.bz2
>
> This is a source code release. 
> (The release corresponds to changeset eac5e8cc546e in our repository, 
> which is also tagged as 2017.0.0).
>
> Users communities produce executables for their respective platforms. 
> Please announce them here.
> Currently the following versions were made available for download:
> MacOS: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0.dmg/download
>  
> (md5: 8bc4a503021fbca143b5904c53ed50d6)
> Win32: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0-win32.msi/download
>  
> (md5: ec86c9090af7b8c19f41c40cffa33721)
> Win64: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0-win64.msi/download
>  
> (md5: 434db5bb989a02b528eeb613ff0fe729)
>
>
> Upgrading from previous versions of Hugin should be seamless. If you do 
> have problems with old settings, these can be reset in the Preferences 
> window by clicking 'Load defaults'.
>
> Know issues
> Hugin does not run native on Wayland because of a bug in the underlying 
> wxWidgets library. 
> The source code contains a workaround which forces the usage of the 
> XWayland emulation layer. 
> This workaround has be activated during compiling by adding 
> -DUSE_GDKBACKEND_X11=on to the CMake command.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/dcd3e1da-31c4-484c-93d3-aecdcb67ab53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Default output name

[Abrimaal]

I will add from myself, what cannot be set up in the filename preferences 
yet.
To abbreviate long suffixes such as "blended_fused" and projection names 
(predefined or defined by a user).
It took a long time to guess which one is which. I am still not sure when I 
see "_fused" - was it composed from a stack or from any arrangement?. 
In the editor there are options to make panoramas "from stack" and "from 
any arrangement", in the saved files there are suffixes "_fused" and 
"_blended_fused".
The suffixes make filenames undesirably long.

The proposal is to introduce alternative suffixes "_stk" and "_any".

Projection names. Fortunately almost each of the projections begins with a 
different letter.
I use this scheme (everybody may use a different) "lastfile-pah-6c" what 
means
pah = panorama created by Hugin, 6 = number of images, c = cylindrical 
projection (I add it manually).
The most of projections can be one or two characters added automatically, e 
for equirectangular, m for mercator, p for panini, r for rectilinear, f for 
fisheye 
for other projections the suffix may be two letters, st for stereographic, 
th for thoby...
or different single letters like u for Miller, l for albers, q for 
equisolid etc.


On Monday, June 19, 2017 at 9:38:26 AM UTC+2, Groogle wrote:
>
> On Sunday, 18 June 2017 at 22:52:25 -0700, Fotografia wrote: 
> > I would like to know it is possible to choose a default output file name 
> > without spaces. 
> > 
> > e.g. default is IMG_8197 - IMG_8201.tif 
> > 
> > I think without spaces imho it would be a better default: 
> > IMG_8197-IMG_8201.tif 
>
> Yes, that's what I do.  Go to File->Preferences->Filenames. 
>
> Greg 
> -- 
> Sent from my desktop computer. 
> Finger groo...@gmail.com  for PGP public key. 
> See complete headers for address and phone numbers. 
> This message is digitally signed.  If your Microsoft mail program 
> reports problems, please read http://lemis.com/broken-MUA 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5ec1141b-3089-483a-b6e4-4f6d26044952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2017.0 rc1 released

[Abrimaal]

Windows 64bit:
I installed the 2017.0.rc1 version in a different folder than the stable 
version 2016.x. The installer removed the stable version what should not 
happen, but it did not remove older (2014 and 2015) versions installed in 
different folders. The 2014.0.0.5 version is a "special" release that 
detects horizontal lines instead of vertical and I use it sometimes. 
Fortunately it was not removed by the installer.

This message is displayed when Hugin finds unconnected images. 

[code]The assistant could not find vertical lines. Please add vertical 
lines in the panorama editor and optimize the project manually.[/code]

Normally there was a message "Hugin found unconnected images"



On Monday, June 5, 2017 at 11:01:50 AM UTC+2, Bruno Postle wrote:
>
> There are fedora packages here for this rc1 release: 
> http://copr.fedorainfracloud.org/coprs/bpostle/panorama/ 
>
> These packages have been built with the Wayland workaround as described 
> below. 
>
> This is an important note for other packagers: various bugs in current 
> versions of wxwidgets mean that a vanilla Hugin build won't run on Linux 
> systems with a Wayland desktop. If your packages are potentially used with 
> Wayland, you must enable the build time option described below. At some 
> point in the future wxwidgets will get fixed and then this advice can be 
> ignored. 
>
>
> On 2 June 2017 15:55:27 BST, Thomas Modes  wrote: 
> > 
> >today we are releasing release candidate 1 of Hugin 2017.0. 
>
> >A first draft of release notes can be found at 
> >http://hugin.sourceforge.net/releases/2017.0.0/en.shtml 
>
> >Know issues 
> >Hugin does not run native on Wayland because of a bug in the underlying 
> >wxWidgets library. 
> >The source code contains a workaround which forces the usage of the 
> >XWayland emulation layer. 
> >This workaround has be activated during compiling (add 
> >-DUSE_GDKBACKEND_X11=on the the CMake command) 
>
> -- 
> Bruno 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/780de0a1-a8bd-45a4-bfd7-0cc7bab6481d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Newbie: Hugin - Fixing horizontal lines and general advice on panoramic stitch

[Abrimaal]

It depends from the point of view. 
In the example above the buildings are in perspective, the object in the 
middle is the street. Vertical lines are necessary, but horizontal are not 
desired.
The projection is Panini general, but it can be also cylindrical, Mercator 
or architectural - it depends from the distance from where the photos were 
taken. 

In the example below the building is in the middle and the projection is 
rectilinear. Horizontal lines were added only on the front wall. No 
horizontal lines on the other buildings, because it would cause enormous 
stretch. To optimize you should try "positions", "positions and view" or 
"positions, view and barrel" - which of them looks the best. The last one 
is used for photos taken with wide angle. 







One more hint - do not add horizontal lines at the bottom of the buildings, 
because streets are not straight, not parallel to the buildings.

example photo 




> "Satisfying": do you mean that without the horizontal lines, they are 
> less than satisfactory? 
>
> What I am wondering is: do the horizontal lines change anything? Or 
> would the result be just as good without the horizontal lines? 
>
> -- 
> Frederic Da Vitoria 
> (davitof) 
>
> Membre de l'April - « promouvoir et défendre le logiciel libre » - 
> http://www.april.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2b95acc3-5217-486c-bf75-783a1bbaa8f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Newbie: Hugin - Fixing horizontal lines and general advice on panoramic stitch

[Abrimaal]

I have not tried with landscapes, but the results with straightening 
architecture are satisfying.

On Tuesday, June 6, 2017 at 10:35:03 PM UTC+2, Frederic Da Vitoria wrote:
>
> 2017-06-06 22:29 GMT+02:00 Abrimaal <abri...@wp.pl >:
>
>> I can only add that detection of horizontal lines require some boring 
>> work what could be easily done by the program.
>>
>> Now you have to:
>> rotate all the images 90 deg (or the final panorama)
>> detect vertical lines
>> rotate the images back
>> change alignment of every line from vertical to horizontal
>>
>> It could be easily performed by
>> "Detect horizontal lines" 
>> or
>> "Detect vertical and horizontal lines"
>> but... I am not a programmer and I can dream only.
>>
>
> Since you have tried: did this improve the end result?
>
> -- 
> Frederic Da Vitoria
> (davitof)
>
> Membre de l'April - « promouvoir et défendre le logiciel libre » - 
> http://www.april.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/33afa17a-2a9d-45af-b7de-012d27a15212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Newbie: Hugin - Fixing horizontal lines and general advice on panoramic stitch

[Abrimaal]

I can only add that detection of horizontal lines require some boring work 
what could be easily done by the program.

Now you have to:
rotate all the images 90 deg (or the final panorama)
detect vertical lines
rotate the images back
change alignment of every line from vertical to horizontal

It could be easily performed by
"Detect horizontal lines" 
or
"Detect vertical and horizontal lines"
but... I am not a programmer and I can dream only.

On Saturday, June 3, 2017 at 3:38:47 PM UTC+2, Stephen Hartley wrote:
>
> Total newbie question here, thanks in advance for any tips on how to 
> improve my first hugin stitch.  Taken using a tripod and rotating ball 
> head, with standard rectilinear lens. No effort was made to rotate around 
> the no-parallax point, I don't know how significant this is for my pano?
>
> Source jpegs:
>
> 1 
> 2 
> 3 
> 4 
> 5 
>
>
> Stitched with Hugin 2016.2.0.be8da0221960 on Mac.  
>
> Spent a day experimenting with hugin, and this is my best result: output 
>  using this 
> pto project file. 
> 
>
>
> Could anyone more experienced give me some pointers on how to fix the 
> following:
>
>
>
>1. Horizon line, particularly at the top of the sea - I added a 
>horizontal line but this has caused the whole image to slant towards the 
>left.
>2. Areas of yellow paving have curved edges.  Again, these should be 
>horizontal, I added a horizontal line, but this does not seem to have had 
>the desired effect - the edges should be parallel to the horizontal edges 
>(top and bottom) of the image.
>3. Four noticeable stitching artefacts: two on the grey railings 
>(fence) in front of the black car, one on the bicycle path, immediately to 
>the left of the painting of the bicycle wheel, and again on the sea 
> horizon 
>line, quite a bump about a quarter of the way into the image from the left 
>edge.  I struggled to add more manual control points for the sea joint and 
>wonder if this might be causing the problem, if so, any known workaround?
>
>
> Thanks in advance for your help and advice,
>
> Steve
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/50bf7b3f-fe02-4343-915c-9140b46e016f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Newbie: Hugin - Fixing horizontal lines and general advice on panoramic stitch

[Abrimaal]

I can only add that detection of horizontal lines require some boring work 
what could be easily done by the program.

Now you have to:
rotate all the images 90 deg (or the final panorama)
detect vertical lines
rotate the images back
change alignment of every line from vertical to horizontal

It could be easily performed by
"Detect and horizontal lines" 
or
"Detect vertical and horizontal lines"
but... I am not a programmer and I can dream only.


On Saturday, June 3, 2017 at 3:38:47 PM UTC+2, Stephen Hartley wrote:
>
> Total newbie question here, thanks in advance for any tips on how to 
> improve my first hugin stitch.  Taken using a tripod and rotating ball 
> head, with standard rectilinear lens. No effort was made to rotate around 
> the no-parallax point, I don't know how significant this is for my pano?
>
> Source jpegs:
>
> 1 
> 2 
> 3 
> 4 
> 5 
>
>
> Stitched with Hugin 2016.2.0.be8da0221960 on Mac.  
>
> Spent a day experimenting with hugin, and this is my best result: output 
>  using this 
> pto project file. 
> 
>
>
> Could anyone more experienced give me some pointers on how to fix the 
> following:
>
>
>
>1. Horizon line, particularly at the top of the sea - I added a 
>horizontal line but this has caused the whole image to slant towards the 
>left.
>2. Areas of yellow paving have curved edges.  Again, these should be 
>horizontal, I added a horizontal line, but this does not seem to have had 
>the desired effect - the edges should be parallel to the horizontal edges 
>(top and bottom) of the image.
>3. Four noticeable stitching artefacts: two on the grey railings 
>(fence) in front of the black car, one on the bicycle path, immediately to 
>the left of the painting of the bicycle wheel, and again on the sea 
> horizon 
>line, quite a bump about a quarter of the way into the image from the left 
>edge.  I struggled to add more manual control points for the sea joint and 
>wonder if this might be causing the problem, if so, any known workaround?
>
>
> Thanks in advance for your help and advice,
>
> Steve
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3071c631-738a-4e5a-884c-6062ac867af9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Cylindrical projection - to the interior of a cylinder

[Abrimaal]

Yes, my mistake. I was thinking about "equidistant" correction of the 
cylindrical view. 
This is obvious that the further objects, especially these at the ends will 
be smaller. 
Panini projection can make them larger, but generally it is sufficient for 
interiors and street views.
it can be compared to a projection into the interior of an elliptical 
surface. 
I think, without manual work in a photo editor, it is impossible to make 
the objects close to the camera smaller, and these far larger.
But what editor... the perspective correction in graphic editors is limited 
to distortions of a rectangle.

On Monday, May 15, 2017 at 9:32:22 PM UTC+2, Erik Krause wrote:
>
> Am 14.05.2017 um 19:38 schrieb Abrimaal: 
> > In the cylindrical projection, the panorama is projected on the external 
> > surface of a cylinder. It is usable for objects viewed from distance 
> (like 
> > Earth from a satellite). 
> > I have many panoramas where the camera is "the centre of the universe". 
> > In the example everybody can see that the objects in the middle are 
> larger, 
> > because the panorama is projected onto a cylindrical surface. 
>
> May be I misunderstand. However, a panorama usually is taken from a 
> single viewpoint. In cylindrical projection it is projected on the 
> inside of a cylinder, not on the outside. Try the following: shoot a 
> panorama from the center of a round room or simply place same sized 
> objects around the camera in equal distance. The wall of the room will 
> unroll to an equally wide stripe, the objects will all be the same size. 
>
> > Can I save the panorama in Hugin as the rectangle, without the 
> distortions 
> > of projections used in cartography (objects viewed from distance)? 
>
> Any projection has distortions. In rectilinear projection f.e. balls in 
> the corners are distorted to ellipses while all lines remain straight. A 
> fisheye will map the balls as circles but all lines not going through 
> the image center will be bent. There is nothing like an undistorted 
> projection. 
>
> More on projections see: 
> http://wiki.panotools.org/Projections 
> http://www.panotools.org/dersch/perspective/Wide_Angle_Perspective.html 
>
> -- 
> Erik Krause 
> http://www.erik-krause.de 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5aed348a-3cb7-4b10-8a87-db81515b97af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Cylindrical projection - to the interior of a cylinder

[Abrimaal]

On Sunday, May 14, 2017 at 7:38:53 PM UTC+2, Abrimaal wrote:
>
> In the cylindrical projection, the panorama is projected on the external 
> surface of a cylinder. It is usable for objects viewed from distance (like 
> Earth from a satellite).
> I have many panoramas where the camera is "the centre of the universe".
> In the example everybody can see that the objects in the middle are 
> larger, because the panorama is projected onto a cylindrical surface.
> The tree at the very left is a part of the tree at the right.
>
> I don't want to use any of fisheye projections, because they distort the 
> vertical lines.
> Is it possible to project the panorama onto the internal surface of a 
> cylinder? 
> Is this the same as rectilinear projection? 
> Certainly not, because rectilinear fails when the field of view is wider 
> than 180 in this case it is 360
> The average distance of objects is the same everywhere. 
> Some viewers can detect it and display as an equidistant looped long 
> rectangle.
> Can I save the panorama in Hugin as the rectangle, without the distortions 
> of projections used in cartography (objects viewed from distance)?
>
>
>
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3da3c7be-da93-4274-8cc8-e6108b3fad4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Cylindrical projection - to the interior of a cylinder

[Abrimaal]

In the cylindrical projection, the panorama is projected on the external 
surface of a cylinder. It is usable for objects viewed from distance (like 
Earth from a satellite).
I have many panoramas where the camera is "the centre of the universe".
In the example everybody can see that the objects in the middle are larger, 
because the panorama is projected onto a cylindrical surface.
The tree at the very left is a part of the tree at the right.

I don't want to use any of fisheye projections, because they distort the 
vertical lines.
Is it possible to project the panorama onto the internal surface of a 
cylinder? 
Is this the same as rectilinear projection? 
Certainly not, because rectilinear fails when the field of view is wider 
than 180 in this case it is 360
The average distance of objects is the same everywhere. 
Some viewers can detect it and display as an equidistant looped long 
rectangle.
Can I save the panorama in Hugin as the rectangle, without the distortions 
of projections used in cartography (objects viewed from distance)?





-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8a4b8090-6b70-4964-9e3e-97db8fe6060c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: need help aligning a set of photos

[Abrimaal]

The photos are not taken from the same point. 
To align them you should work manually. 

If you used a control point detector before, there are many control points 
on the trees and leaves, better to start a new project than remove them any 
photo vs any.

First, you should decide what objects are important to your vision. 
1 Static walls and blurred trees or 2 blurred walls and multiplied tree 
branches. 

If 1 - Add control points on the highest contrasts of the buildings (white 
wall edges vs bricks). Not on the hydrant. The cars could have moved too.
If 2 - Add control points at the base of the trees and between bricks of 
the closer fence on the right.

Add vertical lines only on the white edges on the walls. 
Perhaps you should mask some less visible hydrants and cars, or leave only 
one to avoid multiplication.
The best projection for trees is Mercator, but in this case, the top of the 
tree will be cropped. Use rectilinear.

On Thursday, April 27, 2017 at 9:07:30 AM UTC+2, void star wrote:
>
>
> I have a set of images that I'm trying to align together. 
>
> A sample set of the image sequence is here:  
> https://app.box.com/s/s1urccnz60zoxu0dq97rm634kz4a27rm
>
> I tried from the command line:  align_image_stack.exe -a aligned -C *.jpg
>
> Maybe the Windows build is broken, its been running for several days (I 
> assume it is actually deadlocked inside).
>
> Then I tried to just load all the images into Hugin and click Align, but 
> that didn't get me very far.
>
> I've done a similar thing with astrophotography photos using PixInsight, 
> but it has an easier job aligning stars on a black background.   In this 
> case, maybe the fire hydrant or the mailbox could be used.
>
> After the alignment, I'll probably want to crop each image  down (focusing 
> on the tree).
>
> Suggestions appreciated!
> -Steve
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d9d699d4-663c-4196-9981-14c548b5bbd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: exposure fused from any arrangement panorama bug

[Abrimaal]

There are many repeating details, that could be misaligned by the control 
point finder.
In the Preview you may not see this, because these images are under the 
visible ones. 
Try to disable the first images and check which ones are incorrectly 
aligned.
Check the control points, any photo with any in the Editor. 

On Wednesday, February 22, 2017 at 9:10:34 PM UTC+1, Alex Romosan wrote:
>
> i've been trying to create panoramas exposure fused from any arrangement 
> but the layers to be fused in the final image are completely misaligned. 
> i've managed to work around this by keeping the intermediary blended 
> layers loading them into gimp and then saving them and then manually 
> running enfuse on the new layers and then the final output is just fine. 
>
> if i look at the layers with tiffinfo the only difference is the 
> Position tag which is not present in the file saved from gimp. in the 
> file generated by enblend it is set to some values. i think it is this 
> tag that confuses enfuse. it should probably be set to zero or not 
> set at all because as it is enfuse uses it and misaligns the layers. the 
> output layers from enblend are not cropped but are the size of what the 
> final panorama should be. 
>
> i tried to find the place where this value is set, but i've had no 
> success so far. any idea how to fix this? 
>
> you can see the panorama i got at 
> http://caliban.lbl.gov/test_blended_fused.tif 
>
> --alex-- 
>
> -- 
> | I believe the moment is at hand when, by a paranoiac and active | 
> |  advance of the mind, it will be possible (simultaneously with  | 
> |  automatism and other passive states) to systematize confusion  | 
> |  and thus to help to discredit completely the world of reality. | 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d055d292-9585-4b6b-9a17-c8227bc218a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Keeping the PTO files and temporary Tiff

[Abrimaal]

In the advanced mode, they are in the Stitcher tab. These marked are the 
most useful.

On Tuesday, January 31, 2017 at 9:18:44 PM UTC+1, FrankBa wrote:
>
> HI Abrimaal 
>>>>
>>> Found it !!
>
> I was using the stitcher option in advanced and expert mode and I did not 
> find any way to keep them that way
> I just found it in the simple mode, with the 1,2, 3 steps, just after the 
> create panorama, the screen shot you are refering is appearing
>
> Many thanks for your help 
> frank
>  
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/be867036-edce-4990-a146-0abd19f133ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Keeping the PTO files and temporary Tiff

[Abrimaal]

If you want to keep the partial .tif images, before saving the final 
panorama, check the option "Keep intermediate images".
The same in the Panorama editor and Advanced / Expert interface.

By default all .pto files are saved on the disk in the same folder as the 
panorama, you can use them again. 
In the Batch Processor, the option Remove finished project should be 
unchecked.


On Monday, January 30, 2017 at 10:20:00 PM UTC+1, FrankBa wrote:
>
> Good evening
>
> I'm looking for a way to keep the temporary files that are created during 
> the Stitching process.
>
> I have got some small stitching errors in the pano, and these tiff files 
> are very helpfull to correct this in photoshop used as layers
> Many thanks in advance for your helps
> frank
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f8030a8b-08cf-4649-9620-803cd876ff74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Non-square pixels (aspect ratio) from flatbed scanner

[Abrimaal]

The most of scanners store info about the scanner model in EXIF data. Hugin 
can connect to a camera lens database, but I don't know if any scanner 
database exists. It depends also on the orientation of scanner paper. It is 
important that all parts of the map should be scanned in the same direction.
This is only an idea, don't ask me for details. :)

On Tuesday, January 31, 2017 at 12:07:12 PM UTC+1, Bruno Postle wrote:
>
> I seem to remember that a combination of the g (shear) and r (roll) 
> parameters will correct for squashed images. 
>
> But introducing more optimisation variables is not always helpful. If you 
> can calibrate the distortion by scanning a ruler or similar, you will get 
> much more consistent results by pre-processing all your scans with an image 
> editor before using Hugin. 
>
> -- 
> Bruno 
>
>
> On 31 January 2017 01:30:48 GMT+00:00, John Eklund wrote: 
> >I'm scanning maps in patches for later stitching and realized that many 
> > 
> >flatbed scanners give slightly non-square pixels. (When scanning a 
> >circle I 
> >get an oval). Hugin has no ability to optimize for this parameter. My 
> >solution would be to manually adjust each image in Photoshop before 
> >loading 
> >into Hugin. Is there no elegant way of correcting this? Any ideas? 
> > 
> >Some old HP models are very poor in this regard. My Canon Canoscan 
> >4400F 
> >gives perfect square pixels but I had to replace it because when 
> >painstakingly dismounting the lid, I introduced dust somewhere which 
> >resulted in colored lines that I have been unable to get rid of despite 
> > 
> >cleaning repeatedly. I then bought a used Canoscan 8800F. It outputs 
> >very 
> >slightly non-square pixels, though not much at all so I figured I can 
> >live 
> >with it. Still, I assume it should be impossible to get a perfect 
> >stitch. 
> > 
> >Are we really certain that all cameras have square pixels? 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8c3c2400-4cdf-430e-ab15-e8e0c40bcf6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Other multi-image techniques?

[Abrimaal]

It is possible to create an image like this without blending the moving 
object with the background. Draw a mask around the object on the 1st photo, 
copy the mask to all other photos, then delete the mask from the 1st. The 
same for all images. At the end check if the masks don't overlap.

On Friday, January 13, 2017 at 9:53:50 PM UTC+1, Jeff wrote:
>
> I've used Hugin to make multiple exposure composites (kind of like 
> https://en.wikipedia.org/wiki/Multiple_exposure#/media/File:Lunar-eclipse-2004.jpg)
>  
> but where the camera was hand-held and I was capturing somebody doing some 
> action. The two I can think of are of someone jumping over a stream and 
> another of someone using a rope swing to jump in a river. I'd use hugin to 
> align the pictures, output as multiple layers, then use GIMP to selectively 
> erase from each layer the background (except the base layer), then flatten. 
> Works well!
>
> -Jeff
>
> On Tuesday, June 28, 2016 at 1:32:11 AM UTC-7, bugbear wrote:
>>
>> Whilst Hugin is typically used for panoramas, it can also 
>> be used for HDR via Enfuse. 
>>
>> Does anyone else on the list dabble in other techniques 
>> the involved the manipulation of multiple images? 
>>
>> Once I started listing them, I realised how many there are: 
>>
>> * Panorama 
>> * HDR (exposure stacking) 
>> * Extended DOF (focus stacking) 
>> * Noise reduction (averaging) 
>> * Super Resolution (sub pixel offset stacking) 
>> * Tourist Removal (Median, or manual multi masking) 
>> * exposure adding (photo gathering for astrophotography) 
>> * video post stablisation (inter frame registration) 
>>
>> So - anyone doing anything other than the first two? 
>>
>> (and did I miss any?) 
>>
>>   BugBear 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/87f1d530-875d-4b3e-84ad-a8c6eb6bb915%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Stitching photographs of a large map into a whole map

[Abrimaal]

I see that you are not the only one long time user who has problems with 
maps. I have never managed to stitch any map in Hugin, while I stitch and 
straighten many photos every day. Even when the control points are placed 
correctly, the projection distorts every map. Even when the projection is 
corrected by vertical and horizontal lines, there are many other 
improvements (dedicated for photos) that make the final image erroneus. My 
plea to anybody who understands the methods of stitching flat documents and 
the GUI developer is to add "Flat document mode for beginners" to the main 
menu. Preparing Hugin for maps really requires a lot of work that could be 
accessible from the menu as a preset. 
Scanned paper maps are not computer graphics, they are always distorted by 
folded paper, scanner optical imperfection and photometric corrections 
performed by the scanning software. Some statistics is required, the 
similarity threshold optimized for high contrast and exposure correction 
not as sensitive as in photography. I can participate in the process by 
testing. 


> My questions are:
>
>- *am I correct in thinking my task is something that is fairly easy 
>to achieve, for someone who understands Hugin*
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/74db4b76-964a-4e55-a9e9-cb44f1147822%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: UI Hard work mode

[Abrimaal]

When minimized to tray, there are even more messages. Both pulling up the 
taskbar and text messages from the tray. I know that Hugin is built of many 
.exe files, but can the Batch processor be completely invisible? Just like 
(for example) enblend.exe - no icon, no messages? 

On Friday, December 16, 2016 at 6:43:36 PM UTC+1, T. Modes wrote:
>
>
>
>
>> *I think it is possible to run the batch in a silent (quiet, invisible, 
>> non-invasive) mode *
>> or move the icon to the notification area near the clock. By default as 
>> hidden. 
>> Please, consider this when compiling a new release. 
>>
>
> This is already possible: PTBatcherGUI can be minimized to the task bar or 
> to the tray area, depending on the setting in PTBatcherGUI. So what more
> And the notification from the tray icon can be tuned in the notification 
> settings of the info area of Windows.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4f643a6a-4060-424e-820a-d95f39339542%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: UI Hard work mode

[Abrimaal]

*Hugin vs Windows 10. The Batch Processor icon still blocks the taskbar. *
The Windows taskbar and the bottom of the screen are places where 
everything happens, it's the action centre. 
The user decided that the Windows taskbar should auto-hide, but every task 
scheduled for the Batch processor breaks the comfort.
What is the user's satisfaction when the batch is working? Every user's 
decision must be confirmed by clicking the Batch processor icon. The user 
just begs "please allow me to do anything else on this computer".
I have enough strong CPU, enough RAM to work with HDR photos in the same 
time in another application, but I cannot.

*I think it is possible to run the batch in a silent (quiet, invisible, 
non-invasive) mode *
or move the icon to the notification area near the clock. By default as 
hidden. 
Please, consider this when compiling a new release. 

On Saturday, April 2, 2016 at 8:46:13 AM UTC+2, Abrimaal wrote:
>
> A suggestion:
> A checkbox in settings
> [ v ] Do not display any messages, I am working hard in another program.
> or
> [ v ] Display error messages only
>  
> This applies to the overload of messages generated by hugin in the 
> taskbar, tray and in the pop-up windows. 
> While hugin is stitching panoramas, the user may be working in another 
> application. 
> The detailed pop-up messages can be switched off, but the taskbar 
> notification may be annoying, because it changes the active app to hugin 
> and requires a click, especially when working in full screen with another 
> application.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/731585f9-ade4-431b-9e44-a1ee5c3630e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Manipulating the control points detector settings

[Abrimaal]

or try to use Align image stack instead of Hugin CPfind. It worked for me 
with about 100 video frames, but they were small size (800x600). If you 
have enough RAM, larger images should be displayed too.

On Wednesday, December 14, 2016 at 2:44:48 PM UTC+1, jan t wrote:
>
> Hello all,
>
> I'm trying to algin and clip images taken from a drone of the same scene 
> and spot for use in Particle Tracking. One series of images are about a 100 
> images. 
> My workflow is the following I load up the images and find control points 
> with the Hugin's CPfind + Celeste finder. Then i use the fast preview 
> window to show all of my Control points and delete the bad matches. These 
> bad matches are due to a moving body of water in all of the pictures. After 
> that I let hugin optimise the Geometry. I cut the pictures in the fast 
> preview windows so that i get images of the same frame. Finally I stitch 
> them.
>
> This works fine with about 20 images. But when I use more (about a 140.000 
> control points for ~100 images) the fast preview windows locks up and i 
> can't use it to delete the bad control points. I tried to mask an area so 
> Hugin doesn't try to find Control points in this area but that doesn't seem 
> to work. Furthermore I tried to manipulate the detector settings for the 
> Hugin's CPfind + Celeste. As I understood the syntax of the Arguments, I 
> have to add %p -- (insted of -- the number of control points) to limit the 
> amount of control points found. But that doesn't seem to work either.
>
> How can I change my workflow or manipulate the detector settings as to 
> avoid the program locking up?
>
> Best Regards
>
> Jan
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/03a3f1af-7f1c-4673-affb-768308f194f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Control points editor / Line detection / Projection of a single image

[Abrimaal]

I'd like to see an example how to prepare such script.

On Thursday, December 8, 2016 at 10:28:17 AM UTC+1, bugbear wrote:
>
> In that case I recommend a script. 
>
>   BugBear 
>
> Abrimaal wrote: 
> > How many? Hundreds in every folder and hundreds of folders :) 
> > 
> > On Wednesday, December 7, 2016 at 9:52:18 AM UTC+1, bugbear wrote: 
> > 
> > Abrimaal wrote: 
> >  > No, taken with various cameras, in differe  nt years, seasons, 
> various objects (mainly architecture) 
> > 
> > How many photographs do you have? 
> > 
> > This would affect the degree to which automation is worth 
> > the time (and trouble) to implement. 
> > 
> >BugBear 
> > 
> > -- 
> > 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   hugin-ptx+...@googlegroups.com >. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/hugin-ptx/54927a80-6730-48a5-bf63-c507f62fb490%40googlegroups.com
>  
> <
> https://groups.google.com/d/msgid/hugin-ptx/54927a80-6730-48a5-bf63-c507f62fb490%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/837b4106-f45f-4442-a685-18c94c4a42b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Control points editor / Line detection / Projection of a single image

[Abrimaal]

How many? Hundreds in every folder and hundreds of folders :)

On Wednesday, December 7, 2016 at 9:52:18 AM UTC+1, bugbear wrote:
>
> Abrimaal wrote: 
> > No, taken with various cameras, in different years, seasons, various 
> objects (mainly architecture) 
>
> How many photographs do you have? 
>
> This would affect the degree to which automation is worth 
> the time (and trouble) to implement. 
>
>   BugBear 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/54927a80-6730-48a5-bf63-c507f62fb490%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Control points editor / Line detection / Projection of a single image

[Abrimaal]

No, taken with various cameras, in different years, seasons, various 
objects (mainly architecture)
I am not familiar to any of script languages, but it would look like this

define folder variable: path
for each to last file
set projection: rectilinear
run detect vertical lines
run optimize y,p,r,v,b
run calculate size
run autocrop
save .pto file as original-s.pto
save as original-s.jpg (all images are .jpg)
next

Some files will require manual adjustment, but at least half will be done 
correctly :)

On Tuesday, December 6, 2016 at 6:28:28 PM UTC+1, bugbear wrote:
>
> Abrimaal wrote: 
> > Now I have a lot of single photos to straighten. Every time I load a new 
> image, the projection is changed to Equirectangular, when I need 
> Rectilinear. Repeating it too many times is uncomfortable. 
> > Can I save the settings, that are not included in the Preferences to 
> .ini file? 
> > or start Hugin from a .bat file with desired parameters: rectilinear 
> projection, control point detector set to vertical lines etc. ? 
>
> Are your single photos that need straightening all taken in the same way 
> way ? 
>
> If so, this could help: 
>
>
> http://hugin.sourceforge.net/docs/manual/Panorama_scripting_in_a_nutshell.html#Simple_command-line_stitching
>  
>
>BugBear 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/577aabfa-d4e0-476d-8de3-c38f05257951%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Control points editor / Line detection / Projection of a single image

[Abrimaal]

Now I have a lot of single photos to straighten. Every time I load a new 
image, the projection is changed to Equirectangular, when I need 
Rectilinear. Repeating it too many times is uncomfortable. 
Can I save the settings, that are not included in the Preferences to .ini 
file?
or start Hugin from a .bat file with desired parameters: rectilinear 
projection, control point detector set to vertical lines etc. ?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b62cdbba-5ca9-46ef-b220-940ef6933fba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Is there a way to turn off the photometrics exposure and white balance correction for all images all the time?

[Abrimaal]

In the Preview tab there is an option to uncheck Photometrics, but 
unfortunately checked or unchecked creates identical panoramas.
Try in the Panorama Editor - Photometrics: Custom parameters, then in the 
tab Exposure that appears when you select Custom - Reset or Edit the 
parameters.


On Monday, December 5, 2016 at 10:56:55 AM UTC+1, Mike Maas wrote:
>
> I'd like to be able to create a pano that look like the images I start 
> with but joined.  For some reason hugin chooses really bad white balance 
> corrections and the only way I've found to fix them is to change them in 
> each image to values of 1.  
>
> Also the docs I found imply that setting the camera response curve values 
> to 0 should tell hugin to ignore the image photometrics and presumably not 
> try to fix them which is what I would prefer but instead it appears to 
> revert to linear resulting in a very washed out image.
>
> Thanks for any help/suggestions.
>
> Mike
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9b4a0384-1d0b-487e-b675-bd78fbd2c06d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.