Re: [hugin-ptx] Re: Hugin and wxWidgets 3.1.1
> OK, thanks. So it's likely a wxWidgets' issue. > /J.D. > If it is: Would you be so kind and forward it to https://groups.google.com/forum/#!topic/wx-users/dO5mLAsasKg? Maybe it affects other projects, too. 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/8e5600c9-3b9c-414e-89d8-6c72fa6346ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Improving scan quality
I need *something* to align the images, yes. The scanner isn't replicating the exact position. > That where the missing information. > >> I tried align_image_stack, but it would refuse to work with images of >> slightly different sizes. Which I don't really understand, because it's >> identifying and moving control points, which includes moving some pixels >> beyond the image boundary. So I'm wondering what it's doing - clipping them? >> > Sorry, but control points are not moved. Run align_image_stack with -p > parameter and open pto file in Hugin to see the control points. > What does align_image_stack do, then? > It's not a big deal because the page margins are white space anyway, but >> I'd like to understand what it's actually doing. Is it considering the >> image border to be all control points? >> > A point is a point and not a border > I said a border might be a set of points. Not that a point is a border. > A TIFF file with PNG compression? How should this work? >>> >> >> Ah, the joys of too much editing. >> I tested with PNG and found that 300 dpi with the right settings are >> small enough. TIFF with one of its compression modes may work, too, >> > Sorry, but PNG and 300 dpi resolution have nothing in common. A JPEG and a > TIFF or a BMP can also have 300 dpi resolution. > Sorry, but I was talking about the dpi of the scanner. Plus I wasn't even thinking that dpi is an exclusive domain of PNG, that would be outright silly. It seems you mix a lot up. > It seems you assume a lot about my level of knowledge. If something is unclear to you, please ask, don't just assume. Assumptions tend to be off the mark, and having to deflect such assumptions tends to get into an antagonistic mood. A cooperative mood is much better at clearing up misunderstandings, and much more fun for both sides. -- 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/e026425e-9e42-4c2e-b2f1-5983ad797b52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Improving scan quality
Am Dienstag, 20. Februar 2018 17:57:08 UTC+1 schrieb Toolforger: > > I need *something* to align the images, yes. The scanner isn't replicating > the exact position. > That where the missing information. > I tried align_image_stack, but it would refuse to work with images of > slightly different sizes. Which I don't really understand, because it's > identifying and moving control points, which includes moving some pixels > beyond the image boundary. So I'm wondering what it's doing - clipping them? > Sorry, but control points are not moved. Run align_image_stack with -p parameter and open pto file in Hugin to see the control points. > It's not a big deal because the page margins are white space anyway, but > I'd like to understand what it's actually doing. Is it considering the > image border to be all control points? > A point is a point and not a border. A TIFF file with PNG compression? How should this work? >> > > Ah, the joys of too much editing. > I tested with PNG and found that 300 dpi with the right settings are small > enough. TIFF with one of its compression modes may work, too, > Sorry, but PNG and 300 dpi resolution have nothing in common. A JPEG and a TIFF or a BMP can also have 300 dpi resolution. It seems you mix a lot up. -- 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/6dbff28f-1943-48ac-b4d0-38d0fe86a664%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Improving scan quality
> Am Montag, 19. Februar 2018 21:38:26 UTC+1 schrieb Toolforger: >> >> Correct, I scan each page multiple times. >> > But do you it without moving the page? - then the pages should be aligned. > Or do you move the page between consecutive scans? Then you probably need > align_image_stack. > I need *something* to align the images, yes. The scanner isn't replicating the exact position. I tried align_image_stack, but it would refuse to work with images of slightly different sizes. Which I don't really understand, because it's identifying and moving control points, which includes moving some pixels beyond the image boundary. So I'm wondering what it's doing - clipping them? It's not a big deal because the page margins are white space anyway, but I'd like to understand what it's actually doing. Is it considering the image border to be all control points? The idea is to align the scans, combine them in a way that makes use of the >> added redundancy to reduce noise and speckles. >> > When the images are aligned, you can use hugin_stacker to get the average > image. > Good pointer, thanks. > The background is that I'm scanning my books, for going paperless. Well, > paper-frugal, some books will stay :-) > The scanning will be destructive. I want/need to shed the weight and > volume of all that paper. > Now you wander from the subject. Keep on the track. > Gimme a break! First you complain it's too vague, now I'm providing background and I'm too off-topic for your taste... > I cannot go crazy with storage, the NAS size is somewhat limited. 300 dpi >> TIFF, compressed with the right PNG settings, will fit. >> > A TIFF file with PNG compression? How should this work? > Ah, the joys of too much editing. I tested with PNG and found that 300 dpi with the right settings are small enough. TIFF with one of its compression modes may work, too, but I know how to convert TIFF to PNG so it's pretty much a solved problem - but there's that constraint that I probably cannot go above 300 dpi, storage-wise, so this constrains the options a bit. -- 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/4fb30065-c337-42f5-a41d-0fc55612093b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Hugin and wxWidgets 3.1.1
On 2018-02-20 17:31, T. Modes wrote: > > > Am Montag, 19. Februar 2018 22:18:09 UTC+1 schrieb jdx: > > FYI, the latest version of Hugin from the repository, the latest > version > of wxWidgets from the repository (at the time of writing), gcc-6.3 from > MinGW-W64, WinXP – this is how tabs of preferences dialog look like: > > > The dialog looks fine here with version from repository: MSVC 2015+2017, > Windows 10. OK, thanks. So it's likely a wxWidgets' issue. /J.D. -- 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/b833b24f-e22f-737f-8321-3b1f238965e5%40onet.pl. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Improving scan quality
Am Montag, 19. Februar 2018 21:38:26 UTC+1 schrieb Toolforger: > > Correct, I scan each page multiple times. > But do you it without moving the page? - then the pages should be aligned. Or do you move the page between consecutive scans? Then you probably need align_image_stack. > The idea is to align the scans, combine them in a way that makes use of > the added redundancy to reduce noise and speckles. > When the images are aligned, you can use hugin_stacker to get the average image. > > The background is that I'm scanning my books, for going paperless. Well, > paper-frugal, some books will stay :-) > The scanning will be destructive. I want/need to shed the weight and > volume of all that paper. > Now you wander from the subject. Keep on the track. > I cannot go crazy with storage, the NAS size is somewhat limited. 300 dpi > TIFF, compressed with the right PNG settings, will fit. > A TIFF file with PNG compression? How should this work? -- 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/1795b473-f89c-4233-8c9c-f3039903679d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Hugin and wxWidgets 3.1.1
Am Montag, 19. Februar 2018 22:18:09 UTC+1 schrieb jdx: > > FYI, the latest version of Hugin from the repository, the latest version > of wxWidgets from the repository (at the time of writing), gcc-6.3 from > MinGW-W64, WinXP – this is how tabs of preferences dialog look like: > The dialog looks fine here with version from repository: MSVC 2015+2017, Windows 10. -- 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/f646e950-9edf-490f-83f1-699b965edc2c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
