ON1 can't open some files in Develop
Answered
Hi, new user here. I just updated to PhotoRAW 2021.5 a week ago and decided it was time to move on from Adobe (pun not intended). I navigated to my photo drive in Browse mode and was able to see and develop my files with no apparent issues. I have a LOT of files (somewhere around 200,000 - which Lightroom was able to handle just fine).
Next, I created a cataloged folder starting from the drive's root directory, which took about a day; again, there didn't seem to be any problems, so I took the next step of migrating all my Lightroom edits over. That took about 3 days, but seems to have completed without error. I am NOT using sidecar files, because the concept doesn't fit my workflow.
However, now I have identified several folders which have files that won't open in Develop. They are recent dates, though they have all been on the source drive since before I started using Photo RAW. The files are intact, can be opened with all my other programs including Lightroom, and are definitely in the same folder as listed in PhotoRAW. The photos are visible in thumbnail preview as well as full size in the Browse/catalog module, and I can navigate normally, but when I attempt to edit the files in question, I get the "no" icon as a preview in Develop, and the only button which responds is the one which takes me back to the Browse/catalog module. Oddly, not all the files in the problem folders behave this way - some are editable, others are not. I don't see any differences in the actual files.
I tried deleting one of the problem folders (which disappeared from the Browse/catalog module) and then restoring it from a backup (it reappeared). Nothing changed - the same files which were editable before still are, and the others are not. It doesn't matter whether I choose the file in the Browser or the Catalog pane, it won't open in Develop.
Now, PhotoRAW is still thrashing the disk and using a fair amount of CPU, so I assume it's doing background updates on the catalog. I guess I can wait till it's done doing whatever it's doing, but it seems that it's just creating previews and search patterns, not making the files readable - because Browse to Develop is supposed to work whether you have created cataloged folders or not.
Any suggestions? Something I've overlooked?
-
Are those image B&W by any chance? Normally when that icon is presented it is because the image is in the Grayscale colorspace which Photo RAW does not support. You will have to convert any image files saved in the Grayscale colorspace to an RGB colorspace before Photo RAW can work on them.
You said you are not using sidecars. I highly recommend you reconsider. If you ever have to reset the program for any reason it will trash the database where the edits are saved. Without the sidecar files to save your edits as a backup you will loose them. With the sidecar files the databases can be rebuilt.
As long as the cataloging process is still running you will see high system resource usage. Once that finishes that will drop off to background levels again.
0 -
No, I only shoot color - unless somehow Photo RAW is misreading the metadata, and only in some of the files, that's not it. Oddly, when selecting the image and choosing Develop, it displays correctly for a few moments and then reverts to the "no" icon. The app is still crunching on the catalog, but after running all night the same images still refuse to load. I have quit and restarted Photo RAW, and in fact rebooted the computer (a separate issue) with no change.
I can't get any of the controls to work when in Develop, but here's a capture of the file info taken from the browser:
0 -
Have any of those problem files been edited? What happens if you make a copy of that same file in the Finder so Photo RAW sees it as a brand new image. I'm wondering if the edits have become corrupt for some reason preventing the program from being able to work with it.
0 -
The problem you're describing might have nothing to do with the files. If you go into Edit and the only button that works is Browse, then it could be a problem with On1 not opening the Edit module properly. If you go back to Browse and try to re-open in Edit it will likely work just fine.
This happens to me quite often. All of the files work fine once you get Edit to open properly.
0 -
Going back to Browse, and then to Develop, again causes no changes at all - it still shows the "no" icon for that and other files in the directory. I've tested that multiple times.
However, duplicating that file (so that the name has changed) now permits me to edit the copy - but the original is still definitely not editable. So I guess this means the problem is in the edit data itself, and not the file; but that the edit data is tied to the file name? Just performing a "Duplicate" in the Finder caused the copy to show up in Browse, without any other actions.
How can I remove that edit data from the file permanently (or disconnect it from the file name)? "Reset Settings" doesn't work. Removing the file from the source directory in Photo RAW and then re-adding it doesn't seem to work (if the name is the same). I tried even removing the entire folder inside Photo RAW and re-adding it, with no change in the behavior.0 -
Reset All is supposed to do it.
You could move the photos to another folder OUTSIDE of On1: In On1, right-click and select 'Reveal in Explorer' (or whatever Mac calls it) that will open the correct folder for you. Creating another folder and moving the photos into it will break On1's connection to the file.
I would try copying a few first just to make sure it's working the way you expected.
0 -
Reset All doesn't work; even though it rolls back the edits, the filename is unchanged and Photo RAW still retains whatever link to the name is causing the issue.
Changing either the folder name or the file names, however, does break the link and the file(s) become editable. It's possible to tell from the browser because the cropping is removed when the file has been "fixed". I guess in some cases, changing the folder name might be easier but I have to be careful because my folder names all indicate the shoot and date - it's easier to make selective backups when the naming is consistent. So I'll probably do something simple like batch rename the files with an "a" suffix or something, since their names are just the CR2 alpha strings generated in-camera and aren't particularly useful other than for sequencing. And the name being different will only matter if I have to restore from a backup, which is rare - and would be obvious.
I'll have to try a few more of the folders in question first, but based on my sample testing it looks like this may fix the immediate problem! I'll try to report back either way.
0 -
OK, it's going to be easier than I feared. Once a single file in the affected folder has been successfully edited, it's possible to copy/paste the basic develop settings to the others (and they're typically pretty close anyway) in Browse and they become editable without any fooling around with the filename or switching back to Develop mode. So any time I find a file that has been rendered un-editable I can fix it in situ without too much bother. Thanks to all who pointed the way to my solution.
It does seem, though, that migrating Lightroom edits to the files in some way caused some of them to break for new edits. I don't go back all that often to re-edit older files but I'll just have to keep this in mind if I want to tweak them.
0
Please sign in to leave a comment.
Comments
8 comments