Andrew Dolph, Photographer
 |
Medina | OH | USA | Posted: 1:09 PM on 04.23.07 |
->> I've encountered an issue that I can't seem to resolve, regarding the use of Photo Mechanic v.4.4.3.3 and PhotoShop CS (v.8). Here's a short narrative of what happened last night at the Cav's game:
I dumped all my cards using the ingest method. I opened the PM contact sheet by dragging my selects folder over the PM icon in the dock. I proceeded with editing by tagging, and color-coding the images. I captioned all the images that I wanted to move by using the "info" button to launch the IPTC stationary pad. (Note: I only captioned images, as I used a pre-saved IPTC template that was applied at ingest.) After all that was done, I went through the toning process for a few images, and eventually encountered this error message from PS:
"Could not complete your request because an unexpected end-of-file was encountered." At first glance, this is a rather amusing statement to me, because I read it as the computer saying, "holy crap, I didn't expect that to happen." Considering the importance of moving playoff pictures on deadline, it's a little unnerving at the very least.
Fortunately, I don't check the preference box that wipes the CF card clean after ingest. So, I inserted the cards again, and proceeded with the old standard drag and drop method, which didn't reproduce the error. So, that eliminated one variable — that of PS being the root source of the error. Unfortunately, a few of the affected files were dumped at the half, and you know the rest of the story.
A few issues I've read about regarding PM are a concern, but fall short of being the smoking gun for me. The following have come up in various internet searches:
1) Installing PM over an existing version can be problematic.
2) Opening files by dragging a folder over a doc icon can cause certain types of errors.
3) Using the "right click" method of opening files in PS through PM has been known to produce errors.
4) There are known bugs regarding applying IPTC stationary pad to files after using the ingest procedure.
So, if anyone can definitively articulate a cause of the error, I would really appreciate it.
Thanks!
— Andrew
(I'm running the aforementioned programs on a 17" 2.16 Intel Duo Core, with OSX 10.4.9, if that helps.) |
|
