Neo files not loading back to Photoshop

Answered

Comments

25 comments

  • Avatar
    Michael Knöbl

    I have the same problem, using NEO as a plugin. The NEO plugin mostly (not always...) crashes Photoshop (latest update done) after playing back the edited photo to Photoshop.
    I'm already in contact with the Skylum support.
    The only workaround for me at the moment is to export the photo from Photoshop, then do the editing with the Standalone version of Luminar NEO, export from NEO as TIFF and reimport to Photoshop and do the final editing.
    Curiously this problem started with the latest update of Luminar NEO, the previous version worked fine and fluently without causing any problems.
    WIn 10 Pro, 32GB, NVidia GeForce RTX 2080 Ti, Studio driver V512.15, 16GB 

    0
    Comment actions Permalink
  • Avatar
    Agatha Winter

    Hi guys,

    Sorry to hear that the latest update doesn't work as expected for you!

    Could you please try the following solution:

    1. Make sure Photoshop/Lightroom is not runningIf the app was running, reboot your PC before proceeding. 
    2. Right-click the Luminar Neo icon > Run As Administrator.
    3. Click Luminar Neo> File > Install Plugins.
    4. Click Uninstall next to Photoshop.
    5. Reboot your PC.
    6. Right-click the Luminar Neo icon > Run As Administrator.
    7. Click Luminar Neo > File > Install Plugins.
    8. Click Install next to Photoshop.

    In case there's a message You have to install this software first, click Browse, and navigate to where the .exe file of your host application is. After you show Luminar where the host app is, you will be able to install the plugin for the host.

    Let me know how it goes.

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Dear Agatha, 
    did as mentioned above...
    no, didn't work. The first photo was sent back to Photoshop after editing with NEO (but took a very long time, about 5-10x longer than with the previous version), the second photo edited with NEO wasn't sent back to Photoshop and caused Photoshop to a complete hang (CTRL-ALT-DEL to close Photoshop).

    0
    Comment actions Permalink
  • Avatar
    Agatha Winter

    Hi Michael - I'm sorry to hear that!

    Could you please specify if you're able to export from Luminar Neo when using it in a standalone mode? 

    0
    Comment actions Permalink
  • Avatar
    Hal Masover

    I also tried as you suggested with the same result as Michael, only worse, but perhaps there are some clues in my experience.  First, I noticed that this problem seems to occur when I use the erase tool function to remove sensor spots.  I noticed that I did not have the problem using skin smoothing etc.  I followed your instructions to uninstall and install and now the remove sensor spots tool no longer works!  And despite that, PS freezes when I hit Apply in Neo.  I also tried the same operation with Lightroom Classic.  Again the sensor spot removal took did not work, but after hitting Apply in Neo, the photo loaded back into Lightroom Classic with no issues.  Soooo, how do I get the spot removal tool to work again, and how do we fix the issue with loading back into PS?

     

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Hi Agatha, 
    Luminar NEO works fluently as standalone. The problem only exists when used as Photoshop plugin.

    @Hal: I have to check on my side if this has something to do with the spot removing tool. My first thoughts were, that Neo crashes the plugin within Photoshop, when more than one edits are done within Neo... .

    0
    Comment actions Permalink
  • Avatar
    Elena O'Brien

    Hi guys,

    I am so sorry the issue still persists! Please reach out to us at http://skylum.com/support and we'll get that sorted out for you ASAP.

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Dear all, 
    I'm already in contact with Skylum support... but I think that I found the solution, because on my side, the NEO plugin is suddenly working: 
    After importing the photo to Photoshop immediately save the photo as PSD (f.i. if you edit first with Camera Raw), do this after each step/editing within Photoshop. Then the NEO plugin works as fluently as the previous version did.
    I didn't check if this is a coincidence, so take my hint only as suggestion, but I was able to work on 10 photos in a row without Photoshop crashing... .

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Hi!
    After the NEO plugin for photoshop crashed Photoshop today again, I have now found the proof why it makes Photoshop crash: as Hal already suggested, it's the "Dust removal tool". I didn't use it with the photos I mentioned in my previous posting.
    Today I had to use it, and it causes Photoshop crash only if this tool is used and no other corrections are done.
    I mention it again: Luminar Neo works great as standalone program, but it crashes Photoshop when used as plugin using the dust removal tool. 

    0
    Comment actions Permalink
  • Avatar
    Ivan Azure

    Hi Michael,

    Thank you for sharing the reflections.

    We recommend continuing the conversation via support@skylum.com 

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Hi Ivan, 
    it's already at the support, but no solution found yet... 

    0
    Comment actions Permalink
  • Avatar
    Roman Johnston

    I am experiencing the same thing using the Dust Removal tool. Once done it tries to load back into photoshop and stalls at 50% I can use the new noise plugin without an issue, and all the other features as well. It is specifically the dust removal. 

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Hi Roman, 
    the only "solution" to solve this problem is to export the photo from photoshop and import it in within the standalone version of NEO, after editing export the file from NEO and re-import it to Photoshop when you have additional work to do.
    This works fine for me on my side...

    0
    Comment actions Permalink
  • Avatar
    Roman Johnston

    That is a poor work around. I keep my files in a photoshop format. Do not like .tiff. Straight up pain in the butt. It is one of the reasons I actually got the software is for spot removal. I try to keep up with sensor cleaning but not always possible. 

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    I know what you mean :-(

    0
    Comment actions Permalink
  • Avatar
    Anastasiia Moore

    Hi all!

    I understand your frustration, and I'm really sorry you encounter this issue.

    Our developers are aware of this issue and are doing their best to fix it in the upcoming updates.

    Thanks so much for bearing with us while we fix this.

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    And now the same freezing happens with the new noise reducing tool. Used Neo as plugin -> using the new noise reducing tool and sending back to Photoshop causes Photoshop to freeze.
    Works fine within the standalone Neo program!

    0
    Comment actions Permalink
  • Avatar
    Kate Williams

    Hi Michael,

    That's also a known issue that's under investigation right now. Our specialists are currently looking for the solution, and we'll ship it as soon as it's available. 

    0
    Comment actions Permalink
  • Avatar
    Mitch Park

    Hi All, brand new user here. I'm experiencing the same problem as all the above. I'm able to import and export from the app itself, but the plugin version freezes about halfway through processing in Photoshop. I erased some weeds in some asphalt and got the same issue. I will experiment with another file and try not to erase anything. Thanks.

    Kind of a bummer since I just bought this license tonight :(

    0
    Comment actions Permalink
  • Avatar
    Tania Taylor

    Hi Mitch Park!

    We're sorry to hear that your Luminar experience started with this step. Our specialists are still working on the fix, I'm afraid. In the meantime, we'd recommend that you work with the Erase tool options in the standalone Luminar Neo and then continue your work in Photoshop. If you have any follow-up questions, we'll be happy to answer them at https://skylum.com/support

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Just updated to PS 2023 (V24.0) - the error persists.
    There aren't any problems with the plugins of Topaz Labs, DXO NIK Collection, Skylum Aurora HDR (Great Program btw.), ON1 effects.. just with Luminar... this is curious...

    0
    Comment actions Permalink
  • Avatar
    Margaret Bright

    Hi Michael,

    Please get in touch with our support team at https://skylum.com/support. They will be happy to help!

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    I already did this 7 (!) months ago... the only solution is  - until this date - NOT to use NEO as Plugin within Photoshop.

    0
    Comment actions Permalink
  • Avatar
    Michael Knöbl

    Dear all, 
    it seems, as if the problem has been solved with the latest version of Luminar NEO 1.5.0.
    The edited photo is loading back to PS without any problems on my side.
    Edited sky, removed wires... all working fine... all sending back to PS without causing PS to stall/crash... .
    Still be obeyed...
    Thanks to Skylum if the problem is really solved! 

    0
    Comment actions Permalink
  • Avatar
    Roman Johnston

    Working for me too! Very happy!  Thanks Skylum team!!

     

    0
    Comment actions Permalink

Please sign in to leave a comment.