メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Capture One and Nik Collection 4

コメント

47件のコメント

  • Permanently deleted user

    Opened new ticket with DxO with a number of log files attached.  When SEP or Viveza are called from C1, an error is generated saying they should be standalone.  Quite a few errors and warnings logged even when SEP/Viveza are called from Photolab4.  None fatal but you wonder how clean is the code. Also a number of warnings and errors when called as a Photoshop plugin.  Tested HDR Effects from Capture One, works fine, no log file generated.  SEP and Viveza may still be in the software development life cycle, testing phase, and we the paying customers have the opportunity to test.

    0
  • Clive Moody

    I've been trying to get Nik 4 to work with some 'assistance' from their support team, eventually got C1 to recognise everything except SEF & Viveza which didn't even show in Windows Explorer. As a consequence I asked them for a refund on the grounds of "Nik 4 doesn't work effectively with Capture One as SEP & Viveza aren't avaiable at all". They also suggested looking at C1 forums for workarounds, (these are just too technical for me).

    Their reply was as follows "I'm afraid we can't consider a refund on those grounds, since the Nik Collection has never been promoted as being compatible with Capture One. We provide a fully functional demo version so that our customers can make informed decisions about whether to purchase new versions".

    This was not at all helpful and there was no mention of a bug fix or new version, so I have now uninstalled Nik 4 and re-installed Nik 3 and effectively thrown my money away. I'm on the C1 Fuji version running Windows 10.

    0
  • Permanently deleted user

    I can only guess that the latest version addressed the multitude of issues with Photoshop and Nik 4. Searched for 'Nik 4 issues' and a number of posts have documented failure and performance issues when using photoshop to call Nik 4 apps as a plugin.  I sent DxO some log files that include the errors and warnings issued by SEP and Viveza when called from PS. 

    0
  • Permanently deleted user

    Ruediger Prang

    I attached a number of log files from SFX and Viveza to a response to Steve at DxO and here is his response and mentioned that C1 by any other name allows for smooth interaction with SFX and Viveza.  Even Photoshop calls to SFX or Viveza are generating errors and warnings and calls from C1 log a message that SFX is expecting to be a standalone.  Steve sent me a link and activation code for Nik 3 but they are keeping my money for Nik 4. Good business practice.

     

    Hi Gerald,

    Thanks for your reply.

    The information I've been given by our developers is that the Nik Collection 4 does not deliberately restrict use with certain third party software by 'checking for' incompatible programs in the way you suggest. If you have successfully tested 'spoofing' the identity of Capture One so that the Nik Collection perceives it as a supported application, please let me know and I will ask my colleagues if any further explanation can be provided.

     

    Kind regards,

    Steve - DxO Labs Support Team 1

    0
  • Permanently deleted user

    @Ruediger Prang

    Are there any other modification to info.plist that will allow an instance of renamed C1 app to execute?  I changed <key>CFBundleName in Info.plist after backing up infor.plist and when I tried to open C1 and error stated it could not be opened. I responded to DxO that if C1 runs by any other name, SEP and Viveza runs correctly.

    Found it.  Change 'Executable Name' and CFBundleName and C1 opens and SEP works, File Menuitem is presented in SEP.  I sent DxO a response showing changes and results and log files.

    0
  • Permanently deleted user

    @Gerald Moulder

    The App-Code is signed by the Developer and changes to it will cause an error when you restart the Mac and try to open Capture One...   

    So either you change the CFBundleName and sign the changed code or you leave it unchanged and use the workaround with a running DXO PhotoLab...

    0
  • Permanently deleted user

    @Gerald Moulder

     

    Hi Gerald,

    Thanks for your reply.

    The information I've been given by our developers is that the Nik Collection 4 does not deliberately restrict use with certain third party software by 'checking for' incompatible programs in the way you suggest. If you have successfully tested 'spoofing' the identity of Capture One so that the Nik Collection perceives it as a supported application, please let me know and I will ask my colleagues if any further explanation can be provided.

     

    Kind regards,

    Steve - DxO Labs Support Team 1

    What an interesting remark of the DxO Labs Support Team ;-)

    A hexdump of the Silver Efex Pro 3 Resource shows 

    So why is the string "Capture One" checked with launchedApplications?

    0
  • Permanently deleted user

    @Ruediger Prang. Can you check for the string 'On1 Photo', I've experienced the same problem with SEP and Viveza if On1 is open.

     

    0
  • Permanently deleted user

    You'll find "ON1 Photo RAW" also there...

    0
  • David Brewster

    @Ruediger Prang. Have you confronted DxO with this? How can they argue that their software doesn't deliberately restrict C1 (and On1) if it checks for these apps at launch? Why else would they have 'unsupported' software listed in their code?

    0
  • Permanently deleted user

    DxO sent me a link to Nik 3 and an activation code, think I will download a hex editor and install Nik3 to see if SEP checks for On1 and Capture One.  They may have done a poor job of using old code to create the new.

    I will probably send the example and tell them I found it on the internet.  They may claim this violates the EULA.

    I did change the Executable Name and CFBundleName in info.plist and C1 interaction with SEP was seamless, just like the good old days. When I restored info.plist to the original, SEP balked.

     

    0
  • Permanently deleted user

    @Ruediger Prang 

    Do the lines of hex code where Capture One is found contain Standalone?

    I can't say where the hex code came from  but it was pointed out that Silver Effects Pro 2 from Nik 3 contains Capture One, On1 several version etc with reference to Standalone.  

    Thanks!

    0
  • Permanently deleted user

    @Gerald Moulder

    I didn't analyzed or re-assembled the code. I've just looked for the string and found it there.

    No idea whether it is used in standalone mode or if it's a part of old NIK 2 code...   

    0
  • Permanently deleted user

    Has anyone informed DxO support that the string 'Capture One' embedded in their executable?  I received another response that they are not going to consider this matter further.

     

    0
  • Permanently deleted user

    Has anyone informered DxO support that the string 'Capture One' embedded in their executable?

    Not me. I've just uninstalled NIK Collection 4

    0
  • Permanently deleted user

    I just uninstalled Nik 4 as well.  Based in this fiasco with their poorly written/tested code I'll not upgrade any DxO products.  Fortunately, DxO is not my primary photo editing tool.

    0
  • David Brewster

    As has been pointed out in the other discussion on this topic, Nik 4.2 finally seems to have corrected this issue. I was able to install a new trial of Nik with the 4.2 version and also updated C1 to V14.4.1.16, and going back and forth into Silver Efex Pro (V5.0.4) works as it used to without the need for any workarounds.

    0

投稿コメントは受け付けていません。