QuickProof not working
When I use quickproof 2 or 3 maybe more files get processed pixelated. Anyone have a solution?
I'm running 5.0.2 and 5.2.1 on osx 10.5.8 mostly.
I'm running 5.0.2 and 5.2.1 on osx 10.5.8 mostly.
0
-
Those images that looks pixelated, are they heavily cropped? Because QuickProof does not upscale them to a fixed size. Hence, a cropped image has fewer pixels, which might give a pixelated look. (basically the same answer you gave on the web contact sheet question today) 0 -
I've had this problem a few times as well. I don't think it is a crop issue, I think it is a bug somehow.
Not only are they pixelated, the colors are way off, kind of a posterized look.
I got so annoyed I stopped using quick proof, when I have the time.
One good thing is that the corrupt files are significantly smaller than the normal ones, so sorting by size helped me find them easier, re-process, then deliver.0 -
I used to get this constantly in 5.0.2, not so much in the 5.2 builds.
You sure it's happening in 5.2.1?0 -
Good point, I still frequently use 5.02 for its faster tethering with Canon. Perhaps they've resolved it later releases. 0 -
[quote="Daniel1111" wrote:
I've had this problem a few times as well. I don't think it is a crop issue, I think it is a bug somehow.
Not only are they pixelated, the colors are way off, kind of a posterized look.
I got so annoyed I stopped using quick proof, when I have the time.
One good thing is that the corrupt files are significantly smaller than the normal ones, so sorting by size helped me find them easier, re-process, then deliver.
The fact that the 'corrupt files' are significantly smaller than the normal one, feeds my crop assumption. If you have your Image Preview Size (preferences) at 1000 px for example, your QuickProof output is 1000 px maximum because it uses the preview image for the JPEG QuickProof. A cropped image will have fewer pixels. Hence, it is smaller, and look bad.
When you open the images (good and bad) in Preview or an editor, look for the amount of pixels along the long side and compare.
It sure pays to try to use the latest release when you have a problem.0 -
[quote="Paul_E" wrote:
It sure pays to try to use the latest release when you have a problem.
Without a doubt... and if something like this is brought to our attention on an old version this is the first thing we will suggest.
That said however, it would be beneficial to create a support case and provide us details. We have seen a few reports of this happening but know very little and are unable to reproduce it, and believe me we have tried. Unfortunately those that have reported the issue to us quickly lose patience with our interrogations and suggested tests so we are left without much progress here. So if you can easily recreate the issue we would love to learn how, if not be prepared for a battery of questions.0 -
Thanks Drew. I'll create a case now (though I dont have access to the machine that made the jps). Here are links to the jpgs
www.rapdigital.net/files/C1/581101403_011web.jpg
www.rapdigital.net/files/C1/581101403_011.jpg0 -
Assuming that reprocessing those images yields proper QuickProofs, this is the same as we have seen in a handful of other cases. However, again, the details are few and far between. 0 -
I am pretty confident I have found the smoking gun.
When I receive a corrupt QuickProof, every. single. time.
It has been while this is occurring:
12/10/10 2:54:48 PM Capture One[62038] [SAVE] Patching existing database
12/10/10 2:54:48 PM Capture One[62038] [SAVE] Init took 2 ms
12/10/10 2:54:48 PM Capture One[62038] [SAVE] Updates took 19 ms (-willSaves took 17 ms)
12/10/10 2:54:48 PM Capture One[62038] [SAVE] Commit took 0 ms
12/10/10 2:54:48 PM Capture One[62038] [SAVE] Total save time 47 ms
12/10/10 2:54:48 PM Capture One[62038] Autosave took 53 ms (min=7 ms, max=5.93 s)0 -
[quote="Matt32" wrote:
I am pretty confident I have found the smoking gun.
That smoke still around in Capture One 6?0 -
[quote="Drew " wrote:
[quote="Matt32" wrote:
I am pretty confident I have found the smoking gun.
That smoke still around in Capture One 6?
No, thank god! 😉0
Post ist für Kommentare geschlossen.
Kommentare
11 Kommentare