They save the day for giant prints that will be seen close up. And that would include upsizing with the built in CS5 or CS6 upsizing stuff, and even a properly sharpened print without any special blowup processing.īut when you get up to mural sized prints, I think either PZ5 or Resize7 are worthwhile, if only because they remove grungy looking stair-stepping and pixel clumps. As with sharpening, the screen is a poor indicator of what you will perceive on the print.īottom line for me is that there is not much visible difference if you start with 20mp+ images and make normal sized prints, say up to 24" wide. ![]() This is another classic case of not enough examples to make intelligent decisions, but more than enough information to jump to conclusions! Whatever else, as others have pointed out you simply must make test prints to decide what look you prefer. It's tempting to give PZ5 the prize, but on actual large prints I think Resize7 might give the impression of a little more detail being present. Photozoom5 using SSplineMax_original corrected only for contrast_Resize7 The attached file shows what would be part of an image more than 5 feet tall. I am curious about what others have experienced working with these two products, and what anyone could tell me about the settings in PhotoZoom.īy coincidence I spent a lot of today looking PhotoZoom5 and Resize7, among other things. Convinced it was worthwhile, I purchased to software and tried it on other samples with good results. The PhotoZoom version was much smoother with fewer artifacts. I then magnified both images in Photshop CS5 to where the defects in Perfect Resize were apparent and compared the two. When Perfect Resize did not produce what I wanted, no matter what adjustments I made, I downloaded a trial version of PhotoZoom 5 from BenVista and gave that a try. I admit this was a bit of a challenge, but the painting was a good candidate for it with broad areas of solid color, and I was starting with a reasonably clean jpeg. I wanted to increase it to 22 inches in width at 300/360 dpi. It was a painting about 1200 x 1800 pixels, eight inches wide, and 72 dpi. Only lately, I ran into an image that did not upscale with what I considered acceptble results. I put 6.2.0 back (renamed the program file directory for 6.2.2) and it runs okay.I have been a happy user of Genuine Fractals, now called Perfect Resize, for more than four years. Oh and there’s was no uninstaller for 6.2.2 in “uninstall or change a program”, just 6.1.0 which didn’t point to anything? After re-installing 6.2.0 I now have an uninstaller for that. Haven’t had that with any previous version. Eventually went to the task manager and it locked the whole computer for about 2 minutes then came back to me while I was still trying to rememeber which button was the reset one… Tried to close w/o save and it just stayed there. ![]() Tried again, same thing, a third time as a 2x2 comparison and it just stuck at 85%. Made it to about 85% complete and poof, no more GPAI. Didn’t look great so tried Face Recovery. Okay, so I Installed 6.2.2 and updated to the latest Nvidia studio driver (required for Video AI 3.0.1) then tried resizing a fairly small image. TL DR uninstalled 6.2.2 as unusable for me… I have uploaded the DNG to your Dropbox, which you can use as an example. ![]() It appears that when the source and the destination (to which Gigapixel is to save the file) is the same then the software crashes with the same DNG. It is important to note that when I open Gigapixel AI from start menu and then open the same DNG file from drag-and-drop or File/open then Gigapixel saves the file with a suffix, so the destination file is different from the source file. It appears that there is some issue with that. This opens up Gigapixel AI with the file and it tries to save the file back to the same DNG file at the end and crashes. The problem appears when I try to open a DNG file via “Open with” option from Microsoft windows explorer. It appears that the latest version of Gigapixel AI v6.2.2 also has an issue. I believe I now know the real issue here. It appears that there is a bug in Gigapixel AI (reported via support channel as well).
0 Comments
Leave a Reply. |