Applying metadata when importing

I want to add metadata from my template to photos when I import them; however, the Metadata menu only appears on the AutoImport dialog.
Help references the "Import photos dialog box", but it does not appear on "Import photos from disk."
Is Help incorrect or am I missing something?
How can I add metadata during an import from disk?

You mean you're importing directly from an USB-attached camera?
If you import from a card reader, do the templates apply?

Similar Messages

  • Issue with Metadata when importing 30K images from Photoshop Elements 7

    I'm a new mac user and am moving ~30k images from my PC to my mac. I have photoshop elements 7 that I use on the pc and am moving everything over to Aperture. I maintain all of my organization on the PC using "key words". I made sure to move all of the metadata over to the Mac with the images. However, I would say approx 5,000-10,000 of the images have the wrong Metadata. For example, a key-word "Vacation" is showing up on an image that should say "Christmas". This is just an example and it's creating major issues with my smart albums. The wrong images are in the wrong albums. Help!?!?

    Hi Shellie
    Is anyone familiar with PSEDBTOOL? I've been told it will do a good job applying metadata to files inside PSE but I'm afraid to run it and have it screw up my current library.
    I'm not familiar with that tool. What I will say is that your caution is well founded. If you do try to run anything like that on the PC side, ensure first that you have a backup of any data that might be modified - and that you (a) know how to restore from the backup in case anything goes pear-shaped and (b) you've actually tested your backup (by doing a restore) and are confident with its integrity.
    One other thought has occurred to me since earlier. Let's try a different tool...
      – Locate one of your problematic master files - on the Mac side - as exported from PhotoShop Elephants.
      – Open it in Preview. (It lives in the Applications folder.)
      – Select +Tools > Show Inspector+ (if the Inspector is not already showing from an earlier session).
      – Click on the Inspector icon which resembles a simplified traditional magnifying glass.
    That displays the keywords in the file.
    How do they compare with your expectations (from PSE)? How do they compare with what's showing in Aperture?
    This won't solve the problem, but it might just shed some more light on the problem.
    Regards,
    Gary

  • How can I include metadata when importing libraries?

    I've exported my 100 GB of photos to an external hard drive. Now I would like to split my photos into five libraries and import them including their metadata (modifications and tags, mostly) to my new libraries. Is that possible?

    I actually copied the library with all its content to an external drive of 1 TB. My plan was next to delete all photos on my iMac and then copy photos by year into separate libraries. However, I was recommened to try software that allows me to organise several libraries.
    Thanks anyhow.

  • Error writing metadata when Importing Lr 2.7 catalog in Lr 3 final

    Hi,
    I imported (and sucessfully converted) my Lr 2.7 Catalog in Lr3 final but now, all my photos have  this little icon that says " Error writing metadata "
    Why?
    Thx!

    According to Martin Evening in his Lightroom 2 book p. 178, "If you see the icon shown in Figure 4.74 [the !], click to open the dialog box where you can either choose Import Setting from Disk if you think the external settings are right, or choose Overwrite Settings if you think the Lightroom catalog settings are the most up to date."
    If you did not edit these images in another program like Camera Raw some unknown event caused Lightroom to indicate that the files were edited in another program.  In this case you probably do not want to include this edit.  It will probably work out if you choose Overwrite Settings which will keep the settings that you have in the LR database, disregard the changes from outside LR, and remove the !.
    If you edited these images in another program and you want to keep those changes, choose Import Settings from Disk to bring the external settings into the LR database.
    If you want to write the LR settings to the DNG files go to Metadata > Save Metadata to File or (Ctrl-S).  I strongly recommend saving LR settings to the file.  Others disagree.  In the Catalog Settings under Metadata, check Automatically Write Changes to XMP, if you prefer this to be done automatically.
    Whatever you do, be sure to backup your LR database, at least two or three times, and be sure that all of you images are backed up.
    Follow the above procedures by doing a few files at a time, and check that you are getting what you want before doing them all.

  • Apply metadata to unlinked photos, then sync MD when files available

    I share my master catalog between a desktop and a laptop. The desktop has all the master files (on RAIDs, archived drives, etc.), so all I have access to when I use LR3 on my laptop are the previews of my files. While I know I obviously can't edit (develop) missing files, what I'd love to be able to do is annotate on my laptop, then when I copy the catalog over to the desktop, it will sync this metadata to the actual xmp sidecar files. As it stands now, one can only apply metadata when the linked files are attached.

    So, what the camera writes, the Exif metadata, is inside the photo file, or in another hidden file for each photo?
    It’s “inside” the file.
    How come then it happens that sometimes the date changes after you've written the pictures on a CD, and imported them from that later... shouldn't the metadata stay with the file? It happens mostly with early camera phone pictures...
    A photo can lose the metadata in imperfect copies, or - in the case of early camera phones - there may have been none at all. In which case iPhoto uses the File “Date Created” instead.
    I have a lot of pictures whose dates I really had to change because they were wrong - I just hope this work won't go down the drain further down the road... perhaps when importing into a new Mac, or when using a different program altogether...?
    In the case of moving to a new Mac:
    Simply move the Library to the new machine. That will get all the data, metadata, originals, edited versions and so on.
    In using a different application:
    1. If it understands the iPhoto Library (like Aperture, for instance) then you will have no issue
    2. If it doesn’t, then you export the Pics from iPhoto (File -> Export) and check the box at Title and Keywords. This will mean that your Titles, Keywords +and Descriptions+ (though not explicitly mentioned) will be written to the IPTC data.
    Regards
    TD

  • Problems applying metadata to images when importing from device

    When importing images from a device into lightroom 2 I have created and selected a metadata template in the information to apply section, but when importing the images to the lightroom library it does not apply the metadata to the images. Can anyone help?

    You mean you're importing directly from an USB-attached camera?
    If you import from a card reader, do the templates apply?

  • Bridge crashes when applying metadata

    I'm seeking guidance, but let me preface this post with some information:
    CS6 via Creative Cloud
    All applications up to date via Adobe Application Manager
    All Windows Updates applied including drivers.
    Currently running Bridge 5.0.2.4
    Computer is:
    Win 7 Pro (64 bit)
    Core i5
    12 Gb RAM
    NVIDIA GeForce 310
    I have used CS6 for months prior to this issue starting without incident.
    I have tried moving the data to different drives.
    I have checked/cleared/reset file permissions.
    I have run drive error checks.
    I have uninstalled/CC cleaner/reisntalled all Adobe products multiple times.
    I have run Bridge in 32-bit and 64-bit modes.
    I have tried to reset preferences and other "Ctrl" startup options.
    I have tried to reset preferences and other "Ctrl" startup options after selecing "Run As Administrator".
    I manually deleted the ".BridgeCache" and ".BridgeCacheT" files from the folder of photos.
    Prior to this crashing problem I had already sorted and begun to apply ratings to files (Reject and Start ratings) in this folder without incident.  I even applied metadata (Keywords) to a portion of the 1,321 photos in a folder without incident.  The problem started when I came back the next day and started up work again.  There had been no updates or restarts to the computer.  The only thing that I think updated was Adobe Acrobat, but I cannot be sure.  When I opened Bridge and began to apply Keywords to files the program simply locked up and immediately crashed.  The Windows dialog box did not have any information or options for a crash report.
    This is a normal workfolw that I utilize on a regular (weekly/monthly) basis and why the crashing is happening is beyond me.  I have attempted to troubleshoot many different ways.  Of particular note I when to a different folder of photos that had never been worked on before with Bridge and was able to apply the same workflow without incident.
    Here is an excerpt from the Windows Event Viewer:
    Faulting application name: Bridge.exe, version: 5.0.2.4, time stamp: 0x50d9a019
    Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x12d0
    Faulting application start time: 0x01ce461c31a0ba90
    Faulting application path: C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 60e3cf2b-b210-11e2-834c-f04da2db0ae0
    At this time I cannot difinitively confirm that the files themselves are causing the issue but I will attempt some additional troubleshooting.  At this point I'm not overly impatient because I've already lost the revenue opportunity for selling these photos to customers because the error first started several days ago (4/28/2013 09:31:35 PM was first crash).  However, at this point I am will not entertain the wasting of time by uninstalling all Adobe products, running CC cleaner, and re-installing the products I use.
    Does anyone have any suggestions for me to try for resolution or troubleshooting? 

    I'm wondering if it could be the SD card?  Mine was a cheap brand and I wonder if the invalid handler could be the issue.
    No experience with all of this, use a Mac, Canon and a CF card that I place in a Card reader and use import via Adobe Photodownloader.
    But here is my question, what do you do you with the SD card when your files are copied to the system?
    My workflow is to import the files (including convert to DNG and back up original Raw to second disk, renaming and copyright template)
    But when I have checked my files are OK on the system and I need the CF card for a new job I always put the card back in the camera and use the camera menu itself to format the card.
    I long ago stopped using the delete all function because this used to build up certain data files and that is not the case when you use format.
    I do so every time and while I have used a lot of CF cards (from 128 MB in 2001 to current 32 GB Sandisk Extreme Pro UDMA 7) The only problems I had was losing them.
    Never managed to break one down (not even in the washing machine…) and from about 2003 I always have used the format method for every time I needed to remove the files from the card.
    I don't know much about the difference between inferior manufactures and the superior brands, I find it hard to believe that this would cause your problem alone (If you did not format I would try that first).
    Having said that I would never choose to use other then top quality cards like Lexar and Sandisk and also the fastest or the nearly fastest.
    If you have a cheap compact camera (but then you probably would not visit this forum…) I can image (but do not approve) you include a cheap SD card also. But spending up to 1000 dollar or much more for a nice dSLR and save money on a cheap card instead of using a trustful medium to write your precious files on is not the best workflow.
    CF cards and SD card are very cheap nowadays.
    To compare, the 128 MB in 2001 was about 600 dollar, the super fast and reliable Sandisk Extreme Pro 32 GB was around 200 dollars.
    You can do the math yourself but on my calculator this means three times as cheap while 256 times more space…

  • Error when import  metadata form Oracle Olap (aw) to rpd

    Hi all,
    When import Oracle OLAP analytic workspace to rpd user bi Admin tool, i get error:
    [nQSError: 77031] Error occurs while calling remote service AWImportService11G. Details: Error getting AW version -- IO error: The network Adapter could not establish the connection
    I think that BI server hot support version of analytics workspace.
    BI server: BIEE 11.1.1.5
    Oracle DB: 11g
    AWM: awm 112020B Standalone
    So, can you help me fix it or tell me about suport AW version of BI server.
    Thanks so much.

    user12232768 wrote:
    But this document just help me fix problem with connection string, in this case after that, i get problem with version of AW.So you get the same error again? Or is this a new error? Also, how are you importing into the repository? Are you using the OBIEE Plug-in for Analytic Workspace Manager?
    I also found a similar query in the forum, see if this helps:
    Re: Import OLAP Metadata in OBIEE 11.1.1.5 failing
    Edited by: JaiG on Nov 8, 2012 12:56 PM

  • Same shooting, multiple lenses, how to apply the appropriate lens correction when importing ?

    Hello everyone,
    How do you handle this:
    For each camera, i have a default preset i'm choosing manualy and applying when importing my raw files into lightroom.
    I'd like to also add some default lens correction to those presets.
    The problem is that multiples lenses (meaning different corrections) may be applied.
    How to apply the correct lens correction for each file, in the batch import ?
    Thanks for your ideas ...
    Aymeric

    Update your existing develop presets so that the Lens Corrections are checked (see attached screen shot). Select the develop preset in Import dialog. Lr will automatically apply the appropriate default lens profile to each individual image during import.

  • Missing Metadata Presets when importing sample library following book

    ISSUE: NO METADATA PRESETS available during import. (Aperture 3)
    DESCRIPTION:
    I have just installed Aperture 3. I am following the Aperture 3 book. When importing the sample Wyoming pictures into the Sample Library , I am directed to choose "basic info" as my metadata preset. I am not able to select "basic info" as a metadata preset. The drop down arrow only yields "none" and "edit". Edit is all grayed out.
    I then tried it in the Main/real Aperture 3 library. I tried to import a few pictures from a a hard drive. Same issue. NO METADATA PRESETS AVAILABLE FOR IMPORTING INTO APERTURE 3.
    Thank youl

    Here is the answer for anyone who may hae same problem:
    Delete the following files from Application (Aperture) /Support :
    1: import Presets.plist
    2:MetadataSets.plist
    3:Metadata Presets.plist.
    Removing these has restored the basic metadata presets.
    Hope it helps.
    Thanks

  • File names in Assignments Panel change when applying metadata

    I have just discovered that when you apply metadata through the "User Content Info" window, whatever title you place in the "Document Title" field changes the name that appears in the Assignments panel. The problem with this is that we have asked our users to apply metadata using this window and to put the Product Title in the Document Title field. I had no idea that this would affect the Assignments panel. Yikes!

    Brian
    Yes that would be a pain if you had to do it. The good news is you don't. There a plenty of ways to get to the pics:
    1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
    2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
    3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
    To upload to MySpace or any site that does not have an iPhoto Export Plug-in the recommended way is to Select the Pic in the iPhoto Window and go File -> Export and export the pic to the desktop, then upload from there. After the upload you can trash the pic on the desktop. It's only a copy and your original is safe in iPhoto.
    This is also true for emailing with Web-based services. If you're using Gmail you can use THIS
    If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
    If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
    Or, if you want to access the files with iPhoto not running, then create a Media Browser using Automator (takes about 10 seconds) or use THIS
    Also, for 10.5 users: If you use the extended Open or Attach dialogue (with Column View) you can scroll to the bottom of the Shortcuts and find the Media browser there. Select any pic you want from there.
    Regards
    TD

  • Does AAC Encoder apply when importing or when transfering to iPod?

    I have iTunes set to import using AAC Encoder. CD songs in the iTunes libary on my PC are m4a fles, while downloaded mp3 files remain as mp3 files.
    Are the mp3 songs converted to AAC when transferred onto my iPod? Or does the AAC Encoder only apply when importing into the libary on my PC, in which case why do mp3 files stay as mp3 files?
    Reason for asking is concern that converting from mp3 to AAC reduces sound quality.
    iPod   Other OS   60GB Video

    Graham,
    The import setting you select in your iTunes Preferences applies specifically to songs you add directly from a CD.
    It does not affect songs that are added to your library that are already mp3's (or any other format for that matter).
    Have a look at: http://docs.info.apple.com/article.html?artnum=301509
    When you synch the files to your iPod they will remain whatever they are in iTunes - nothing changes in the transfer.
    iTunes can convert files (see http://docs.info.apple.com/article.html?artnum=93123 if you're interested in details on that) but you are right, there is a loss of audio fidelity.

  • Bridge CS6 crashes when I apply metadata

    Similar problem to this: http://forums.adobe.com/message/5025995
    The problem started suddenly last week. If I try to apply metadata or keywords to an image, Bridge closes. Sometimes I can apply one or two keywords before this happens, but not many and it always closes after applying more than a few keywords. Before this started, I had no problems with Bridge CS6.
    Have tried updating graphics card drivers, resetting preferences, rebooting, changing the locatioon  of the photos, with no luck.
    Win7-64 bit, 3GB RAM
    Version=1
    EventType=APPCRASH
    EventTime=130075875636681628
    ReportType=2
    Consent=1
    UploadTime=130075875638241658
    ReportIdentifier=164771e9-8b45-11e2-84ee-002186f773e8
    IntegratorReportIdentifier=164771e8-8b45-11e2-84ee-002186f773e8
    Response.BucketId=91441965
    Response.BucketTable=4
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=Bridge.exe
    Sig[1].Name=Application Version
    Sig[1].Value=5.0.2.4
    Sig[2].Name=Application Timestamp
    Sig[2].Value=50d9a019
    Sig[3].Name=Fault Module Name
    Sig[3].Value=StackHash_616b
    Sig[4].Name=Fault Module Version
    Sig[4].Value=6.1.7601.17725
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4ec4aa8e
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000374
    Sig[7].Name=Exception Offset
    Sig[7].Value=00000000000c40f2
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.4
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=616b
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=616b82bd806673b43f5b3a110bcea586
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=dd62
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=dd6240926115030fc2df7dbe321d314b
    UI[2]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
    UI[3]=Adobe Bridge CS6 has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[5]=C:\Windows\system32\GDI32.dll
    LoadedModule[6]=C:\Windows\system32\USER32.dll
    LoadedModule[7]=C:\Windows\system32\LPK.dll
    LoadedModule[8]=C:\Windows\system32\USP10.dll
    LoadedModule[9]=C:\Windows\system32\msvcrt.dll
    LoadedModule[10]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.76 01.17825_none_2b253c8271ec7765\gdiplus.dll
    LoadedModule[11]=C:\Windows\system32\ole32.dll
    LoadedModule[12]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[13]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\icuuc40.dll
    LoadedModule[14]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[15]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[16]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\icudt40.dll
    LoadedModule[17]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\MSVCR100.dll
    LoadedModule[18]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\icuin40.dll
    LoadedModule[19]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Symlib.dll
    LoadedModule[20]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\amtlib.dll
    LoadedModule[21]=C:\Windows\system32\WINHTTP.dll
    LoadedModule[22]=C:\Windows\system32\webio.dll
    LoadedModule[23]=C:\Windows\system32\SETUPAPI.dll
    LoadedModule[24]=C:\Windows\system32\CFGMGR32.dll
    LoadedModule[25]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[26]=C:\Windows\system32\DEVOBJ.dll
    LoadedModule[27]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[28]=C:\Windows\system32\NSI.dll
    LoadedModule[29]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[30]=C:\Windows\system32\SHELL32.dll
    LoadedModule[31]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\BIB.dll
    LoadedModule[32]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\ExtendScript.dll
    LoadedModule[33]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\ScCore.dll
    LoadedModule[34]=C:\Windows\system32\WS2_32.dll
    LoadedModule[35]=C:\Windows\system32\d3d9.dll
    LoadedModule[36]=C:\Windows\system32\VERSION.dll
    LoadedModule[37]=C:\Windows\system32\d3d8thk.dll
    LoadedModule[38]=C:\Windows\system32\dwmapi.dll
    LoadedModule[39]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\d3dx9_43.dll
    LoadedModule[40]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AXEDOMCore.dll
    LoadedModule[41]=C:\Windows\system32\UxTheme.dll
    LoadedModule[42]=C:\Windows\system32\MSIMG32.dll
    LoadedModule[43]=C:\Windows\system32\WINMM.dll
    LoadedModule[44]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobeXMP.dll
    LoadedModule[45]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\MSVCP100.dll
    LoadedModule[46]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobeXMPFiles.dll
    LoadedModule[47]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\ACE.dll
    LoadedModule[48]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\BIBUtils.dll
    LoadedModule[49]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AXE8SharedExpat.dll
    LoadedModule[50]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\CoolType.dll
    LoadedModule[51]=C:\Windows\system32\IMM32.DLL
    LoadedModule[52]=C:\Windows\system32\MSCTF.dll
    LoadedModule[53]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[54]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
    LoadedModule[55]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\adobe_caps.dll
    LoadedModule[56]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[57]=C:\Windows\system32\propsys.dll
    LoadedModule[58]=C:\Windows\system32\ntmarta.dll
    LoadedModule[59]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[60]=C:\Windows\system32\profapi.dll
    LoadedModule[61]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AGM.dll
    LoadedModule[62]=C:\Windows\System32\msxml6.dll
    LoadedModule[63]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Required\PhotoshopAdapter.apl
    LoadedModule[64]=C:\Program Files\Common Files\Adobe\Plug-Ins\CS6\File Formats\Camera Raw.8bi
    LoadedModule[65]=C:\Windows\system32\PSAPI.DLL
    LoadedModule[66]=C:\Windows\system32\OPENGL32.dll
    LoadedModule[67]=C:\Windows\system32\GLU32.dll
    LoadedModule[68]=C:\Windows\system32\DDRAW.dll
    LoadedModule[69]=C:\Windows\system32\DCIMAN32.dll
    LoadedModule[70]=C:\Windows\system32\mscms.dll
    LoadedModule[71]=C:\Windows\system32\USERENV.dll
    LoadedModule[72]=C:\Windows\system32\icm32.dll
    LoadedModule[73]=C:\Windows\system32\WindowsCodecs.dll
    LoadedModule[74]=C:\Windows\system32\apphelp.dll
    LoadedModule[75]=C:\PROGRA~1\OpenAFS\Client\Program\AFS_SH~1.DLL
    LoadedModule[76]=C:\Program Files\OpenAFS\Common\afsrpc.dll
    LoadedModule[77]=C:\Program Files\OpenAFS\Common\afspthread.dll
    LoadedModule[78]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_88e41e092fab0294\MSVCR80.dll
    LoadedModule[79]=C:\Program Files\OpenAFS\Common\afshcrypto.dll
    LoadedModule[80]=C:\Program Files\OpenAFS\Common\afsroken.dll
    LoadedModule[81]=C:\Program Files\OpenAFS\Common\afsauthent.dll
    LoadedModule[82]=C:\Program Files\OpenAFS\Common\afsprocmgmt.dll
    LoadedModule[83]=C:\Windows\system32\NETAPI32.dll
    LoadedModule[84]=C:\Windows\system32\netutils.dll
    LoadedModule[85]=C:\Windows\system32\srvcli.dll
    LoadedModule[86]=C:\Windows\system32\wkscli.dll
    LoadedModule[87]=C:\Program Files\OpenAFS\Common\libafsconf.dll
    LoadedModule[88]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[89]=C:\Windows\system32\MPR.dll
    LoadedModule[90]=C:\Windows\system32\Secur32.dll
    LoadedModule[91]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[92]=C:\Windows\WinSxS\amd64_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_8448b2bd328df189\MFC80U.DLL
    LoadedModule[93]=C:\Windows\WinSxS\amd64_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727. 6195_none_bc20f59b0bdd1acd\MFC80ENU.DLL
    LoadedModule[94]=C:\PROGRA~1\OpenAFS\Client\Program\afs_shl_ext_1033.dll
    LoadedModule[95]=C:\Users\rmunde.AD\AppData\Roaming\Dropbox\bin\DropboxExt64.17.dll
    LoadedModule[96]=C:\Windows\system32\dbghelp.dll
    LoadedModule[97]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCP90.dll
    LoadedModule[98]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCR90.dll
    LoadedModule[99]=C:\Windows\system32\EhStorShell.dll
    LoadedModule[100]=C:\Windows\System32\cscui.dll
    LoadedModule[101]=C:\Windows\System32\CSCDLL.dll
    LoadedModule[102]=C:\Windows\system32\CSCAPI.dll
    LoadedModule[103]=C:\Program Files (x86)\DisplayFusion\Hooks\AppHookx64_A8B98FDD-7B80-43AA-B9C7-82B660068E89.dll
    LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[105]=C:\Windows\system32\rsaenh.dll
    LoadedModule[106]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[107]=C:\Windows\system32\mssprxy.dll
    LoadedModule[108]=C:\Windows\system32\SnacNp.dll
    LoadedModule[109]=C:\Windows\System32\drprov.dll
    LoadedModule[110]=C:\Windows\System32\WINSTA.dll
    LoadedModule[111]=C:\Windows\system32\AFSRDFSProvider.dll
    LoadedModule[112]=C:\Windows\System32\ntlanman.dll
    LoadedModule[113]=C:\Windows\System32\davclnt.dll
    LoadedModule[114]=C:\Windows\System32\DAVHLPR.dll
    LoadedModule[115]=C:\Windows\system32\dlumd64.dll
    LoadedModule[116]=C:\Windows\system32\wtsapi32.dll
    LoadedModule[117]=C:\Windows\system32\nvd3dumx.dll
    LoadedModule[118]=C:\Windows\system32\powrprof.dll
    LoadedModule[119]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI64.dll
    LoadedModule[120]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\FileInfo.dll
    LoadedModule[121]=C:\Windows\system32\OLEACC.dll
    LoadedModule[122]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\adbeape.dll
    LoadedModule[123]=C:\Windows\system32\WINSPOOL.DRV
    LoadedModule[124]=C:\Windows\system32\COMDLG32.dll
    LoadedModule[125]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\WinFeatures.dll
    LoadedModule[126]=C:\Windows\system32\XmlLite.dll
    LoadedModule[127]=C:\Windows\system32\LINKINFO.dll
    LoadedModule[128]=C:\Windows\system32\SearchFolder.dll
    LoadedModule[129]=C:\Windows\System32\cscobj.dll
    LoadedModule[130]=C:\Windows\system32\tquery.dll
    LoadedModule[131]=C:\Windows\System32\StructuredQuery.dll
    LoadedModule[132]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\SwitchBoardClient.dll
    LoadedModule[133]=C:\Program Files\Common Files\Adobe\APE\3.3\adbeapecore.dll
    LoadedModule[134]=C:\Program Files\Common Files\Adobe\APE\3.3\adbeapeengine.dll
    LoadedModule[135]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[136]=C:\Windows\system32\MSASN1.dll
    LoadedModule[137]=C:\Windows\system32\WININET.dll
    LoadedModule[138]=C:\Windows\system32\Normaliz.dll
    LoadedModule[139]=C:\Windows\system32\iertutil.dll
    LoadedModule[140]=C:\Windows\system32\urlmon.dll
    LoadedModule[141]=C:\Windows\system32\msi.dll
    LoadedModule[142]=C:\Windows\system32\DSOUND.dll
    LoadedModule[143]=C:\Windows\system32\mlang.dll
    LoadedModule[144]=C:\Windows\system32\credssp.dll
    LoadedModule[145]=C:\Windows\system32\schannel.DLL
    LoadedModule[146]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobePSL.dll
    LoadedModule[147]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\tbb.dll
    LoadedModule[148]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\tbbmalloc.dll
    LoadedModule[149]=C:\Windows\system32\wbem\wbemprox.dll
    LoadedModule[150]=C:\Windows\system32\wbemcomn.dll
    LoadedModule[151]=C:\Windows\system32\wbem\wbemsvc.dll
    LoadedModule[152]=C:\Windows\system32\wbem\fastprox.dll
    LoadedModule[153]=C:\Windows\system32\NTDSAPI.dll
    LoadedModule[154]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\FastCore.8BX
    LoadedModule[155]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\MMXCore.8BX
    LoadedModule[156]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\libmmd.dll
    LoadedModule[157]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\MultiProcessor Support.8BX
    LoadedModule[158]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\PLUGIN.dll
    LoadedModule[159]=C:\Windows\system32\MMDevAPI.DLL
    LoadedModule[160]=C:\Windows\system32\wdmaud.drv
    LoadedModule[161]=C:\Windows\system32\ksuser.dll
    LoadedModule[162]=C:\Windows\system32\AVRT.dll
    LoadedModule[163]=C:\Windows\system32\AUDIOSES.DLL
    LoadedModule[164]=C:\Windows\system32\msacm32.drv
    LoadedModule[165]=C:\Windows\system32\MSACM32.dll
    LoadedModule[166]=C:\Windows\system32\midimap.dll
    LoadedModule[167]=C:\Windows\System32\shdocvw.dll
    LoadedModule[168]=C:\Windows\system32\slc.dll
    LoadedModule[169]=C:\Windows\System32\ieframe.dll
    LoadedModule[170]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobePIP.dll
    LoadedModule[171]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\LogSession.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Adobe Bridge CS6
    AppPath=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe

    Here is the report that includes the faulting module. Is this what you meant?
    Description:
    Faulting application name: Bridge.exe, version: 5.0.2.4, time stamp: 0x50d9a019
    Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x64c
    Faulting application start time: 0x01ce1f655f6c8caf
    Faulting application path: C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 130d23f2-8b59-11e2-84ee-002186f773e8

  • Adding metadata at import --why is this much easier to do in LR?

    Adding metadata at import time is a pain. The presets have helped a bit but Aperture still needs improvement. I have four areas of trouble:
    1. In order to fill out a metadata preset I have to create a new temporary image version or risk changing the metadata for an existing master, fill out the fields, save the preset, delete the temporary version. I can't create a new metadata preset at the moment of import I have to do the steps above in advance of importing.
    2. If i want to have a metadata view that has the 12 fields I use on import but only have 4 fields filled out in advance I can't do that without first selecting the preset then selecting the view with the blank fields.
    3. In the import panel the image Information block, Files Location/filename block and Time Adjustment block take up so much room that on my MBP-15 the metadata block is nearly off the bottom of the screen.
    4. Whatever metadata I use must apply to all images. There is no way to have different metadata for different images at the time of import. This requires me to open the project to add image specific metadata after import or run the import more than once for different images.
    If anyone has workflow solutions or workarounds for theses bottlenecks please let me know. Here is hoping that v2 will improve on these points.

    I guess I had
    a problem with the title of this question.
    Some men see things as they are
    and ask "Why?" I dream things that
    never were and ask, "Why not?"
    --Robert F. Kennedy
    Sorry if I gave offense. I wasn't trying to start a flame war about Aperture vs. LR or whatever-that's not enlightening. I expect that for many years to come Aperture will be my primary digital imaging workspace.
    I am still tinkering with Lightroom and will do so until my demo version expires in 25 more days. I think that Aperture is a dramatically better program than Lightroom. I think that over the next couple of years the gap will widen even further and the advantages of Apple's sound engineering decisions will really start to show up in v2 v3 and beyond.
    Still when I work in the current version of Lightroom I find myself processing images more quickly and spend less time fiddling around with the program's UI than while working in Aperture. I have noticed other posts commenting on the same thing.
    If there are other users who like me love Aperture but find their work going faster in Lightroom doesn't it make sense for us to have a discussion with each other to find out...why?
    The future belongs to those who prepare for it today. - - Malcolm X
    Pro Mac 2.66Ghz/8GB/250GB + 1TB RAID 0 wi SoftRAID in bays 2,3/X1900   Mac OS X (10.4.8)   MacBookPro 2.16Ghz/2GB/100GB 7200rpm

  • Develop settings when importing RAW + jpeg

    When importing NEF files from my D700 I apply the landscape sharpening pre-set and am happy with the results.  However on my Fuji X20 I import RAW+jpeg rather than just RAW, in this situation if I use the landscape sharpening pre-set sharpening is applied to the jpeg as well as the RAW resulting in the already sharpened in camera jpeg being grossly over sharpened.  If on the other hand I use none for the develop pr-set no sharpening or noise reduction is applied to the jpeg and a minimum amount applied to the RAW file, more or less what I want except I want the higher landscape sharpening applied to the RAW files.  Is there anyway to modify the built in pre-sets so that they only get applied to the RAW files when importing RAW+jpeg pairs?
    Dave Rosser

    I believe the answer is No, you cannot apply a preset at Import time based on file type. 
    What you can do is after you import, filter on File Type and set it to JPG and apply another preset that changes the sharpening settings of the filtered set of files, then go back and turn off the filter and work with both sets of images as you want.
    To filter by File Type, you need to go to Library Grid, enable the filter bar with the backslash \ key if necessary, then select Metadata, and either change one of the existing filter columns to say File Type or add a new File Type column.
    Once you have created and applied the filter, you can save it as a filter preset that can be applied by the filter preset selector at the very right and just above the thumbnail strip at the bottom, even in Develop mode.
    You might make one for raw and for jpg in case you want to swap between the two, and if you shoot JPGs with more than one camera model, you can add the camera model to the filter criteria.

Maybe you are looking for