3/3/2024 0 Comments Free Quick CPU 4.8.0![]() Hugins camera and lens database: /home/casey/.hugindata/camlens.db Operating System: Linux 4.8.0-46-generic x86_64 I tried to read everything applicable and search around - sorry if this is an old question. zip), so I assume that's related? If I do similar panos in hugin with 16bit-integer tiffs (before any GMIC work) it all works fine. GMIC outputs 32bit float images (examples included in. Remapper is nona (with cropping enabled, but i don't think it made a difference turning it off?), blender is default enblend. File format choice for output doesn't seem to matter. I'm doing an "exposure corrected, low dynamic range" pano output. There is no exposure adjustment happening (that I'm aware of). I can see the images fine in the fast preview window - everything looks great. ![]() Is there some file format issue happening? Or have I messed up my. ![]() In any case, these results seem truly white: they open as white in linux gimp, windows gimp, photoshop (CS2), etc., so I don't think it's just a viewing issue? Gimp 2.9.5 in linux has some trouble opening high-precision images, but I can usually work around it. zip file) is output_from_hugin.tif, which opens as all-white for me. That uses just two images and stitches them together the result (in the. ![]() zip is about 591 MB - I can make a smaller one if that would be more useful: Here is an example.pto if anyone has a second to check it - the. I'm trying to make a pano from images that I ran through gmic -median_files, but the resulting pano is always all white. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |