|
Understanding Image Editing |
|
Bibble 5 is a non-destructive image editor, meaning that adjustments you make to your images in Bibble 5 will never alter the data in the original image. You are free to experiment and alter your images as much as you want, knowing that you can always revert to the original version. As a non-destructive image editor, the adjustments you create are stored either in an "sidecar" XMP file, within the Bibble 5 catalog file, or both. As such, you will need to create an output image using Bibble 5's Output Batch tools or File -> Save As menu options to allow your image adjustments to be visible to other applications. When you edit a photograph in Bibble 5, a new Version is created that contains the adjustments you've made. Bibble allows more than one set of image adjustments to be made on a single photograph, allowing you to efficiently make many versions of a single image. Creating a new version does not make a copy of the original Master File, but rather just allows you to apply different image adjustment and metadata to the same Master Image. Image files that are opened and edited within Bibble 5 are called Master Files. Bibble 5 stores its settings in an XMP file that is slightly different that other popular image editors and Asset Management applications. We do this to prevent Bibble from overwriting settings created by other applications and to circumvent limitations inherent in the current XMP standard (such as only being able to export the metadata from one Version at a time, or the inability to save different settings for a RAW file and a JPEG that were created in camera as a RAW+JPEG pair). Bibble 5 uses a similar, but slightly different filename to store this enhanced XMP data. The XMP filename is created by simply adding ".xmp" to the end of the complete filename for the image file it describes (while many other applications build the XMP filename by first dropping the image file extension (like "jpg", "nef" or "cr2") before adding "xmp"). So a Bibble 5 XMP file would look like img_0000.jpg.xmp while an XMP from other applications for the same image would simply be img_0000.xmp. Bibble 5 will allow you to create a "standard" XMP file that other applications will read - but this will of course limit the settings that the other applications see to those officially supported by the XMP standard (one set of metadata per image file). Other applications store image adjustments in sidecar XMP files, and metadata added in other applications can be imported into Bibble 5. These include:
Likewise, applying any of these settings to images in Bibble will write this data back to the XMP file for those images. Many applications allow you "sync" settings from XMP files with the settings they hold in their internal databases. Once this "sync" process is complete, adjustments made in Bibble will appear in those applications as well. See the section on Keywording & Metadata for additional information. XMP Data Exclusive to Bibble 5 Settings from image editing tools within Bibble and other applications are also stored within XMP files; however, these settings are not shared amongst applications from different manufacturers. This is due to the technical differences in implementing various image adjustment tools. These differences in how the various tools are implemented give each application its own image quality characteristics, and prohibit image adjustment settings from being shared between applications. Using Bibble 5 in no way limits what you can do with your images or which applications you can use edit or manage your digital photographic files. Metadata Collection During Import Bibble 5 reads and collects metadata embedded in image files, in Bibble XMP files, standard XMP files and in Bibble 4 '.bib' files. The process and order of collecting metadata from these various sources is shown below.
| ||||||||||||||||||