- This topic has 4 replies, 2 voices, and was last updated 2 weeks, 3 days ago by
.
-
Posts
-
I think the maybe the most outstanding feature of Nitro, is the way it allows image processing with files system and photos resources in parallel
Assuming that you work with a referenced file in Photos, one thing that would enhance this functionality one step further is if it was possible to open a image from the Nitro photos interface and “export” the photos settings as xmp file with the referenced file, thus enable a “new version” to be available via the file system interface
Is this possible and/or feasible?
Yes, that is already possible. In the Export UI, you can export an original + metadata.
That goes both ways – you can export from the file system -> Photos (which adds it to the library + the edits, non destructively!) and you can export from Photos to the file system, which will output an XMP with ratings / edits.
I am aware of that, but that was not really what I wanted
As far as I understand the current options are:
Save a NEW image to photos
Save a NEW to the file system
Copy the image + adjustments to the file systemWhat I asked about was the creation of a just a metadata file linked to an already existing file (referenced by photos) in the file system, referable with the file reference used by photos by default
No, the app cannot do that. I suppose it would be possible, but that would only work for referenced files, which would make for an odd interface. However, if you export the original + metadata and put the XMP file next to the original file (deleting the original Nitro produced), then Nitro would read it.
Thanks
Yes I know, actually part of my workflow
What I am actually trying to achieve is some way to facilitate a form of a basic versioning functionality without creating copies, something I really miss I Nitro, but that I understand is difficult to achieve in a system lacking a catalogue function
I also have tried other variations on this theme such as xmp name swapping file copies (thinking about an external tool for this)
Another thing I have tried to explore is the possibility to create versions by “commenting out” relevant parts of the xmp file structure.
It is really fun to be able to play around with these odd activities without risking any impact on the core functionality of the application. I understand that this would add extra complexity for the application and perhaps user confusion, I keep it for myself
- You must be logged in to reply to this topic.