Which wrappers support meta data saving?

Hello all -
I am getting closer to creating a workflow that works for all my cameras. The last challenge I am having is trying to decide what to do with my mp4(gopro created) that Prelude doesn't like and can't add meta data to. Mainly I want to add Production names, etc to the files but then I want to add comments and markers too as the tool is meant to be used.
Qs
1 - is there any way to use the mp4s and get the ecosystem to save such data in xmp files?
2 - what are others doing in this case? I'd transcode(nothe topic I know) but I decide what equivalent codec to use from the Quicktime wrapper list or other(?) that can also store meta data.
3 - Anyone know of a list of wrappers that do support meta data???
thanks
Rich

Hi Michael.
Ah, cool. Thanks for the info. I'll try the Match Source route too. Yesterday I took a few samples (MTS from another camera) through the ingest process and cam up with a set of sample sizes. Interesting range shift in each when viewing in QuickTime(I know, not always the best). I need to pull them up in Premiere side by site and see if they read any differently.
Anyway, I did set up some GoPro specific codecs in AME and thus had then in PL for my tests. See attached for size comparisons. The ones marked with GPS are from GoPro studio with Med and Low tests run. The AME CF's are with Cineform's 100% and 50% quality.
Now I am very curious what the Match source will do. I'll be it will be lower size, by a lot, and theoretically retain the vast majority of the quality of the original. I guess the benefit of going with the AME CF mode is that it really does move towards an intermediate editing format right? That the other thing I was considering shooting for, but my first goal was to at least get consistent logging for all my camera's base formats[ MTS(AVCH.264), Mov(H.264), and MP4(I guess H.264)]
I'm seeing the light at the end of the tunnel. Thanks for both of your replies!
Rich
PS- the nubers at the end of each are the factors of increase in size freme the source

Similar Messages

Meta data in Master pages?

In which way can meta data be added to a master page? Unlike to ordinary pages, the page properties dialog offers no tab for adding meta data.
For me this is a problem because I have a Google Translate plug-in embedded in my website. Using the Corrections function in Google's Website Translator I can improve the machine translation results on my website. One of the requirements to make this work is adding some specific meta data in the web page to be corrected. Without having those meta data in my master pages, some translations in pieces from these master pages are simply awful, while the rest of my website is very well corrected now.

Hi Sijmons,
as far as I know there's no way to place the widget before the </head> but I'm not omniscient...
But another problem is also, as far as I can tell... That widgets don't include the code you put in directly in the page where you put the widget in... So the code will not show up in the html code of the page itself... It works like an iframe or better it is an iframe. The widget is a page itself that shows up in the page you inserted it because there is the following code
<iframe id="widget2-frame" src=".//Welcomefiles/widget2markup.html" ...
Isn't it Keywords the same as MetaData? As far as I know inserting keywords in html code itself or inserting keywords in the content of your page while you're writing it is the same. Just use synonyms while typing text.
If you want you could edit the site post-publishing adding it, but as you have to do it every time you publish all over again it's really a mess (if you have a lot of pages).
Regards,
Cédric

Adobe Audition not saving Meta Data

I'm trying to save file information within an mp3 or wav file for our broadcast software (AudioVault) to read it and the information does not save.
We use versions 1.5 and Version 3 and they both exhibit the same behavior.
I have followed the info below but it doesn't work.
The File Info command opens a dialog box in which you can see and add metadata—descriptive information that a computer can process and search—about the open audio file. For example, metadata can include history, loop, and Broadcast Wave information.
For audio files in WAV, mp3, or CEL format, you can use the File > XMP Info command to add XMP metadata. This extensive metadata can be shared across databases, file formats, and platforms. (See Add or edit XMP metadata.)
1. In Edit View, choose File > File Info.
2. Click the tabs at the top of the dialog box to navigate between different sets of properties.
3. Set properties as desired, and click OK.
To preserve file information when you save files, select Save Extra Non‑Audio Information in the Save dialog box.
It is not saving the start and end date. Here's what I'm doing. Open mp3 file. File-File Info, toggle text field names to Radio Industry.
Fill out Description, Advertiser, start date, end date, click ok. click file, save as (clicking save extra audio infomation)
now close the file and reopen it and the start and end date are gone. Ideas?

After talking with BE I discovered that the following procedure will save
the
meta data providing it is saved in a WAV format (mp3 doesn't work.)
Open your mixdown in the waveform view.
Hit ctrl P and the wave properties window will appear.
Fill out title, artist. Cut number, category and date.
When you save as make sure save extra non-audio info is checked
Then in the dropdown save as type choose WAV windows pcm.
Your completed file can now be dropped into an AV import folder that should
transfer
Into the system with all the information in their proper fields.

Adding a custom meta data field which lists out content id based on query

How can we add a custom meta data filed which lists out content id based on query like dDocType <matches> `AssociatedProduct`?
Or other alternative would be to have a custom metadata field such that it allows selection of content id using link wizard which we typically use in site studio. It would be preferable to have this second option as it is user friendly. Can we do this on a check-in screen?
-Pratap

Thanks for the reply Deepak.
We got it resolved. We did following changes in /ucm/custom/SiteStudio/resources/ss_custom_field_resources.htm file and it worked cleanly.
Added following section at the end before body tag
===================================================================================================
<@dynamichtml ss_parent_definition_field_entry@>
     <$include super.std_edit_entry$>
     <$if isQuery and isTrue(isQuery)$></td><td><$endif$>
     <$include ss_contributor_base_scripts$>
     <script type="text/javascript" src="<$HttpRelativeWebRoot$>resources/<$SSContributorSourceDir$>/sitestudio/wcm.contentserver.popup.js"></script>
     <script language="JavaScript">
     function OnSelectParentId()
          var selectParentIdOptions = {};
          selectParentIdOptions.httpCgiPath = '<$HttpCgiPath$>';
          selectParentIdOptions.queryText = 'dDocType <matches> `Country`';
          selectParentIdOptions.coreContentOnly = '<$if coreContentOnly and isTrue(coreContentOnly)$>1<$else$>0<$endif$>';
          selectParentIdOptions.callback = function( returnParams )
               returnParams = returnParams || {};
               if( returnParams && returnParams['dDocName'] && ( returnParams.dDocName.length > 0 ) )
                    // Set the actual metadata value
                    <$if isQuery AND isTrue(isQuery)$>
                         for (var i=0; i < document.<$formName$>.elements.length; i++)
                              var elt=document.<$formName$>.elements;
                              if (elt.name=="<$fieldName$>")
                                   elt.value = returnParams.dDocName;
                    <$else$>
                         document.<$formName$>.<$fieldName$>.value = returnParams.dDocName;
                    <$endif$>
          WCM.ContentServerPopup.ChooseManagedDocument(selectParentIdOptions);
     </script>
     <input type="button" value="<$lc("wwBrowse")$>..." onclick="OnSelectParentId();">
<@end@>
======================================================================================
Then modified the section which show xWebsiteSection, xRegionDefinition etc to include my custom meta data defitnion as well ('xParentContentType')
===================================================================
<@dynamichtml std_edit_entry@>
     <$if fieldName and ( fieldName like "xWebsites|xDontShowInListsForWebsites" )$>
          <$include ss_website_query_text_field$>
     <$elseif fieldName and strEquals( fieldName, "xWebsiteSection" )$>
          <$include ss_website_section_field_entry$>
     <$elseif fieldName and strEquals( fieldName, "xRegionDefinition" )$>
          <$include ss_region_definition_field_entry$>
     <$elseif fieldName and strEquals( fieldName, "xParentContentType" )$>
          <$include ss_parent_definition_field_entry$>
     <$else$>
          <$include super.std_edit_entry$>
     <$endif$>
<@end@>
====================================================================
This worked fine.
Regards,
Pratap

Meta Data are saved but after some seconds lightroom displays again that arent up to date...

Hello,
i've started to use keywords. Also i export all files back to the XMP-Format. On some files the changes are not permanent/lasting.
My smart-collection tells me 5 seconds later that the meta-data should be saved again..
Do you have any suggestions?
Thank you

Yes, there are lots of issues like this. Mostly I find that closing the catalog and opening it will solve the problem, or you can read the metadata from the files after saving them. It seems to be a problem that Adobe cannot or will not fix.
Re: How to See what Metadata is in Conflict
Re: LR4 Problem Saving Metadata
and others that I think you can find yourself

In VA02 transaction which exit is triggering when saving the data

hi all sap gurus,
In VA02 transaction which exit is triggering when saving the data

Hi Reddy,
The <b>user exit</b> and badi tried for this transactions are
V60F0001                SD Billing plan (customer enhancement) diff. to billing plan
V46H0001     SD Customer functions for resource-related billing
V45W0001     SD Service Management: Forward Contract Data to Item
V45S0004     Effectivity type in sales order
V45S0003     MRP-relevance for incomplete configuration
V45S0001     Update sales document from configuration
V45P0001     SD customer function for cross-company code sales
V45L0001     SD component supplier processing (customer enhancements)
V45E0002     Data transfer in procurement elements (PRreq., assembly)
V45E0001     Update the purchase order from the sales order
V45A0004     Copy packing proposal
V45A0003     Collector for customer function modulpool MV45A
V45A0002     Predefine sold-to party in sales document
V45A0001     Determine alternative materials for product selection
SDTRM001     Reschedule schedule lines without a new ATP check
<b>Business Add-in</b>
BADI_SD_SCH_GETWAGFZ     Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001     SD Customer functions for resource-related billing
<b>Reward pts if found usefull :)</b>
Regards
Sathish

I want to restore 300 Gigs of data, saved to Time Machine, on my new iMac 27". I want my OS on the 256G SSD, but I want all the other data (which can be separated) on the 2TB internal hard drive. How do I do that?

I want to restore 300 Gigs of data, saved to Time Machine, on my new iMac 27". I want my OS on the 256G SSD, but I want all the other data (which can be separated) on the 2TB internal hard drive. How do I do that?

The Apple article will transfer everything from one volume to another. Doing what you want is not simple, unfortunately.
See Transferring Home Folders not on a Startup volume, especially scenario #1 in the gray box there.
That's just recently reworded and revised; please advise if it's not clear or you have problems with it.

Dynamically how to get the meta data of an ui element which is custom one

Hi All ,
In SRM , I want to know the meta data declarations of an UI element in my webdynpro component ..How to know this ..Can anyone help me in this ..I want to know the meta data of an ui element .
Sandeep

You really aren't supposed to read the properties of active UI elements directly. Instead they should be bound to context attributes and then you read these attributes via normal context APIs. If you absolutely needed such access because this is a standard SAP WD, then consider that the WDDOMODIFYVIEW is the only part of th event loop where you are allowed access to the View and its UI elements.

How could Ecatt support a FM which has export parameter data type as any

Hi,
I have created a FM which has export parameter data type as 'Type ref to data'.
The actual paremeter value for this export parameter is a dynamically generated internal table, which does not have a abap dictionary data type.
Could I use the 'FUN' ecatt command to test this FM? How could I get this reference export parameter?
Thanks a lot in advance!

Hi,
Wouldn't it be enough if you define parameter in test data container as reference to table type with structure of type c(1000) (or more/less characters depending on how much data you need to pass)?
I'm not 100% sure if filling this table with data will work (this is reference after all) but if this is an issue than create 2 parameters: 1 of table type and second of reference type. Then inside your script before FUN use ABAP...ENDABAP to assign your table parameter to reference parameter and use second one as input for FUN command.
I think that either first or second solution should work.
Best regards
Marcin Cholewczuk

Workflow for avchd clips and meta data

Just started using a Panasonic AG-AF100 on a 5 month project. Will be producing 1000's of clips. So I have off-loaded the first 3 cards we shot and have discovered something about avccam material. If you just copy the .MTS files from their /stream folder or rename the file with a name instead of its original number produced in the camera you lose the timecode and other meta data.
If I leave the clips in that folder and other card folders in their associated directories and "import" clip with Premiere Media Browser it retains the timecode. Trouble is that I cannot see thumbnails in Media Browser and the clip number means little. Bridge on my Win7/64bit machine shows thumbnails (but no preview) and a double-click will preview in Win Media Player.
On my main edit station (Vista/64bit) Bridge neither shows thumbnails or previews and I get no avchd .mts playback in Windows Media Player. Everything worrks the same within Premiere, nice solid editing and playback of avchd clips. (I will probably upgrade this machine to Win7 next week)
So my request for advice/questions are:
Suggestions for managing and organizing large qualities of clips with what will be similar names, etc
Previewing updates or options to find media
How do you manage AVCHD material and still maintain meta data?
Thanks so much!! As I get older and the technology seems faster, stronger, sharper, the demands on my brain get tougher.
Rick

Rick,
If you just copy the .MTS files from their /stream folder or rename the file with a name instead of its original number produced in the camera you lose the timecode and other meta data.
If I leave the clips in that folder and other card folders in their associated directories and "import" clip with Premiere Media Browser it retains the timecode.
You mustmustmust keep the files in their folder structure, if you intend to maintain timecode. You've clearly discovered this Good you did so early. The folder structure thing is really not a big deal; there is very little need to manipulate these at the OS level, and the Media Browser in PPro makes it reasonably easy to bring these in for editing. You can pre-build a folder structure into which you can offload each card's worth of clips.
Trouble is that I cannot see thumbnails in Media Browser and the clip number means little. Bridge on my Win7/64bit machine shows thumbnails (but no preview) and a double-click will preview in Win Media Player.
On my main edit station (Vista/64bit) Bridge neither shows thumbnails or previews and I get no avchd .mts playback in Windows Media Player. Everything worrks the same within Premiere, nice solid editing and playback of avchd clips. (I will probably upgrade this machine to Win7 next week)
Windows 7 has built-in splitters and decoders for H.264 media, so that's the reason you can at least get thumbnails in Bridge and playback the files in WMP there. The Media Browser, even on Windows 7, won't show thumbnails as they are not saved into the folder structure the way that P2 saves a poster image into the folder structure. Note that even "standard" containers like AVI or MOV do not display a thumbnail in Media Browser.
As far as Bridge is concerned: I know a lot of people like it, but from my perspective, it's just about worthless for video. This is largely an application designed for photography workflows that has been shoehorned into "working" with video. I don't even like it for AVI/MOV.
The ugly truth is that Bridge is not going to be much, if any, help in this workflow. However, there may be another tool in the suite that will accomplish what you need: OnLocation. You won't get thumbnails, but you can browse through the folder structure without knowing you're doing it, import clips to preview them, and add metadata. You could do this for each card you offload. Then, in Premiere, simply use Media Browser to navigate to your OnLocation Project, and it will open up just like a folder, listing all your clips with the metadata you added. Granted, it is not a perfect workflow, but once you added that metadata, it will flow with the files wherever you move them around in the Adobe suite--it won't go elsewhere, as it's not injected into the files themselves. So long as you're editing in Premiere, you're good.
Now, there is another thing you can do that may make clip management even easier, though it does require a bit of forethought in pre-production. It will really depend on the type of project you're shooting, but you can preload metadata on to an SD card and into the camera, and then automatically record this to the clips as they are shot! I don't have an AVCCAM to give you exact workflow steps, but I do this all the time with my P2 workflow and it's a tremendous help once you hit the edit bay.
If you haven't already, head over to the Panasonic support site: Support Desk Top / Broadcast and Professional AV. You'll need to register for a "PASS" membership (it's free, and you don't need to register a camera), but you can then download the AVCCAM Viewer application. Unfortunately, this application is not quite as helpful as P2 Viewer is (it's rather cartoony, actually), but it does have the metadata editor in it that will let you create your metadata files in advance and save them to an SD card. Then, after consulting the camera manual , you can set those metadata files to be a data source for the footage as you record it. Here's what you can add to the metadata files and, summarily, the clips:
Once you load this into the camera's memory, that data is saved into the clips, and is readable by Premiere. The "User Clip Name" field can be set to auto-increment (again, this is going off my knowledge of the way metadata works in a P2 camera, but the AVCCAM should be similar) so that each clip has a base name and then a serial number. When you're done with a particular scene/shot, you'd load the next metadata files, reset the indexing, and continue. Lather, rinse, repeat.
The biggest hole in the metadata workflow, at least as it pertains to AVCHD/AVCCAM, is that there is no tool (that I'm aware of) that lets you edit this metadata after the fact. With P2, you can--there are a number of applications, both free and payware, that let you do this--but I've yet to find one that works with AVCCAM. Even Panasonic's own AVCCAM Viewer is incapable of this, it seems.
The major advantage to adding file metadata like this is that it travels wherever the clips go, and into whatever application they land in. Not being able to edit it after the fact, though, just plain sucks. This is where the clip metadata you'd add in the Adobe applications comes into play, with the obvious disadvantage that it's only useful in Adobeland. As always, ain't no such thing as a free lunch.
So that's my take on this--it's good you're looking into this before you have a couple terabytes worth of footage on hand Let me know if I can help fill in any details that I might have overlooked. And be sure to check on the Panasonic site linked above for firmware updates to the AF100--I see one came out just a few days ago. It's always good to stay current.
Good luck!

VIDEO_TS meta data for Front Row?

Front Row in Leopard supports playing VIDEO_TS folders. You can also add cover art by saving a file as preview.jpg in the parent directory. The folder structure would be like the following.
/Users/fred/Movies/The Day the Earth Stood Still/VIDEO_TS/
/Users/fred/Movies/The Day the Earth Stood Still/preview.jpg
/Users/fred/Movies/Cloverfield/VIDEO_TS/
/Users/fred/Movies/Cloverfield/preview.jpg
/Users/fred/Movies/Attack of the Killer Tomatoes/VIDEO_TS/
/Users/fred/Movies/Attack of the Killer Tomatoes/preview.jpg
This works great, however I was wondering if there is any equivalent method for adding meta-data to VIDEO_TS folders. Obviously you cannot do the normal process of storing it as MPEG4 tags in an MPEG4 video file via iTunes. If it was possible I would presume the most logical method would be to store an XML file in each folder something like this.
/Users/fred/Movies/The Day the Earth Stood Still/VIDEO_TS/
/Users/fred/Movies/The Day the Earth Stood Still/preview.jpg
/Users/fred/Movies/The Day the Earth Stood Still/metadata.xml
/Users/fred/Movies/Cloverfield/VIDEO_TS/
/Users/fred/Movies/Cloverfield/preview.jpg
/Users/fred/Movies/Cloverfield/metadata.xml
/Users/fred/Movies/Attack of the Killer Tomatoes/VIDEO_TS/
/Users/fred/Movies/Attack of the Killer Tomatoes/preview.jpg
/Users/fred/Movies/Attack of the Killer Tomatoes/metadata.xml
I suspect that unfortunately this is not currently possible but does anyone know for certain?

Unfortunately it looks like currently there is no way to do it and Apple have been sorely neglecting Front Row (it has fallen well behind even the Apple TV which is far from state of the art). As Snow Leopard is concentrating on performance enhancements rather than new features, I do not hold out hope for any significant change for well over a year.
Note: Apple TV is not necessarily a bad product, indeed I bought one for my parents, it is merely like Front Row extremely limited, too limited for many people which is why it sales are (allegedly) so poor. I think the comment raised by more than one pundit that it fails to replace a box under your TV is an extremely important one. It does not replace your DVD player (there are still comparatively few movies on the iTunes store - assuming you are in a country which has any at all), the movies are too expensive compared to DVDs and do not offer either as good quality or as many features. It also fails to replace a video recorder or these days a DVR since it has no TV capabilities. As such it has to be treated as an additional box if at all, and as an additional box it increases the spaghetti factor and thus fails the WAF (Wife Acceptance Factor) even if it is by far the easiest to use product.
I have therefore switched to using Plex which is a Mac version of XBMC. Plex allows you to use VIDEO_TS folders just like Front Row (indeed the same folders can be used in both), but it does have a built-in 'library' which stores meta-data and artwork for these VIDEO_TS folders and any other videos you might have. It uses plugins called 'scrapers' to search sites like http://www.imdb.com for metadata about the movies, I have even written a 'scraper' to search Amazon for those few DVDs not listed on IMDB.
See http://www.plexapp.com
Since Plex does an excellent job handling VIDEO_TS (i.e. DVDs) it can 'replace' a box - the DVD player and also means the kiddies do not destroy your fragile discs.
PS. Horror of horrors, even Microsoft Media Center is 'better' than Front Row. This is practically the only category Microsoft has actually genuinely earned first place in rather than cheating/bribing/stealing/buying its way to.

Images (w/correct meta data) are in catalog and on disk, but LR 5.7 considers them new on Import

For reasons explained below, I want to try to re-import all my images into LR and hope that none/few are in fact considered new and are imported. Yet, for some folders, LR is apparently unable to detect that my source images are already in the catalog, and are on disk, and that the source file meta data matches what LR knows about the images. When I click an image in LR and Show in Finder, I do see the imported image on disk. I can edit the image in the Develop module. So, it seems good, but all is not well.   Sorry for the long post here, but I wanted to provide as much info as I could, as I am really seeking your help, which I'd very much appreciate.
Here are some screen shots that illustrate the problem:
Finder contents of the original images
LR folder hierarchy
an image as seen in LR
Finder content of external LR copy of images
import showing 10 "new" photos
The original images ... (I'm not sure why the file date is April 2001 but the actual image date is January 2011; I may have just used the wrong date on the folder name?)
The LR folder hierarchy ...
An image as seen in LR ...
The external folder containing the images in the LR library
But on import of the original source folder, LR sees 10 "new" photos ...
I tried "Synchronize Folder ..." on this particular folder, and it simply hangs half-way through as seen in the screen shot below.   IS THIS AN LR BUG?   This is really odd, since "Synchronize Folder ..." on the top-level folder completes quickly.
I have a spreadsheet of of the EXIF data for the original files and those created by LR. (I extracted this info using the excellent and free pyExifToolGui graphical frontend for the command line tool ExifTool by Phil Harvey.)   Almost all of the Exif data is the same, but LR has added some additional info to the files after import, including (of course) keywords. However, I would not have expected the differences I found to enter into the duplicate detection scheme. (I didn't see a way to attach the spreadsheet to this posting as it's not an "image".)
I'm running LR 5.7 on a 27" iMac with Yosemite 10.10.2, having used LR since LR2. I have all my original images (.JPEGs and RAWs of various flavors) on my internal drive on the Mac.   To me this is like saving all my memory cards and never re-using them.   Fortunately, these files are backed up several ways.   I import these images (copying RAWs as DNG) into LR with a renaming scheme that includes the import number, original file creation date and original file name.   There should be one LR folder for each original source file folder, with the identical folder name (usually a place and date). I store the LR catalog and imported images on an external drive. Amazingly and unfortunately my external drive failed as did it's twin, same make/size drive that I used as a backup with Carbon Copy Cloner.   I used Data Rescue 4 to recover to a new disk what I thought was almost all of the files on the external drive.
So, I thought all would be well, but, when I tried "Synchronize Folder" using the top-level folder of my catalog, the dialog box appeared saying there were over 1000 "New" photos that had not been imported. This made be suspicious that I had failed to recover everything.   But actually things are much worse than I thought..   I have these counts of images:
80,0061 files in 217 folders for my original source files (some of these may be (temporary?) copies that I actually don't want to import into LR)
51,780 files in 187 folders on my external drive containing the LR photo library
49,254 images in the top-level folder in the LR catalog (why different from the external file count?)
35,332 images found during import of the top-level folder containing original images
22,560 images found as "new" by LR during import
1,074 "new" images reported by Synchronize Folder ... on the top-level folder in the catalog; different from import count
Clearly things are badly out of sync.   I'd like to be sure I have all my images in LR, but none duplicated.   Thus, I want to try to import the entire library and have LR tell me which photos are new. I have over 200 folders in LR. I am now proceeding to try importing each folder, one at a time, to try to reconcile the differences and import the truly missing images. This will be painful. And it may not be enough to fully resolve the above discrepancies.
Does anyone have any ideas or suggestions? I'd really appreciate your help!
Ken

Thanks for being on the case, dj!   As you'll see below, YOU WERE RIGHT!      But I am confused.
    1. Does the same problem exist if you try to import (not synchronize) from that folder? In other words, does import improperly think these are not duplic
YES. Import improperly thinks they are NOT duplicates, but they are in fact the same image (but apparently not the EXACT SAME bytes on disk!)
    2. According to the documentation, a photo is considered a duplicate "if it has the same, original filename; the same Exif capture date and time; and the same file size."
This is my understanding too.
    3. Can you manually confirm that, for an example photo, that by examining the photo in Lightroom and the photo you are trying to synchronize/import, that these three items are identical?
NO, I CAN'T! The ORIGINAL file name (in the source folder) is the SAME as it was when I first imported that folder. That name is used as part of the renaming process using a custom template. However, the file SIZES are different.    Here is the Finder Get Info for both files. Initially, they appeared to be the same SIZE, 253KB, looking at the summary. But, if you look at the exact byte count, however, the file sizes are DIFFERENT: 252,632 for the original file and 2252,883 for the already-imported file:
This difference alone is enough to indicate why LR does not consider the file a duplicate.
Furthermore, there IS one small difference in the EXIF data regarding dates ... the DateTimeOriginal:
                                                                                               CreateDate              DateTimeDigitized                    DateTimeOriginal              FileModifyDate                              ModifyDate
ORIGINAL name: P5110178.JPG                                     2001:05:11 15:27:18    2001:05:11 15:27:18-07:00        2001:01:17 11:29:00        2011:01:17 11:29:00-07:00       2005:04:24 14:41:05
After LR rename: KRJ_0002_010511_P5110178.JPG    2001:05:11 15:27:18    2001:05:11 15:27:18-07:00        2001:05:11 15:27:18        2011:01:17 11:29:02-07:00       2005:04:24 14:41:05
So ... now I see TWO reasons why LR doesn't consider these duplicates.   Though the file NAME is the same (as original), the file sizes ARE slightly different. The EXIF "DateTimeOriginal" is DIFFERENT.   Therefore, LR considers them NOT duplicates.
     4a. With regards to the screen captures of your images and operating system folder, I do not see that the filename is the same; I see the file names are different. Is that because you renamed the photos in Lightroom (either during import or afterwards)?
I renamed the file on import using a custom template ...
        4b. Can you show a screen capture of this image that shows the original file name in the Lightroom metadata panel (it appears when the dropdown is set to EXIF and IPTC)?
SO ....
The METADATA shown by LR does NOT include the ORIGINAL file name (but I think I have seen it displayed for other files?). The File SIZE in the LR metadata panel (246.96 KB) is different from what Finder reports (254 KB). There are three "date" fields in the LR metadata, and five that I've extracted from the EXIF data.   I'm not sure which EXIF date corresponds to the "Data Time" shown in the LR metadata.
I don't understand how these differences arose.   I did not touch the original file outside LR.   LR is the only program that touches the file it has copied to my external drive during import. (though it was RECOVERED from a failed disk by Data Rescue 4),
NOW ...
I understand WHY LR considers the files different (but not how they came to be so). The question now is WHAT DO I DO ABOUT IT?   Is there any tool I can use to adjust the original (or imported) file's SIZE and EXIF data to match the file LR has? Any way to override or change how LR does duplicate detection?
Thanks so very much, dj.   Any ideas on how to get LR to ignore these (minor) differences would be hugely helpful.

Problem writing meta data changes in xmp in spite of enabled settings

Dear Adobe Community
After struggling with this for two full days and one night, you are my last hope before I give up and migrate to Aperture instead.
I am having problems with Lightroom 5 writing meta data changes into xmp and including development settings in JPEG, inspite of having ticked all three boxed in catalog settings.
In spite of having checked all boxes, Lightroom refused to actually perform the actions. I allowed the save action to take a lot longer than the saving indicator showed was needed, but regardless of this no edits made in the photo would be visible outside Lightroom. I also tried unticking and ticking and restarting my compute.
Therefore, I uninstalled the program and the reinstalled it again (the trial version both times). I added about 5000 images to Lightroom (i.e. referenced). After having made a couple of changes for one photo in development settings, I tried closing the program. However, then this message was then displayed:
I left the program open and running for about 5-5 hours, then tried closing the program, but the message still came up so I closed the program and restarted the computer. I tried making changes to another photo, saving and then closing and the same message comes up. The program also becomes unresponsive, and of course still no meta data has been saved to the photo, i.e. when opening it outside Lightroom, the edits of the photos is not shown.
What do do? I would greatly appreciate any insights, since I have now completely hit the wall.
Oh yes, that´s right:
What version of Lightroom? Include the minor version number (e.g., Lighroom 4 with the 4.1 update).
Lightroom 5.3
Have you installed the recent updates? (If not, you should. They fix a lot of problems.)
I installed the program two days ago and then for the second time today.
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
What kind(s) of image file(s)? When talking about camera raw files, include the model of camera.
JPEG
If you are getting error message(s), what is the full text of the error message(s)?
Please see screen dumps above
What were you doing when the problem occurred?
Trying to save metadata + trying to open images that it seemed I had saved meta data to
Has this ever worked before?
No
What other software are you running?
For some time Chrome, Firefox, Itunes. Then I closed all other software.
Tell us about your computer hardware. How much RAM is installed? How much free space is on your system (C:) drive?
4 GB 1333 MHz DDR3
Has this ever worked before? If so, do you recall any changes you made to Lightroom, such as adding Plug-ins, presets, etc.? Did you make any changes to your system, such as updating hardware, printers or drivers, or installing/uninstalling any programs?
No, the problems have been there all the time.

AnnaK wrote:
Hi Rob
I think you succeeded in partly convincing me. : ) I think I will go for a non-destrucitve program like LR when I am back in Sweden, but will opt for a destructive one for now. Unfortuntately, I have an Olypmus- so judging from your comment NX2 might not be for me.
Hi AnnaK (see below).
AnnaK wrote:
My old snaps are JPEG, but I recently upgraded to an Olympus e-pl5 and will notw (edited by RC) start shooting RAW.
Note: I edited your statement: I assume you meant now instead of not.
If you start shooting raw, then you're gonna need a raw processor, regardless of what the next step in the process will be. And there are none better for this purpose than Lightroom, in my opinion. As has been said, you can export those back to Lightroom as jpeg then delete the raws, if storage is a major issue, or convert to Lossy DNG. Both of those options assume you're willing to adopt a non-destructive workflow, from there on out anyway (not an absolute requirement, but probably makes the most sense). It's generally a bad idea to edit a jpeg then resave it as a jpeg, because quality gets progressively worse every time you do that. Still, it's what I (and everybody else) did for years before Lightroom, and if you want to adopt such a workflow then yeah: you'll need a destructive editor that you like (or as I said, you can continue to use Lightroom in that fashion, by exporting new jpegs and deleting originals - really? that's how you want to go???). Reminder: NX2 works great on jpegs, and so is still very much a candidate in my mind - my biggest reservation in recommending it is uncertainty of it's future (it's kinda in limbo right now).
AnnaK wrote:
Rob Cole wrote:
There is a plugin which will automatically delete originals upon export, but relying on plugins makes for additional complication too.
Which plugin is this?
Exportant (the option is invisible by default, but can be made visible by editing a text config file). To be clear: I do not recommend using Exportant for this purpose until after you've got everything else setup and functioning, and even then it would be worth reconsidering.
AnnaK wrote:
Rob Cole wrote:
What I do is auto-publish to all consumption destinations after each round of edits, but that takes more space.
How do you do this?
Via Publish Services.
PS - I also use features in 'Publish Service Assistant' and 'Change Manager' plugins (for complete automation), but most people just select publish collections and/or sets and click 'Publish' - if you only have a few collections/services it's convenient enough.
AnnaK wrote:
Would you happen to have any tips on which plugins I may want to use together with Photoshop Elements?
No - sorry, maybe somebody else does.
Did I get 'em all?
Rob

Should the web page address be included in the file name in the meta data dialog box?

In the page properties > meta data > below is a field with the label file name: (the the area to type in the field), after the field, it is labeled .html.
I have 2 questions here.
1. If I type in http//:www (my page url), do I include .html at the end? I didn't know if this is automatically added because it is off to the side of the field?
2. If I type in the entire URL address: http//:www (etc, etc).html, after closing the page properties dialog box, I make it a habit to double check my work. What happens is the http//:www.xxx changes to (htttpwww.xxx). It drops the //: on the URL.
So would it be better to just type in www.xxx (without the http//:www.xxx)
and do you type in the .html at the end?
I am assuming this will help with SEO page ranking or at least makes it easier for the search engines to crawl your site??
I hope this makes sense.
Advise would be very helpful.
Ben

You are absolutely correct with the URL Ben. Taking your above example, you just need to type in "Services" in the file name and the webpage will be exported as services.html and the URl will be www.xyz.com/services.html.
All the webpages (be it parent page or child page) gets physically saved at the root directory of your website on the server (where your website resides).
This name is just the name of the file using which it is physically stored and called from the server. It does not help search Engines to crawl deeper inside the website.
As I explained, "name which you wants the .html file to be stored with" here means the name of the physical file which is getting saved on the server.
Most users leave the file name same as Page name. If you have it different from page name then this will be the workflow :
Page Name : About
File Name : test
domain : www.mysite.com
Now if you are using a Menu Widget, it will list "About" in the Menu. And when end user will click on "About" then it will call the file named "test.html" from the server location (where all the files of your website are stored).
And it will open a page with address "www.mysite.com/test.html"
Hope I am able to explain the concept of File Name here. Please let us know if you have further queries on this.
Regards,
Sachin

Photoshop CS3 crashes when meta-data is edited

We are using Photoshop CS3 on our G5 Mac running Leopard. When we open any JPG or EPS file and attempt to edit the meta data it crashes Photoshop completely (before we can even attempt to save the file). It does not matter which meta data field we are editing it happens to all of them. Not sure what has changed on the system as we have not done any updates recently. Thought it might be a corrupt preference file but not sure which one to delete? Any help will be greatly appreciated!
Sincerely,
Courtney
Version:1.0 StartHTML:0000000167 EndHTML:0000046049 StartFragment:0000000451 EndFragment:0000046033
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport version="1.1" crVersion="2.5.0.02272007" applicationName="Photoshop" applicationVersion="10.0" build="10.0 (10.0x20070321 [20070321.m.1480 2007/03/21:16:39:00 cutoff; m branch]), ©1990-2007 Adobe Systems Incorporated">
<time year="2012" month="6" day="13" hour="12" minute="38" second="55" />
<user guid="F048B041-9AD8-4F8C-8952-F1317D9FCF9F" />
<system platform="macintosh" osversion="10.5.8" applicationlanguage="en" userlanguage="en" oslanguage="en_GB" ram="3072MB" machine="i386" model="MacPro1,1" cpuCount="4" cpuFreq="2660MHz" busFreq="1332MHz" />
<crash exception="Unmapped Memory Exception" instruction="607823e4">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x24dc5ff2" symbolname="unknown"/>
<stackStatement index="1" address="0x90bd857b" symbolname="__Z30SendEventToEventTargetInternalP14OpaqueEventRefP20Op aqueEventTargetRefP14HandlerCallRec"/>
<stackStatement index="2" address="0x90bf4ecc" symbolname="_SendEventToEventTarget"/>
<stackStatement index="3" address="0x90c070a8" symbolname="__Z29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCa llRefP14OpaqueEventRefPv"/>
<stackStatement index="4" address="0x90bd94f6" symbolname="__Z23DispatchEventToHandlersP14EventTargetRecP14OpaqueEve ntRefP14HandlerCallRec"/>
<stackStatement index="5" address="0x90bd857b" symbolname="__Z30SendEventToEventTargetInternalP14OpaqueEventRefP20Op aqueEventTargetRefP14HandlerCallRec"/>
<stackStatement index="6" address="0x90bf4ecc" symbolname="_SendEventToEventTarget"/>
<stackStatement index="7" address="0x90c61a6c" symbolname="_ToolboxEventDispatcher"/>
<stackStatement index="8" address="0x90cb4b28" symbolname="_GetOrPeekEvent"/>
<stackStatement index="9" address="0x90cb47f2" symbolname="_GetNextEventMatchingMask"/>
<stackStatement index="10" address="0x90cb460e" symbolname="_WNEInternal"/>
<stackStatement index="11" address="0x90cb456d" symbolname="_WaitNextEvent"/>
<stackStatement index="12" address="0x90cb32a9" symbolname="_ModalDialog"/>
<stackStatement index="13" address="0x90ce98a2" symbolname="_RunStandardAlert"/>
<stackStatement index="14" address="0x00077e9e" symbolname="unknown"/>
<stackStatement index="15" address="0x000781cc" symbolname="unknown"/>
<stackStatement index="16" address="0x000d6589" symbolname="unknown"/>
<stackStatement index="17" address="0x000d6975" symbolname="unknown"/>
<stackStatement index="18" address="0x0007a0df" symbolname="unknown"/>
<stackStatement index="19" address="0x00060129" symbolname="unknown"/>
<stackStatement index="20" address="0x000601bd" symbolname="unknown"/>
<stackStatement index="21" address="0x000602d0" symbolname="unknown"/>
<stackStatement index="22" address="0x0021998e" symbolname="unknown"/>
<stackStatement index="23" address="0x002199e9" symbolname="unknown"/>
<stackStatement index="24" address="0x00002fd2" symbolname="unknown"/>
<stackStatement index="25" address="0x00002ef9" symbolname="unknown"/>
<stackStatement index="26" address="0x00000002" symbolname="unknown"/>
</thread>
</backtrace>
<registerSet>
<register name="CS" value="0x00000017"/>
<register name="DS" value="0x0000001f"/>
<register name="SS" value="0x0000001f"/>
<register name="ES" value="0x0000001f"/>
<register name="FS" value="0000000000"/>
<register name="GS" value="0x00000037"/>
<register name="EFLAGS" value="0x00010286"/>
<register name="EIP" value="0x24dc5ff2"/>
<register name="EAX" value="0x24348904"/>
<register name="EBX" value="0x0242fc6a"/>
<register name="ECX" value="0x00000023"/>
<register name="EDX" value="0x02d0a0e9"/>
<register name="ESI" value="0x29349900"/>
<register name="EDI" value="0000000000"/>
<register name="EBP" value="0xbfffcfd8"/>
<register name="ESP" value="0xbfffcf6c"/>
</registerSet>
<binaryImageSet>
<binaryImage start="0x00001000" end="0x016e0fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/Adobe Photoshop CS3"/>
<binaryImage start="0x01b9a000" end="0x01e1afff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeAGM.framework/Versions/A/Ad obeAGM"/>
<binaryImage start="0x01ec4000" end="0x01fc4fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/Ad obeACE"/>
<binaryImage start="0x01fe3000" end="0x02004fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeBIBUtils.framework/Versions /A/AdobeBIBUtils"/>
<binaryImage start="0x02011000" end="0x0202afff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeBIB.framework/Versions/A/Ad obeBIB"/>
<binaryImage start="0x02034000" end="0x02298fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeCoolType.framework/Versions /A/AdobeCoolType"/>
<binaryImage start="0x02314000" end="0x02337fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeAXE8SharedExpat.framework/V ersions/A/AdobeAXE8SharedExpat"/>
<binaryImage start="0x02349000" end="0x0239efff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeXMP.framework/Versions/A/Ad obeXMP"/>
<binaryImage start="0x023ac000" end="0x023c7fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobePDFSettings.framework/Versi ons/A/AdobePDFSettings"/>
<binaryImage start="0x023e0000" end="0x02496fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/FileInfo.framework/Versions/A/Fi leInfo"/>
<binaryImage start="0x024c4000" end="0x024c9fff" type="__TEXT" path="/System/Library/Frameworks/TWAIN.framework/Versions/A/TWAIN"/>
<binaryImage start="0x024d2000" end="0x0263dfff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeOwl.framework/Versions/A/Ad obeOwl"/>
<binaryImage start="0x02696000" end="0x0269cfff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeCrashReporter.framework/Ver sions/A/AdobeCrashReporter"/>
<binaryImage start="0x026a3000" end="0x026bffff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/LogTransport.framework/Versions/ A/LogTransport"/>
<binaryImage start="0x026ca000" end="0x02a1ffff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeLinguistic.framework/Versio ns/3/AdobeLinguistic"/>
<binaryImage start="0x02bb8000" end="0x02bfffff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/adobe_caps.framework/Versions/A/ adobe_caps"/>
<binaryImage start="0x02c0f000" end="0x02c4efff" type="__TEXT" path="/System/Library/PrivateFrameworks/vmutils.framework/Versions/A/ vmutils"/>
<binaryImage start="0x02f00000" end="0x02f01fff" type="__TEXT" path="/System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings"/>
<binaryImage start="0x06799000" end="0x067a7fff" type="__TEXT" path="/System/Library/CoreServices/Encodings/libSimplifiedChineseConv erter.dylib"/>
<binaryImage start="0x067ac000" end="0x067befff" type="__TEXT" path="/System/Library/CoreServices/Encodings/libTraditionalChineseCon verter.dylib"/>
<binaryImage start="0x067c2000" end="0x067c3fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ATS.framework/Versions/A/Resources/ATSHI.dylib"/>
<binaryImage start="0x0687f000" end="0x06889fff" type="__TEXT" path="/System/Library/PrivateFrameworks/URLMount.framework/URLMount"/ >
<binaryImage start="0x1824b000" end="0x18251fff" type="__TEXT" path="/System/Library/Filesystems/URLMount/afp.URLMounter/Contents/Ma cOS/afp"/>
<binaryImage start="0x182e7000" end="0x182f1fff" type="__TEXT" path="/System/Library/Frameworks/AppleTalk.framework/Versions/A/Apple Talk"/>
<binaryImage start="0x183e1000" end="0x18420fff" type="__TEXT" path="/System/Library/Frameworks/AppleShareClientCore.framework/Versi ons/A/AppleShareClientCore"/>
<binaryImage start="0x1a3ec000" end="0x1a3f7fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Plug-Ins/Extensions/Enable Async IO/Enable Async IO.plugin/Contents/MacOS/Enable Async IO"/>
<binaryImage start="0x1a3fc000" end="0x1a3fcfff" type="__TEXT" path="/usr/lib/libmx.A.dylib"/>
<binaryImage start="0x1a500000" end="0x1a50dfff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Plug-Ins/Extensions/FastCore.plugin/Contents/MacOS/FastCore"/>
<binaryImage start="0x1a584000" end="0x1a5e9fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Plug-Ins/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore"/>
<binaryImage start="0x1a687000" end="0x1a6d3fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Plug-Ins/Extensions/MultiProcessor Support.plugin/Contents/MacOS/MultiProcessor Support"/>
<binaryImage start="0x1a6da000" end="0x1a82cfff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Required/AdobeADM.bundle/Contents/MacOS/AdobeADM"/>
<binaryImage start="0x1b69d000" end="0x1b69ffff" type="__TEXT" path="/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types"/>
<binaryImage start="0x1b6a3000" end="0x1b6a4fff" type="__TEXT" path="/Library/ScriptingAdditions/QXPScriptingAdditions.osax/Contents /MacOS/QXPScriptingAdditions"/>
<binaryImage start="0x1d000000" end="0x1d2bcfff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Required/ScriptingSupport.plugin/Contents/MacOS/Scri ptingSupport"/>
<binaryImage start="0x1d5e5000" end="0x1da2dfff" type="__TEXT" path="/Library/ScriptingAdditions/XSLT Tools.osax/Contents/MacOS/XSLT Tools"/>
<binaryImage start="0x1dc00000" end="0x1de08fff" type="__TEXT" path="/System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/Ra wCamera"/>
<binaryImage start="0x1e5f0000" end="0x1ece1fff" type="__TEXT" path="/Library/Application Support/Adobe/Plug-Ins/CS3/File Formats/Camera Raw.plugin/Contents/MacOS/Camera Raw"/>
<binaryImage start="0x1f105000" end="0x1f539fff" type="__TEXT" path="/Library/Application Support/Adobe/Adobe Version Cue CS3/Client/3.0.0/VersionCue.framework/VersionCue"/>
<binaryImage start="0x1f953000" end="0x1f9e5fff" type="__TEXT" path=""/>
<binaryImage start="0x23593000" end="0x23598fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXCore Image.A.dylib"/>
<binaryImage start="0x23988000" end="0x23b0dfff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Resources/GLEngine. bundle/GLEngine"/>
<binaryImage start="0x23b3b000" end="0x23cc2fff" type="__TEXT" path="/System/Library/Extensions/GeForceFXGLDriver.bundle/Contents/Ma cOS/GeForceFXGLDriver"/>
<binaryImage start="0x23cec000" end="0x23d08fff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Versions/A/Resource s/GLRendererFloat.bundle/GLRendererFloat"/>
<binaryImage start="0x252e1000" end="0x25316fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_epic.framework/adobe_epic"/>
<binaryImage start="0x25336000" end="0x25342fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_eula.framework/adobe_eula"/>
<binaryImage start="0x25354000" end="0x25362fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_personalization.framework/adobe_per sonalization"/>
<binaryImage start="0x2536b000" end="0x25378fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/asneu.framework/asneu"/>
<binaryImage start="0x25399000" end="0x253a9fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_regist ration"/>
<binaryImage start="0x25538000" end="0x259b0fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/AdobeLM_libFNP.dylib"/>
<binaryImage start="0x25ae8000" end="0x25b40fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/AdobeUpdater.framework/AdobeUpdater"/>
<binaryImage start="0x40000000" end="0x400a6fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/AdobeJP2K.framework/Versions/A/A dobeJP2K"/>
<binaryImage start="0x90009000" end="0x90025fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib"/>
<binaryImage start="0x90026000" end="0x900a0fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/PrintCore.framework/Versions/A/PrintCore"/>
<binaryImage start="0x900a1000" end="0x900a1fff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Acce lerate"/>
<binaryImage start="0x900a7000" end="0x900a7fff" type="__TEXT" path="/System/Library/Frameworks/vecLib.framework/Versions/A/vecLib"/ >
<binaryImage start="0x900a8000" end="0x900dffff" type="__TEXT" path="/System/Library/Frameworks/SystemConfiguration.framework/Versio ns/A/SystemConfiguration"/>
<binaryImage start="0x900e0000" end="0x900f0fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis"/ >
<binaryImage start="0x90105000" end="0x90129fff" type="__TEXT" path="/usr/lib/libxslt.1.dylib"/>
<binaryImage start="0x9012a000" end="0x9012ffff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/CommonPanels.framework/Versions/A/CommonPanels"/>
<binaryImage start="0x90130000" end="0x90328fff" type="__TEXT" path="/System/Library/Frameworks/JavaScriptCore.framework/Versions/A/ JavaScriptCore"/>
<binaryImage start="0x90329000" end="0x90329fff" type="__TEXT" path="/System/Library/PrivateFrameworks/InstallServer.framework/Versi ons/A/InstallServer"/>
<binaryImage start="0x904b8000" end="0x90545fff" type="__TEXT" path="/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit"/>
<binaryImage start="0x90546000" end="0x90565fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib"/ >
<binaryImage start="0x90583000" end="0x9058ffff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Versions/A/Librarie s/libGL.dylib"/>
<binaryImage start="0x90590000" end="0x90623fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ATS.framework/Versions/A/ATS"/>
<binaryImage start="0x90624000" end="0x9070cfff" type="__TEXT" path="/System/Library/Frameworks/CoreData.framework/Versions/A/CoreDa ta"/>
<binaryImage start="0x9070d000" end="0x90766fff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Versions/A/Librarie s/libGLU.dylib"/>
<binaryImage start="0x90767000" end="0x90767fff" type="__TEXT" path="/System/Library/Frameworks/AudioUnit.framework/Versions/A/Audio Unit"/>
<binaryImage start="0x90768000" end="0x907e5fff" type="__TEXT" path="/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreA udio"/>
<binaryImage start="0x908d5000" end="0x908d5fff" type="__TEXT" path="/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa"/>
<binaryImage start="0x90929000" end="0x90958fff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/AE.framework/Versions/A/AE"/>
<binaryImage start="0x90959000" end="0x90960fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A .dylib"/>
<binaryImage start="0x90961000" end="0x909befff" type="__TEXT" path="/usr/lib/libstdc++.6.dylib"/>
<binaryImage start="0x909bf000" end="0x90a1bfff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/HTMLRendering.framework/Versions/A/HTMLRendering"/>
<binaryImage start="0x90b67000" end="0x90ba1fff" type="__TEXT" path="/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/C oreUI"/>
<binaryImage start="0x90ba5000" end="0x90bb3fff" type="__TEXT" path="/usr/lib/libz.1.dylib"/>
<binaryImage start="0x90bd1000" end="0x90ed9fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/HIToolbox.framework/Versions/A/HIToolbox"/>
<binaryImage start="0x90f41000" end="0x90f45fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib"/>
<binaryImage start="0x90f46000" end="0x90f5efff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/OpenScripting.framework/Versions/A/OpenScripting"/>
<binaryImage start="0x90f5f000" end="0x91130fff" type="__TEXT" path="/System/Library/Frameworks/Security.framework/Versions/A/Securi ty"/>
<binaryImage start="0x911cb000" end="0x911cdfff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dyl ib"/>
<binaryImage start="0x911ce000" end="0x91261fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/Ink.framework/Versions/A/Ink"/>
<binaryImage start="0x91262000" end="0x92162fff" type="__TEXT" path="/System/Library/QuickTime/QuickTimeComponents.component/Content s/MacOS/QuickTimeComponents"/>
<binaryImage start="0x921b2000" end="0x921b8fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/Print.framework/Versions/A/Print"/>
<binaryImage start="0x921eb000" end="0x92516fff" type="__TEXT" path="/System/Library/Frameworks/QuickTime.framework/Versions/A/Quick Time"/>
<binaryImage start="0x92517000" end="0x92524fff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL"/ >
<binaryImage start="0x92526000" end="0x92526fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon"/ >
<binaryImage start="0x92527000" end="0x92568fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.d ylib"/>
<binaryImage start="0x92569000" end="0x92630fff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Fram eworks/vImage.framework/Versions/A/vImage"/>
<binaryImage start="0x9263b000" end="0x92643fff" type="__TEXT" path="/System/Library/Frameworks/DiskArbitration.framework/Versions/A /DiskArbitration"/>
<binaryImage start="0x92644000" end="0x926d1fff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/LaunchServices.framework/Versions/A/LaunchServices"/>
<binaryImage start="0x926d2000" end="0x927d9fff" type="__TEXT" path="/System/Library/Frameworks/WebKit.framework/Versions/A/WebKit"/ >
<binaryImage start="0x927da000" end="0x9290dfff" type="__TEXT" path="/System/Library/Frameworks/CoreFoundation.framework/Versions/A/ CoreFoundation"/>
<binaryImage start="0x9290e000" end="0x92be8fff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/CarbonCore.framework/Versions/A/CarbonCore"/>
<binaryImage start="0x92be9000" end="0x92cc9fff" type="__TEXT" path="/usr/lib/libobjc.A.dylib"/>
<binaryImage start="0x92cca000" end="0x92ccafff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Fram eworks/vecLib.framework/Versions/A/vecLib"/>
<binaryImage start="0x92f34000" end="0x93a2dfff" type="__TEXT" path="/System/Library/Frameworks/WebKit.framework/Versions/A/Framewor ks/WebCore.framework/Versions/A/WebCore"/>
<binaryImage start="0x93a2e000" end="0x93a59fff" type="__TEXT" path="/usr/lib/libauto.dylib"/>
<binaryImage start="0x93a5a000" end="0x93a61fff" type="__TEXT" path="/usr/lib/libgcc_s.1.dylib"/>
<binaryImage start="0x93aa0000" end="0x93aabfff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A .dylib"/>
<binaryImage start="0x93afe000" end="0x93b05fff" type="__TEXT" path="/System/Library/Frameworks/AGL.framework/Versions/A/AGL"/>
<binaryImage start="0x93b06000" end="0x93fd7fff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Versions/A/Librarie s/libGLProgrammability.dylib"/>
<binaryImage start="0x93fd8000" end="0x94111fff" type="__TEXT" path="/usr/lib/libicucore.A.dylib"/>
<binaryImage start="0x94112000" end="0x9416cfff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/CoreText.framework/Versions/A/CoreText"/>
<binaryImage start="0x9416d000" end="0x941acfff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib"/ >
<binaryImage start="0x941bd000" end="0x94244fff" type="__TEXT" path="/usr/lib/libsqlite3.0.dylib"/>
<binaryImage start="0x94245000" end="0x942c2fff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Fram eworks/vecLib.framework/Versions/A/libvMisc.dylib"/>
<binaryImage start="0x942c3000" end="0x942c7fff" type="__TEXT" path="/usr/lib/system/libmathCommon.A.dylib"/>
<binaryImage start="0x94392000" end="0x94486fff" type="__TEXT" path="/usr/lib/libiconv.2.dylib"/>
<binaryImage start="0x94487000" end="0x94552fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ColorSync.framework/Versions/A/ColorSync"/>
<binaryImage start="0x94553000" end="0x94603fff" type="__TEXT" path="/System/Library/Frameworks/Kerberos.framework/Versions/A/Kerber os"/>
<binaryImage start="0x94604000" end="0x9460efff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/CarbonSound.framework/Versions/A/CarbonSound"/>
<binaryImage start="0x949ff000" end="0x94ab1fff" type="__TEXT" path="/usr/lib/libcrypto.0.9.7.dylib"/>
<binaryImage start="0x94c6f000" end="0x94cc0fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/HIServices.framework/Versions/A/HIServices"/>
<binaryImage start="0x94cc1000" end="0x94d0afff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/Metadata.framework/Versions/A/Metadata"/>
<binaryImage start="0x94d50000" end="0x94d7dfff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Fram eworks/vecLib.framework/Versions/A/libvDSP.dylib"/>
<binaryImage start="0x94da4000" end="0x94da4fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/ApplicationServices"/>
<binaryImage start="0x94da5000" end="0x95445fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics"/>
<binaryImage start="0x95446000" end="0x9546ffff" type="__TEXT" path="/usr/lib/libcups.2.dylib"/>
<binaryImage start="0x955f1000" end="0x95606fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/ImageCapture.framework/Versions/A/ImageCapture"/>
<binaryImage start="0x9571a000" end="0x9571dfff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/Help.framework/Versions/A/Help"/>
<binaryImage start="0x9571e000" end="0x957c5fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/QD.framework/Versions/A/QD"/>
<binaryImage start="0x958a9000" end="0x958bffff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/DictionaryServices.framework/Versions/A/DictionaryServices"/>
<binaryImage start="0x958c0000" end="0x95b3cfff" type="__TEXT" path="/System/Library/Frameworks/Foundation.framework/Versions/C/Foun dation"/>
<binaryImage start="0x95bc0000" end="0x95f7efff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Fram eworks/vecLib.framework/Versions/A/libLAPACK.dylib"/>
<binaryImage start="0x95f7f000" end="0x9603afff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/OSServices.framework/Versions/A/OSServices"/>
<binaryImage start="0x96047000" end="0x96063fff" type="__TEXT" path="/System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreV ideo"/>
<binaryImage start="0x96064000" end="0x961b6fff" type="__TEXT" path="/System/Library/Frameworks/AudioToolbox.framework/Versions/A/Au dioToolbox"/>
<binaryImage start="0x96203000" end="0x96282fff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/SearchKit.framework/Versions/A/SearchKit"/>
<binaryImage start="0x96283000" end="0x9630dfff" type="__TEXT" path="/System/Library/PrivateFrameworks/DesktopServicesPriv.framework /Versions/A/DesktopServicesPriv"/>
<binaryImage start="0x9630e000" end="0x963effff" type="__TEXT" path="/usr/lib/libxml2.2.dylib"/>
<binaryImage start="0x96403000" end="0x9640ffff" type="__TEXT" path="/System/Library/PrivateFrameworks/HelpData.framework/Versions/A /HelpData"/>
<binaryImage start="0x96410000" end="0x967adfff" type="__TEXT" path="/System/Library/Frameworks/QuartzCore.framework/Versions/A/Quar tzCore"/>
<binaryImage start="0x967ae000" end="0x967ccfff" type="__TEXT" path="/usr/lib/libresolv.9.dylib"/>
<binaryImage start="0x967cd000" end="0x96874fff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Fr ameworks/CFNetwork.framework/Versions/A/CFNetwork"/>
<binaryImage start="0x96875000" end="0x97073fff" type="__TEXT" path="/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit"/ >
<binaryImage start="0x97074000" end="0x97076fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/SecurityHI.framework/Versions/A/SecurityHI"/>
<binaryImage start="0x97077000" end="0x97487fff" type="__TEXT" path="/System/Library/Frameworks/Accelerate.framework/Versions/A/Fram eworks/vecLib.framework/Versions/A/libBLAS.dylib"/>
<binaryImage start="0x97488000" end="0x974c6fff" type="__TEXT" path="/System/Library/Frameworks/OpenGL.framework/Versions/A/Librarie s/libGLImage.dylib"/>
<binaryImage start="0x974c7000" end="0x974c8fff" type="__TEXT" path="/usr/lib/libffi.dylib"/>
<binaryImage start="0x97743000" end="0x978d2fff" type="__TEXT" path="/System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/ CoreAUC"/>
<binaryImage start="0x978d3000" end="0x978dcfff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/SpeechRecognition.framework/Versions/A/SpeechRecognition"/>
<binaryImage start="0x978dd000" end="0x978ddfff" type="__TEXT" path="/System/Library/Frameworks/CoreServices.framework/Versions/A/Co reServices"/>
<binaryImage start="0x978fc000" end="0x9790cfff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis"/>
<binaryImage start="0x97912000" end="0x9793afff" type="__TEXT" path="/System/Library/PrivateFrameworks/Shortcut.framework/Versions/A /Shortcut"/>
<binaryImage start="0x97a74000" end="0x97bdbfff" type="__TEXT" path="/usr/lib/libSystem.B.dylib"/>
<binaryImage start="0x97bdc000" end="0x97c00fff" type="__TEXT" path="/usr/lib/libssl.0.9.7.dylib"/>
<binaryImage start="0x97c3e000" end="0x97c80fff" type="__TEXT" path="/System/Library/Frameworks/Carbon.framework/Versions/A/Framewor ks/NavigationServices.framework/Versions/A/NavigationServices"/>
<binaryImage start="0x97cd0000" end="0x97cd7fff" type="__TEXT" path="/usr/lib/libbsm.dylib"/>
<binaryImage start="0x97d28000" end="0x97e70fff" type="__TEXT" path="/System/Library/Frameworks/ApplicationServices.framework/Versio ns/A/Frameworks/ImageIO.framework/Versions/A/ImageIO"/>
<binaryImage start="0xb0000000" end="0xb0004fff" type="__TEXT" path="/Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/../Frameworks/ahclient.framework/Versions/A/ah client"/>
<binaryImage start="0xba900000" end="0xba916fff" type="__TEXT" path="/System/Library/CoreServices/Encodings/libJapaneseConverter.dyl ib"/>
<binaryImage start="0xbab00000" end="0xbab21fff" type="__TEXT" path="/System/Library/CoreServices/Encodings/libKoreanConverter.dylib "/>
</binaryImageSet>
</crash>
Console Log Message:
Version:1.0 StartHTML:0000000167 EndHTML:0000002013 StartFragment:0000000451 EndFragment:0000001997
Process:         Adobe Photoshop CS3 [306]
Path:            /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/MacOS/Adobe Photoshop CS3
Identifier:      com.adobe.Photoshop
Version:         10.0 (10.0x20070321 [20070321.m.1480 2007/03/21:16:39:00 cutoff; m branch]) (10.0)
Code Type:       X86 (Native)
Parent Process: launchd [105]
Interval Since Last Report: 27167 sec
Crashes Since Last Report:           2
Per-App Interval Since Last Report: 22482 sec
Per-App Crashes Since Last Report:   2
Date/Time:       2012-06-13 12:38:57.741 +0100
OS Version:      Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: 934B74CE-A232-4279-83E3-64E67008480C
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

I can confirm that this is a user preference problem, as there is no problem on a newly created user account. However, deleting the 'obvious' preference files from ~/Library/Preferences (Adobe and Photoshop prefs and plists) has had no effect.
I have moved ALL preference files from ~/Library/Preferences, restarted and relaunched Photoshop. This has resolved the original Photoshop issue. I now have to reapply all of the other user preferences for all other applications/devices. (Resolving the original issue has probably created more work, but at least we can use Photoshop!)
It would be nice to hear if anyone has any idea which preference file may of caused the issue.
Thanks.

Which wrappers support meta data saving?

Similar Messages

Maybe you are looking for