I really am getting tired of this release. Edits are not being picked up in browse and the update badges are missing since the update. This affects roughly 90% of my images. It shows that edits have been applied to the image but browse displays an unedited, or incomplete edit. Refresh image has no effect. Opening in develop then applies the edits, but in order to have browse show the edited version you have to change a setting in order to force an update. Also here and there there is corruption e.g. displaying just a quarter of the image. I have tried the rename folder trick and also touching the sidecars. I have also tried saving the folder, deleting it within ON1 and then restoring the folder but it doesn’t help and I end up re-editing the images one by one.
It is also not possible to export from browse if the preview is not updated, you get an error. It would be nice to maybe add a translation of Error 1016 for us non-insiders, or maybe a list of error codes in the manual.
Starting Export Mon Jun 27 15:21:11 2022
Exporting 1 photos with 1 presets
Error 1016 exporting 5D4_0196.CR2
Ending Export Mon Jun 27 15:21:12 2022
If you haven't sent all of this in to tech support, you need to do that.0
I reported a similar export error, 1026, that also displayed with no useful information in 2022.0 There was no more information than that in the log file. There was no information about which file failed or why. I got the expected "We can't reproduce it, so we're done researching it" response. If they bothered to put some effort into logging useful information, we'd all be better able to troubleshoot problems like this.0
You can Google the error codes. They come from the OS, the program is only recording them.
It's hard to be sure if such error codes come from the OS. Googling "1016" returns mostly hits for the Diablo game. "1026" returns mostly Disney Plus hits. And I researched 1026 before I reported it to tech support. The link above contains 'answers' for "10016", which is not what the question in the link asked about. EventID.net used to be helpful resource for identifying such errors, but it's apparently shut down for good.
Regardless, a dialog with an error code and nothing more is still sloppy programing. ANY additional feedback would be helpful. Expecting an end user to understand what lead to a COM or file save error with no details is ridiculous.
Dev won't improve it, Tech support won't investigate, and management doesn't seem to care what happens. They clearly don't look at the user forums.
I'm sure that you're tired of hearing these responses, but it's not just the 2022.5 release ; this situation hasn't improved in the 4 years I've used On1. Like many others, I want to see this product to succeed and to replace others, but the company seems to keep doing every it can to distance existing customers from wanting to stick with them. Just because ON1 can't reproduce problems doesn't mean they didn't happen, and aren't still happening.
Again Brian and Rick, I'm not directing this at you, who clearly go above and beyond to help users here. But in reality, this is what the company should be doing. If the company paid attention to these forums, they would see the real frustration that their users face. A number of users have posted that they've had enough of the poor service they receive from the company, myself included. Having a bad reputation for customer service will quickly kill any company, even when the customers want it to survive.0
You have to be more specific — Google "Windows 1016 error" or "Mac xxxx error". Lower numbered error codes are generally reserved for the OS. Programs are supposed to use higher numbers which don't conflict with those from the OS.
Most users won't understand what the error codes mean in the first place. You have to understand how the OS works for them to have much meaning.
I don't know of any company which provides more than the error number when reporting them. For one thing there is the context in which they are raised, what was the code doing when the error occurred. Users won't know that. They are meaningful to the engineers.0
That's the point that I'm trying to make. Displaying an error code with no additional information is of little use - tech support doesn't even know what to do with it. No details are displayed or logged anywhere that would be of any help to the developers.
"Error 1016 while saving file xxx" or "Error 1026 while corrupting the Settings file" would be more helpful. Something in the logs that would useful to dev or support seems like an obvious first step - isn't that what the logs are for?
I've submitted several crash logs, and it seems that no one there knows what to do with them.0
I get the same error message when trying to export files to jpeg "Error 1016 exporting..."
Hopefully this will be corrected soon. Just noticed that this is Technical support Windows and I'm on Mac but so the problem is on both systems.0
Can you provide more details on precisely what you were doing please? A screen shot showing your Export dialog would be very helpful. You can collapse any of the panels which are not being used and resize the window so we can see all the panels and their settings for those you are using.0
OK..so does this help, I've chosen a folder on desktop as a destination0
Unfortunately, no. 🙁 I was looking for something more like this.
So you are exporting a full sized JPEG with no Resizing being done?
What is the Destination for the exported file?
Are you using Background Export? Have you tried toggling that setting?
Have you run a Disk First Aid check on the drive you are exporting to? Have you gone through the Delete Settings/Reset ON1 Photo RAW steps?
After doing some more Google searching for error code 1016 it appears it can be caused by many different factors — an incorrect DNS setting for instance. Obviously this is not the cause for an export as DNS isn't involved. This gets back to what I was saying earlier that before you can interpret the error code you have to know what the program code was attempting to do which is why it is so difficult to provide the user with a better explanation. It seems that it is frequently caused by some kind of corrupt setting in either the program involved or in some system setting.0
Did more testing. Very strange, there are folders and smart folders that I can export files and some that I can't?
Will see the actual folders if there is anything different there.0
You did not answer any of my questions and that makes it difficult to proceed.
- So you are exporting a full sized JPEG with no Resizing being done?
- What is the Destination for the exported file?
- Are you using Background Export? Have you tried toggling that setting?
- Have you run a Disk First Aid check on the drive you are exporting to?
- Have you gone through the Delete Settings/Reset ON1 Photo RAW steps?
Sorry, I was away from home last night so to answer your questions:
- yes I'm exporting a full sized JPEG with no resizing done before
- Destination was a folder on desktop on a system drive, changed that into a folder on an external HDD.no change in results
- using background export does not make a difference
- ran the Disk First Aid, no change
- this I have not done...am I about to lose something in resetting On1 Photo Raw? Smart albums? Yes, I have backed them up so I guess I could import them afterwards.
One thing also that has come after the last update: When I quit the program, I'm left with the dialogue "Progress - Shutting Down - Stopping data sources" and this will not end..eventually I will have to do a Force Quit.0
I do not recommend trying to recover your Albums with a restore. If the data that was backed up was corrupt when it was backed up the restore will also restore the corruption. A better method is to add a keyword to those photos in the Albums. I use the Album name for my Keyword. It is then an easy step to search for those keywords to recreate the Albums. The whole idea of the Reset is to let the program rebuild its data from a clean start.
Smart Albums are just the results of a set of search criteria. They will be rebuilt by recreating the search and saving it as a Smart Album once again.
The hang during shut down is a known problem. Force Quitting is the only solution for now. I thought I had gotten rid of it by removing the mobile app from my mobile devices. It worked for about a week but I've been experiencing the hang again lately.
Try the Delete Settings option first. That only clears your preferences and the program's state settings. It won't touch your Catalogs or Albums. It leaves the program's internal databases intact so all you have to do is reset your Preferences and you're back in business. It fixes many problems. Only do the Reset if the Delete Settings option does not work.0
Thanks I will try that. One thing that I found interesting is that while I can't export a picture, if I make a version of that picture then that version can be exported.
About the shut down...that seems to be gone for now..strange.
OK...deleting settings made no difference. I think I will submit an error report and add what I have done so far. I know now that for the pictures that the export fails, I can do a version that can be exported. Longish workaround but will have to do for now.
Thank you for your help!0
The hang during shut down does seem to be random. Although I have noticed that it seems to happen more frequently when I’ve left the program running for longer periods.0
The clean export from a version is interesting and something that you should tell support about.0
Interesting that a version exports, similar to my problem. I have the problem that browse doesn’t always pickup applied edits and doesn’t show any badges and if I attempt to export the image ON1 crashes or gives an error. Creating a version forces browse to apply the edits and displays the edit badges and export works. This is similar to what I do; go into edit and make a change i.e. increase sharpening by 1. This also forces browse to pick up the edits.0
thanks for the tip. I made a very minor edit on 4 pictures and after making the change, I could export the pictures. I would also like to apologise for stepping into your subject. I didn't realise I was on Windows troubleshooting until afterwards---doh! Interesting to se that both Windows and Mac seem to suffer from same problem.0
It would help if you opened a support ticket to let them know I am not the only one with this issue. I am in the process of making minor changes to hundreds of photos and I am terrified all will be lost with any new release and I have to do this all over again:-(0
Today I had the same problems as described in the first comment.
I exported a few files that I had not used since several month. Out of 36 files I had 8 error messages that they could not be exported. After creating a version and exporting this version the error message disappeared and the jpg file had been created. I experimented with creating a copy/duplicate of the file and exporting also worked flawlessly.
I recorded a video to showcase the problem and did send the link and the respective file to support.0
I did open a support ticket last night. I also added this thread onto it.0
Hi Gerry and Volker, does the export for you work on any photos? I just found out that I can export other photos but not the ones that I took during 2019 (without doing anykind of an edit or a version).0
For me it is where browse doesn't pick up the applied edits, e.g. there is no edited badge but there are edits. There are a lot! Opening the photo in edit applies the edits (although many times the sliders haven't moved - another issue) and if you make a minor change and return to browse the export works.0
I can confirm your observation. I just did a quick test with photos from several years. The export problem only occurs with the photos from 2019, or more precise, with photos that were edited in 2019 and consequently have a .on1 sidecar created in 2019 most probably with version 2019. When I open the file in edit and apply a small change e.g. in Develop/Tone&Color/Exposure export works just fine. I assume this creates a new modified .on1 sidecar file that does not cause any problem.
Additional information: I import all my files with a custom preset which had a last update in 2022. There may be a conflict with this preset and the .on1 files from 2019.0
Jorma and Volker,
You may have hit the nail on the head. I have been going through all my photos. The problem photos could all have been edited in 2019 (I often go back and re-edit). From 2020 onwards I don't seem to have a problem. It is a bit difficult for me to check as I had touched (updated the created and modified dates) all the sidecars to try and fix this.0
I forgot to mention, that with one export from a photo edited in 2019 I saw this error message0
For your missing edits, have you tried renaming the folder those photos are in? That will force the program to reread the .on1 files and should recover your edits without having to take them into the Editor and make any changes or to create a new version to recover their edits.0
Been there, done that, got the T-shirt. It appears that 2022.5 can't handle images edited in 2019 whatever the current version was then. Editing now causes a new correct .ON1 to be created. Seems far-fetched, but the evidence does seem to point that way. I have passed this on to support.0
It was worth a shot. 😎0
Please sign in to leave a comment.