I am not a regular, but came by your website from a your
post about color-correction (which I like), and man did I
enjoy your Reminiscences!
Regulars may remember some posts of mine from a year or
two back concerning scanning ancient family documents.
Can anyone see what the hell is going on here?
Java Jive wrote:
Can anyone see what the hell is going on here?
I've only used Hugin/Panotools/PTgui with full colour images, have you
tried converting e.g. to greyscale TIFF?
So I used IrfanView Thumbnail viewer to convert them all first to 16.7m colour bitmaps, *.bmp, then the bitmaps back to greyscale *.png, and
this seems to have sorted the problem. The new *.png all have loaded
into Hugin.
In article <to9spn$2prqe$1@dont-email.me>,
Java Jive <java@evij.com.invalid> wrote:
Can anyone see what the hell is going on here?
$ mogrify -type Grayscale myimage.png
Can anyone see what the hell is going on here?
But this is the unusable result:
www.macfh.co.uk/Temp/Hugin.png
Rrrrrrrr!
A couple of days ago, on a previous tree now completed, I was getting a message that one scan was colour when all the others were greyscale, but
all other imaging software that I loaded it into showed it to be
greyscale. The only thing that was different about this section was
that I noticed I'd begun to move the document fractionally too soon
before the scan had completed, and that consequently a thin slice of the trailing edge of it was corrupted, but, as it was mostly empty, to save myself having to set up everything all over again just to rescan that section, I'd copied the bit that wasn't empty from the overlapping edge
of another successful scan. For some reason, Hugin alone stubbornly maintained that the result was a colour scan, and in the end I did have
to go through the chore of rescanning the single section so that I could stitch it.
Now, I'm trying to do a large tree of 4x15 scanned sections - which I
think must be drawn on something like wallpaper backing paper - and, despite all the scans being done identically as greyscale, Hugin
maintains that the first two sections are greyscale and all the rest are colour ...
Greyscale section acknowledged by Hugin as greyscale:
www.macfh.co.uk/Temp/01B.png
Greyscale section claimed by Hugin to be colour:
www.macfh.co.uk/Temp/01C.png
Can anyone see what the hell is going on here? What is different about
the first two scans, and why does it think all the others are colour
when no other software that I've tried agrees with it?
On 25/12/2022 18:12, Mike wrote:that's tedious, so before reading your post I searched on the web for a batch command, and so discovered ...
In article <to9spn$2prqe$1@dont-email.me>,
Java Jive <java@evij.com.invalid> wrote:
Can anyone see what the hell is going on here?
$ mogrify -type Grayscale myimage.png
Yes, thank you.
I found that both Windows apps, IrfanView and PaintShop Pro 8, treat both genuine grayscale and 8-bit palette with greyscale colours as 'greyscale', so there's nothing to be done there. Linux GIMP can convert each file manually under Image, Mode, but
mogrify -colorspace Gray *.png
... which has solved the problem, and I'm now in business, though have yet to see whether I'm going to have to set the control points manually or automatically.
For some reason or other, probably too many areas looking the same, the latter tends not to work well with this type of input, and I've been getting botched results with it. The manual method, though tedious, tends to work quite well though.
Every now and then, I have a piece of luck and the Windows Image Composite Editor (ICE) program gets it right first time, which happened with the last tree, but sadly not with this one.
Regulars may remember some posts of mine from a year or two back
concerning scanning ancient family documents. A cousin of mine has done
a great deal of work in genealogy, creating some pretty large family
trees which I've scanned in sections. By hook or by crook, I've managed
to stitch together all the smaller ones, mostly 3x3, 3x4, or 3x5 scans,
but even on some of those I've seen some weird behaviour when trying to
use Hugin to stitch the sections together. Particularly that some
scans, although originally scanned identically to the others, are
assessed by Hugin to be somehow different from the others.
On 25/12/2022 14:05, Java Jive wrote:
Regulars may remember some posts of mine from a year or two back
concerning scanning ancient family documents. A cousin of mine has
done a great deal of work in genealogy, creating some pretty large
family trees which I've scanned in sections. By hook or by crook,
I've managed to stitch together all the smaller ones, mostly 3x3, 3x4,
or 3x5 scans, but even on some of those I've seen some weird behaviour
when trying to use Hugin to stitch the sections together.
Particularly that some scans, although originally scanned identically
to the others, are assessed by Hugin to be somehow different from the
others.
On a tangent, are you using the right tool for the job? Stitching images
of bits of family tree sounds a lot of effort that might be better
directed towards using a genealogy database program -- 'gramps' comes to mind.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 70:28:52 |
Calls: | 6,656 |
Calls today: | 2 |
Files: | 12,200 |
Messages: | 5,332,151 |
Posted today: | 1 |