Aurora HDR 2019 crashes when trying to load a .auh file

Comments

17 comments

  • Avatar
    Paul Christensen

    Tom, thanks for doing the legwork on this problem and providing a solution.  I am having the same issue and your workaround works for me.  I also prefer to crop first.  

    Why do we have to debug this software for this company?  

    0
    Comment actions Permalink
  • Avatar
    Denis Kotsee

    Tom, Paul, I'm sorry to hear that you've encountered this issue. Could you please let me know what is the format of your source photos? What camera are they shot on?

    Also, are you able to reliably reproduce the crash by doing just the following:

    1. open image in Aurora
    2. apply crop
    3. save Aurora document
    4. restart Aurora
    5. try to open the document you saved in Step 3
    1
    Comment actions Permalink
  • Avatar
    Tom Fortuna

    As stated in my original post; it works just fine with a SINGLE image. Using 2 images however: Doing nothing other than a crop produces an .auh that will successfully reload. I repeated this time enabling ghost reduction, auto align and a crop with no other edits which produced an .auh that just sat indefinitely at "making it  awesome". This is a new behavior, normally Aurora just disappears and I'm back at the desktop.

    0
    Comment actions Permalink
  • Avatar
    Tom Fortuna

    Forgot to mention this is happening using .NEF files shot with a Nikon D5600 the same with ones shot with my D3300.

     

    0
    Comment actions Permalink
  • Avatar
    Paul Christensen

    Windows 10 64 bit, Intel 620 graphics card, Nikon D7100, .NEF format. Aurora HDR 2019.

    1.  Opened Aurora.  Selected 3 .NEF photos.  No crop; No editing.  Saved .auh file.  Reopened file. Opened correctly.

    2. Opened Aurora.  Selected 3 .NEF photos.  Selected 'Auto Align'.  No Crop. No editing. Saved .auh file.  Reopened file.  Opened correctly.

    3. Opened Aurora.  Selected 3 .NEF photos.  Selected 'Auto Align'.  Cropped composite image. No editing. Saved .auh file.  Reopened file.  Program CRASHED.

    0
    Comment actions Permalink
  • Avatar
    Denis Kotsee

    Tom, Paul, thank you for getting back to me. I'm sorry I'm late with my reply.

    I got a response from the QA team yesterday about this issue: it seems to be connected to either alignment+ghost reduction+crop or chromatic aberration removal+crop. Anyway, we're working on resolving this issue before the next update for Aurora.

    0
    Comment actions Permalink
  • Avatar
    Tom Fortuna

    Denis, Thank you for looking into this. I'm glad that you QA team was able to tell you the same thing that Paul and I have already told you. Maybe someday Skylume will test their own software and do so before it is released but at least this is still usable unlike Luminar 3.  

     

    0
    Comment actions Permalink
  • Avatar
    David Hardy

    Having the same issue - ugh!  I hope the bug fix will happen soon.  Frustrated.

    0
    Comment actions Permalink
  • Avatar
    Alan O'Brien

    The Skylum product for PC has been half-baked from day one with the introduction of Aurora 2018. This crop error bug has brought my in-progress projects to a halt. It's frustrating to say the least that Skylum feels that releasing a partially crippled PC version is acceptable. 

    0
    Comment actions Permalink
  • Avatar
    Anastasia Davis

    Hi Alan! Please note that there are only minor differences between Windows and Mac Aurora HDR 2019.
    Indeed, there are some issues in both versions but we are working on them.

    0
    Comment actions Permalink
  • Avatar
    Michael Sojka

    I am having this problem too.   Wow is all I can say that here I am buying the software four months after this problem was identified and the consumer did the software QA to document it and a patch/fix has still not been implemented.   Why are these issues not listed in the FAQ and a newbie like me has to do a google search to even find this thread in the forums?   

     

    0
    Comment actions Permalink
  • Avatar
    Terry Rogers

    Hi Michael. Please contact us via https://skylum.com/support and we will do our best to help you.

    0
    Comment actions Permalink
  • Avatar
    Michael Sojka

    I did and sent Windows event crash files and the auh files.  Waiting to hear a response.  Thanks

    0
    Comment actions Permalink
  • Avatar
    Terry Rogers

    Michael, our technical support replied to your email. Please let us know if that solution helps.

    0
    Comment actions Permalink
  • Avatar
    Alan O'Brien

    Is there a solution for this? I contacted support and received the standard, "It will be fixed in the next update" which we are still waiting for. This is not just an inconvenience, this is a critical flaw that has brought our work to a stand-still. I have had 40 images in limbo since February with no solution in sight. Will there be an incremental update to fix this or are you waiting to fix this in the next full update? Do you have an estimate of when we can expect this to be fixed? 

    0
    Comment actions Permalink
  • Avatar
    Michael Sojka

    Hey Alan - I don't work for Skylum and don't know why they don't put some workarounds on the FAQ.  I found and others have posted in an other thread that you should be able to use this work-around. 1) Don't crop your HDR images before saving the auh file.  2) Do all cropping post saving of the auh.  

    If you do this, the auh should load OK without crashing Aurora.   It is not optimal but better than being stuck with no way forward.   The bug is that images already cropped cause a problem while uncropped ones seem to work OK.   

    Hope that helps you.  You sound pretty frustrated which all I can say is I've been there too.  Good luck.  Hopefully Skylum will do something for us that have been experiencing these problems beyond "I'm sorry".    

    0
    Comment actions Permalink
  • Avatar
    Alan O'Brien

    Hey Michael, thanks for the post.

    Yes I did see the work-around of not cropping in Aurora. While it's a workable option moving forward, as you noted, it doesn't help for any in-progress files. I've seen other software companies fix less critical issues than this in a matter of days. I'm just surprised and frustrated that this work-stopping, critical flaw hasn't been fixed yet. My experience with Skylum software has been frustrating to say the least with a history of software bugs and problems in both Aurora 2018 and 2019. 

    Anyway, all that aside, thanks for reaching out and for taking the time to document this work-around for anyone that may come across this thread. 

     

    0
    Comment actions Permalink

Please sign in to leave a comment.