![]() I'm just glad the two-tiered method for saving non-destructive edits exists! It saved me from having to dig into my backups to restore files. It could be a bad block on a disk, cosmic rays. I believe this to be a case of the sidecar file being corrupted in some way. It has happened to one and only one of my photos among thousands and thousands in my library. And we're running experiments to see if the problem is reproducible. If you are using Windows Authentication I think you will face this issue. I've already been in touch with ON1 about this phenomenon. And yes, I did stop and restart Photo RAW after the sidecar file was regenerated. That's enough to refresh the sidecar file. For example, raise the Exposure slider and then Undo the operation. Sklum removed the ability to create custom workspaces and workflows, which made using Luminar. I quickly open the Develop module and make a token change. Luminar 4 is a HUGE STEP BACKWARD from its predecessor, Luminar 3. The sidecar files are generated when a processing change is made. By renaming the sidecar, Photo RAW used its internal database to appy the changes instead. ![]() Apparently, Photo RAW reads the sidecar if its present. You did not need to worry if you did not have a fast computer, as all of the images are. Photo RAW keeps its own copy of the changes in its internal database. Version 3 included a powerful cloud-based batch image editing feature. how did those edits come back? Remember I said the ON1 sidecar file is a backup of the non-destructive edits. ![]() And even better news! All of my non-destructive edits are intact. Well - our does anyway.I restart Photo RAW. We still are missing the TOC synchronisation but I feel more hopeful than before that we will find a fix for this as well.Īdvice to other project support managers: If you can't get a response from Adobe TCS support, try going to your corporate account manager first they seem to be able to pull strings that make thing happen. Guess what? RH lets you put the space there, but then goes to pieces when you publish to the RH server, sprewing its files all over the place and making a general mess of things without generating a single helpful error message.Īfter spotting and removing the trailing space, everything went according to plan, except for the dysfunctional Search, which was resolved by copying the missing files into the whxdata and whdata folders. What happened there was, we finally found we had a spurious trailing space character after the project name in the SSL layout. We had problems publishing to the RH server I will probably need to create a separate item about that in the RH server forum. Re-installing RH10 on the local computer had no effect at all. By "working problem" I mean (in our case) a new project This fixes the dysfunctional Search problem. The missing JS packages in whxdata can be inserted via a simple copy-paste operation from a working project (but insert only the missing packages). Things are finally moving toward a resolution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |