It's powerful functionality but not without limitations and idiosyncrasies. You can set up your import profiles to detect multiple versions on import and create the version sets automatically. It's often referred to here as "versioning". I'm not at home right how so I can't experiment with moving version sets but when I say "PSU's version management" I mean the way that PSU let's you associate separate image files in "version sets". You may have good reasons not to follow any of my suggestions but I thought it might be helpful to make them anyway. You can use PSU's version management to keep the various file together. If you're willing to output separate files for each version of the original image, then you should be able to get away with just using a "standard XMP" file. It saves the step of having to output extra image files and the disk space that is needed to do that but disk space is cheap enough now to not be an issue. I think the ability to store multiple versions simply by storing the adjustments in a sidecar file is pretty nifty. From what you said, it sounds like you have no need to use AS's catalog either. I knew that I didn't want to manage my metadata with AS so I made the decision not to use it's virtual version capabilities or its catalog feature either. If I wanted multiple versions of an image, I just created multiple image files the same as I do now with photo ninja. I had experimented with AS a long time ago and used it strictly as a raw processor. Perhaps that's an option you can live with.
The Corel article says that AS will let you create "standard XMP" sidecar files. I have no idea if it would be possible or not or if it would make sense to do that. dop file get moved as well? I realize that the metadata in the AS sidecar would not get synchronized this way but at least the AS settings that are stored in their proprietary xmp files would stay with the image files. %existingExtention%.xmp files (the ones created by AS) just like some of the other proprietary files that other raw processing programs create? If a user moves a Raw file that was processed with DxO, doesn't the. I understand your point about Corel distorting the standards but would it not be possible to treat the. If you moved the CR2 files the xmp files (created by PSU) would be moved also but the. I'm just guessing here, but I would expect that when you import the CR2 files, that PSU would create xmp files for them because it wouldn't recognize the existing ones due to the naming conventions used by AS. From what I read on the Corel link, the sidecar files should be named %filename%.cr2.xmp. Your comments seem to assume that they are sidecar files. Perhaps I'm misunderstanding you, but I believe that the. (And, preferably, don't try this at home. But if you really want to experiment with what I sketched above, then at least do a backup first.
Corel aftershot 3 exif missing ps3#
You may want to rethink your needs or your use of PS3 w.r.t. I first thought it might be important to have the CR2 files added as versions (assuming the version detection in PS3 works with non-image files too) but I don't think that actually matters for the moving operations, since there's no way (that I know) to simply drag a version set in the folder view. (You might even get XMP sidecars generated for your CR2 sidecars, which would be kind of odd.) Hope for the best and prepare for the worst. I have no idea how well that would work - or what side effects it might have. (Make sure the files are sorted by name.)Ĥ. Drag and drop as you please the images files, always selecting an image file along with its. cr2 files (perhaps by using Verify Folder).ģ. cr2 extension to the list of recognized extensions.Ģ. If you're adventurous enough, I guess you could try the following:ġ. I doubt there's any straightforward way to achieve what you want in PS3.
0 kommentar(er)
