Capture One opens wrong version of Photoshop
Today for no known reason, C1 20 began to invoke the 32 bit version of PS whenever Edit With or Open With was chosen from the context menu and I cannot make it revert to opening the 64 bit version. Using that same menu to browse to the 64 bit exe file works once until PS is closed and then it's back to 32 bit city.
The config file has the correct location but is being ignored:
<AutoOpenProgramPath>C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe</AutoOpenProgramPath>
Any suggestions?
EDIT: I have gone to a work-around by renaming the 32 bit exe but that's not a fix.
-
Hi,
Did you try to reconfigure the OpenWith plugin so that the 32-bit version is eliminated (unchecked) ? It should then no longer appear in the list.0 -
The plugin doesn't seem to differentiate between versions, only one entry for Photoshop is listed (Adobe Photoshop CS6). If I uncheck that then PS doesn't appear at all.
0 -
Well, not a big surprise given the way this plugin works. Sorry. I have already commented this issue in this very long thread :
0 -
I tried copying a config file from a backup but nothing changed (didn't really expect it to since the config in use already listed the correct, 64 bit version). I wonder if C1 has a Registry entry that affects this?
0 -
Hi,
Here is something that you could try.
1. Close C1 and open the following file in Notepad or any other text editor (an XML editor would be nice) :
C:\Users\<user>\AppData\Local\CaptureOne\Defaults\BuiltInOpenWithPluginSettings.xml2. This file describes the external programs that were unilaterally elected by C1 as eligible for external editing.
3. Each entry has a true/false value corresponding to the checkboxes in the OpenWith configuration window.
4. Either set the value to false for PS 32-bit or remove the whole entry entirely (if it exists). Be sure to delete the whole block to preserve the XML structure (make a backup copy of the file before proceeding) :
<KeyValueSerializableOfStringBoolean>
<Key>c:\program files (x86)\adobe\adobe photoshop xxxx\photoshop.exe</Key>
<Value>true</Value>
</KeyValueSerializableOfStringBoolean>5. Launch C1 and test.
However, be aware that you cannot control when this file will be rebuilt. So, the unwanted entry might reappear. Just try to set it to false in that case.If all this doesn't work, I suspect that C1 is looking for photoshop.exe by using the PATH environment variable of your system. Open a Windows Command Prompt and enter this command :
C:\>echo %PATH%Check whether the path to the 32-bit version of PS appears in the displayed text. In which case, edit your environment variables and eliminate it.
If this doesn't help either, there is probably some other mechanism at work when invoking PS. We'll have a look then.
1 -
Among the many quirks related to the OpenWith plugin, there's also something that you should be aware of. When starting, the plugin looks in the registry for what applications are registered as being able to handle files having one of the following (hard-coded) extensions :
".jpg",".jpeg",".tif",".tiff",".dng",".png",".psd",".psb",".crw",".cr2",".cr3","arw","sr2","srf",".nef",".nrw",".orf",".raf",".raw",".rw2",".srw",".x3f"
I extracted this list from the plugin code, which I have partially disassembled. Programs identified during this process will be added to the list anyway. In my case, the OpenWith plugin list contains programs that are totally irrelevant in the context of image editing, for example Firefox, my Hexadecimal editor, the Nero CD Burner, Word...
So, if you want Photoshop 32-bit to be ignored, you should have a look at the registry (HKEY_CLASSES_ROOT branch) and search for all entries referencing the path of the 32-bit version of photoshop. It could be that for some file extensions listed above, both versions of Photoshop have been added to the OpenWithList registry subkey related to this file type. And in some cases, the 32-bit version might be the default.
0 -
Samoreen, thank you for your good work. The 32 bit version was called out in the XML file so I replaced it with the path to the 64 bit version and it's working well. I have stored a copy in a zip file in the event this issues arises again. I am also archiving your posts on this matter for future reference. Again, thanks.
I owe you a beer.
0 -
You're welcome.
Greetings from Fontainebleau, France.0 -
Salutations from Indiana, USA. :)
0 -
> I have stored a copy in a zip file in the event this issues arises again.
Unfortunately, I think that this will happen sooner or later. I have found a way to (more or less) definitively clean up the OpenWith plugin program list.
1. Navigate to this page : https://www.winhelponline.com/blog/remove-unwanted-entries-open-with-menu-windows/
2. Apply the instructions found in the section named "Remove unwanted items from “Open with” menu for a specific file type" for each extension listed in my message above. Delete all entries relating to programs you don't want to appear in the OpenWith plugin. You can also delete all entries containing only letters, including the MRUList. You might have a few surprises when looking at these registry keys because there are usually a lot of leftovers there. So, it's worth having a look anyway.
You can also clean up the OpenWithProgids keys but these ones are usually cleaner and I'm not sure that the OpenWIth plugin looks in there when building its list.
Once I did this, I got a much cleaner list in the OpenWith plugin.
Of course, this will also affect the global behavior of the Open with context menu in Windows Explorer but that's not a big deal. Unwanted changes can be easily fixed.
Well, this is again a demonstration that the registry approach for managing external editors in C1 is absolutely wrong. This part of the program has to be re-designed.
0 -
I will add this to the info archives but I will just monitor the behavior for now because I'm curious how long it will be before it happens again.
0
投稿コメントは受け付けていません。
コメント
11件のコメント