Open With Plugin
I have just installed 13.1.1 and my Open With plugin appears not to be working any more.
Obviously the Edit With and Open With menu items are not populated any more.
It's a little bit annoying as I have had only just figured out how to get my apps working through these menus :(
Has anyone got any ideas on how to fix this or am I putting a support request in?
Regards,
Mark
Addendum: From other posts it looks like there is a problem with the Open With Plugin 1.0.1. I have downgraded C1 for the moment, Open With Plugin 1.0.0 has returned and so have my apps.
-
Not saying i can help fix, but certainly went through a lot of troubleshooting to fix my issue so may be able to pass on some experience from that...
Just wondering what is in your BuiltInOpenWithPluginSettings.xml file?
C:\Users\<user>\AppData\Local\CaptureOne\Defaults\BuiltInOpenWithPluginSettings.xml
And what applications are you trying to use via the plugin?0 -
Gerry,
I am sorry, but I don't think I am going to be much help. I should have been clear that the procedure that Howard and I have used does not work with 13.1.1 (or the 1.0.1 openwith plugin). I myself have not been able to get 13.1.1 working with plugins yet, so reverted. The procedure works for me with 13.1.0.
Just trying to understand your post, are you saying that images that you imported while using the updated version 13.1.1 are not visible in the reverted version 13.1.0? If so, this is a surprising development. I must admit I reverted almost immediately, did not import any images ar 13.1.1 and therefore have not seen this behaviour. It sounds like you have put in a support request, but if not I would recommend you do so. The response I got was that it was a bug and is with the software team.
Others seem to have the plugin working, particularly on other versions of Windows than Windows 10, but I have not been able to figure out why as of yet. If a solution is found of course I will update with a post.
0 -
I just tried performing a parellel installation of 13.1.1 (retaining 13.1.0) and found the same behaviour, 13.1.1 has no plugins. However, if I start the older 13.1.0 version I see the plugins as normal. I checked the settings between the two versions I find them the same, both in the user config file and the BuiltInOpenWithPluginSettings.xml file.
I even tried to see if I could get openwith 1.0.0 plugin working with 13.1.1 by copying some files around (not recommended) and no joy, C1 must check the version of th openwith plugin being used, found it was the incorrect version for 13.1.1 and immediately disabled it.
So I uninstalled all and put 13.1.0 back on. I suspect we are all waiting to see if the support team arrive at an answer. Hopefully sooner than later (being overly optimistic I know🙄☺️).
0 -
Hi Mark,
>>I even tried to see if I could get openwith 1.0.0 plugin working with 13.1.1 by copying some files around (not recommended) and no joy, C1 must check the version of th openwith plugin being used, found it was the incorrect version for 13.1.1 and immediately disabled it.
This is the expected behavior. C1 and the C1 plugins are written using the Microsoft .Net Framework. For each application, the framework checks the consistency of all the program components. So, it's impossible to mix components built for different versions unless the developers have allowed this, which is not usual practice.
0 -
I did not expect it to work but in the style of 'clutching at straws' I thought I would give it a try 😁.
0 -
I have spent some hours trying to understand the cause of the problem but I have to admit that the only solution is to get a fix from the C1 developers. They don't seem to be in a hurry, though.
0 -
Likewise, I have expended some effort trying to figure it out and think you are right that we must await the developers.
I am happy to stay with 13.1.0 for the moment, I only looked because my OCD engineering mind needed to see if I could find a solution and hopefully help others with this problem.
If this was a major update it would be a lot more frustrating. I am not sure how this could have been missed in testing. Having been a software tester in my time, I would have expected since the plugin was part of the update that there would have been some focus on the testing of it.
0 -
Just trying to understand your post, are you saying that images that you imported while using the updated version 13.1.1 are not visible in the reverted version 13.1.0?
Mark, in a word, yes to your question. Also welcome to the world of OCD........ What I'm having a difficult time understanding is how a program as powerful and sophisticated as C1 can a. be broken so easily, and b. not have our benefactors scramble to fix it..... For me, the difference between the versions made an enormous difference in usability..I found the change in the cloning and healing layer and the before / after view very useful. Anyway, I guess we will have to wait for the programmers to come up with a fix...
0 -
Gerry, I know it's a little poor. I do like the tools C1 has and the way it processes images, so we can only hope this sort of thing is a bump in the highway.
It's strange that you are not seeing some of your images. I suppose it depends on how much editing you have done, but you could reimport the images, or so a sync or maybe a database integrity check would help as I understand that if there are database errors then the integrity checks are supposed to fix them.
If you have done a lot of editing then from 13.1.1 you could export the edited images as eip, this will bundle the edits with the image and then when you reimport again in 13.1.0 it should import the edits also. I have not tried it but I have seen some YouTube videos on the topic.
0 -
Thanks, Mark.
I will try to re-import something back into 13.1.0 to see if it will work. That said, I've recently found the (finally) consistent way to import and store files within C1, so I've got a lot of images now under that engine. Oh well.....
0 -
Hi Mark,
I was finally able to get the 13.1.0 build to load. ( licensing sign in issue). It does give me access to the previous catalog, so I'm back to work. I did report the bug to tech support, and have had some feed back. They have sent it up the chain, and will advise me when it is fixed.
0 -
Gerry,
Woohoo! Glad you got it working again. Now we wait for the fix to 13.1.1 😜.I had a similar response to my support request on this topic.
M
0 -
COOL. Thanks again for your kind help. Now I've got a bunch to process!
0 -
I have no solutions for this issue other than to say I am also having the same problem with the 'Open With' plugin. I just installed 13.1.1 a few days ago. I installed a new licence rather than upgrading because it was a good deal with last weekends coupons. I had no issues with C1-12.
0 -
Geoff,
Hopefully you have gathered that 13.1.0 seems to work ok with plugin, you should be able to download 13.1.0 from the website. 13.1.1 did not give me much apart from plugin heartache :D At least you can use the new goodies like the heal tool, which I think does a really good job.
0 -
Goeff,
I second the recommendation. I've even been able to access my NIK software using the 13.1.0 version of C1. Hope this is of help.
0 -
It is known by when there will be a solution to the problem
0 -
Not to my knowledge.
1 -
If the release minor version number is even, the OpenWith plugin works. If it is odd, it doesn't. However, for some users, this works reversely. So, it's like being tortured with alternating current : there's at least one moment where you feel positive.
0 -
@Samoreen
> definitively drop this plugin and to incorporate a real external editor manager into C1 directly
Could you suggest more detailled?
> Sorry for getting technical again but I think that there are some Windows 10 mechanisms that the C1 (plugin) developers don't seem to be aware of.
Full ack.
> let the user specify once and for all what applications should be used as external editors, the executable location of each aplication and which export parameters should be used for each of these external editors.
I would prefer too.
> The good ones are able to acknowledge the mistake and fix it.
The point is: The GOOD ones.
@SFA: Hi Grant,> I finally managed to get them working with some help from the C1 support team and have even posted a detailed instruction to others on how to get this stuff working.
Where can I find this detailled instruction?
> If they do (having a bety test program) then they need to make me one of the testers, because I seem to find the problems :D.
Maybe you wouldn't believe but I had a very close discussion with former C1 support two years ago to spring last year about some more serious database "malfunctions" in Windows version only. They needed more than three month to understand that theese problems were (and particulary are today) real issues. One of the reasons was that they testet on Mac only even when I told them that theese issues do not appear on MacOS (one of the phone answers was "I do not have access to a Windows PC.", really) . But they never found the reason. Till today. I have given up - this "support" is not worth my working time.
> No Matter, it's not a big task to undertake a one time registration of the application in Windows and so make it available to the Windows version of the Plugin manager.
Registration works with some application. With some registration alone is not enough. Answer from C1 support" This is a fact that we cannot change. It is only Windows that chooses the apps to use or not." Therefore I would be interested in you knowledge in this matter.
On MY PC it seems that there are other mechanisms affecting this matter as some of apps shown by OpenWithPlugin are changing sometimes (really!) without changing anything on installation of them. As examples apps from TopazLabs appear only a few within the plugin but not every week the same. Very strange. First I thought it would depend on frequency of using but was wrong. I have seen, Howard has a similiar problem with Capture One and Topaz products...
@Mark Witherington: Hi Mark,I had a look at your instructions to get apps into your Open with list. I have tried this way long time ago - but it may work on your PC, it doeasn't on mine. Point 8) does not. ;) I have always to "Choose another App..." when I want to use some applications.
Regards
Ernst
0 -
>> @Samoreen
>> definitively drop this plugin and to incorporate a real external editor manager into C1 directly
> Could you suggest more detailled?
Hi,
I think that the most practical way to handle this is the Lightroom implementation. There's an "External Editors" tab in the Preferences dialog and the user can select any application as an external editor and set the export settings for that specific application. That's quick, easy, simple and... it works. The *user* decides what applications appear in the Edit with menu.
See this video for details : https://www.youtube.com/watch?v=GzHcZRPYUVY
> " This is a fact that we cannot change. It is only Windows that chooses the apps to use or not."
This answer from the support is just ridiculous and demonstrates a vast ignorance about the Windows system and its programming API.
0 -
>> " This is a fact that we cannot change. It is only Windows that chooses the apps to use or not."
> This answer from the support is just ridiculous and demonstrates a vast ignorance about the Windows system and its programming API.
Actually, it is the approach they chose that locks them into a mechanism that lets Windows (allegedly) decide. I have already explained elsewhere how C1 proceeds to build the list of eligible external editors. This mechanism relies entirely on the contents of the Windows registry related to file types associations. This information is by nature unstable and unreliable because any application, any utility and any user can (sometimes wrongly) change it at any time. This also forces C1 to rebuild the list each time it is launched. Which is nonsense. This is a big design mistake. Only a user choice based approach can work correctly.
Please also note that Lightroom allows any external application installer to automatically installs itself as a Lightroom external editor. This is what DxO, Topaz, the Nik plugins etc. are doing.
0 -
@Samoreen
> I think that the most practical way to handle this is the Lightroom implementation.
This way I know well. ;) I missunderstood your statement and rather hoped you could suggest external editors that works with existing C1 as we would expect. I would prefer the Lightroom way in this special matter too. But this will come or not (as I suspect) when or if Phase One developer will get it. But we only can wait (and pay for next update).
Kind regards
Ernst
0 -
> and rather hoped you could suggest external editors that work with existing C1 as we would expect.
Actually, that's C1 that should work with *any* external application taking a file path as an argument on the command line. External Editors don't have to be C1-ware and reversely, C1 should not be external editor-aware. The only condition for an external editing mechanism to work correctly is that the host application has to be able to 1) export an image file according to the user settings and 2) pass the location of this file to the external editor executable as an argument on the command line. That's it. Anything else is superfluous.
Currently, C1 has 2 problems with this. For some users, the OpenWith plugin is just not initializing properly. I had no problem with this in version 13.1 while some buddies could not use it. Now, in version 13.1.1.31, the plugin is working for some of my fellow photographers but it no longer works for me.
Secondly, even when the plugin "works", it assumes that the OS is able to provide enough information allowing it to build a list of potential external editors installed on the user's system. This is plain wrong and even when it allegedly works, the plugin makes many mistakes when building this list. And not only this doesn't work properly but this necessitates a lot of code executed each time C1 is launched. Nonsense.
Only the user knows what applications he wants to use as external editors. But currently, the whole mechanism is working reversely, as it pretends to know this better than the user. This is just a faulty design.
So, there's one thing I'm pretty sure of : this plugin will never work correctly for all users. This is just impossible. This code has to be re-written. I'll bet my shirt on this.
MfG.0 -
Anyone know where i can download 13.1.0 from?
I made the mistake of just upgrading to 13.1.1 and yes, plugins is now completely broken... zero plugins available and unable to get work. I have not got hours to spare to try and debug or tinker to try and get them to work. Would rather just downgrade.
I thought i had kept the 13.1.0 installer, but obviously i must have deleted it - appreciate any pointers on where to download 13.1.0.
TIA
Howard
0 -
Hi Howard,
Welcome to the glitch... Unless you deleted the previous verson from your hard drive after you installed it, you most likely have it . If not, You may want to try here:
https://account.captureone.com/en/account/download,
and click on "previous Version". Good luck!
Gerry
0 -
Try here: https://account.captureone.com/en/download/archive/COArchiveWin
It helped for me.
0 -
Hi,
1. Go to the Phase One site and open your customer account.
2. Click on Support in the top menu.
3. On the support page, in the "Software download and archive" box, click on "Go to software archive".
4. The first available download for your OS is the previous minor or major version whatever the previous version actually was. So, currently, it's version 13.1.0 (the current version being 13.1.1).
0 -
MANY THANKS guys - downloaded successfully.
Installed without any issues and now the Plugins are all working as before - fantastic.Looking forward to this being fixed in the next update - i won't be upgrading until i see this is specifically mentioned as being fixed in the release notes of the next update.
Again, many thanks for the pointers.
0 -
I've used Affinity Photo to do some extra editing on a few photos this week and it was quite painful not having the "open with" plugin not working.
So tonight, I gave up and like others above in this thread, I have rolled back to 13.1.0. It's now working, but needs fixing to move forward
0
Please sign in to leave a comment.
Comments
77 comments