Depending on how you get these back into Mylio (import? watched source folder?) Mylio will treat them as new photos with separate XMP. You edited your photos (presumably in an external editor) and saved new versions as TIFF, JPEG, or PSD. I think Mylio could improve this by adding an optional ability to “split” these, or at least access the JPEG separately when needed. I would argue most users strongly prefer for Mylio to “stack” these together & treat them as one photo by default. It seems to me there are at least two distinct scenarios to be considered here: There are many other instances where I either do not want to share an xmp file between a raw and jpg photo and just have an xmp file exclusively for one or the other. They are rated, labelled, “metadated” differently. I have instances of the same photo as tif, psd, rw2 and jpg. The same as JPG goes for TIFF and DNG files.
#How to move files in fastrawviewer software#
You only have to be careful, that if you change something in Mylio in a JPG file, you have to save the metadata to the file “by hand” (or if your other software can handle an XMP sidecar, that is the way Mylio currently operates). rename all RAW sidecar files and set the other software also to use the standard wayĪfter this, you can import your files again to a new Mylio and you should be alright.
If you have a JPG and RAW file with the same name in one folder, Mylio will handle them as a stack an keep their metadata consistent. RAW files should have an XMP sidecared with the same name, but extension replaced by XMP. Here Mylio is not standard, but at least has a function to save the data into the file (Save metadata to file). JPG files should contain the metadata in the file.
#How to move files in fastrawviewer update#
Maybe they can read this data once, but I wonder what happens, if you update metadata in digiKam and check in ON1 if it reads it again.įrom the mentioned software I only have DxO. I am not sure how much your mentioned software is really compatible with this way. Is there a setting or import process (version fix) that addresses this (in my case) problem? Thanks. These are very standard xmp formats and I have had no problem using these files with any of the popular processing software (ON1, Affinity, DXO, Luminar). It also compromises my backup process since, with partition 1 as a vault (however that happened), this drive is no longer an exact duplicate (triplicate actually) of my collection.Īs much as I would like to use Mylio I cannot with this limitation. This largely affects the raw files - no gps, ratings, labels, etc - since this metadata cannot be embedded, unlike for jpgs. Mylio made the other partition (1 of 2) a vault as well, suffering the same fate as follows.)Īll xmp files of the format were not transferred (and were deleted from the backup partion - 1 of 2). The intended Mylio vault was to have been on a partition (2 of 2) of a drive used as a backup. I set up a partition on an external usb drive as a vault/library and imported the files using “Add without moving.” (note: an unexpected result as well. They create XMP files for both the jpg and raw (RW2 in my case): and. I have been using Fast Raw Viewer and digiKam, both very standards based applications. I have spent months digitizing a life long slide collection (about 30K) and processing those photos (culling, rating, captioning, key wording, adding GPs co-ords, adding capture dates). Just installed Mylio and bumped into the XMP issue touched on in this post and a few others that I have browsed. I believe Mylio follows Adobe’s practice. For example, by default Lightroom creates its own sidecar files by REPLACING the original file extension with. Which is what Adobe apps use in practice. You could literally interpret this to allow your file naming convention. (This is called a sidecar XMP file.)įrom Part 3, Storage in Files () , base filename = “XXXXXXX.MOV”Īdmittedly, Adobe (owner of XMP spec) is a bit ambiguous in their documentation:įor applications that need to find external XMP files, look in the same directory for a file with the same name as the main document but with an. The issue is not having an exact match on the “base” filename. So this means that the actual filename cannot have any periods? So I hope this should be documented since file export templating from apps like Lightroom - do allow periods in the file name and it seems like Mylio doesn’t seem to like this.