Skip to main content

Issue C1 20.0.2 and Open With plugin

Comments

81 comments

  • NNN634411414117438868
    I have the same problem.
    0
  • pgrat
    I feel less alone 😉
    0
  • Samoreen
    Hi,

    I do not have this problem (running Windows 10 Pro 1909). A fellow photographer of mine on a french forum is affected, though. She switched back to a previous version and the plugin now works normally. Could one of you please share the offending DLL (C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\OpenWithPlugin.dll) so that I can compare it with mine which is working normally ? Just to see whether yours was corrupted.
    0
  • pgrat
    Hi Patrick,
    I didn't want to install this problematic update on my desktop computer running Win 10 Pro 1909 ...
    I send this to your contact email.

    Thanks
    0
  • Samoreen
    Hi Pascal,

    Thanks for the files.

    The DLL dated 01-17-2020 that you sent me is strictly identical to mine. This doesn't mean that the bug is elsewhere. Just, the problem doesn't appear on my system.

    The DLL dated 11-27-2019 from the previous C1 version is not identical to the one above. There are slight differences. However, they do have the same internal assembly version number and product version number which is bad programming practice and can only generate confusion for the installers.

    I guess you'll have to wait for a fix. Another example of lack of regression testing.
    0
  • pgrat
    Hi Patrick,

    Thank you very much ! It's indeed curious that the same code works on the Pro version of the OS and does not work properly on its Home version!
    We will therefore wait for the support to respond positively to this issue.
    The regression tests seem to be incomplete ...
    0
  • Adam Tidswell
    I`ve got the same problem .. I don`t need the plug in, just want the irritating display box to go away ...... Windows 8.1 here
    0
  • Samoreen
    pgrat wrote:
    It's indeed curious that the same code works on the Pro version of the OS and does not work properly on its Home version!


    Actually, the plugin appears to also fail on a Windows 10 Pro system. Not on mine, however.
    0
  • Samoreen
    Adam52 wrote:
    I`ve got the same problem .. I don`t need the plug in, just want the irritating display box to go away


    By the way, I don't see any way to disable the plugin. Maybe you could try to move the C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith folder out of C:\Program Files\Phase One\Capture One 20\Plugins ? C1 should no longer try to open it.
    0
  • Paul Steunebrink
    The issue - like many issues - does not seem to affect all users. I have no issues with 20.0.2 on both Win8.1 and Win10 (1909) and the Open With plugin.

    Please do report to support, it needs attention.
    0
  • pgrat
    Paul_Steunebrink wrote:

    Please do report to support, it needs attention.


    The report was sent on Monday (20998) and remains unanswered to this time.
    0
  • pgrat
    Samoreen wrote:

    By the way, I don't see any way to disable the plugin.


    I think this plugin can't be disabled since it contributes to the functionality of C1. And that's what's really annoying ...
    0
  • Samoreen
    pgrat wrote:
    The report was sent on Monday (20998) and remains unanswered to this time.


    Don't hold your breath. Here is what I received this morning :

    Since the launch of Capture One 20 our Support department has been flooded with tickets, and we are still trying to get to the bottom of the pile. We can see that your request is one of the ones that have waited the longest, and we are trying to give those tickets the attention that they need, and will prioritize it, if your issue still needs handling.

    A lot of the issues that users wrote to us about have already been addressed, either by an actual fix or with an article in our Help Center (https://support.captureone.com/hc/en-us), so you might not need our assistance anymore.
    We haven't read each and every support request, but if you still need help with this, please just let us know by replying to this message - we don't need details just a word to indicate that we need to respond.
    If we don't hear from you within a week, we will assume that you found an answer to your request.

    We apologize for the prolonged reply time, and assure you that we are doing our best to learn from this.


    This appears to confirm that regression testing has not be done seriously before releasing version 20. When a maintenance release adds new bugs (like this one) instead of stabilizing the software, this is an obvious sign of a lack of testing. It also seems that the "new" (downgraded) support organization for those users who are only C1 customers and didn't purchase Phase One hardware is too weak.

    Also, I understand that if we do not reactivate within one week the support requests that have not been handled yet, we have no chance to get a fix within a reasonable amount of time.
    0
  • IanS
    Samoreen wrote:
    pgrat wrote:
    The report was sent on Monday (20998) and remains unanswered to this time.


    Don't hold your breath. Here is what I received this morning :

    Since the launch of Capture One 20 our Support department has been flooded with tickets, and we are still trying to get to the bottom of the pile. We can see that your request is one of the ones that have waited the longest, and we are trying to give those tickets the attention that they need, and will prioritize it, if your issue still needs handling.

    A lot of the issues that users wrote to us about have already been addressed, either by an actual fix or with an article in our Help Center (https://support.captureone.com/hc/en-us), so you might not need our assistance anymore.
    We haven't read each and every support request, but if you still need help with this, please just let us know by replying to this message - we don't need details just a word to indicate that we need to respond.
    If we don't hear from you within a week, we will assume that you found an answer to your request.

    We apologize for the prolonged reply time, and assure you that we are doing our best to learn from this.


    This appears to confirm that regression testing has not be done seriously before releasing version 20. When a maintenance release adds new bugs (like this one) instead of stabilizing the software, this is an obvious sign of a lack of testing. It also seems that the "new" (downgraded) support organization for those users who are only C1 customers and didn't purchase Phase One hardware is too weak.

    Also, I understand that if we do not reactivate within one week the support requests that have not been handled yet, we have no chance to get a fix within a reasonable amount of time.


    Yes, I had one of those emails which also said I was receiving it because mine was one of the oldest requests, I have been waiting for weeks ☹️

    Capture One A/S is now a separate business unit which is why they have a new support team.

    Capture One management must be aware that they have serious issues with support and hopefully they will address them urgently. Operating as a new business unit should focus management minds on such issues but we will just have to wait and see if reality matches aspiration. 😊
    0
  • pgrat
    IanS wrote:

    Capture One management must be aware that they have serious issues with support and hopefully they will address them urgently. Operating as a new business unit should focus management minds on such issues but we will just have to wait and see if reality matches aspiration. 😊


    There is indeed a problem with the quality of the support that requires energetic action from C1.
    During the installation of the new v20, I had the surprise to see that the activation was done on the serial key of the beta. I indicated my surprise to the support which systematically answered outside to the problem, as if it was a bot programmed to answer "pre command" when it was not the case!
    The programmer(s) may not have seen this as an anomaly or even not seen at all, but it's perfectly illogical and a misunderstood problem due to the generalization of licenses for all products, even free ones.
    Operating simultaneously a new functional organization and a new major version of the software is certainly not a good idea.
    0
  • Paul Steunebrink
    pgrat wrote:
    ...
    During the installation of the new v20, I had the surprise to see that the activation was done on the serial key of the beta.

    If you participated in the Capture One 20 beta program, then you are aware that the beta ran with a serial key as well, provided to you. Using this key was part of the beta testing, as activation rules has changed from earlier versions.

    This 'beta key' remained active a week after the release, which gave beta testers some extra time to make the switch to the new version.

    Once the beta key expired, you could activate the program again with a license key you bought, or a 30-day trial key, or stop using Capture One 20.

    I do not see any issue in this, other than that it may be misunderstood by some users. Or as we say, not a bug, just a feature. 😉
    0
  • Samoreen
    Hi,

    I further investigated the case and there's something that those Windows users who have the problem could try :

    - Exit C1.
    - Go to C:\Users\<user>\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn (the actual name may vary).
    - You'll possibly find there several subfolders, each one corresponding to a different release of C1 20. Open the one corresponding to version 20.0.0.2 : 13.0.2.13.
    - Open the file named user.config in Notepad.
    - Look for the PluginsDictionary section. The entry corresponding to the OpenWith plugin has a tag named <IsEnabled>. It should be set to true. If it is set to false, set it to true, save user.config and relaunch C1.

    I'm not sure that this will directly solve the problem but this will force C1 to re-evaluate its environment and possibly enable the plugin.

    NB : This is not a way to disable the plugin (if it is working correctly on your system). If the IsEnabled tag is set to true, setting it to false will force C1 to do some checking operations but the value will eventually be reset to true and the plugin will be enabled anyway.
    0
  • Samoreen
    Whatever happens with that OpenWith plugin, I insist : handling external editors this way is just absolutely ridiculous. The request for a "normal" external programs manager has been made since a long time. C1 is the only program I'm aware of that is handling this feature in such a convoluted way. This doesn't make sense.

    Hello C1 team : just look at how Lightroom is handling this. That's the way to go.
    0
  • IanS
    Samoreen wrote:
    Whatever happens with that OpenWith plugin, I insist : handling external editors this way is just absolutely ridiculous. The request for a "normal" external programs manager has been made since a long time. C1 is the only program I'm aware of that is handling this feature in such a convoluted way. This doesn't make sense.

    Hello C1 team : just look at how Lightroom is handling this. That's the way to go.


    I agree wholeheartedly. I can't see anyone defending the current situation as it makes no sense.

    The Mac OS handles this but Windows doesn't. Windows version needs to be fully supported. Given that Capture One is now a separate business unit the management team will recognise that the current "tough you should use a Mac" thinking is now inappropriate, particularly over such a trivial programming matter.

    No need to look to LR, the free Faststone has a simple external editing function.

    Senior management need to get a grip on this quickly. It is simply not a professional way to operate particularly given Capture One's rank in the software price hierarchy. Users expect better treatment.
    0
  • Samoreen
    IanS wrote:
    No need to look to LR, the free Faststone has a simple external editing function.


    There's a major difference, though. When handling an image to an external program, C1, Lightroom, DxO Photolab and others need to pre-process the RAW file in order to send a TIFF or JPEG file to the external editor. If the external program is expecting a RAW file, Lightroom has another way to send the file to the external editor. This can be done via a script (I already provided scripts for doing this in Lightroom) or with a specific plugin (like the DxO plugins managing the roundtrip between Lightroom and DxO Photolab).

    FastStone Image Viewer just sends the file "as is". It's just a viewer. If the file is a RAW file, it just displays the embedded JPEG or optionally converts the RAW file to TIFF or JPEG by using a rather simplistic process. There is no way to specify how the RAW file should be converted to a TIFF or JPEG file before sending it to the external program. Or you have to convert the RAW file in FIV before calling the external editor.
    0
  • Epipactis
    pgrat wrote:
    Hi,
    installed last evening, version 20.0.2 brings a issue with the Open With plugin which cannot initialize and is declared disabled. This issue prohibits the use of the "Open with" and "Edit with" functions.
    A reinstall did not change anything.
    I send a request to the support currently without response (it was not the usual).
    Win 10 Home 1909.

    Hi
    I have the same problem (Win Pro 1909). Did you get a response from the support ?
    0
  • pgrat
    Epipactis wrote:

    Hi
    I have the same problem (Win Pro 1909). Did you get a response from the support ?


    Hi, no response at this time ... 🤭

    I watched the Samoreen test this morning and there was unfortunately no change.
    0
  • charles kasler
    I have the same issue, I reported it & tech support just referred me to this thread.
    0
  • Samoreen
    Hi,

    Did those who are having this problem try to launch C1 as an administrator ?
    0
  • Samoreen
    Also, I have noticed strange things in the C1 / OpenWith log files. But I'm not having the problem. Could someone hit by this bug please zip all the log files stored in C:\Users\<user>\AppData\Local\CaptureOne\Logs, including C:\Users\<user>\AppData\Local\CaptureOne\Logs\Plugins\com.phaseone.openwith.log ? I will have a look.
    0
  • pgrat
    Samoreen wrote:
    Hi,

    Did those who are having this problem try to launch C1 as an administrator ?


    Hi,
    same result.
    I have attached the plugin log file to my request
    [2020-01-28 09:07:12.918][000][ID:001, ]{APPL } | Application started, version PluginHost 1.0 - Located at: C:\Program Files\Phase One\Capture One 20.0.2\P1.C1.PluginHostProcess.exe
    [2020-01-28 09:07:12.918][000][ID:001, ]{APPL } | Running on Microsoft Windows NT 6.2.9200.0
    [2020-01-28 09:07:12.947][028][ID:001, ]{PLUG } | InitializationStarting
    [2020-01-28 09:07:12.983][035][ID:001, ]{LOG } | Log file initialized.
    [2020-01-28 09:07:12.983][000][ID:001, ]{PLUG } | Parameters: C:\Program Files\Phase One\Capture One 20.0.2\Plugins\OpenWith BuiltInOpenWithPlugin com.phaseone.openwith
    [2020-01-28 09:07:13.001][017][ID:001, ]{PLUG } | Discovering...
    [2020-01-28 09:07:13.006][004][ID:001, ]{PLUG } | Discovering from path: C:\Program Files\Phase One\Capture One 20.0.2\Plugins\OpenWith with entry point: BuiltInOpenWithPlugin
    [2020-01-28 09:07:13.008][001][ID:001, ]{PLUG } | Dlls discovered: C:\Program Files\Phase One\Capture One 20.0.2\Plugins\OpenWith\OpenWithPlugin.dll C:\Program Files\Phase One\Capture One 20.0.2\Plugins\OpenWith\P1.C1.Localization.dll
    [2020-01-28 09:07:13.059][051][ID:001, ]{PLUG } | Discovery OK
    [2020-01-28 09:07:13.060][000][ID:001, ]{PLUG } | Creating a new instance...
    [2020-01-28 09:07:13.626][566][ID:001, ]{PLUG } | Exception of Type : System.Reflection.TargetInvocationException
    **| Message : Une exception a été levée par la cible d'un appel.
    [2020-01-28 09:07:13.626][000][ID:001, ]{PLUG } | Exception of Type : System.InvalidCastException
    **| Message : Impossible d'effectuer un cast d'un objet de type 'System.String[]' en type 'System.String'.
    [2020-01-28 09:07:13.626][000][ID:001, ]{PLUG } | Plugin exiting

    ********************************************************************************
    0
  • Samoreen
    Thanks Pascal,

    The error reported in your log is also reported in the log of other users having the same problem with OpenWith. This is an obvious programming error (bug). The log indicates an attempt to convert a string array type object into a mere string, which automatically raises an exception that is not catched by the code, obviously.

    In my log, although the plugin is working for me, I can also see very strange things like this :

    [2020-01-30 10:15:06.054][985][ID:014, ]{PLUG } | path - System.IO.FileNotFoundException: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\firefox.exe
    **| at System.Drawing.Icon.ExtractAssociatedIcon(String filePath, Int32 index)
    **| at BuiltInOpenWithPlugin.BuiltInOpenWithPlugin.GetAssociatedIconFromPath(String argPath)


    This indicates that the plugin is trying to find firefox.exe in the folder where the OpenWith plugin is installed ? ? ? Which doesn't make sense. But the exception is catched by the code since the plugin continues to work. I also have the same error with architect.exe (PDF Architect, my PDF Editor). Absolute nonsense.

    As already stated above : please C1 team, drop this terrible piece of code and implement a built-in external program manager like in Lightroom.
    0
  • pgrat
    Samoreen wrote:

    This indicates that the plugin is trying to find firefox.exe in the folder where the OpenWith plugin is installed ? ? ? Which doesn't make sense. But the exception is catched by the code since the plugin continues to work. I also have the same error with architect.exe (PDF Architect, my PDF Editor). Absolute nonsense.


    I also had that with the V12 ...

    [2019-04-22 11:20:14.019][000][ID:001, ]{PLUG } | InitializationOk: P1.C1.Plugins.Common.Wcf.IPluginHostOpenWith, P1.C1.Plugins.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=45b76d0ca35b690a| P1.C1.Plugins.Common.Wcf.IPluginHostSettings, P1.C1.Plugins.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=45b76d0ca35b690a
    [2019-04-22 11:20:51.875][855][ID:007, ]{PLUG } | GetSettingsAsync
    [2019-04-22 11:20:52.899][024][ID:010, ]{PLUG } | path - System.IO.FileNotFoundException: C:\Program Files\Phase One\Capture One 12 Sony\Plugins\OpenWith\firefox.exe
    **| à System.Drawing.Icon.ExtractAssociatedIcon(String filePath, Int32 index)
    **| à BuiltInOpenWithPlugin.BuiltInOpenWithPlugin.GetAssociatedIconFromPath(String argPath)
    [2019-04-22 11:20:52.901][001][ID:010, ]{PLUG } | path - System.IO.FileNotFoundException: C:\Program Files\Phase One\Capture One 12 Sony\Plugins\OpenWith\Iridient X-Transformer.exe
    **| à System.Drawing.Icon.ExtractAssociatedIcon(String filePath, Int32 index)
    **| à BuiltInOpenWithPlugin.BuiltInOpenWithPlugin.GetAssociatedIconFromPath(String argPath)
    0
  • IanS
    Samoreen wrote:
    IanS wrote:
    No need to look to LR, the free Faststone has a simple external editing function.


    There's a major difference, though. When handling an image to an external program, C1, Lightroom, DxO Photolab and others need to pre-process the RAW file in order to send a TIFF or JPEG file to the external editor. If the external program is expecting a RAW file, Lightroom has another way to send the file to the external editor. This can be done via a script (I already provided scripts for doing this in Lightroom) or with a specific plugin (like the DxO plugins managing the roundtrip between Lightroom and DxO Photolab).

    FastStone Image Viewer just sends the file "as is". It's just a viewer. If the file is a RAW file, it just displays the embedded JPEG or optionally converts the RAW file to TIFF or JPEG by using a rather simplistic process. There is no way to specify how the RAW file should be converted to a TIFF or JPEG file before sending it to the external program. Or you have to convert the RAW file in FIV before calling the external editor.


    Again, agreed 😊

    However, all we need is a mechanism to load a program into the plugin. All of the rest is taken care of. I am beginning to wonder if there is any competent management at Capture One. In these social media days failure to react to what is obviously not only a significant issue, but a trivial programming fix, doesn't bode well. Splitting a business into separate business units can expose the competence of the management. Allowing such a situation to continue for so long is a public demonstration of lack of leadership.

    The fact that Capture One will not even acknowledge the problem and issue a statement is again a failure of management in any company in 2020. Capture One get your act together and please recognise the concerns of your customers. They pay your wages?

    Ian
    0
  • Samoreen
    Samoreen wrote:
    - Look for the PluginsDictionary section. The entry corresponding to the OpenWith plugin has a tag named <IsEnabled>. It should be set to true. If it is set to false, set it to true, save user.config and relaunch C1.

    I'm not sure that this will directly solve the problem but this will force C1 to re-evaluate its environment and possibly enable the plugin.


    This doesn't work. Sorry. This change doesn't enable the plugin and the IsEnabled tag is immediately reset to false.
    0

Please sign in to leave a comment.