Timeline for How can I migrate my photos from Lightroom 3 to Bibble 5?
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2011 at 23:43 | comment | added | Jay Lance Photography | The implication being that in transferring to a 3rd-party product, the only data from the XMP file that is kept is the standard EXIF data as I have stated elsewhere. | |
| Mar 3, 2011 at 23:24 | comment | added | Jay Lance Photography | Additionally, Adobe does a pretty good job of recognizing and displaying these XMP values across their product lines, there is no such guarantee of 3rd-party products being capable of reading them in, and in fact many 3rd-party products simply erase values they don't recognize and start from scratch, as you've discovered. | |
| Mar 3, 2011 at 23:24 | comment | added | Jay Lance Photography | It is a subtle point, but an important distinction because while it is true that a user could conceivably go in and 'unadjust' any adjustments made in another program... For some of the values that would be very easy, but for others (Temperature for example) it would be impossible to do without knowing what the starting value was... Information that is not stored in the XMP file. | |
| Mar 3, 2011 at 23:24 | comment | added | Jay Lance Photography | 'Edits' in Lightroom parlance are stacked record of what changes were made to the file and the order they were made. In Lightroom it is possible to move back and forth within the editing stack, thereby undoing any changes that you may have made. What is stored in the XMP are the results of edits made in Lightroom, not the edits themselves. | |
| Mar 3, 2011 at 22:53 | comment | added | lindes | So, as far as I can tell, even if one renames/copies the XMP file to the name that Bibble expects, it won't heed (and will remove) the Adobe-added adjustments, replacing them with its own (starting from scratch). So, I believe this answer to be basically correct, that it would require either Bibble to update their software to honor Adobe's way of representing things, or a 3rd party to right a conversion utility. | |
| Mar 3, 2011 at 22:51 | comment | added | lindes |
So, I was curious enough about this that I went and checked it out. A few data points: (1) Lightroom does store (at least some) "edits" in XMP files (if so configured), e.g. fields like <crs:Exposure>+0.75</crs:Exposure> inside an xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/ block; (2) bibble does, too, but (a) the filenames are different (appending .xmp instead of replacing the suffix (e.g. .CR2) with .xmp), and (b) the changes are different, e.g. bopt:sat="51", referencing xmlns:blay="http://www.bibblelabs.com/BibbleLayers/5.0/", and in a different structure.
|
|
| Mar 2, 2011 at 21:04 | comment | added | Joey | Lightroom 2 at least uses an SQLite data base which you can scrape for the development settings and transfer them to Bibble. Assuming that Bibble has either an API or another way of setting development settings. But a quick and dirty hack-job of such a thing might be possible in a weekend of coding. | |
| Mar 1, 2011 at 23:35 | vote | accept | apparat | ||
| Mar 1, 2011 at 23:20 | comment | added | Jerry Coffin | Quite true -- the only way this is going to happen is if Bibble Labs implements it. | |
| Mar 1, 2011 at 22:11 | history | edited | Jay Lance Photography | CC BY-SA 2.5 |
added 18 characters in body
|
| Mar 1, 2011 at 21:53 | history | answered | Jay Lance Photography | CC BY-SA 2.5 |