Skip to main content

⚠️ 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

Comments

47 comments

  • Gerald Moulder

    Okay C1 Users with Nik software, here is another workaround for the two Nik4 apps that were rewritten.

    Open Silver Effects Pro and Viveza as standalone apps then open Capture One.  Now you can select a file and 'Edit With' SE or Viveza in Nik 4 and have the File->Save option available in the toolbar.  Changes made in SE or Viveza will be saved to the TIF file C1 sent for editing.  Leave the Nik4 apps open and cmd-Tab (Mac) back to C1. If you happen to close SE or Viveza and need to call the again you will need to close C1 and reopen Nik first then C1.  

    Also, from the workaround opening Photolab4 then sending TIF files from C1, Silver Effects Pro and Viveza displays 'You're modifying "_DSC1231.tif" from DxO PhotoLab even though C1 made the call.

    4
  • Ruediger Prang

    it's a NIK issue!

    But if you change C1's Application name from 'Capture One 21' to 'Capture_One 21' (<key>CFBundleName in Info.plist within C1 container) Silver Efex Pro 3 and all other NIK Collection 4 apps will not recognize, that C1 is running... Then they provide the standard Open/Save dialog and you are able to save the changes into the tiff... ;-).

    You will see them after returning to C1!

     

    see also this discussion...

    1
  • David Brewster

    Didn't work for me. Couldn't get C1 to start after making that change. Never mind. To be honest the changes in Nik 4 aren't that significant – reckon I'll stick with Nik 3 until they can be bother supporting all their customers. 

    1
  • David Brewster

    The response I got back from DxO was: 'Unfortunately we have never supported the use of our software with Capture One.  If Capture One added compatibility with our software, we would suggest asking them if they are adding it again with this new version.'

    This is plainly rubbish. If I have C1 open, I can't open any file in SFX3 – even if the file wasn't created by C1. And I get this message in SFX3:

    That message must have been created by DxO.

    I don't think I've ever before come across one application that won't operate properly simply because another unconnected application is open.

    Very frustrating. I've gone back to DxO support with this situation. Interesting to see if they say anything other than 'we don't support you'.

     

    1
  • Gerald Moulder

    I opened a ticket with DxO about Silver Effects Pro and Viveza not returning changes to Capture One ( the same is true for On1). Their response is they do not support C1 or On1 and those software companies must add support to their products. I pointed out that Nik 3 and legacy apps in Nik 4 work seamlessly, only the two that were rewritten have failed.  Due to their response, I opened a ticket against SEP standalone and Vivesa standalone with do not present a 'File' menu item if C1 or On1 are open even though C1 or On1 were not used to execute SEP or Viveza.  I found if you have DxO Photolab4 active when using Capture One or On1 to call Silver Effects or Viviesa, the tif file is updated when 'Apply' is clicked and C1 and On1 show the changes.

    1
  • David Brewster

    Gerald - that's fascinating re the effect of having Photolab 4 open. I've just tried it with Photolab 2 (after an update supporting Nik 3) and it worked as you describe: TIFF files sent from C1 open in the new Nik apps as they used to (interestingly with a note at the bottom saying the file was opened from Photolab 2) and edits save back as they should. So that's a great workaround for those of us who have a old copy of Photolab (even if, like me, you very rarely use it).

    There's some odd programming going on in all this.

    For the record, my version of DxO Photolab 2 is the Essential version, not the Elite version.

    1
  • James Grove

    DxO support have got back to me, to say they  are working on a fix, which should be available next week.

    1
  • Gerald Moulder

    Still broken.  used Nik uninstaller to remove Nik4 collection then downloaded and installed new version.  Should have checked version numbers first but I trust DxO.  C1 interaction with Silver Effects Pro and Viveza the same, workarounds required to apply updates.  

    1
  • ---

    guess not, use the standalone apps.

    0
  • David Harrington

    Thanks, I will try this.  Did not realize there was already a thread about t his; I should have looked more closely.

    Dave

    0
  • Shane Baker

    DxO Mark support told me they do not support use with C1.

    An off-topic comment: all the propaganda from DxO on Nik 4 seems to stress its close integration with Adobe software. I know Adobe is the proverbial 800lb gorilla in the market, but given the viable alternatives to Adobe, I would have thought keeping generic and supporting other established software as well was in DxO's interests. 

     

    0
  • ---

    @Shane

    they have to use their resources carefully (considering adobe has 90% of the market ) and probably only a very small fraction of c1 user are using nik filters and do not have PS  but while they have a clear priority they are also interested to learn about the issues with c1.  and as a general observation, you can study how unimportant c1 in reality for third party companies is with their failed plugin initiative. 

     

     

    0
  • David Harrington

    Ruediger's suggested solution works for me. The first time I tried it, Nik crashed but the file was still passed correctly.  No crash on subsequent tries.

    Thanks for the advice.

    Dave

    0
  • James Grove

    Is this a deliberate attempt by Nik to render the plugins inoperable in C1? It seems a little odd that it checks to see if its running first!

    In relation to the work around, does this solve the edit with option inside C1? Or does the workaround only work with the standalone plugins?

    Looks like I am going to ask for a refund from DxO and return back to V3

    0
  • James Grove

    I got it to work, but you need to change the name from inside the container, not the application name inside the applications folder.

    While it does work, I am unsure why DxO have done this? Its either a bug or, more worryingly, its a deliberate move :-(

    0
  • David Harrington

    Changing the name in the container solved the file handling issue between Nik and C1,  but after a reboot C1 would  not start, with the OS giving a message that I did not have permission to open the app.  Undoing the change to the container got C1 running again but the problem with Nik reappeared, as expected.  I will continue to experiment.

    0
  • Peter Smith

    Can someone give me the exact "go to folder" instruction please. I cant find the CFBundleName referred to by Ruediger Prang.

     

     

    0
  • Ruediger Prang

    Can someone give me the exact "go to folder" instruction please.

    @Peter Smith

    you have to select the "Capture One 21" app in the Applications folder and Control-click, which let you examine the package content.

    Here open the Contents folder and find the file Info.plist.

    This can be edited with a text editor or XCode. But pay attention, that 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...   

    0
  • David Brewster

    I know our numbers are small compared with PS users, but if we each add our voice to this issue by raising it with DxO directly they might at least reopen the workaround. https://support.dxo.com/hc/en-us/requests/new

    0
  • James Grove

    David B - Yup, given the work around and the various contradictory messages from DxO I think it's a deliberate move, that they were fully aware off. 

    In fact on Friday they updated the release notes to say you have to open PS with Rosetta to get the plugins to work, something that wasn't in the release notes on the release day.

    Support finally got back to me and suggested I reboot my computer! 

    I have since asked for a refund, 

    0
  • ---

    i have issues with Viveza with all applications other than DXO PL including PS where some files can't be processed. this is foremost a total unacceptable  shi..y release. 

     

    0
  • David Brewster

    Well spotted. That works for me. So we have two options – DxO didn't need to make it this hard but nice to know we can use their software. 

    0
  • Gerald Moulder

    Thanks for the update, lets hope they can get it right.  Maybe they should ask the C1 beta testing community to help out before the next release is put in production.

     

     

    0
  • Ruediger Prang

    I found if you have DxO Photolab4 active when using Capture One or On1 to call Silver Effects or Viviesa, the tif file is updated when 'Apply' is clicked and C1 and On1 show the changes.

    @Gerald: Thank you for this workaround! It works also with DXO PhotoLab2...

    0
  • Villiers Road Studio

    Thank you Gerald for the workaround - I am not convinced SilverEfex is such a good program that it worth this silly workaround though - Capture One itself over the years has become pretty darn good at B&W.   thoughts ?

     

    0
  • Gerald Moulder

    While testing the workarounds, I processed an image in Silver Effect Pro and the used the B&W tool on the original to compare results.  Opening both images in C1, I adjusted the color sliders in the B&W tool until the orignal matched what SEP returned. The changes could be saved as a preset so realistically you do not need SEP.  The benefits of SEP are the presets and thumbnail previews, and the opportunity to look for workarounds when the SEP is released without thorough testing. 

    0
  • ---

    when you only use the most basic features than of course you will not see much difference, this is true for probably every imaging software but this is not what SFX is made for...

    0
  • ---

    just got informed a new version is available, before installing the new version make sure to delete the old versions before. 

    0
  • Francesco Borsotti

    Just downloaded and installed the new version (4.0.8). On my MacBook Pro 2016 with Catalina SFX and Viveza behave exactly as the previous versions... 

    0
  • James Grove

    Yep, extremely annoyed I had asked for refund and cancelled the request on the basis they were providing a hot fix, which has made no difference to the existing problems posted here. 

    0

Please sign in to leave a comment.