Problems with 5Pro not previously experienced with 4Pro
Bestseller has recently purchased about 15 upgrades to Capture 5 Pro. So far only two users are testing the product before it goes on release to the other users and a third has given up and gone back to Capture 4. We are experiencing several problems, not least that the program does not show the process wheel on each processed image after the image has been processed. I have had multiple discussions with our own IT support here on the various problems and they just come up blank.
I have the following findings to share with you:
The process wheel vanishes after process on images where the file name has been changed.
All adjustment made to these renamed images are lost when the program is closed and reopened.
Once capture is reopened, I can re-process the same renamed image and the Process Wheel remains in place with all adjustments.
This is an incredibly annoying problem and one aspect of the program that should just work. We have tried looking into user folder access here. If folders were read/writable, but we are clueless why one image will work and another does not just because we changed its file name.
Help!! I have 13 users just waiting to get onboard.
I would really like to discuss this issue over the phone and get our IT people involved. Can you please call me:
Kind Regards
Jonathan
I have the following findings to share with you:
The process wheel vanishes after process on images where the file name has been changed.
All adjustment made to these renamed images are lost when the program is closed and reopened.
Once capture is reopened, I can re-process the same renamed image and the Process Wheel remains in place with all adjustments.
This is an incredibly annoying problem and one aspect of the program that should just work. We have tried looking into user folder access here. If folders were read/writable, but we are clueless why one image will work and another does not just because we changed its file name.
Help!! I have 13 users just waiting to get onboard.
I would really like to discuss this issue over the phone and get our IT people involved. Can you please call me:
Kind Regards
Jonathan
0
-
This is essentially a user-to-user forum, Jonathan - if you want to talk in depth to Phase One about this, you'll really need to raise a support case with them. 0 -
Jonathan,
Please open a support case. From your description it sounds like you are accessing the images off of an external volume and the errors that are occurring suggest some issues with that volume. A support case is the best option to determining the cause of the error.0 -
HI,
Just a note on this, we have experienced the same problem with our captures here. When you changed the file name in the software then process off, this information is not stored as capture pro has not created a new cos file for the new file name you gave it, once you close and reopen the image it drops the adjustments/process icon as you mention, this i think is because the all the adjustments and process info was stored in the original cos file for the image not the new cos file which was generated by the name change, when you relaunch the software. So at the end of the day for example you created 40 files, realised you need to change the name (for whatever reason), and you change them all, close and reopen the programme it will generate another 40 cos files with the new names and no information. If you go to the capture/settings 50 folder you will see you now have 80 cop files for the 40 images (old and new).
Iirc, previous versions of capture pro used to overwrite the original cos file straight away with the new name, without the necessity of having to apply all your adjustments/profiles etc all over again, as you renamed it in the software not externally say using Adobe bridge.0 -
I find that file functions, in my case deletions, are much more reliable if I restart CO after it initially creates the .cos and proxies. If I try to delete before restarting then my .cos files are either not deleted or are instantly recreated while the raw or proxy is being deleted. You might also have a problem if CO is doing some background processing on the file when you try renaming/deleting. I have to let the current image activity indicator stop before trying to delete. 0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare