Why is Bridge creating XMP files in CS6?

I'm using the CS6 beta on a new set of photos. All I've done so far is batch rename all the files (all raw, all CR2) and edited the IPTC metadata - to add my name, the project name, etc. Now I've got a side-car file for every photo. CS5 just included this stuff in the original file, why not CS6?

Hi,
The 'Camera Raw Database' is written to a local directory on your machine, and won't travel (without an extra step) if you copy the CR2 file to another machine. If you use DNG then the metadata will be stored in the file.
If you store the camera raw settings in the Camera Raw database and plan to move the files to a different location (CD, DVD, another computer, and so forth), you can use the Export Settings To XMP command to export the settings to sidecar XMP files.
You may have been using, and wanting, sidecar .xmp files, but just had them hidden in previous Bridge versions. To hide the .xmp file from the Content panel's display, go to View> Show Hidden Files and toggle the checkmark OFF, by selecting it.
regards,
steve

Similar Messages

Create XMP files from existing edited files

I just learned I needed to have the box checked in the Prefs menu in order for LR to automatically write XMP files in the images' folder. Now I need to go and create XMP files for all the photos I have previously edited. How can I do that?

That worked this time. I read in the forums that's what I should do, but it wasn't working. No XMP files were showing up with the image files. I did a restart of LR, maybe that did it.
Thanks!

Why doesn't Lightroom 4 create xmp files for mov files?

This would be useful for moving files to other applications and databases. As far as I can tell Adobe doesn't share any metadata for .mov files between any of it's CS6 programs either, Bridge, Prelude, Premiere, etc. As a still photographer who is now shooting DSLR video I want to get metadata entered as soon as possible for my still and video files. It would be best to do both stills and video at the same time. Camera Bits Photo Mechanic is the only program I've found so far that does this. Canto Cumulus is able to read Photo Mechanic's xmp files. I don't really need Photo Mechanic in my workflow except for this issue.

Familiarize yourself with this table
Camera Raw plug-in | Supported cameras
The Olympus E-P5 was first supported by Lightroom 5.
There is no backward compatibility with Lightroom 4.
So your choices:
Upgrade to Lightroom 5
Download the free DNG converter, convert all the Raw files from the E-P5 to DNGs then edit the DNGs in Lightroom 4
Camera raw, DNG | Adobe Photoshop CC

Why does Bridge open raw files (ndg) in Raw window even though the 'Open in Photoshop' option is...

I don't understand why in Bridge there are 2 choices, -1- Open raw and -2- Open in Photoshop and yet both choices give you the same result--The raw window opens with PS below it. After having worked on my raw NEF files I save it to dng. My thinking behind this, is that I alreay have done what was needed and would now like to start working on it within Photoshop. It seems that the only way to automatically open it directly within PS is if I save it as a tiff, psd or jpg. But since this is not what I want to do then why must I add extra steps as opposed to just opening it hwere I want. I mean the 2 choices are there, so why not do what it is being asked?

If I may step in in this discussion, I always use DNG but never have used ACR to achieve this result.
As Curt stated the changes made in ACR to a Raw file (or for that matter a DNG file) are undoable without problems.
My workflow (using Canon CR2 but that is not important, let's say a dSLR generated Raw File) is to use Photodownloader in Bridge (not perfect by far but still the best and easiest way for me).
I connect my CF card using a card reader and let Adobe Photodownloader do the work.
Inhere I use several options:
- convert the CR2 file to a DNG
- back up the original CR2 on a separate disk
- rename the DNG to yyyymmdd (shot date) and sequence number
- add a metadata template for copyright to all the DNG files.
Sorting out the keepers I open the DNG in ACR and either hit Open (for open directly in PS) or use save as Tiff or PSD depending on next step in development or simply hit Done to apply changes and leave it for later use.
The advantage of having both ACR in PS and Bridge is huge. The only difference between both is that by default PS has the Open Button selected and Bridge (open in Camera Raw) has the Done button selected, thats all.
But here is the good part, you can use both simultaneously! For example have PS in film strip mode with multiple files selected and when changes are ready hit Save as start the process but locks up PS itself. Switch to Bridge and use Open in Camera Raw and start with the next job while ACR PS is still running in the background
When I open a DNG in PS using ACR in either PS or Bridge I continue developing with actions and fine tune with layer mask, brush etc etc.
Sometimes use Save As for PSD with the layers still active (huge files) when needing to revisit or not quite ready. But mostly I use an action to flatten the files and save as PSD.
Both DNG and PSD are ending up in my archive, my clients receive whet they want, PSD, Tiff but mostly jpeg and resized.
When having the job finished and every once in a while I clear out the original CR2 files from Back up because in all the years I use DNG (at least 5 years) I never had to use the original CR2 instead of the DNG that is thoroughly backed up as is the original PSD.
But since disk space is cheap you can choose to keep them.
An other option is to include the original raw file in the DNG but I would not recommend that because the file size is getting almost twice as big.
The biggest plus side for me using DNG is that the xmp data is written directly to the file while original CR2 or NEF needs an xmp side car file next to it with this data.
However saving changes to metadata is taking a bit longer to a DNG then to an XMP side car file, depending on system resources and time this never been a real problem for me

Why do I have XMP files in my iPhone pictures?

I have been an iPhone user for the past 3+ years. When I connect my iPhone via USB to my Windows PC I can open Windows Explorer and see what files are on my iPhone. Starting this month, I started seeing .XMP files in my pictures for the first time. The files show no images and all are 1.24 K in size.
Questions:
1) What are these .XMP files?
2) Why are they showing up on my iPhone all of a sudden?

Hi Comstock2544,
I had the same problem during the last year.
According to some experts, .XMP are metadata files, something called "sidecar" files: they contains information about some of your pictures (e.g.: date of capture), and must be inthe same path of them to work properly (although probably useless on our pc).
And... they aren't actually of Adobe: they are standardized widely.
In our case, they are created by iOS when you crop and modify some pics with th iPhone tool. They serve to store information about your editing, without lose information from the original pictures.
In facts, if you crop one of your pics and save it, when you come back to re-crop it, you can see that the rest of the image cropped is still there.
A friend friend was able to delete them (I had 3) just deleting them, but I'm still unable to do that with the new ones. Anyway, you can just ignore tham and it'll be fine.
P.S.: You can open them with the notepad to see what info they store.

Why is Bridge not listed in the CS6 Extension Manager?

Title says it all realy. Is this a bug, or a feature regression? How should extensions for Bridge be installed? Back to the manual and error prone way?

You can find the answer in FAQ( http://forums.adobe.com/community/creativesuites/extensionmanager/faq ). There is a FAQ link in the Extension Manager user forum page( frame on the right ).
Q: Bridge CS6 was NOT listed in Extension Manager CS6
Mar 18, 2012 10:50 PM
Starting from CS6, Bridge is not supported by Extension Manager anymore. That is why you cannot see it in Extension Manager.
Q: How can I install extensions for Bridge CS6?
Mar 18, 2012 10:43 PM
Because Bridge CS6 is not supported by Extension Manager anymore, you have to install them manually.
For MXP extension, you can convert it to ZXP extensions with Extension Manager CS6. Then try steps below.
For ZXP extension, use utility software such as 7-zip, WinZip or WinRAR to extract it to a folder.If there is no mxi file after extraction, then it is a CSXS extension.
For CSXS ZXP extension, move the folder to following folder.
Windows: "C:\Program Files (x86)\Common Files\Adobe\CS6ServiceManager\extensions\"
Mac: "/Library/Application Support/Adobe/CS6ServiceManager/extensions/"
For non-CSXS ZXP extension, check the content of the MXI file. Copy all source files defined in "..." to the corresponding destination folders manually. If you are not sure where these files should be copied, please paste the mxi file here.

Media Encoder will not Encode MPEG but creates XMP file

When I place an MPEG video file in my adobe media createor folder it automatically creates the same file name with an XMP extension with approx 4kb of data. However it will not encode the file and it will not show up in the Queue. Anyone know why?
Trying to convert to FLV - Web 512x288
Also is there a way to automatically remove the item from the queue once it has encoded. Our media encoder queue gets full of converted videos and then crashes.

When i try to add the file manually it says error decompressing. Is this just a corrupt file? Seems to be happening a lot.

Why is bridge cs4 skipping files when batch renaming images?

When batch renaming in bridge, I select all the files and then start with the first image to rename them. Over the last few months, it is randomly skipping images. It will also jump the number that image should have gotten, so typically we can manually go through and rename the file so it will line up properly.
Just wondering why this is happening all of the sudden when it worked perfectly for years!

Sorry Patrick, Did not see the previews before, only saw the thread via
email and they don't show the samples you provide.
After seeing those files it looks definitely like corrupted images. I cannot
imagine Bridge to cause this. Rereading your post, it more looks the result
of a bad functioning write/read process on the external HD or a bad USB
cable.
Assuming you have back up could you test this on either an other HD or a
DVD. Just copy the files again to those devices and retry. That would proof
the fault lies with the external HD.
Could you report back on that?
Thanks for your tips. I tried, BUT didnt solve my problem.
Have you seen how the pictures are distracted ?
They seem hav gotten some kind of alien-verystrange-crazy-adjusments

Why vi dll creates ini file on its own?

Hello,
I have built my LabVIEW project as shared library (dll).
My system looks like this: main exe file loads dll, and this dll loads VI dll.
With LabVIEW 2011 it was ok, but when I switched to 2013 my VI dll started to write into main exe ini file.
When dll is loaded those lines appears in main exe ini file:
[LVRT]
RTTarget.ApplicationPath=C:\Users\user\Documents\LabVIEW Data\Remote Development\startup.rtexe
RTTarget.VIPath=C:\Users\user\Documents\LabVIEW Data\Remote Development
Does someone know what causes this and how to turn it off?

I got the same thing when I built an exe. I have a custom INI file, it has the following entries:
[Oscilloscope 2013]
server.app.propertiesEnabled=True
server.tcp.serviceName="My Computer/VI Server"
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=False
DebugServerWaitOnLaunch=True
FPFont="Segoe UI" 15
appFont="Segoe UI" 15
dialogFont="Segoe UI" 15
systemFont="Segoe UI" 15
BDFont="Segoe UI" 15
The only dll it calls is lvanlys.dll. After running the EXE the following are appending to the INI file
RTTarget.ApplicationPath=C:\Users\XXX\Documents\LabVIEW Data\Remote Development\startup.rtexe
RTTarget.VIPath=C:\Users\XXX\Documents\LabVIEW Data\Remote Development
Regards,
mcduff

XMP files not being created with DNGs...

I'm used to using Bridge with ACR to process Nikon NEFs. But a recent camera update has me experimenting with converting the D3's NEFs to DNG files and editing them with CS2 and Bridge 1.04 which works better on my system. I've also experimented with CS3 and Bridge 2.1.1.9 with the same DNG files.
In both cases XMP files are not being created when working with DNG files. I have enabled "Save image settings in : Sidecar ".xmp" files" turned ON. But they do not seem to be generated and I assume the ACR adjustments are being embedded in the DNG file. Meanwhile doing edits on NEF files continues to create .xmp files as expected.
I find .xmp files to be very useful and I'm wondering why they're missing with DNG files? Are they hiding somewhere other than in the same folder that the images reside in?
Thanks.
Russell

> The information contained in the XMP file is stored in the DNG file so there is no need for a separate file.
Aww, yuck!! That's a real drag...
When editing lots of files (yesterday's shoot produced 8GB) I back everything up to off-line storage and then, after doing all my edits and crops in ACR, I only have to copy over the small XMP files which takes no time at all.
So if I re-edit the DNG with ACR I have to re-copy ALL the files again to the off-line storage.
I used to sometimes even save 2 versions of the xmp files when I needed 2 different crops of the same images, such as doing a wide screen 'cinema' crop for a corporate client's Intranet presentation of their event, as well as more standard crops to be used for their newsletters.
Guess I won't be using DNG any more..
Thanks for the help Kees :-)
Russell

Why does CC have less file types than CS6?

I have both DW CS6 and CC installed on my system. Can anyone tell me why CS6 has more file types available from the "file/new" menu than CC has? For example, CS6 has 18 "HTML" types, yet CC has only 2. Also, CS6 has a "get more content" link on the dialog, whereas CC does not.
Is there any way to get CC to have all of those file types available, or do I need to create the file in CS6 and then switch to CC for the rest of my work?

kenbrody wrote:
Is there any way to get CC to have all of those file types available, or do I need to create the file in CS6 and then switch to CC for the rest of my work?
If you want those starter files in Dreamweaver CC, it's very easy to copy them across. Go to the following location:
C:\Program Files (x86)\Adobe\Adobe Dreamweaver CS6\configuration\BuiltIn\Layouts (Windows)
/Applications/Adobe Dreamweaver CS6/configuration/BuiltIn/Layouts (Mac)
Copy all the files except the first four, which begin with HTML5_
Paste them into the following location:
C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC\configuration\BuiltIn\Layouts (Windows)
/Applications/Adobe Dreamweaver CC/configuration/BuiltIn/Layouts (Mac)
You will need Administrator permission to do this.
Once you have copied them, you will find them in your New Document dialog box. The names won't be fully spelled out, but they should be recognizable.

Why does Bridge Need Illustrator to Save as PDF compatible file?

1. Why does Bridge need Illustrator files to be saved as PDF files? "PDF Compatible File" ticked in the save menu.
2. Why does saving with this info take so long, even on decent fast modern systems?
3. Why does Bridge not consistently render the Illustrator files in FULL RESOLUTIONS, seemingly shooting for half resolution much of the time, and simply stopping at that?
4. Why does "clicking" on the preview inside Bridge bring up the full resolution?
5. How do I shortcut this process so that every file is previewed in Full RESOLUTION, instantly?
What is the point of Bridge? What's its reason for existence?
First time user of Bridge.

Since someone is bound to say that this should be asked in the Bridge section... it already is. And has been referenced back over here.
You can find it here:
http://forums.adobe.com/message/5655632#5655632
Answer wherever you see fit, if you're up to the task of dealing with someone attempting to have a broader view, perhaps also suffering from somewhat objective analysis that sometimes contains direct criticism of the way Adobe does things.

What happened to .xmp files?

I have noticed recently that my Bridge program (cs4) has not been automatically exporting .xmp files into the folder where I store my images. I have been doing a lot of reading, but still can't seem to find a solid answer as far as what to do.
I have figured out how to export .xmp files into another folder, but what's the point of that? I want the metadata for my images to stay with my images. When I move them from folder to folder using Bridge, the xmp files used to move also, so I never lost my metadata.
I also empty my cache fairly often. I noticed that Bridge was no longer exporting xmp files when I emptied my cache and ALL my metadata that I had added to my images was gone, just like that.
I am a photographer and need that information to go somewhere permanent automatically, not in the cache which is supposed to store temporary file information.
Anyone have any idea?
Thanks so much!

Tai Lao wrote:
Your post #29 is completely blank
Strange, I responded using email and this normally functions well, maybe the chance in formatting and quoting did not get through?
I don't want you to think I'm ignoring you.
How could you think of that...
here is a copy of the mail, hope the formatting keeps clear!
>> Omke Oudeman wrote:
>>
>> As far as I understood the producing of magenta colorcast is a fault by
>> Pentax and the recovery utility does only work on original Pentax DNG, the
>> PEF files already have some compression and don't display all the sensor
>> data, Right?
>
> Wrong, very wrong. But that is definitely off topic.
It is what I understood (after briefly scanning through page) from this post that advices to shoot in K20 generated DNG instead of the PEF format.
http://www.pentaxforums.com/forums/pentax-dslr-discussion/67532-how-use-k20s-black-pixels- hidden-dngs.html
>> Omke Oudeman wrote:
>>
>> …I did something else, I opened 2 files in ACR, one the original CR2 and the
>> other the DNG conversion of it. ............ I could not find one single >>difference between both files…
>
> That is irrelevant. The issue is that there is some information inside the
> raw files that is not currently used either by the Pentax software or by
> Adobe, but that a third party (Gordon B. Good in this case) was able to
> utilize in order to improve the quality of certain converted raw files.
For your files in certain conditions at high iso this seems to be the case, the DNG files converted by Adobe DNG converter do miss the border pixels needed for the script from GordonBGood.
I tried to download that application but it seems only for Windows, how do you manage to use it?? Thought you have given up on Windows long time ago??
Nevertheless I also tried the apply image method you quoted from Bruce Fraser in an other post, using subtract with offset 128 and both perfectly the same.
I do agree that Raw converters from nowadays can get more out of the Raw data then they did 8 years ago, trying an 8 year old raw file gives a much better result (but then you also have to keep in mind that our knowledge and skills in Digital imaging have grown in combination with better color management understanding and good calibration soft and hardware is also due to this!)
Also I'm not afraid my benefit from the future Raw converters will differ if I use DNG instead of the original Raw, but that is my personal believe. The result I get nowadays for combination of DNG and PS are already more then satisfying, and sure it will be better in the future but for that I have also faith in DNG :-)
> Yes, I use PSDs exclusively. However, if you don't think TIFF will be around
> in 15 years, why do you think DNG will? After all, *+Adobe owns the TIFF
> format+* as well as the PSD format.
>
> If you trust Adobe to keep the DNG alive for 15 more years, why don't you
> trust that same corporation to keep supporting TIFF, a format for which they
> paid darned good money to acquire?
That is just a question of the market, as you could see that our young friend that started this post never uses it and I do hear more voices saying they don't use it or don't see the use for it. Eventually there will be no need for letting seldom used formats taking space in menu's and applications.
DNG however is still talk of the town, whether you like it or not. And therefore more likely to be around in 15 years time. But you are right, If I was to know about what was going on in 15 years from now I would not be a photographer but a fortuneteller and in my free time bathing in countless money :-) :-)
> Another one of the reasons why I don't like DNGs is, number one, that they
> take an awful lot longer to open than the raw files.
That I still can't understand unless you have chosen to use the original raw file included and created a double size for the file. But as stated in earlier post, not the case on my system.
> Not that any of this—or anything else in the world for that matter—should be
> an issue for me then.
Statistically you have lived the greatest part of your life and knowing your health is not something to be jealous of (to put it mildly) your statement about this also is something only time will learn.
Let's wish we still can have a long period for our little chats, agreed or not.
I will give up on getting you to DNG (for now as it is...) :-) :-)
Vriendelijke groet,
Con cordiales saludos
感谢你和亲切的问候

.xmp files showing up in my SD card when accessing RAW files in Finder... Very weird!

Hi,
I'm having a very weird problem... I'm using a 4GB Scandisk SD card and am shooting my RAW photos on a Canon Rebel 2ti. I'm using a Macbook Pro, 2011 2.3Ghz i5, 4gb of Ram, with Lion v. 10.7.2 and am accessing the SD card RAW files through Finder. I'm secondary clicking on the image file or double clicking them as PS is my default opening program for RAW files. When I hit the "Done" key on any of the Photoshop files, a new .xmp file shows up in Finder. When I open it, it's a Microsoft Messenger for Mac 8 License Agreement...
I do have Microsoft Office 11 installed and have never used Messenger. It's not a huge deal, but it's driving me crazy and it's totally weird!
Thanks,
-Dave

It's a lot of separate, unrelated things happening to you in one long chain, but each step is normal and explainable.
You are opening raw files straight from a card into Photoshop. Photoshop will open them in Camera Raw. Camera Raw's preferences are set to save changes in XMP sidecar files. You are clicking Done, which applies the default Camera Raw processing, and that change generates an XMP file to store these new settings. That's why an XMP file is showing up in the same folder. On a computer, that's fine. But writing back out to a camera card with a device other than the camera is not recommended. What is recommended is to use another, faster way to preview raw files on a card without changing them (Adobe Bridge, Lightroom, Apple Aperture, Photo Mechanic, etc.), so that the card's left untouched as it should be.
If you don't want the XMP file to be generated, you have to do just one of the following:
In Camera Raw preferences, change the "Save image settings in" option to "Camera Raw database", not "Sidecar XMP files".
Instead of clicking Done every time, which applies any changes, click Cancel instead, if you were just looking and not editing.
Use something other than Photoshop to preview raw files. Most of the other ways are faster than opening them in Photoshop. The recommended workflow is to use a camera downloading utility to look through all the images on the card at once (instead of one by one as you are doing), and then select only the ones you want to bring into your computer. Bridge (via File > Get Photos from Camera, not by browsing), Lightroom, Aperture, and iPhoto all have that capability.
As to why double-clicking an XMP file opens a Messenger license agreement: As you probably know, the system has to figure out what program should open a file with a given filename extension. It sounds like maybe both Adobe and Microsoft have used the XMP extension, and the Office installer probably associated it with some type of MS Messenger file. So when you double-click an XMP file, Mac OS X opens Messenger. Since you have not used Messenger before, it's showing you the "first run" screen for Messenger, and Microsoft has set it up so that you have to click Agree on the license agreement before using it. If you never click Agree, it will still be the "first run" next time you open Messenger, whether you meant to or not. You can use Get Info in the Mac Finder to reassign XMP to open in another program.
You probably didn't expect so many things to happen from just opening a raw file off a card, but that's the way it worked out.

Creating A File Resource Using Tomcat JNDI

Hi guys,
My problem is that I am creating a web service and I cannot get to a properties file without creating an absolute reference to that file. If I was creating a servlet I would simple use getServletContext() method to get a relative reference to it. However since it is an axis web service i have to deploy my applications in the WEB-INF/services directory, and because it does not interact with the axis servlet I cannot use getServletContext(). So i thought I could create a JNDI file resource reference in the tomcatHome/conf/context.xml file, similar to how I created a JNDI connection pool. The resouce definition looks like this;
<Resource name="resource/dialogueEngineConfig" auth="Container"
type="java.io.File"
url="file:/Applications/apache-tomcat-5.5.1/webapps/axis2/META-INF/DialogueEngine.properties">
</Resource>now I tried to access the resource in my code like this;
// Obtain our environment naming
Context envCtx = (Context) new InitialContext().lookup("java:comp/env");
// Look up our file
File f = (File) envCtx.lookup("resource/dialogueEngineConfig");However I get a NamingException; 'Cannot create resource instance'
I don't understand why I cant create a file resource in JNDI, it seems like a simple enough thing to do. Am I doing something wrong or missing something? Any help would be greatly appreciated.
Thanks

Hello xalien,
I have the same problem. I need to access external xml config file via JNDI from my servlet, running on Tomcat 5.0.28. Have you manage to define an URL resource? If so, please provide an example how to do it. Many thanx.

Why is Bridge creating XMP files in CS6?

Similar Messages

Maybe you are looking for