Skip to main content

Exporting Issues

Comments

11 comments

  • Kevin Pinkerton

    I have an issue exporting that I can use to cause ON1 to crash and shutdown in a bad way. But I know how to get around it.

    Actually there are several issues with exporting.

    - If I export a raw file in browse, I have to pause several seconds after starting the batch export (of a single file) before doing a second export of the same raw file (a different saved export setup, going to a different directory). If I go to quickly into the second export, ON1 will always crash in a nasty way.

    - I have an export setting that generates a jpg in the same directory as the raw file. I star rate and color code the raw image prior to exporting. When the jpg is created, it will have the same star rating and color code as the raw file. I like this and want it to be that way. I also have an export setting that creates a jpg in a separate directory. If I use that export before using the first one I mentioned, the first will will not always put the star rating and color code on the jpg it creates in the same directory as the raw file. That is annoying. Especially since I usually have sort by rating turned on when processing these images. I thought I had a workaround for this problem, but it is not consistent. The work around was to always export the raw to jpg in the same directory BEFORE using the export that puts the jpg in a separate directory.

    Kevin

    0
  • Rick Sammartino Community moderator

    Kevin, wow, you have export issues that I've never heard of !

    Greg, yes, there are plenty of posts here about Export problems. Going to Browse first is the best work around we have until On1 fixes the problem. Even if you go to Browse first, there may still be times when Export isn't correct.

    The best 'Guess' (because On1 won't say) as to when the next maintenance update will be released is sometime in June. Fingers crossed that these bugs will be fixed with that release.

     

    1
  • Brian Gibson

    My main Export problem is that it is incredibly SLOW.

    I wasn't aware of switching to Browse mode before exporting, so I'll have to give that a try.

    1
  • Gregory Hopkins

    Hmmm.  I guess On1 leaves me no choice but to continue with Adobe LR & PS. This export problem did not exist in earlier versions, albeit other issues did exist. I guess the developers broke the export option while fixing something else?

    Regardless, Adobe and Skylum Luminar 3 will be my go to post processing tools until On1 fixes the issues. I can't keep switching workflow only to find I hit a wall when I go to produce the JPEG. Even when PR 2019 does export the results are far from professional and reliable.

    I really hated when my professional colleagues laughed at me when I started moving to On1. Sadly, no one does the things Adobe can do as well as they do it. Between Skylum and On1, I paid more than the annual subscription to the Adobe photographer's package. I guess my colleagues were right, I am sorry I spend the last 18 months hoping for something better.

    Photo Raw 2019 and On1 are taking on a giant in the industry. Although they do many things right, they are not ready for primetime. For now, I absolutely must return to Adobe in order to satisfy my clients and maintain my reputation. 

    1
  • Darryl Brooks

    My export issue is simple. After 3-4 exports. It will crash on the next 2-3. If I haven't lost patience by then, I can get a few more out. Still have one foot in Adobe.

     

    0
  • Darryl Brooks

    Removed all catalogs. Followed someones' advice to stop applying lens correction automatically. Crashed on 4th export. That was the last thing I know to try. I'll be in Lightroom until the next update. 

     

     

    0
  • Martin Evans

    On1 crashes for all the time exporting even if I go back to browse first. Worse, my whole screen goes and my monitor says there is no signal and even if I leave it for ages it never comes back. The machine itself is still working as caps lock key can be turned on/off and the button on my keyboard to hibernate still works. The event log says:

    Faulting application name: ON1 Photo RAW 2019.exe, version: 13.2.0.6564, time stamp: 0x5c4ed1ab
    Faulting module name: nvoglv64.dll, version: 25.21.14.1967, time stamp: 0x5c8de4af
    Exception code: 0xc0000409
    Fault offset: 0x0000000000ee51f9
    Faulting process ID: 0x2660
    Faulting application start time: 0x01d4e9978af8de01
    Faulting application path: C:\Program Files\ON1\ON1 Photo RAW 2019\ON1 Photo RAW 2019.exe
    Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispci.inf_amd64_b87987c5cf0d5bfa\nvoglv64.dll
    Report ID: b8511328-9930-402e-8c82-2f10f8e75995
    Faulting package full name:
    Faulting package-relative application ID:

    It is really tiresome as this only happens when using on1 and mostly (although not all the time) when exporting.

    0
  • Kevin Pinkerton

    Martin,

    I did a quick google of nvoglv64.dll and found many places where that was the faulting module during crashes. Even with nVidia drivers. There was mention on one thread about using the physx feature of the nVidia driver. I am only making a wild guess here, but if you are using nVidia drivers, have you configured the nVidia control panel to use the physx setting for ON1 Photoraw? This is a link that mentioned this physx issue. It may have nothing at all to do with your problem.

    https://forums.geforce.com/default/topic/1005038/seeking-tech-advice-to-fix-nvoglv64-dll-crashes-and-weird-opengl-render-offset/

    0
  • Martin Evans

    Thanks Kevin. I am obviously using the nvidia drivers with a 1060 (6GB). I haven't set any application settings in my nvidia settings at all and in any case, as far as I can see, physx is not one you can change per application. My physx setting is "auto-select (recommended)" and the only other 2 options are cpu or GTX 1060, there doesn't seem a way to turn it off.

    The thread you link to is 2 years old now. I have the very latest driver for my card. I can happily play games with this card without any issues.

    I was a little remiss with the event log I posted as it is often followed with:

    The description for Event ID 1 from source NVIDIA OpenGL Driver cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Unable to recover from a kernel exception. The application must close.


    Error code: 3 (subcode 2)
    (pid=9824 tid=9180 on1 photo raw 2019.exe 64bit)

    Visit http://www.nvidia.com/page/support.html for more information.

    The message resource is present but the message was not found in the message table

    0
  • Martin Evans

    I believe I've sorted my issues with exporting now (crashes). I went through running the reliability history, dism.exe, sfc and lastly dzdiag and found a few issues. I removed GPUteak (which was very old and from a previous nvidia card I had) - this was showing errors in event viewer. However, the registry change at https://devtalk.nvidia.com/default/topic/1024452/opengl/bug-report-nvoglv64-dll/ stopped the crashes for me.

    I also discovered how to reset the display driver when my screen goes blank using on1 but the computer is still running - hit windows + ctrl + shift + b.

    Hope this helps others. (BTW, I'm using a 1060 6GB card).

    0
  • Gregory Hopkins

    Okay. There seems to be some serious issues with Photo Raw export and other things. I've been told On1 knows about it and plans a fix to be contained in a update. It could be as early as June, but no guarantee. 

    I got the feeling they know they broke the software, but can't fix it without causing still more problems. An alternative is to replace the export software module with a better, more robust module. Besides cost, all those software hooks or links have to re-coded and tested, and hopefully, tested, again.

    I haven't touched On1 software in over a month. Thankfully, I still have Adobe's Creative Cloud subscription so I can still work. Photo Raw has been off my radar - out of sight out of mind.

    When a company breaks code or cuts corners with sub-par modules, the overall cost in money, time, reputation and loyalty is a whole lot more than doing it write the first time.

    Photo Raw initially seemed like it might replace at least one Adobe tool. While On1 fumbles, Adobe is making their software an absolutely necessary requirement for professionals. I just can't pay the bills with On1. Retail price for On1 is not really cheaper than Adobe CC and recent issues actually make it more expensive. In the case of On1, I paid a decent amount of money for software taking up space on a drive. Yeah, I'm not happy and I'm not impressed. I haven't heard a word from On1 - only rumors from others frustrated users and trainers. I cannot honestly recommend Photo Raw to colleagues, students, friends or family. Processing client work that cannot be correctly exported means I wasted my money. I recommend you don't waste your money and for the same price, get professional software.

    1

Please sign in to leave a comment.