Re: [hugin-ptx] Problems stitching with newer versions of Hugin

On Tuesday, 7 May 2024 at 16:19:55 +, wirz wrote: > On 07/05/2024 10:19, Greg 'groggy' Lehey wrote: >> On Monday, 6 May 2024 at 15:58:31 +, wirz wrote: >>> While I don't know what differs between the versions of hugin / >>> enblend that are packaged in freeBSD,

Re: [hugin-ptx] Problems stitching with newer versions of Hugin

On Monday, 6 May 2024 at 15:58:31 +, wirz wrote: > On 06/05/2024 06:05, Greg 'groggy' Lehey wrote: >> I've been making documentary panoramas of my house every week for the >> past 10 years, and for a long time I was using version 2018.0.0 of >> hugin on an old machi

[hugin-ptx] Purpose of this list (was: align_image_stack parameters)

On Wednesday, 17 April 2024 at 23:39:07 -0700, Chris wrote: > T.Modes, Wie du sicher weißt, bedeutet das deutsche Wort "Gift" etwas ganz > anderes als das englische Wort "gift" :). > Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie > haben etwas unterschiedliche

Re: [hugin-ptx] Disappearing posts

On Monday, 8 April 2024 at 10:13:09 -0700, Chris wrote: > This is my third post. The previous two attempts have both disappeared. > There was no suggestion that they might have been awaiting moderation. What > is going on? I don't know, but I'd guess that it's at your end. It's not moderation:

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

On Thursday, 28 March 2024 at 18:09:38 -0700, Venkat wrote: > Your example showed the file names in alphabetical order. My > understanding was that this isn't what you wanted. > We were providing alphabetical order so that even when we pass > --sort we would end getting the right order

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

On Wednesday, 27 March 2024 at 13:44:34 -0700, Venkat wrote: > Thanks for taking a stab at this. > >> You don't say how you "provide the individual images". If you >> specify the names in the order you want, you're half way there. But >> you're using the undocumented --sort option, which imposes

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

ons. Any pointers would be really appreciated. Current messages: On Monday, 25 March 2024 at 23:48:02 -0700, Venkatramani Sankarlingam wrote: > On Mon, Mar 25, 2024 at 4:09 PM Greg 'groggy' Lehey > wrote: > >> On Monday, 25 March 2024 at 11:19:52 -0700, Venkat wrote: >>>

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

On Monday, 25 March 2024 at 11:19:52 -0700, Venkat wrote: > > Cool thanks for the note. I will see if we could tweak the assistant to > handle cpfind --prealigned. If you have the information handy, it would be > helpful as well. Again, I may be misunderstanding, but I'm not sure that

Re: [hugin-ptx] Providing order of images in Hugin assistant

On Monday, 25 March 2024 at 8:55:19 -0700, Venkat wrote: > > We are trying to use the hugin assistant in code to stitch a > panoramic image. We were wondering is there command line parameter > to force the order of images. I don't understand the question. If you're using the "command line",

Re: [hugin-ptx] Hugin making spiral panorama

[Rearranged for clarity] On Tuesday, 20 February 2024 at 7:55:43 -0800, Graham Jantz wrote: > On Monday, February 19, 2024 at 6:06:07 PM UTC-7 Groogle wrote: >> My workaround, which works in 99% of the cases: start with a very few >> images and align them in the fast panorama preview window. If

Re: [hugin-ptx] Hugin making spiral panorama

On Monday, 19 February 2024 at 14:08:36 -0800, Graham Jantz wrote: > Hi all, looking for some advice on running Hugin. I have a panorama of 83 > photos that I'm trying to stitch together but the resulting image it's > giving me is a weird spiral shape. I used the assistant and went through >

Re: [hugin-ptx] Hugin 2022.0 Black blotches on final stitches

On Saturday, 11 November 2023 at 22:08:34 -0800, Robert Mahar wrote: > ( OK, well 2022.0.0.a0962865f932 ) > > I often get black regions in final stitches. For smaller projects, not > often. "Me too". This seems to be happening more frequently. Until recently I was using the 2018 version, then

Re: [hugin-ptx] Hugin 2023.0.0 released

On Saturday, 11 November 2023 at 0:58:54 -0800, T. Modes wrote: > Hi all, > > today we are releasing Hugin 2023.0.0 The FreeBSD port has been updated to this version. Update your source tree and build /usr/ports/graphics/hugin. It will take a little longer for the package to become available.

Re: [hugin-ptx] Multi-row panoramas

On Tuesday, 22 August 2023 at 20:54:51 -0400, Hugin developers list wrote: > The pop-up did occur and I chose do not link. The resulting image was very > wide and narrow. Both wide and narrow? I have difficulty believing this. I've tried all three answers and find that if I select "Link

Re: [hugin-ptx] Multi-row panoramas

On Tuesday, 22 August 2023 at 8:24:24 -0400, Stanley Green wrote: > Thank you Greg, I really appreciate all the work you guys are putting into > solving my problem > >> On Aug 22, 2023, at 7:48 AM, Greg 'groggy' Lehey wrote: >> >> On Tuesday, 22 August 2023 at 6

Re: [hugin-ptx] Multi-row panoramas

On Tuesday, 22 August 2023 at 6:57:45 -0400, Stanley Green wrote: > I tried stitching different pair combinations. A lot of detail missing here. > Row 1 & 3: No problem > Row 1 & 2: No problem > Row 2 & 3: No problem Except that the second and third variants only give you part of the pano. >

Re: [hugin-ptx] Multi-row panorama

On Monday, 21 August 2023 at 20:36:26 -0600, dgjohnston wrote: > Greg, thanks for the additional information. The images in this set > are well suited to the quick run though using the Fast Pano Preview > because of the randomness of the rocks, trees, and water. It’s hard > to detect any minor

Re: [hugin-ptx] What do I wrong?

On Monday, 21 August 2023 at 3:42:13 -0700, Martin wrote: > > I just started to test Hugin, and prepared four well matching levelled > images . I got this bent panorama: Without seeing the input files, it's hard to know if anything went wrong. But you can fix this from the Move/Drag tab in the

Re: [hugin-ptx] Multi-row panorama

hat. I'm confused. A week ago I wrote: On Tuesday, 15 August 2023 at 11:02:08 +1000, Greg 'groggy' Lehey wrote: > > My suggestion: use the Align tab on the Fast Panorama Preview. Specifically, 1. Load the files from the "Load Images" tab in the Fast Panorama Preview. 2. Sel

Re: [hugin-ptx] Multi-row panorama

On Thursday, 17 August 2023 at 6:12:55 -0400, Hugin developers list wrote: > David, > We transfer is not cooperating. I tried sending it several time to > the email address shown on your responses to me. I'm almost happy. I set up an account, but it didn't make it clear how it worked. If you

Re: [hugin-ptx] Multi-row panorama

On Wednesday, 16 August 2023 at 13:35:48 -0400, Hugin developers list wrote: > Beautiful day, less than beautiful results > > I shot a set of 18 images( 3 rows / 6 panels). I imported the raw > images into Capture One and then exported the images as Tiffs. I > tried to stitch the 18 images into a

Re: [hugin-ptx] Multi-row panorama

On Monday, 14 August 2023 at 15:12:37 -0400, Stanley Green wrote: > Is anybody familiar with this video tutorial? > https://www.youtube.com/watch?v=OaLNFKh82Dg > "Producing multi-row image panoramas with Hugin" No, I haven't watched it. I'll try to find time to do so later. > In this tutorial,

Re: [hugin-ptx] Multi-row panoramas

On Friday, 11 August 2023 at 17:57:46 -0400, Stanley Green wrote: > I am trying to learn how to try to stitch a multi-row pano using Hugin (Mac). > > Tomorrow I plan to take 6 shots (2 rows, 3 shots per row) and see > how it goes. Any tips for making work? I used to make a lot of multirow

Re: [hugin-ptx] Re: automatically solving vignetting at sunrise and down in a series of panoramas

On Wednesday, 5 July 2023 at 22:47:00 +0100, Bruno Postle wrote: > Yes, something like this (all on one line, Google will mangle this email): > > enblend -o project.tif -l 27 project.tif project0001.tif Is this documented anywhere? I see a brief mention of the syntax on the man page, but

Re: [hugin-ptx] Re: Vuze Camera 3D 360° VR. Parameters for import and stitching photo

On Wednesday, 1 March 2023 at 10:33:44 -0800, Francesco Sorrentino wrote: > > Il giorno mercoled� 1 marzo 2023 alle 17:47:25 UTC+1 T. Modes ha scritto: > >> Could you provide a sample set of images so we can have a look? > > Of course! Due to group size restrictions, I send four photos at a time

Re: [hugin-ptx] is "downscale final pano = 70% of max width" overriden by "calculate optimal size"?

On Sunday, 22 January 2023 at 10:38:34 -0800, T. Modes wrote: > bruno...gmail.com schrieb am Sonntag, 22. Januar 2023 um 12:25:21 UTC+1: >> This 'calculate optimal size' function uses the 70% default. > > The calculate optimal size button is using by default no additional scaling > factor. (So it

[hugin-ptx] HEADS UP: Don't use gmail! (was: Control Point dialog features)

I've been chasing up a mail configuration problem delivering mail to Gmail (hint: make sure you have an SPF record or similar), and in the process came across this message and about 30 more that were filed as spam: On Friday, 21 January 2022 at 10:34:06 -0800, johnfi...@gmail.com wrote: > I want

Re: [hugin-ptx] Re: How to export panos to Google Maps?

On Tuesday, 4 January 2022 at 4:03:54 -0800, Carlo wrote: > Can anyone see this one? > https://goo.gl/maps/xJxgPLeSrAdgLmQHA Yes, looks fine; not too far from where I used to live. > I just published it with iPhone and the Street View app. And that's my problem. WHY does Google insist on a

[hugin-ptx] How to export panos to Google Maps?

I have a relatively standard 180°x360° panorama of a street crossing that I wanted to put on Google Maps. I had investigated this some time in the past and discovered that I needed various metadata if the vertical angle wasn't 180°, and put it in the "too hard" basket. But this pano is complete.

Re: [hugin-ptx] HDR Tutorial

On Saturday, 13 November 2021 at 16:32:12 -0500, Stanley Green wrote: > > I have one problem remaining with the finished panorama, if you look > at the rocks on the left side of the image, you will see a > ghost. Between images one and two the guy sat down. > > I was able to clone stamp it out in

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

On Wednesday, 14 July 2021 at 16:35:03 -0400, Hugin developers list wrote: > Thank you. Yes, Affinity uses control points very similar to Hugin. > I did not bother to insert CPs because I was only trying to point out that > Hugin was having trouble finding the cPs, but Affinity had no such

Re: [hugin-ptx] Hugin 20.0 does not see external drive

On Wednesday, 28 April 2021 at 4:31:07 -0700, Brian Charles wrote: > I just updated Hugin on my Ubunto distro and it does not see my external > drive. It is seen in my file explorer. Any suggestions? Hugin doesn't see (disk) drives. If anything, it sees mounted file systems, but I don't

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

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

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

On Monday, 1 February 2021 at 0:25:51 +, Hugin developers list wrote: > I take many nature landscape panoramas in which most features are > not straight like buildings. So when I want to remove CPs, the > rectangle selection (Ctrl + right click) is unhandy, as I have to > draw many

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

[sequence recovered] On Sunday, 3 January 2021 at 10:57:52 -0800, Abrimaal wrote: > 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: >>> today we are releasing beta 1 of Hugin 2020.0.0 >> >> A FreeBSD package is

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

On Sunday, 13 December 2020 at 9:18:08 +, Bruno Postle wrote: > On Sun 13-Dec-2020 at 11:43 +1100, Greg 'groggy' Lehey wrote: >> On Saturday, 12 December 2020 at 5:40:30 -0800, T. Modes wrote: >>> Hi all, >>> >>> after a long beta 1 phase without

[hugin-ptx] Stitching vertical panoramas (was: Greetings and hello!)

You will probably get more responses with a descriptive Subject: line. On Thursday, 12 November 2020 at 11:48:56 -0800, EM Matthews wrote: > Is there a way to stitch together vertical panoramas using hugin? The same way you stitch any panorama. Hugin detects the control points and arranges the

Re: [hugin-ptx] Some typo

On Sunday, 1 November 2020 at 9:11:01 -0800, Cristian Marchi wrote: > > Hi, while translating new strings I've found some typo: > > PanoOperation.cpp row 603 e 1277 > "...have to have to same size" I think it should be "...need to have the > same size" "Have to have" is perfectly correct

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

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

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

On Monday, 5 October 2020 at 14:21:34 -0700, Henk Tijdink wrote: > Hello Thomas > > Removing the control points in the Nadir did the job. Did you read my reply? For me it worked out of the box, and produced better results than you attach. See

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

On Friday, 2 October 2020 at 6:50:35 -0700, Henk Tijdink wrote: > I have send the pictures with Wetransfer. OK, I have good news and not-so-good news. First the good news: the panos stitched out of the box with no problems. First I had to tell Hugin about the lens: circular fisheye, 190°

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

On Thursday, 1 October 2020 at 21:46:17 -0700, Parasar Ghimire wrote: > 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. > My general

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

On Thursday, 1 October 2020 at 7:33:02 -0700, Henk Tijdink wrote: > Dear readers, > I've bought a Meike circular fisheyelens 6.5 mm f2 for a MFT camera. and > want to use it for making full spherical panorama's. > You get than partly a circle On the long side of the sensor it is shaved > off.

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

On Thursday, 3 September 2020 at 15:12:19 -0700, Elias Tsolis wrote: > Compiling enblend do not result support for GPU for enfuse. I followed > these information for compiling hugin / enblend (included enfuse). > > ... > Then, to get information on the extra features enabled in enblend i run: >

Re: [hugin-ptx] Hugin 2019.2.0 released

On Monday, 30 December 2019 at 1:31:31 -0800, 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: >

Re: [hugin-ptx] Re: Request : forum migration

On Friday, 22 November 2019 at 14:13:25 +, ChameleonScales' wrote: > So I finally deleted my Google account completely and I'm sending > this email as a test to see if copying the subject line from the > topic's web page (in this case Re: [hugin-ptx] Re: Request : forum > migration) puts it as

Re: [hugin-ptx] How to email in existing topic

On Thursday, 21 November 2019 at 14:42:25 +, Hugin developers list wrote: > Hi, sorry to ask but I didn't find an answer in the FAQ or > elsewhere. I just subscribed to the mailing list using my email > (not a Google account) and I would like to add a post to an existing > topic. Adding a

Re: [hugin-ptx] OpenGL preview button greyed out

On Tuesday, 1 October 2019 at 16:07:13 +0100, Bruno Postle wrote: > I'm no expert, but this looks fine. > > I suggest deleting/renaming your ~/.hugin file to reset your preferences. That's a bit drastic. You can also just rename it: bash$ mv ~/.hugin ~/.hugout That way you replace it if that

Re: [hugin-ptx] Request : forum migration

On Tuesday, 23 July 2019 at 9:41:36 +0800, RizThon wrote: > > The discourse interface is from my point of view way better than > google groups, but migrating to discourse will probably be quite > some work and a change for all people used to the mailing list Yes, I was thinking something like

Re: [hugin-ptx] Request : forum migration

On Sunday, 21 July 2019 at 7:09:18 -1000, David W. Jones wrote: > On July 21, 2019 5:12:13 AM HST, "J. Schneider*" wrote: >> Hi, >> I have a question about how Disourse or an alternative would be used. >> My >> short seach and wikipedia reading on Discourse didn't answer this. >> What would a

Re: [hugin-ptx] Linux distro of choice?

On Monday, 15 July 2019 at 20:39:54 -1000, David W. Jones wrote: > On 7/13/19 8:38 PM, Greg 'groggy' Lehey wrote: >> I've tried all three of these distros. I decided against Fedora, but >> that was well over 10 years ago, so it's not relevant to modern >> releases. I

Re: [hugin-ptx] Linux distro of choice?

On Saturday, 13 July 2019 at 20:34:05 -1000, David W. Jones wrote: > On July 13, 2019 5:51:33 PM HST, Terry Duell wrote: >> Hello Greg, >> >> On Sun, 14 Jul 2019 12:20:10 +1000, Greg 'groggy' Lehey >> wrote: >> >>> I'm seeing a few issues with Hugin ru

[hugin-ptx] Linux distro of choice?

I'm seeing a few issues with Hugin running on FreeBSD. While I don't think it has anything to do with FreeBSD, it would be nice to compare its behaviour with what happens under Linux. What distro should I choose? Greg -- Sent from my desktop computer. Finger groog...@gmail.com for PGP public

Re: [hugin-ptx] Re: Removing control point detectors (was: autopano-sift-c failed with error code: 2)

On Thursday, 20 June 2019 at 10:34:39 +0200, Jens Scheidtmann wrote: > Hi Greg, > > Am Do., 20. Juni 2019 um 04:05 Uhr schrieb Greg 'groggy' Lehey > : >> >> On Tuesday, 18 June 2019 at 9:46:32 -0700, T. Modes wrote: >>> Am Dienstag, 18. Juni 2019 02:25:15 UTC+2

Re: [hugin-ptx] Re: Removing control point detectors (was: autopano-sift-c failed with error code: 2)

On Tuesday, 18 June 2019 at 9:46:32 -0700, T. Modes wrote: > Am Dienstag, 18. Juni 2019 02:25:15 UTC+2 schrieb Groogle: >> >> Please don't remove panomatic until cpfind functions reliably under >> all circumstances. >> > I'm not aware of problems with cpfind. There are no reports in the bug >

[hugin-ptx] Removing control point detectors (was: autopano-sift-c failed with error code: 2)

On Monday, 17 June 2019 at 8:27:35 -0700, T. Modes wrote: > Am Montag, 17. Juni 2019 11:52:21 UTC+2 schrieb Henk Tijdink: >> >> When you take Autopano Sift-C from the default settings, then yoy can take >> away Autopano (A. Jenny) from the default settings too. >> > I will remove all other cp

Re: [hugin-ptx] stitching 4 pictures with meike 6.5mm f2.0

On Friday, 3 May 2019 at 11:27:38 -0700, giuseppe.porci...@gmail.com wrote: > Hi, > > I have problems in stitching 4 pictures from a sony a5000 (aps-c) and meike > 6.5 f/2.0 manual lens. > I choosed "fisheye circular lens" and I inserted a 190 degree HFOV value > (as for meike specs) and also 185

Re: [hugin-ptx] Re: Hugin 2019 crash at startup

On Friday, 3 May 2019 at 20:11:23 +0200, giuseppe porciani wrote: > 2019-05-03 8:52 GMT+02:00, T. Modes : >> Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle: >>> (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time() >>> should not be called with 0, or

Re: [hugin-ptx] Re: Hugin 2019 crash at startup

On Thursday, 2 May 2019 at 23:52:24 -0700, T. Modes wrote: > Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle: >> >> (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time() >> should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the >> timestamp >>

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

On Monday, 29 April 2019 at 19:04:23 -0700, James Proctor wrote: > On Monday, April 29, 2019 at 6:26:49 PM UTC-7, Groogle wrote: >> >> On Monday, 29 April 2019 at 18:19:23 -0700, James Proctor wrote: >>> If you have ideas re. my bigger problem of creating a true 360° pano >>> from the original

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

On Monday, 29 April 2019 at 18:19:23 -0700, James Proctor wrote: > If you have ideas re. my bigger problem of creating a true 360° pano > from the original fourteen images, I'd appreciate! See earlier posts > in thread for clarification. As I suggested, put the images somewhere where somebody can

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

On Sunday, 28 April 2019 at 16:34:44 -0700, 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.

[hugin-ptx] Hugin 2019 crash at startup

I've received a bug report against Hugin 2019.0 running on FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237585 Summary: after "normal" error messages on startup, it receives: (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time() should not be called with 0,

Re: [hugin-ptx] Is there a tutorial for stitching dual lens photos?

On Tuesday, 9 April 2019 at 18:05:44 -0700, CarbonMan wrote: > I have a Samsung Gear 360. I would like to convert an image into a skybox. > How do I go about doing that? I have only used Hugin for stitching when > there were multiple images that needed to be stitched together. In this > case

Re: [hugin-ptx] Hugin 2019.0.0 released

On Friday, 5 April 2019 at 23:39:27 -0700, T. Modes wrote: > Hi all, > > today we are releasing Hugin 2019.0. The FreeBSD port has been updated. You can build from source now, and in a few days the package will be available. Greg -- Sent from my desktop computer. Finger groog...@gmail.com for

Re: [hugin-ptx] stitching two circular fisheye images

On Friday, 5 April 2019 at 7:14:20 -0700, giuseppe.porci...@gmail.com wrote: > Hi, > I would like to use hugin to stitch 2 circular fisheye image. > I have a sony a5000 aps-c camera and I would like to buy a meike 6.5mm > circular fisheye lens for sony aps-c sensor. > The image will fit into the

Re: [hugin-ptx] Hugin 2019.0.0 rc1 released

On Saturday, 23 March 2019 at 2:05:42 -0700, T. Modes wrote: > Hi all, > > today we are releasing release candidate 1 of Hugin 2019.0. If anybody wants a FreeBSD port, please contact me. Greg -- Sent from my desktop computer. Finger groog...@gmail.com for PGP public key. See complete headers

Re: [hugin-ptx] Re: nona, verdandi and --wrap parameter

On Tuesday, 1 January 2019 at 23:48:44 -0800, T. Modes wrote: > Am Dienstag, 1. Januar 2019 09:45:40 UTC+1 schrieb stephan...@wanadoo.fr: >> >> I'm trying to use Hugin to batch stitch many partial equirectangular >> panorama made with my custom rig (Xiaomi Yi 2k x4) >>

Re: [hugin-ptx] Aligning multiple image stacks in the same pano - any way to do this automatically?

On Friday, 19 October 2018 at 19:42:34 -0700, Geoffrey Liu wrote: > I have a panorama, 42 images in total, 14 frames of 3 exposure stacks each. > As part of my workflow, I align the 3 images in each stack. > > So far the only way I've found to do this is to: > > ... I do something very similar.

Re: [hugin-ptx] libpano gcc 8 warnings

On Sunday, 23 September 2018 at 23:43:38 +0100, Bruno Postle wrote: > > > On 23 September 2018 13:48:10 BST, Andreas Metzler wrote: >> >> building libpano with gcc 8 (instead of 7) triggers a couple of new >> warnings that might be interesting: >> >> parser.c: In function 'ReadImageDescription':

[hugin-ptx] Offensive behaviour (was: Wrong assumptions)

On Wednesday, 19 September 2018 at 8:22:08 -0700, T. Modes wrote: > Am Mittwoch, 19. September 2018 06:00:08 UTC+2 schrieb Groogle: Nein, er schrieb das am Mittwoch, 19. September 2018 14:00:03 +1000. Er hat mit UTC+2 nichts am Hut. Wo die 5 Sekunden Versatz entstanden sind, ist mir ein Rätsel.

[hugin-ptx] Offensive behaviour (was: BigTIFF)

This is mainly addressed to Thomas Modes, but since it's not the first time I've seen him behave like this, I think it's time to come out in the open. On Tuesday, 18 September 2018 at 10:00:34 -0700, T. Modes wrote: > Am Dienstag, 18. September 2018 05:46:34 UTC+2 schrieb Groogle: >> >> There is

Re: [hugin-ptx] Re: BigTIFF

On Monday, 17 September 2018 at 16:30:17 -0700, Battle wrote: > HI Thomas, > I hate to be a kludge, ... My guess is that you were looking for a different word. To quote OED, a kludge is "a hastily improvised and poorly thought-out solution to a fault or ‘bug’." > I see that in regular Hugin

Re: [hugin-ptx] Help!!! Hugin not stitching correctly with fisheye lens

On Thursday, 6 September 2018 at 8:58:30 -0700, T. Modes wrote: > Hi Greg, > Am Donnerstag, 6. September 2018 07:12:04 UTC+2 schrieb Groogle: >> >> TO HUGIN DEVELOPERS: It seems to me that there are bugs involved here, >> possibly relating to circular fisheye lenses. I take photos with full >>

Re: [hugin-ptx] Help!!! Hugin not stitching correctly with fisheye lens

On Wednesday, 5 September 2018 at 12:43:40 -0700, jiangjia...@gmail.com wrote: On Wednesday, 5 September 2018 at 12:55:36 -0700, jiangjia...@gmail.com wrote: Once is enough,especially since you included relatively large images (for email). It would have been better to put all the images on

Re: [hugin-ptx] Re: Stitching errors despite numerous and precise manual control points

On Monday, 27 August 2018 at 12:11:41 -0700, Hugin developers list wrote: > @ Greg, Panostar:thanks for the detailed responses. > > Concerning the zenith/nadir: the two pictures in question are "horizon" > ones (shot horizontally). > > Concerning entrance pupil/parallax errors, the area that poses

Re: [hugin-ptx] Stitching errors despite numerous and precise manual control points

On Friday, 24 August 2018 at 17:26:06 -0700, Hugin developers list wrote: > Dear All, > > I'm working on a relatively high precision 360x180 panorama, and have an > issue with the stitching. > 1) In the ground tiling, the stitching makes irregular cracks, even tough > the control points that I

Re: [hugin-ptx] Re: What causes highlight clipping to gray in hdr mode?

On Tuesday, 21 August 2018 at 13:39:18 -0700, Matija Kogoj wrote: > I believe to have figured this out -* colour space*. > > Working on other scenes in the meantime I found that jpgs from my camera > were written in AdobeRGB97, which is proprietary. Using 16bit TIFF files, > exported from RAW,

Re: [hugin-ptx] strange issues with 360 pano?

On Monday, 13 August 2018 at 22:04:50 -0700, clepsydrae wrote: > > Here's what I've gotten to > now that I'm not > optimizing translation. Very happy with the results. Just need to > understand why translation optimization confused it so

Re: [hugin-ptx] Re: strange issues with 360 pano?

On Monday, 13 August 2018 at 21:50:18 -0700, clepsydrae wrote: > Aha -- it seems to be related to optimization of translation... I inspected > the .pto and saw some extreme-seeming values for TrX, TrY, and TrZ. I > started over and did not optimize translation and the issue doesn't happen.

Re: [hugin-ptx] strange issues with 360 pano?

On Monday, 13 August 2018 at 17:50:53 -0700, clepsydrae wrote: > I have uploaded all the test images and the demo .pto here > -- but be warned > that it is a 2GB file. It is uploading now and should be done at the latest > in ~45 minutes

Re: [hugin-ptx] strange issues with 360 pano?

On Monday, 13 August 2018 at 15:31:59 -0700, clepsydrae wrote: > Howdy -- I'm attempting a pano made of 14 images (~10mm on a 1.62x APS-C). > CPFind doesn't find CPs well unless I drag the images to a rough correct > overlap, so I do that first. > > Then CPFind finds the CPs, I remove some CPs

Re: [hugin-ptx] Crop to maximal area issue

On Sunday, 5 August 2018 at 3:00:37 -0700, Capri Flyhennessy wrote: > Hi Greg, > > Here are the jpg's I am using: > https://drive.google.com/open?id=1tQ78OvePAh1hb9B_g3XIWhZY48_0L4id > > And the script: > pto_gen -o project.pto *.jpg > cpfind -o project.pto --multirow --celeste

Re: [hugin-ptx] Crop to maximal area issue

[reformatted] On Saturday, 4 August 2018 at 2:42:31 -0700, Capri Flyhennessy wrote: > On Saturday, August 4, 2018 at 2:52:15 AM UTC+2, Groogle wrote: >> On Friday, 3 August 2018 at 11:08:00 -0700, Capri Flyhennessy wrote: >>> >>> I am quite new to Hugin but I am writing a bash script to >>>

Re: [hugin-ptx] remapping and blending issues

On Friday, 3 August 2018 at 18:01:53 -0700, Matija Kogoj wrote: > ... > > I don't know what else to do, and have not found anything relating to these > issues in the documentation. > > At the link you will find a zip file with the panorama in question, the > save file, result... >

Re: [hugin-ptx] Crop to maximal area issue

On Friday, 3 August 2018 at 11:08:00 -0700, Capri Flyhennessy wrote: > Hi, > > I am quite new to Hugin but I am writing a bash script to automatically run > through all of my panoramas and I have bumped into an irritating issue that > I do not really know how to fix. > The whole process works but

Re: [hugin-ptx] Re: RAW support with hugin ?

On Wednesday, 11 July 2018 at 8:29:20 -0400, Robert Krawitz wrote: > On Wed, 11 Jul 2018 14:15:19 +1000, Greg 'groggy' Lehey wrote: >> On Tuesday, 10 July 2018 at 8:10:08 -0700, Albert Szostkiewicz wrote: >>> As much as I wish to stay with Linux (which is my main operating >

Re: [hugin-ptx] Re: RAW support with hugin ?

On Tuesday, 10 July 2018 at 8:10:08 -0700, Albert Szostkiewicz wrote: > Personally I am interested in stitching 360 full, true HDR images. I > am hoping to stitch and get as much of original data as I can. With > PtGui for eg. I am able to throw my Canon RAWs directly and proper > exposure merge

[hugin-ptx] Raw image support with hugin (was: RAW support with hugin ?)

On Thursday, 5 July 2018 at 0:33:45 -1000, David W. Jones wrote: > > So when you add a bunch of RAW files to Hugin, it proceeds to popup > a bunch of windows, one for each frame? No. It displays a window "Could not decode (file name). Abort". And I think that's correct. Greg -- Sent from my

[hugin-ptx] cpfind function (was: Best Linux distro for Hugin?)

On Monday, 4 June 2018 at 12:30:17 +1000, Greg 'groggy' Lehey wrote: > I've been having a strange issue with Hugin for some time now, and > I've traced it to a difference between the Microsoft and FreeBSD > versions. On the FreeBSD version, the control point detectors find no > co

Re: [hugin-ptx] Re: Documentation for project (.pto) files?

On Sunday, 17 June 2018 at 0:23:16 -0700, T. Modes wrote: > Am Sonntag, 17. Juni 2018 06:47:41 UTC+2 schrieb Groogle: >> >> One thing I haven't found is a description of the project file. I >> suppose I could UTSL, but can anybody point me to documentation? > >

[hugin-ptx] Documentation for project (.pto) files?

I'm currently going through the documetation on the wiki, which is sorely in need of it. I'll submit patches when I'm done, but first I need to understand it. One thing I haven't found is a description of the project file. I suppose I could UTSL, but can anybody point me to documentation? Greg

[hugin-ptx] Control point finder problems (was: Best Linux distro for Hugin?)

On Monday, 4 June 2018 at 18:37:36 +0200, Gunter Königsmann wrote: > Also cpfind will fail if you have once set up the lens parameters wrong by > a big enough factor once and hugin remembers that lens and your parameters. Yes, I've run into that, especially as in this case I was using a fisheye

[hugin-ptx] Control point finder problems (was: Best Linux distro for Hugin?)

On Monday, 4 June 2018 at 11:18:13 +0100, Bruno Postle wrote: > On 4 June 2018 03:30:17 BST, Greg 'groggy' Lehey wrote: >> I've been having a strange issue with Hugin for some time now, and >> I've traced it to a difference between the Microsoft and FreeBSD >> versions. O

[hugin-ptx] Best Linux distro for Hugin?

I've been having a strange issue with Hugin for some time now, and I've traced it to a difference between the Microsoft and FreeBSD versions. On the FreeBSD version, the control point detectors find no control points at all between the first and last images of a circular panorama. There's no

Re: [hugin-ptx] Problems with PNG images on 2018.0 on FreeBSD

On Wednesday, 30 May 2018 at 17:27:22 +1000, Greg 'groggy' Lehey wrote: > On Wednesday, 30 May 2018 at 6:56:07 +0100, Bruno Postle wrote: >> >> >> On 30 May 2018 04:26:03 BST, Greg 'groggy' Lehey wrote: >>> I've just received a bug report on Hugin 20

Re: [hugin-ptx] Problems with PNG images on 2018.0 on FreeBSD

On Wednesday, 30 May 2018 at 6:56:07 +0100, Bruno Postle wrote: > > > On 30 May 2018 04:26:03 BST, Greg 'groggy' Lehey wrote: >> I've just received a bug report on Hugin 2018.0.0.5abfb4de7961: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228547 > >> I s

[hugin-ptx] Problems with PNG images on 2018.0 on FreeBSD

I've just received a bug report on Hugin 2018.0.0.5abfb4de7961: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228547 It seems that this package can't process PNG files. I've checked and confirmed, and also that it does appear to run with the Microsoft package downloaded from the web site

Re: [hugin-ptx] Re: q: when i creat panorama, error occured. pop up massage is "Could not open project file:/private/var/folders/tn/xvbzh64d1fzcttckmsj_bk800000gn/T/TemporaryItems/" please help me.

On Monday, 9 April 2018 at 17:27:04 -0700, Paul Yang wrote: > How can i change the Temporary dir? > I try to change preferences menu. But can't change. I've run into similar problems on other platforms, but I haven't found the details yet. Somehow there's more to this problem than you have

[hugin-ptx] FreeBSD port updated (was: Hugin 2018.0 released)

On Saturday, 3 February 2018 at 23:58:20 -0800, T. Modes wrote: > Am Samstag, 3. Februar 2018 23:31:05 UTC+1 schrieb Groogle: >> >> The tarball for 2017.0 was called hugin-2017.0.0.tar.bz2. Does the >> project intend to truncate the name from now on, or was this an >> oversight? > > This was an

  1   2   3   4   >