[hugin-ptx] Re: libpano13-2.9.21 release candidate rc1

Andreas Metzler schrieb am Dienstag, 26. Oktober 2021 um 08:21:25 UTC+2: > > > Could you please test, if this fixes your issues? > [...] > > -set(_common_libs ${TIFF_LIBRARIES} ${ZLIB_LIBRARIES} ${JPEG_LIBRARIES} > ${PNG_LIBRARIES}) > > +# check if libm needs additional linker flag > >

[hugin-ptx] Re: libpano13-2.9.21 release candidate rc1

Hi Andreas, Andreas Metzler schrieb am Sonntag, 24. Oktober 2021 um 08:47:07 UTC+2: > > afaiu the rc files (resource files) are a windows thingy, i.e. this > should be changed: > > 8X- > --- libpano13-2.9.21~rc1+dfsg.orig/CMakeLists.txt > +++

Re: [hugin-ptx] Re: Hugin 2021.0 beta 1

Hi Harry, hvd...@gmail.com schrieb am Sonntag, 24. Oktober 2021 um 17:20:44 UTC+2: > See attached. > One will stay fuzzy as I am not entirely sure how to translate that and if > it even has an equivalent in Dutch. > thanks. I committed the changes. Thomas -- A list of frequently asked

[hugin-ptx] Re: libpano13-2.9.21 release candidate rc1

Hello, Andreas Metzler schrieb am Sonntag, 24. Oktober 2021 um 08:47:07 UTC+2: > > which can be fixed with > 8X- > --- libpano13-2.9.21~rc1+dfsg.orig/CMakeLists.txt > +++ libpano13-2.9.21~rc1+dfsg/CMakeLists.txt > @@ -119,7 +119,7 @@ FIND_PACKAGE(PNG REQUIRED)

Re: [hugin-ptx] Re: Hugin 2021.0 beta 1

Hi Harry, hvd...@gmail.com schrieb am Donnerstag, 21. Oktober 2021 um 22:23:48 UTC+2: > Please find Dutch translation attached for the hugin-2021.0_beta1.tar.bz2 > tar ball. > thanks for the translation. But there are still some strings missing: >msgfmt -c --statistics nl.po 1684 translated

[hugin-ptx] Re: Hugin 2021.0 beta 1

Just an reminder for the translators. Some languages have only a handful of untranslated strings: ca_ES.po 1686 translated messages, 9 fuzzy translations, 9 untranslated messages. ca...@valencia.po 1686 translated messages, 9 fuzzy translations, 9 untranslated messages. fr.po 1686 translated

[hugin-ptx] Re: How to increase success rate with pano_modify?

Hi Juha, Juha Kallioinen schrieb am Dienstag, 19. Oktober 2021 um 20:28:39 UTC+2: > If there's just a single/few control points between images, does it pay to > manually create more points in th GUI, or will those be too inaccurate? No, in most cases manually picked cp will be more accurate

[hugin-ptx] Re: How to increase success rate with pano_modify?

The main cause is there is only a single control point between image 2 and 3. Then the optimizer goes haywire. It sets the TrZ parameter of all images >=3 to -1.003 and then the output does not contain the images >=3. And now you try to calculate the HDR crop - the area which is contained in

[hugin-ptx] Re: libpano13-2.9.21 release candidate rc1

Windows binaries (64 bit) of rc1 can be found in the beta 1 release of Hugin 2021.0. see https://groups.google.com/g/hugin-ptx/c/HWycn8CfunI -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to

[hugin-ptx] Hugin 2021.0 beta 1

Hi all, today we are releasing beta 1 of Hugin 2021.0.0 Source tarball can be downloaded at sourceforge: https://sourceforge.net/projects/hugin/files/hugin/hugin-2021.0/hugin-2021.0_beta1.tar.bz2/download Verify its checksums: md5: 68c815c918ef3fb8e91f80b62664f4b4 hugin-2021.0_beta1.tar.bz2

[hugin-ptx] Re: How to increase success rate with pano_modify?

Juha Kallioinen schrieb am Donnerstag, 14. Oktober 2021 um 17:26:15 UTC+2: > Now to the problem: > > Most often if pano_modify works it finishes in a few seconds. > > Do you have any advice on what could I do to have a better chance of > getting pano_modify to do its thing? > Can you provide

Re: [hugin-ptx] Documentation of Fields in PTO i-lines

kfj schrieb am Dienstag, 21. September 2021 um 11:28:33 UTC+2: > - The cropping area of the two circular fisheye images is not placed > correctly, parts of the image which show the inside of the lens are > inside the cropping area, some content is cut off so much that the > output has black

Re: [hugin-ptx] Documentation of Fields in PTO i-lines

kfj schrieb am Montag, 20. September 2021 um 10:19:39 UTC+2: > Okay, what's the 'dual lens assistant' and where can I find it? > Start with new project and add single image. Then run user defined assistant: Edit>User defined assistant>Assistant for dual lens images -- A list of frequently

[hugin-ptx] Re: Attempting to Stitch 46 photos from DJI Spark 360 Pano

francis@gmail.com schrieb am Montag, 20. September 2021 um 11:56:40 UTC+2: > DJI.assistant don't work i have update like this > Arguments=-p > 'y$FileSequence=$GimbalYawDegree,p$FileSequence=$GimbalPitchDegree,r$FileSequence=$GimbalRollDegree' > > -w+! %0fpos.txt -@ %imagelist%. > There

Re: [hugin-ptx] Documentation of Fields in PTO i-lines

kfj schrieb am Sonntag, 12. September 2021 um 13:04:25 UTC+2: > Now it's clear. I was also a bit miffed that hugin would silently > consume my PTO with a C field to a PTO with an S field, when the two > have quite different meaning. > And I could be a bit miffed that you ignored the dual

[hugin-ptx] Re: Attempting to Stitch 46 photos from DJI Spark 360 Pano

francis@gmail.com schrieb am Sonntag, 19. September 2021 um 17:06:46 UTC+2: > When i try exittols command > exiftool -p > "y${Filename;s/DJI_//;s/\..*$//;$_-=1;}=$CameraYaw,p${Filename;s/DJI_//;s/\..*$//;$_-=1;}=$CameraPitch,r${Filename;s/DJI_//;s/\..*$//;$_-=1;}=$CameraRoll" > > -ext

Re: [hugin-ptx] libpano13-2.9.20 unit tests fail on FreeBSD

bruno...@gmail.com schrieb am Sonntag, 12. September 2021 um 22:59:02 UTC+2: > The tests seem to have been broken since this commit, which suggests a > problem with the test suite: > It is fixed now. The reference files for the tests contains also the version number. So this numbers need

[hugin-ptx] Re: Hugin & Enblend 360 spherical panorama wrap flag

John Eklund schrieb am Sonntag, 29. August 2021 um 22:15:17 UTC+2: > Enblend has an option -w, --wrap[=MODE] wrap around image boundary, where > MODE is "none", "horizontal", "vertical", or "both"; default: none; without > argument the option selects horizontal wrapping. > > When using the

[hugin-ptx] Re: how reset the center of panoramas by batching

d938...@gmail.com schrieb am Montag, 23. August 2021 um 09:34:57 UTC+2: > > 2. Yaw:120 ->Apply > > The rotation of pano can be done on the command line with pano_modify --rotate-panorama=120,0,0 --output=output.pto input.pto This is scriptable. -- A list of frequently asked questions is

Re: [hugin-ptx] hugin and vigra patches for OpenEXR 3

Hi Bruno, I committed an other approach for detecting OpenEXR 3 to Hugins default branch. (I tested Fedora 35 in a virtual machine. Hope it works also for you.) Thomas -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message

Re: [hugin-ptx] hugin and vigra patches for OpenEXR 3

Hi Bruno, we have already a FindOpenEXR.cmake file. I would prefer to keep the necessary changes in this file and not spread it over several places as your patch (main CMakeLists.txt and FindOpenEXR.cmake). Also when you change the paths for the include statements there are more changes

Re: [hugin-ptx] Re: focus stacking tool with Hugin

matou@gmail.com schrieb am Montag, 12. Juli 2021 um 18:20:16 UTC+2: > I was only unhappy with enfuse default parameters as set by Hugin. I agree > with you when you write that I could go further with enfuse and try getting > better results with it. > In the enfuse manual there is a

[hugin-ptx] Re: is hugin_hdrmerge broken?

kfj schrieb am Mittwoch, 30. Juni 2021 um 23:05:13 UTC+2: > I saw hugin produce such pgm files, and I could never figure out why they > would be needed: the exr should have all the nececssary information, > because it holds linear RGBA. What's the pgm good for? > In Hugins HDR workflow all

[hugin-ptx] Re: is hugin_hdrmerge broken?

kfj schrieb am Mittwoch, 30. Juni 2021 um 11:39:05 UTC+2: > Am I doing something wrong or is hugin_hdrmerge broken? > Hugin_hdrmerge is intended to merge linear exr files only - not for LDR images. And for this use case it works. I added a better error message to make it clearly and prevent

Re: [hugin-ptx] Is there any way to keep pixels unchangeable with Hugin?

bruno...@gmail.com schrieb am Dienstag, 29. Juni 2021 um 12:30:56 UTC+2: > > I don't think that nona (the Hugin remapping tool) dithers output images, Nona does dithers the output. Also the vignetting parameters should be reset to 0. Also the interpolator can be changed with the command line

[hugin-ptx] Re: pto_gen doesn't make a list of variables to optimize

ChameleonScales schrieb am Freitag, 18. Juni 2021 um 21:41:27 UTC+2: > When I do a pto_gen, no matter what arguments I put in, the generated pto > contains an emty list of variables that should be optimized. > > Without this list being filled, I can't change the anchor image before > running

[hugin-ptx] Re: How to get enblend compiled with OpenCL support?

GnomeNomad schrieb am Sonntag, 13. Juni 2021 um 00:02:48 UTC+2: > How to get enblend with OpenCL support? > Only the development version (default branch) supports OpenCL. This is work in progress and currently it is not faster than the normal version. It needs to be activated when compiling

Re: [hugin-ptx] Re: lux - FOSS multiplatform image and panorama viewer

kfj schrieb am Mittwoch, 9. Juni 2021 um 09:04:59 UTC+2: > > My intention is to have this bahaviour: if the .pto extension is already > assigned (like, to hugin), and lux is installed afterwards, the first > doubleclick on a .pto after the installation of lux should result in a > dialog

Re: [hugin-ptx] Re: lux - FOSS multiplatform image and panorama viewer

kfj schrieb am Dienstag, 8. Juni 2021 um 18:50:42 UTC+2: > It's likely that a windows system doesn't have > associations for some of these extensions (especially .pto, .lux and > .exr), in which case the doubleclick should even work without the dialog. > If Hugin installer is used, it

[hugin-ptx] Re: Hugin on MacOS Big Sur?

mumf...@gmail.com schrieb am Freitag, 28. Mai 2021 um 09:48:06 UTC+2: > > Does anyone know if there's a way to fix this? > > This was already asked here https://groups.google.com/g/hugin-ptx/c/5_eLt83Ijpk and here https://groups.google.com/d/msg/hugin-ptx/XSzG_GaL00w/p1YBFD9tAgAJ The

[hugin-ptx] Re: unable to build hugin 2020.0.0

sc...@cinesite.com schrieb am Mittwoch, 19. Mai 2021 um 20:41:57 UTC+2: > Now I am stuck on this issue. > Can anyone help me? > > ``` > In file included from > /images/personal/industrial/kiln/working/hugin-2020.0.0/src/hugin1/hugin/huginApp.h:32:0, > from >

[hugin-ptx] Re: Random green pixels with Hugin 20.0 on Windows

Thanks. It appears there updates to several libs. So it not so easy to isolate the necessary 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

[hugin-ptx] Re: Random green pixels with Hugin 20.0 on Windows

Hi, good to hear. pj.ha...@gmail.com schrieb am Dienstag, 4. Mai 2021 um 23:38:27 UTC+2: > Odd that the Linux version of Hugin does not seem to have this issue. > Some subtle difference in the underlying libraries between the difference > OS platforms maybe. > What is the output of enblend

[hugin-ptx] Re: Random green pixels with Hugin 20.0 on Windows

Hi, first you need to narrow down the issue. The issue can be introduced during (a) remapping by nona or (b) by blending with enblend/enfuse. Check the intermediate (remapped) images - you can activate them on the stitcher tab. If the remapped images show already the green spots (case (a)),

[hugin-ptx] Re: Feature request - control point tab image preview for HDRI

Preferences>control point editor there is already the choice between linear, logarithm and gamma. -- 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

[hugin-ptx] Re: Hugin 2019.2.0 crashes during start on Mac OS 10.13.6

stue...@gmail.com schrieb am Montag, 12. April 2021 um 22:59:46 UTC+2: > > But now it seems I have a problem. Hugin 2019.2.0 crashed will working on > a > very large panorama. Since then I cannot start it again. > I already deleted Hugin Preferences in library preferences folder. It just >

[hugin-ptx] Re: libpano13-bin: out of bounds read in PTinfo

pola lemu schrieb am Donnerstag, 22. April 2021 um 19:04:58 UTC+2: > I am not sure the following patch is or not suitable. > Thanks for the diagnose and the patch. I committed a slightly modified version. -- A list of frequently asked questions is available at:

[hugin-ptx] Re: Stitching dual fisheye image from Mi Sphere

m.ra...@gmail.com schrieb am Donnerstag, 25. März 2021 um 08:16:53 UTC+1: > I've attached the original image and my Hugin file here > . > > Any idea on how to improve my stitching result? > You have optimized

[hugin-ptx] Re: Tough time with mosaic

jmuc...@gmail.com schrieb am Montag, 22. März 2021 um 18:54:42 UTC+1: > I figured adding the h and v points would help. Is that wrong? > > What's the rule (of thumb?) for deciding on the projection? > No that's right. When you want straigt horizontal and vertical lines you have the use the

[hugin-ptx] Re: Filename %date variable not working correctly

jmuc...@gmail.com schrieb am Sonntag, 21. März 2021 um 20:08:52 UTC+1: > Yes, png traditionally didn't have exif data. I'm no expert, but there are > PNG tags, I believe. See here: https://exiftool.org/TagNames/PNG.html > Could be these still aren't read by exiv2. This is what I already

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

kfj schrieb am Sonntag, 21. März 2021 um 13:08:59 UTC+1: > The key feature is *viewing* PTO files without having to stitch them > first. The recent addition of optional 'proper' stitches of what you see > in the live view is a nice-to-have extra. > I did a short test on Windows. When

[hugin-ptx] Re: Tough time with mosaic

jmuc...@gmail.com schrieb am Montag, 22. März 2021 um 00:30:10 UTC+1: > I'm having a rough time trying to make a perspective-corrected mosaic with > two photos of a poster in a museum, both taken at sharpish angles. Any help much appreciated. > There are 2 problems: * For scanned images

Re: [hugin-ptx] Hugin freezing during blending

Monkey schrieb am Montag, 22. März 2021 um 11:45:09 UTC+1: > Not that I would expect it to be default - I assume that's going to be > Verdandi at some point - but what "necessary" features is it missing? > I thought, this is obviously. Multiblend does not support all bitdepths and necessary

[hugin-ptx] Re: Filename %date variable not working correctly

T. Modes schrieb am Sonntag, 21. März 2021 um 10:13:33 UTC+1: > The displayed date/time is the EXIF DateTimeOriginal > (Exif.Photo.DateTimeOriginal in exiv2 speech). PNG files have no EXIF data, > the metadata are stored differently. So this is expected. > I did some

Re: [hugin-ptx] Hugin freezing during blending

gunter.ko...@gmail.com schrieb am Samstag, 20. März 2021 um 17:00:32 UTC+1: > Hmmm... One partially related question: Would it make sense to make > multiblend the default for new hugin installs? > > Multiblend does not support all necessary features needed by Hugin. So it can't currently be the

[hugin-ptx] Re: Filename %date variable not working correctly

jmuc...@gmail.com schrieb am Samstag, 20. März 2021 um 20:06:56 UTC+1: > Problem 1 > > For example, using "%filename - %time" as the template, a jpeg produces > > IMG_3664 - 01/18/46 PM.pto > > Hugin is using the system setting for the date/time formatting. On my system the date/time format

[hugin-ptx] Re: Project files

Viktor schrieb am Mittwoch, 17. März 2021 um 18:38:08 UTC+1: > Hello! > > I'm just getting started with Hugin, but I encountered a problem: When I > saved the project the filenames got incorrect inside the project file. To > make it even more interesting it only happens when working inside >

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

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:

[hugin-ptx] Re: Feature request: Align Image Stack batch & remove CP from crop area

mkogoj...@gmail.com schrieb am Dienstag, 2. März 2021 um 13:20:51 UTC+1: > Moreover, since the cropped area will not be used regardless I imagine it > would make sense to *remove any control points from it automatically.* The crop is normally set first and then cpfind is started. So no cp in

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

I found this a little bit sad. Instead of merging the developing power everyone is working on its own code. Yes, it is easier to work on own code. But for the longer one it would be better to combine the developing skills and work on a common code base. This would also have the advantage that

[hugin-ptx] Re: Newbee: How to activate images?

Kai Mewes schrieb am Sonntag, 28. Februar 2021 um 19:43:47 UTC+1: > I think the tutorial is at this point a bit ambiguous for me. > I have not written the tutorial. But I think you missed the point to use "select all" from the context menu and instead selected all manually. The context menu is

[hugin-ptx] Re: Newbee: How to activate images?

Ok, the problem is that you optimized the translation parameters of all images at one. You need to optimize TrXYZ of all images except the first (or another anchor) and add roll as optimisation parameter: * So reset all translation parameters (select all images and choose reset parameters from

[hugin-ptx] Re: Newbee: How to activate images?

Kai Mewes schrieb am Sonntag, 28. Februar 2021 um 11:38:59 UTC+1: > Sorry, with attached .pto file I can not post here ?! > That should work, at least with the web interface. Otherwise use a file hoster or cloud solution and post the link. -- A list of frequently asked questions is available

Re: [hugin-ptx] Re: Build fails - missing MSGFMTConfig.cmake

Hi Zupino Zupino schrieb am Sonntag, 28. Februar 2021 um 08:55:57 UTC+1: > Thank you Thomas, > passing the path to main source dir instead of ../src does work. I do get > another error with missing wxWidgets, still have to look into that. > you need to install the wxWidgets dev package (on

[hugin-ptx] Re: Newbee: How to activate images?

Kai Mewes schrieb am Samstag, 27. Februar 2021 um 22:03:12 UTC+1: > As additional info, I could not do the "quick panorama preview", because > under the tabs "Assistant", "Preview", "Projection", "Move/Drag" and "Crop" > only an empty window with grid without images appears, but the control

Re: [hugin-ptx] Re: Build fails - missing MSGFMTConfig.cmake

Zupino schrieb am Samstag, 27. Februar 2021 um 17:11:26 UTC+1: > $ cmake ../src > CMake Warning (dev) in CMakeLists.txt: > No project() command is present. The top-level CMakeLists.txt file must > contain a literal, direct call to the project() command. Add a line of > code such as > >

[hugin-ptx] Re: Build fails - missing MSGFMTConfig.cmake

Zupino schrieb am Samstag, 27. Februar 2021 um 09:35:50 UTC+1: > What I noticed is that I do not have CMAKE_MODULE_PATH set, so I set it > with export CMAKE_MODULE_PATH='/home/' and > run again cmake, but still same error. CMAKE_MODULE_PATH is a variable inside the CMake build system, not an

[hugin-ptx] Re: Build fails - missing MSGFMTConfig.cmake

Zupino schrieb am Freitag, 26. Februar 2021 um 20:44:40 UTC+1: > after creating a my-build dir and running cmake ../src from there, I get > an error > > ``` > CMake Error at translations/CMakeLists.txt:7 (find_package): > By not providing "FindMSGFMT.cmake" in CMAKE_MODULE_PATH this project

[hugin-ptx] Re: Camera response curve calibration (gamma)

mkogoj...@gmail.com schrieb am Dienstag, 23. Februar 2021 um 21:53:38 UTC+1: > I want to check if the photo stacks I am working with are linear or not. > Yes; raw files are supposed to be linear, but Hugin does not work with > CR2, only tiff. If I convert the cr2 to tiff it will probably add a

[hugin-ptx] Re: Camera response curve calibration (gamma)

mkogoj...@gmail.com schrieb am Freitag, 19. Februar 2021 um 11:30:17 UTC+1: > I want to convert CR2 files to linear tif with no adjustments, Wait, when you input linear images you should set the camera response curve to linear. Then the parameters Ra/../Re have no effect. -- A list of

[hugin-ptx] Re: Camera response curve calibration (gamma)

mkogoj...@gmail.com schrieb am Freitag, 19. Februar 2021 um 11:30:17 UTC+1: > For example - there are Ra to Re parameters in the Emor method in "image > parameters" part of Exposure tab; is there a way to know what those > parameters are and how they can be graphed, or at least know what they

[hugin-ptx] Re: Preview work space does not show complete picture

Daniel Pittoors schrieb am Freitag, 19. Februar 2021 um 08:49:08 UTC+1: > Preview space only shows fraction of loaded picture overview on Mac - did > not have this issue on Windows? > see https://groups.google.com/d/msg/hugin-ptx/XSzG_GaL00w/p1YBFD9tAgAJ and

Re: [hugin-ptx] New release for mac?

Bob Campbell schrieb am Mittwoch, 3. Februar 2021 um 07:13:03 UTC+1: > and the mac docs don’t tell you what you need for cmake options & vars. So > I feel like I’m at a bit of a dead-end. If anyone’s working on it, I’ll > try to help, but right now I’m stuck. > I don't have access to a Mac.

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

ChameleonScales schrieb am Sonntag, 31. Januar 2021 um 19:15:50 UTC+1: > calculation of the correlation is expensive > > I assumed the correlation was also calculated when you detect CPs. That > said I didn't necessarily mean to show it at all times. Just when you press > Fine-tune all would

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

ChameleonScales schrieb am Sonntag, 31. Januar 2021 um 16:54:09 UTC+1: > So I was using the Debian repository version (2018) and in this version > the header did not change to "Correlation". I just tried on the latest > appimage and indeed this has been solved, so that's my mistake. > So you

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

ChameleonScales schrieb am Samstag, 30. Januar 2021 um 20:54:39 UTC+1: > As this wiki page > > explains, after Fine-tuning all Points, the Distance column shows the > correlation. I find this confusing. Distance and

[hugin-ptx] Re: GPU usage with Hugin

alvaroh...@gmail.com schrieb am Freitag, 29. Januar 2021 um 18:58:39 UTC+1: > El viernes, 29 de enero de 2021 a las 17:27:33 UTC+1, T. Modes escribió: > >> >> >> alvaroh...@gmail.com schrieb am Freitag, 29. Januar 2021 um 13:38:51 >> UTC+1: >> >>&g

[hugin-ptx] Re: GPU usage with Hugin

alvaroh...@gmail.com schrieb am Freitag, 29. Januar 2021 um 13:38:51 UTC+1: > I'm finding too slow the process (40+ mins each panorama), specifically > the autooptimiser part. I was wondering if there is any way of make this > tool to take advantage of the GPU power or maybe antoher kind of

[hugin-ptx] Re: About Control Points 'Distance' in Hugin scripting

Hi, alvaroh...@gmail.com schrieb am Mittwoch, 27. Januar 2021 um 12:39:39 UTC+1: > I've noticed that the 'Distance' parameter in the control point tab (in > Hugin interface) is playing an important role in the overall stitching > quality (i don't really understand how hugin manage this

[hugin-ptx] Re: Changing crop changes stitching success

talk2...@gmail.com schrieb am Samstag, 23. Januar 2021 um 13:32:41 UTC+1: > Hi there, > > But does the program not stitch the images together, and THEN crop the > final image ? > >> >> No. It process only the pixels in the crop area. Why should it process many pixels first and then crop them

[hugin-ptx] Re: Any reason to use Enblend over Verdandi?

As I already written verdandi --seam=blend is already using a hard seam as first step. Then the already seamed images are used for Poisson blending. Here only information from the direct neighbourhood of the seam of the first image are used as border condition. So when the differences at the

Re: [hugin-ptx] An addition for the Hugin Tutorials page

Donald Johnston schrieb am Freitag, 22. Januar 2021 um 18:40:43 UTC+1: > It would be a lot easier for someone to find … I don’t usually think of > looking for links inside other tutorials. > > You want a link to a tutorial, but don't look into tutorials??? So it's only about the link and not

[hugin-ptx] Re: Any reason to use Enblend over Verdandi?

Hi Monkey, verdandi has 2 blending modes: - hard seam: this is the fastest one and relies to 100 % on Hugin photometric optimization. For me this works fine in about 3/4 of the cases. If there are bigger color/exposure differences at the image edges between the images then I use blend seam

[hugin-ptx] Re: An addition for the Hugin Tutorials page

Hi, this tutorial is already linked in the tutorial "Stitching murals using mosaic mode", Advanced techniques section. So not sure if an additional link is needed. Donald Johnston schrieb am Montag, 18. Januar 2021 um 23:15:20 UTC+1: > Could I recommend that the following link on linear

[hugin-ptx] Re: Changing crop changes stitching success

Hi, talk2...@gmail.com schrieb am Montag, 11. Januar 2021 um 14:17:29 UTC+1: > Hello - The Assistant created a perfect stitch of 3 photos, but I wanted > more than the auto-crop. However, when I changed the crop size (to > anything outside of autocrop) the saved file has stitching errors (eg.

Re: [hugin-ptx] Re: [PATCH] Install MIME type icon into the hicolor theme

akl schrieb am Freitag, 18. Dezember 2020 um 10:42:38 UTC+1: > On Monday, 25 May 2020 at 18:59:11 UTC+1 T. Modes wrote: > > Appears that the file rename got applied, but the installation directory > is still: > Fixed in repository. Nobody complained in a half year or dur

Re: Man page problems (was: [hugin-ptx] Hugin 2020.0.0 released)

Groogle schrieb am Sonntag, 13. Dezember 2020 um 11:53:40 UTC+1: > But since 2020.0.0 > the build doesn't build the man page any more. I didn't want to debug > the build process. In each case I did a 'make all'. The beta version > built the man pages (it seems), while the release version

Re: [hugin-ptx] Bad results with cpfind

aks schrieb am Mittwoch, 16. Dezember 2020 um 18:35:45 UTC+1: > 1. “Fine-tune all Points” after running the “Create control points” > process. This command is found in the Edit pulldown menu. The control point > distances get normalized in a way to make it easier to notice the outliers. > The

[hugin-ptx] Hugin 2020.0.0 released

Hi all, after a long beta 1 phase without bugs reported we are releasing today Hugin 2020.0.0 Source tarball can be downloaded at sourceforge: https://sourceforge.net/projects/hugin/files/hugin/hugin-2020.0/hugin-2020.0.0.tar.bz2/download or at launchpad:

[hugin-ptx] Re: Some typo

Am Sonntag, 1. November 2020 18:11:01 UTC+1 schrieb Cristian Marchi: > > > Hi, while translating new strings I've found some typo: > I will wait until weekend before committed the changes. Maybe other typo are found until then and so I have only once (again) to update the translations file.

[hugin-ptx] Re: Editor rendering issues on macOS 10.15.7

Am Donnerstag, 29. Oktober 2020 07:56:53 UTC+1 schrieb Peter: > > While I'm able to make it through the basic assistant flow, it seems any > adjustments I make to the editor cause it to render incorrectly, making it > unusable. Has anyone else seen this and know how to fix it? I was having >

[hugin-ptx] Re: Consecutive Roll Pitch Roll Pitch Roll transform into one set of Y P R?

Hi Alister, Am Mittwoch, 28. Oktober 2020 03:51:26 UTC+1 schrieb dawns...@gmail.com: > > > I am running nona in a script because I have 100 images to process. > My question is can I use nona to line by line in a script > roll by $roll1 > pitch by $pitch1 (which takes it out of the field of

Re: [hugin-ptx] [patch] typo "normaly"

Thanks to all. I committed a fix for the typo. Am Montag, 26. Oktober 2020 13:23:43 UTC+1 schrieb Daniel Md: > > Rather, > > An equirectangular image normally has *a* ratio of 2:1 > > I.e adverb precedes verb. > > On Mon, Oct 26, 2020, 8:00 AM Harry van der Wolf > wrote: > >> I saw this one as

[hugin-ptx] Hugin 2020.0 beta 1 release

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:

[hugin-ptx] Re: No succes stitch spherical pano from Meike 6.5 mm circular fisheye.

Hi Henk, Am Donnerstag, 1. Oktober 2020 16:33:02 UTC+2 schrieb Henk Tijdink: > > > In PTGUI is the lens in te database. > It gives the following values for the Meike lens. This for the Jpeg files > from the camera > F theoretic 6,5 mm After optimizing are the >

[hugin-ptx] Re: Auto calculation of Yaw, pitch and roll failed in some computers

Hi Parasar, Am Freitag, 2. Oktober 2020 06:46:17 UTC+2 schrieb Parasar Ghimire: > > Hi Thomas, > Thanks for replying. Please find the attached images. This set of pictures > works on my computer when I align them but doesn't work on other computers. > Please advise me if I am missing something.

[hugin-ptx] Re: Auto calculation of Yaw, pitch and roll failed in some computers

Parasar Ghimire schrieb am Donnerstag, 1. Oktober 2020 um 15:33:30 UTC+2: > Where I am having problem is that, it works on some computers and does not > work on others for the same 8 photos. I am using the same set of photos to > do this test on different computers. > I cannot standardize the

[hugin-ptx] Re: enfuse is not compiled with GPU support even when enblend is....

Am Freitag, 4. September 2020 01:41:00 UTC+2 schrieb Elias Tsolis: > > > Until that moment, all perfect... > > then... enfuse saying NO GPU acceleration information by running: > enfuse --version --verbose > > it printed: > enfuse 4.1.5 Extra feature: dmalloc support: no Extra feature: image

[hugin-ptx] Re: cant see full screen preview

Probably an issue with hidpi screen. The same as in https://groups.google.com/d/msg/hugin-ptx/XSzG_GaL00w/p1YBFD9tAgAJ lalv...@gmail.com schrieb am Dienstag, 4. August 2020 um 16:36:15 UTC+2: > I have installed the latest Hugin on my iMac. All works on Catalina > 10.15.5 However, I can t make

Re: [hugin-ptx] Control Point search fails on fairly simple images

Am Donnerstag, 9. Juli 2020 01:38:38 UTC+2 schrieb Shaunak De: > > Thank you so much for taking the time to help me debug this. This probably > is entirely my error in using the tool. > You are using a field of view (fov) of the input images of 100 deg. The mentioned tutorial states: *We

[hugin-ptx] Re: enblend performance / multiprocess safety

Am Sonntag, 28. Juni 2020 22:35:05 UTC+2 schrieb Jani: > > Nona works well! I can fork 12 processes and speed up the "nona -r hdr -m > EXR_m -o out rig1.pto A.exr B.exr C.exr D.exr" part from 56s per frame to > 7s per frame (on average). > That's somehow surprising. Nona is already running

[hugin-ptx] Re: Auto cropped panoramas

Am Sonntag, 28. Juni 2020 13:32:26 UTC+2 schrieb Stanley Green: > > When I “Load images”, “Align”, and “Create panorama”, I end up with a > fully cropped image, i.e., all of the black spaces are cropped out. > Normally this is not a problem, but occasionally, I’d like to see what may > have

[hugin-ptx] Re: can't get fulla (or Hugin) to work for vignetting (and chromatic aber cor)

Am Dienstag, 23. Juni 2020 03:56:03 UTC+2 schrieb Alister Ling: > > There are two pairs of bracketed images which may be confusing things. > i.e. I have 2 stacks in there. I can't seem to find the right stitch tab > check boxes that will give me useful output. The output is really bad if I >

[hugin-ptx] Re: How to determine commands for "Load Images..."

Am Dienstag, 16. Juni 2020 18:14:00 UTC+2 schrieb Mikey: > > Hello in the Hugin GUI you can use the button "Load Images..." in the > Simple view interface to load images. I noticed that it takes some time and > it there appears to be some processing when a user loads images using this >

[hugin-ptx] Re: Panotools wiki cleanup

Hi Eric, Am Donnerstag, 4. Juni 2020 17:06:33 UTC+2 schrieb Erik Krause: > > I thought of all the GSoC articles and all articles about the panotools > photoshop plugins (which don't work any more) or other non-functional > software. > > What do you think? > I have no objection. With the

[hugin-ptx] Re: Adjust horizon in single image

Am Donnerstag, 4. Juni 2020 14:44:38 UTC+2 schrieb Matija Kogoj: > > The gaps that appeared at the edges of the source files were corrected by > setting --coarse-mask variable in enblend options. > Now I'm lost. Enblend is not involved when reproject a equirectancular image. It should only

[hugin-ptx] Re: Adjust horizon in single image

Hi, Am Sonntag, 31. Mai 2020 22:03:30 UTC+2 schrieb Matija Kogoj: > > P.S. does anyone know what the correct value for focal length in an > equirectangular image is? 0? This might be causing the above gap. > For an equirectangular image use a hfov of 360 deg. Using the focal length could

Re: [hugin-ptx] Re: Optimizer GUI x Script

Hi, Am Samstag, 30. Mai 2020 16:19:56 UTC+2 schrieb LF Martins: > > This I can't reproduced. When only the variables of the second images are > marked for optimisation, then only the variables of second images are > modified. > > > No, I meant that even if only one image is set to be optimized

[hugin-ptx] Re: Optimizer GUI x Script

Hi, that are a lot of questions... Am Freitag, 29. Mai 2020 02:42:40 UTC+2 schrieb LF Martins: > > > and it happens even if in the project sets the optimization as only: > # specify variables that should be optimized > v r1 > v p1 > v y1 > v TrX1 > v TrY1 > v TrZ1 > > > This I can't reproduced.

[hugin-ptx] Re: how to build Hugin?

Hi, Am Montag, 25. Mai 2020 02:11:26 UTC+2 schrieb O.Bouizi: > > Would you mind adding -DENABLE_LAPACK:BOOL=ON in INSTALL_cmake? In the > section "Important variables"? It might be helpful. > I'm not sure if using LAPACK brings some advantages. The options was added to silence a compiler

<    1   2   3   4   5   6   7   8   9   10   >