Re: [hugin-ptx] Problems with stitching a GigaPano ...

On 11/29/2017 12:23 PM, Terry Duell wrote: On Wed, 29 Nov 2017 20:13:46 +1100, David W. Jones wrote: I've been using Hugin for many years, maybe it's me, but how do you stitch *part* of a project? Deselect the images not wanted for that part, stitch and save, then

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On Thu, 30 Nov 2017 09:39:47 +1100, Paul Elliott wrote: Hi, I've been following this thread as I'm having similar problems stitching a 312 image pano to a final size of over 600Mpx. Using some of the options above in the thread I've got it to work with JPGs and

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Hi, I've been following this thread as I'm having similar problems stitching a 312 image pano to a final size of over 600Mpx. Using some of the options above in the thread I've got it to work with JPGs and I'm now stitching Tiffs for the final output. In the process I tried breaking it down

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On Wed, 29 Nov 2017 20:13:46 +1100, David W. Jones wrote: I've been using Hugin for many years, maybe it's me, but how do you stitch *part* of a project? Deselect the images not wanted for that part, stitch and save, then select the images for the next part, and so

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Ah, thanks. Never tried that. On November 29, 2017 3:33:04 AM HST, 'dkloi' via hugin and other free panoramic software wrote: >In a preview window, only selected images get stitched into the final >pano. > >On Wednesday, 29 November 2017 09:13:53 UTC, GnomeNomad

Re: [hugin-ptx] Problems with stitching a GigaPano ...

In a preview window, only selected images get stitched into the final pano. On Wednesday, 29 November 2017 09:13:53 UTC, GnomeNomad wrote: > > > > On November 28, 2017 10:41:18 PM HST, Terry Duell > wrote: > >On Wed, 29 Nov 2017 17:03:49 +1100, Emad ud din Bhatt >

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On November 28, 2017 10:41:18 PM HST, Terry Duell wrote: >On Wed, 29 Nov 2017 17:03:49 +1100, Emad ud din Bhatt > >wrote: > >> *"One approach to stitch very large projects is to split your project >up >> into sub-projects, stitch each, then stitch the

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Hello Emad, On Wed, 29 Nov 2017 17:03:49 +1100, Emad ud din Bhatt wrote: I had same enblend issues. Enblend kept working working and nothing happened at the end memory errors. I checked it with better RAM but no success. OK, which version of Enblend and which OS?

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On Wed, 29 Nov 2017 17:03:49 +1100, Emad ud din Bhatt wrote: *"One approach to stitch very large projects is to split your project up into sub-projects, stitch each, then stitch the sub-panos.*" interested to know how to do it. If i output partial images than how can

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Hi Terry, Yes i am referring to gigapixel pano and gigapixel images. For example 68000x18000 I had same enblend issues. Enblend kept working working and nothing happened at the end memory errors. I checked it with better RAM but no success. *"One approach to stitch very large projects is to

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Hello Emaad, On Wed, 29 Nov 2017 15:51:17 +1100, Emad ud din Bhatt wrote: Hi All, Following this thread. I have raised this issue many times that hugin cant stitch high res and gigapixel images. Lets c if you people can help me out as well :) I assume you mean a

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Hi All, Following this thread. I have raised this issue many times that hugin cant stitch high res and gigapixel images. Lets c if you people can help me out as well :) On Mon, Nov 6, 2017 at 11:47 AM, wrote: > I use also version 4.2 > > This night I will try again

Re: [hugin-ptx] Problems with stitching a GigaPano ...

I use also version 4.2 This night I will try again a run without parameters -- 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"

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Which version of enblend was that? I have enblend 4.2 on this laptop and have never used either of those settings. On 11/05/2017 12:01 AM, jojaeger12031...@gmail.com wrote: Yeah this really looks like modern art :D The size was calculated by hugin. I have player around with the options: For

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Yeah this really looks like modern art :D The size was calculated by hugin. I have player around with the options: For me the best setting is: --pre-assemble --primary-seam-generator=nearest-feature-transform No black holes & full size panorama Am Samstag, 4. November 2017 06:12:01 UTC+1

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Try specifying nft as the seam generator instead of graph cut in the enblend options. I ran into problems where the default seam generation method was coming up with really bizarre seams, hence leading to weird results in the final stitch. On Friday, 3 November 2017 07:39:06 UTC,

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Wow, that's a major abstract/psychedlic blowup in middle of the 2nd (larger) image. I have no idea where it might come from. Anyone else? Just out of curiousity ... was that 36336 pixel width set by Hugin (using the Stitcher tab's "Calculate Optimal Width" button), or a width you specified?

Re: [hugin-ptx] Problems with stitching a GigaPano ...

This night hugin success the build process with no error. One with a width of 2 One with a width of 36336 But here you can see yourself, something went wrong: www.dropbox.com/s/bjswqcl2s4nurg2/20k_36k.png?dl=0 Am Freitag, 3. November 2017 01:09:25 UTC+1 schrieb GnomeNomad: > > > > On

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On November 2, 2017 1:20:04 PM HST, Sean Greenslade wrote: >On Thu, Nov 02, 2017 at 12:42:36PM -0700, jojaeger12031...@gmail.com >wrote: >> Thanks for your reply. >> Yeah I've readed just in the moment, that it is deprecated. >> >> Exsample from Enblend: >>

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On Thu, Nov 02, 2017 at 12:42:36PM -0700, jojaeger12031...@gmail.com wrote: > Thanks for your reply. > Yeah I've readed just in the moment, that it is deprecated. > > Exsample from Enblend: > http://enblend.sourceforge.net/gigapixel.htm > > Here the machine just have 2GB RAM and it works for a

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Image cache sounds like something that keeps entire images in memory so they can be accessed faster. What I am not sure is if enblend has a tile cache like the gimp that splits the image into tiles and acts only on as many tiles at a time as fit into the RAM. ... In case that enblend wants to

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Thanks for your reply. Yeah I've readed just in the moment, that it is deprecated. Exsample from Enblend: http://enblend.sourceforge.net/gigapixel.htm Here the machine just have 2GB RAM and it works for a bigger solution. Or is this a different version of enblend? Am Donnerstag, 2. November

Re: [hugin-ptx] Problems with stitching a GigaPano ...

On Thu, Nov 02, 2017 at 12:20:51PM -0700, jojaeger12031...@gmail.com wrote: > Hi Gunter, > I also see, that the RAM could be to less. > But for this thing, it would be perfect, when i could activate image-cache > option. > > Best Regards, > Johannes The image-cache feature was deprecated in 4.1

Re: [hugin-ptx] Problems with stitching a GigaPano ...

Hi Gunter, I also see, that the RAM could be to less. But for this thing, it would be perfect, when i could activate image-cache option. Best Regards, Johannes Am Donnerstag, 2. November 2017 19:56:25 UTC+1 schrieb Gunter Königsmann: > > According to my Maxima On Android your output picture

Re: [hugin-ptx] Problems with stitching a GigaPano ...

According to my Maxima On Android your output picture will already use up nearly 5 Gigabytes before compression. And I don't know if for stitching the image one "before" and one "after" version has to be kept and how much temporary data is needed for this process. Also I don't know if internally