Smart objects generate huge ( 10 GB) temp files ??

Hi folks. I think there's a bug in CS3's smart object handling. Everytime I move (not resize!) a smart object, the temp file's size increases by some 100-200 MB. I easily get over 10 GB just by moving around a single object repeatedly.
I find that quite weird, given that normal layer moving does not significantly alter the temp file's size. And PS only has to store the smart objects new X and Y coordinates as the object itself does not change. Am I missing something ? Anybody knows what's going on ?

Converting Smart objects back to embedded layers would be a very useful addition. "Return to layers" would be a good term for it.
If you are looking for real world examples where this would be useful Chris
to simplify and bring down the file size of a file that has got out of hand with smart Objects. Some sort of global command "embed all Smart objects" in the layer/smart objects menu would also be useful for this purpose.
Objects of the same res and profile could then be non-destructively edited by swapping them in and out of smart objects for direct editing within the master document.
would be particularly useful when for example you need to detach a single instance of a duplicated SO from the others.
There is sometimes a need to return layers, and adjustments back into the master document to directly modify how they interact with their surroundings in terms of color and masking - for compositing. Its useful for simplicity to have them tucked away as SO's still
Of course data loss due to resampling, bit depth and modes could be greeted with a warning, perhaps the warning could be contextual "this operation will result in data loss, will decrease file size by 75%, change its mode from LAB, and resample the embedded pixels to 120%".
What happens to the smart-filters? if they are there, a choice either to rasterise them or abandon them

Similar Messages

Photoshop CS4 smart object template just overwrote a raw file - HELP

So. I've been working in Photoshop extensively for about 6 years now and I am well aware that nothing we do in Photoshop or Lightroom is supposed to overwrite a raw file. I'm not talking about changing it to something a little lighter or darker, I'm talking about replacing a picture of one baseball player with another one - and the original? Gone.
Here's what happened: I have a poster template that contains several layers, 7 of which are smart objects. I change the pictures in the template by right-clicking the smart object layer and selecting "replace smart object," browsing to the new image, selecting, and here is what SHOULD happen: the target picture opens in Adobe camera raw, I make some small edits, click done or okay or something similar, and that new image has replaced the old one in the template. What DID happen was this: I followed the procedure above and selected my target raw file, the picture that was already in the template (the one I was trying to replace with my target file) opened in Adobe camera raw. I thought - Hey, that's wierd! Closed the ACR dialog and tried again. Same thing happened. I opened lightroom and saw - to my HORROR - that the target file had been changed to the same image that was in the template.
If it clarifies: pictures of player A (who played in 2009) is in all of the smart object layers in my template. I want to make that poster be of player B (who played in 2012) so I begin replacing all the smart objects. When I get to the 3rd image in the poster template, Photoshop overwrites my raw file of player B with the smart object photo of Player A. There were no photos of player A on the network drive that the picture of Player B was on. But there's one now. My raw file shows that it was modified about 10 minutes ago.
We tried undoing in Photoshop. That did nothing. We tried deleting the xmp file. That did nothing. We removed it from the lightroom catalog and reimported it. It is now a picture of Player A from 2009 and my picture of Player B from 2012 is just gone.
Anybody have any idea what this could be and how we could avoid it in the future?
Best,
Jamey

mojoimagery wrote:
Now - JJ - when you say "overlay files" - what do you mean? Because that feels like a good description for what happened.
We performed no save operation at any point during the sequence of events that ended with the image in one raw file being replaced by the image in the smart object.
As I wrote Smart Object layers embedded object is a copy of the original and if you replace it you replace it with a copy of some other object. Embedded object are copies and independent from the original. If after creating a smart Object layer who's embedded object is a copy of a raw file and its conversion settings. You change the original RAW files RAW conversion settings the smart object layer raw conversion setting are not changes for its a copy with independent raw conversion settings. When you replace a smart object layers contents you will replace the embedded object and you should replace it with an object the has the same pixel size and orientation. Because there is an associated transform for the object in the layer that is not replaced. The replacement is also a copy. If the original smart object was created using File Open where you choose a RAW file ACR would open with the RAW files current conversion settings. In ACR you can changes the setting then hold down the shift key to change the open image button to an Open Object button. Using that button ACR will open a smart object layer in Photoshop the contents of the embedded object is a copy of the RAW file and the current ACR settings. No File is written Photoshop is not a File Editor its a Document editor that has many data structures for different layer types. When you replace the contents of a smart object you will be put into a "Place" file selection dialog if you choose a raw file it should have the same orientation as the image being replaced because of the associated transform. When you choose a RAW file ACR will open and you can change the conversion settings however there will be no Open Image button instead there will be an OK button. There is also a save image button and you can save a RAW file that is a DNG file not a CR2 file. Like the DNG converter. If you click the OK button the embedded object in the smart object layer will be replaced with a copy of the selected RAW file and the current ACR settings. Again there is no file written Photoshop is not a File editor just the embedded smart object data is replaced in Photoshop smart object layer's data structure.
I do not think the use of smart objects in you process caused what you are experiencing and because it only happens once an a while I feel its more likely caused by some human error made during the processing in those cases. I would look elsewhere for what causing the overlay. In the place file selection dialog it is possible to rename files perhaps even by accident. Programs like LR and Bridge can rename and copy files perhaps overlay other files.

Is there a way to open a smart object, but get the original instead of a temp file?

Working with large amounts of images and PSD files.
1. We create a smart object from say, a .jpg file on a layer, then filter, etc.
2. Double clicking the smart object creates a new window with that object as a .psB file.
3. When the file is saved and closed, the .psB file is deleted.
This is how smart objects work, we know.
What we need to do is:
1. We create a smart object from say, a .jpg file on a layer, then filter, etc.
2. Double clicking the smart object will open the ORIGINAL .jpg file
3. When the file is saved, the original .jpg file is saved in its altered form, and is reflected in the .psd file
We realize that Smart objects were created for reasons, of which we are aware.
Yet, we have several designers who use the same .jpg's but want the original to be changed so that the next developer has that changed .jpg.
Trie thus far:
ScriptListener cannot be used to tie it to a double click event on a smart object, because when the smart object is created it is already a copy of the original.
Creating a variable to call the original does not 'appear' to work, because it is accessing the .psB file instead of the original .psD file.
I think with early versions of PS there was a way to insert an image like a .jpg into a layer, and the link to that .jpg was retained. Thus, when you double click on that layer, the original .jpg is brought up to be edited, the .jpg file is now altered, and is reflected in the .psd file after finishing.

No, not too late.
InDesign is for layout for press in this case.
Photoshop is for design, which is using the .jpg's.
I'm half way there, but stuck at:
Getting a file location reference when the .jpg is first brought into PS as a layer.
Getting a script to write the location of the file into the medata for the PSD in some field
Reading back the metadata file location for the .jpg and bringing it back into the PSD again.
Any help would really be appreciated.
I can make the completed script(s) available when its complete, as this has possibilities for other uses, batch process, and more.

SMART OBJECTS TEMP FOLDER

I use smartobjects a lot when I am creating collages or my graphics in photoshop. What is surprising me these days is that when I import a photo as a smart object, if I click it in the layers panel it opens in a separate window, so I can edit just that particular photo, by adding adjustment layers, duplicating etc. My surprise is that when I try to save it it opens the temp folder.
Now I can't save my new edits, because this was very useful in case I want to change or edit the adjustment layer. If I still got the background, I can merge all layers and save it and all changes will be updated in the main document, but if I don't like the changes, that means I will have to start all over again.
Anyone knows why this is happenning to me. I have the current CS5 12.0.4.
Thank you,
Shadreck

srukweza wrote:
I use smartobjects a lot when I am creating collages or my graphics in photoshop. What is surprising me these days is that when I import a photo as a smart object, if I click it in the layers panel it opens in a separate window, so I can edit just that particular photo, by adding adjustment layers, duplicating etc. My surprise is that when I try to save it it opens the temp folder.
Please clearify two things for me. How do you import a photo as a smart object? and when you wrote duplicating what did you dupe.
When I do collages I populate my Collage templates with image files using Photoshop's menu File>Place. The image layers are smart object and embedded it the layer is a copy of the original image file. It can be any image file type RAW, PSD, Jpeg, PNG etc. When I double click on an image layer smart object icon in the layers palette Photoshop Opens the embedded file in the smart object layer. If the embedded file is a RAW file ACR open first I can re-adjust the current smart objects raw setting an then open the image in Photoshop. Then I have a choice of closing the image without saving in which case no update is made to the smart object layer. Or I can use menu File>Save... . When I do a save I see a message that has a progress bar that states the Smart Object is being updated . What happens is the embedded file in the smart object is updated with the changes I made to it. Once it is updated the changes are also reflected into the document containg the smart opject layer. The smar object is also still open in Photoshop which I x out of it in Photoshop. You may have to reduce the smart object Image view zoom out to be able to see the updating smart object message when you do do the save to commit the changes into the smart object. Once you update the smart object layer the embedded image file is not the original image for it now contains you new update. On my CS2, CS3 and CS5 systems I never see save opening a temp folder. I see the smart object layer being updated when I use menu File>Save...

How do I stop automatic placement of files as a smart object in Photoshop CS4?

I have done numerous searches on the internet to find out how to stop Photoshop from placing files as a smart object. I followed the suggestion of going to Edit > Preferences > General to uncheck the "Place or Drag Raster Images as Smart Obejct" but that option does not appear in Photoshop CS4. Does anyone know how to deal with this issue in CS4?

This may sound strange, but to avoid the "Smart Object" designation, just stop "placing" the files. Either open them, or copy and paste them into Photoshop.
If you're just opening raster files in Photoshop, they come in as pixels - drag a newly opened raster file onto your target Photoshop file. If you're copy/pasting art from Illustrator, you can choose at the time whether it is a "Smart Object," or "Pixels." Sounds like you want pixels.

CS5 is opening raw files as a smart object to files im currently working

I just bough new CS 5 and find this big error. When i open raw file in Camera Raw and i have opened some jpg in CS5, it always opened as a smart object to this small jpg i have opened before. The same is doing my CS 5 when i drag some file from desktop, it always ended as a smart object in file im currently working with. Normaly it has to open as a new file not as a smart object in this file im already working with.

How are you opening your RAW files? If you are dragging and dropping them onto Photoshop, on top of an already opened file's workspace - all files will be placed as smart objects. If you drag the files to anywhere else in the interface, for instance the grey area on top of the workspace, they should open as usual. If you are opening them via Bridge or by double-clicking them in Explore, they should open as normal.

Multiple Smart Objects into existing photoshop file

I need to somehow get bridge to---
Import multiple files into an existing photoshop file (with a predetermined size ) as smart object layers in photoshop.
The options that Bridge currently offers falls short in 2 area
Load Files into Photoshop Layers-- does not import smart objects and creates a new photoshop file that ends up being as large as the largest imported file
Place into Photoshop--only lets you do one at a time
I need "Place into Photoshop" with multiple files
Is there a way to do this?
Thanks!!

I don't think it is possible, but to be sure drop this question also in the
PS forum if you already have not done so.
Is there a way to do this?
Thanks!!

Place smart object into pre-existing Photoshop file

There's not a way to do this in Bridge, but maybe there is a way to script it?
I've never used a Bridge Script but would love to how to implement them, if I can get a script to do this...
I need to Import multiple files into an existing photoshop file (with a predetermined size ) as smart object layers in photoshop.
The options that Bridge currently offers falls short in 2 area
Load Files into Photoshop Layers-- does not import smart objects and creates a new photoshop file that ends up being as large as the largest imported file
Place into Photoshop--only lets you do one at a time
I need "Place into Photoshop" with multiple files
Is there a way to do this?
Thanks!!

Please try this version, I've tested this in CS4...
#target bridge
if( BridgeTalk.appName == "bridge" ) {
PlaceFiles = new MenuElement("command", "Place Files In Photoshop",
                               "at the end of Thumbnail");
PlaceFiles.onSelect = function () {
    placeFilesInPhotoshop();
function placeFilesInPhotoshop(){
    var sels = app.document.selections;
    for (i = 0; i < sels.length; i++) {
var t = new Thumbnail(sels[i]);
      sendPicToPhotoshop(sels[i].path);
function sendPicToPhotoshop(fileName) {
    function _placeFile(fileName) {
      if (!app.documents.length) return;
      var id35 = charIDToTypeID( 'Plc ' ) ;
      var desc8 = new ActionDescriptor();
      var id36 = charIDToTypeID( 'null' );
      desc8.putPath( id36, new File(fileName));
      var id37 = charIDToTypeID( 'FTcs' );
      var id38 = charIDToTypeID( 'QCSt' );
      var id39 = charIDToTypeID( 'Qcsa' );
      desc8.putEnumerated( id37, id38, id39 );
      var id40 = charIDToTypeID( 'Ofst' );
      var desc9 = new ActionDescriptor();
      var id41 = charIDToTypeID( 'Hrzn' );
      var id42 = charIDToTypeID( '#Pxl' );
      desc9.putUnitDouble( id41, id42, 0.000000 );
      var id43 = charIDToTypeID( 'Vrtc' );
      var id44 = charIDToTypeID( '#Pxl' );
      desc9.putUnitDouble( id43, id44, 0.000000 );
      var id45 = charIDToTypeID( 'Ofst' );
      desc8.putObject( id40, id45, desc9 );
      executeAction( id35, desc8, DialogModes.NO );
    var bt = new BridgeTalk;
    bt.target = "photoshop";
    var myScript = ("var _ftn = " + _placeFile.toSource() + "; _ftn(" +
                    fileName.toSource() +");");
    bt.body = myScript;
    bt.send();

Opening a Photoshop smart object file in Illustrator looks horrible (antialiasing problem)

Hello all,
This problem is killing me and I really wish I had done this logo in Illustrator, but I didn't now I have to suffer. Help!
I am doing a freeland job for a friend so I am not all that and a bag of chips with Illustrator. I am better at Photoshop but I need the vector, so I did my logo in photoshop and created a smart object out of it. I saved a version as a tiff and one as a jpg. My friend is creating his own leaflet in Word and the logo works beautifully there. I am creating a flyer for him in Illustrator and the logo is aliased in Photoshop but when I put it in Illustrator it looks antialiased and bad. He also has a little cheapy yahoo sitebuilder website until I create a website for him and the same logo(jpg) will not open in the yahoo site for him. I work and go to school so I don't have the time to recreated the logo in illustrator. It looks really good the way it is until I put it in Illustrator. Any ideas? please?
Thanks to anyone that answers this question, and kudos for taking time out of your busy day to calm my angst( or add to it)please don't add to it...

Hello Noel and c,
I created the logo in photoshop
( to make vector in photoshop, I need the scalability, I made the logo a smart object)
I then saved a copy as a jpg(for web) and a tif for print. I am creating a flyer in Illustrator, so I have to bring the logo into illustrator, when I do it looks like an aliasing problem. I had that aliasing problem in photoshop, but I still had text.... so I could antialias the text. In Illustrator the logo is just a tif, or jpg(I have tried both) It is not a text, but an image and it looks antialiased. In some programs the logo looks good, in some programs the logo looks bad. The only layer I have in the good photoshop file that I saved as a jpg, and as a tif is one layer that has text and the logo on it- this is a smart object. I have additional work files that have multiple layers, but I do not want multiple layers on my final print, web file. When I open up my laptop, I will save a screenshot.
Thanks so much

Smart Objects back-end question? How did it get so smart?

When i am working on a master PSD file with smart objects, i can see how those smart object layers are linked to the actual source files on my local computer hard drives.
When i go to edit a smart object layer on the master PSD file by double clicking on the SmartObject layer Icon, but on another computer, Photoshop recalls that source file even though it doesn't exist on that new computer.
It creates a file in the file path:
System Hard Drive
var
tmp
folders.501
TemporaryItems
source_file.psd (but named with the actual source file name).
How does this work? How does photoshop generate a new source file?
What happens to that source file? does it always live in that file path?

<<i can see how those smart object layers are linked to the actual source files on my local computer hard drives.>>
I'm afraid you're seeing wrong. Smart Objects are linked to nothing external to your PSD file. The original (raster, vector, RAW, PDF) image or object is IN you master PSD file. It's embedded. When you mess with the visible Smart Object, Photoshop consults the internal original but doesn't alter it.
When you edit a Smart Object, what's opening is a temporary file... merely a place for Photoshop to access the original image or object that is the basis for the Smart Object.

Smart Objects: RGB inside CMYK

Just two days before completing a two week job the client decided (still dont know why) the job had to be delivered with open layers on CMYK.
After two weaks and 6 jobs and hundred of layers latter had almost all work done..in RGB. I started to panic thinking of the time I would waste just appling curves,levels,etc... to every layer,while keeping things open if they wanted last minute changes.
Thats when it struck me..why not leaving everything as it was (RGB) and convert it to a smart object and then convert the parrent file to CMYK?
I has suprised how it works just fine.In the end the client agreed it was better to keep things as they were,but it sounds a really nice possibility and to some extend makes perfect sense as one would retain the full Gamut of RGB (AdobeRGB or any other) and could convert to proper CMYK acording to needs.
As anyone experienced this?

Mark -
There are a few gross errors in Photoshop that are seen as bugs, but go uncorrected for years due to the amount of work needed to fix them - not to mention - get it worked into the correction cycle in development. Marketing is steering the train. Go think about that oxymoron for a few weeks...
;o)
One major problem is the conundrum of being able to open an untagged file, assign a color space, then look at it. That in itself is counter intuitive and basically a HUGE hole in the application with respect to color management. With the new proposed architecture of creating the entire application Smart Photoshop - You not only eliminate this issue, but also have created a new and improved workflow - integrating source color images into the working space, tagged or untagged, with consistency for all. Adobe products are now far and wide enough to have the majority rule, so why not capitalize on it and implement a global workflow. This logic works for many industries Adobe serves. From 2d, 3d to motion video, cell phone, bio medical, and who knows what's next. It's image history preservation in its simple form.
In English, whittle down 9 options to 2 for color policies and change the logic between RGB and CMYK file handling. Convert to working space. Have the working space 32 bit Pro Photo RGB. Files flow into it as well as color space conversions. Now remember, this is a choice feature and not a force fit. It's a marketing born inception that caters to the masses for best practice. If you want to work outside that environment, its your choice, but it's not advisable unless you are resurrecting trash, re-assigning really bad pictures, or it does not work for your requirement and a new additional per-dim needs to be created. I'm offering a choice. Two choices to be specific. Road or off road travel. For here now, and tomorrow. It's a creature of growth, just like the implementation of Smart Objects that has morphed more possibilities as well as options. But Smart Objects is a representation of Adobe's expanded free for all mentality to push the envelope of development for market share. My advice is to back on the whizz bang wow factor and get some damn control of the features grained in deep rooted experience from power users....
Smart Photoshop is needed because users are not getting it Gentleman and Ladies. Expecting most users to become geeks is not going to happen. It's a given from a marketing stand point, but they refuse to see how to address it for one reason or another. Maybe too busy dealing with the company merge and product integration. Im pretty sure its quite an undertaking, but its time to make the best - better....
I remember Bruce Fraser talking about Chris and Thomas wanting 12 ish choices for color policies fearing too much restrain for growth. Thank you Bruce for 9, but my friend, we need even less.... Smart Photoshop gives 2 choices. Structure or Chaos. Right now we only have chaos. My vote is to have uniformity with very little user understanding and awareness. That's good implementation. The software has to become intelligent people.....
I'm game. Who has balls here?
nice to see ur pair Rich.

Smart object in PSD CS5`

Why does ps create a temp ai file when placing smart object? Editing is linked temporary file instead of original.

I assume you used CS5 in both offices?
Before CS5, SOs did not work on the principle of external links. If you were using CS4 or earlier, it's not likely you saw an edited SO just because you made an edit to your original AI file. There's no connection between the two.
Up to CS5, SO data is stored INSIDE Photoshop. When you double click an SO, that temporary file (the one you're asking about) opens to make your edits, then "disappears" once you save it. That's how and when the SO is updated.
It's my understanding that there's a plug-in or patch for CS5 that WILL permit linking. I don't have it but have read references to it in this forum. Someone will be along who knows more. But if such an add-on does exist, it's possible your success in the first office was due to it, and the machine in the second office didn't have it loaded?

Smart Object Sampling Technique.

Hope I named this topic aptly. I'm pretty new to the whole up/downsampling technique thing. In years of web design, I just never had any real need of it.
However, I ran into the following scenario:
We have a big PS file full of pixel art & photographs, some of both are smart objects. We'd like to resize a bunch of them, but need bicubic for some, nearest-neighbor for others.
Is there any way to set sampling techniques for each smart object?
(If not, where does one post feature requests? ;D)
Cheers!

First you need to know th all smart objects are not created equal. An embedded smart object is a copy of something "Photoshop" can be just about anything Photoshop supports. A Raw with Raw settings, A PSD file, A Layer, A layer set etc. Smart Objects can resized two ways.
The first way is the re adjust the transform associated with the Smart Object Layer (Ctrl/Command+T). Transform I believe uses your user id Photoshop preference for interpolation. When a smart object is resized this way Photoshop first renders the pixels for the smart object the resize those pixels like a raster layer using your default interpolation method. Even if the embedded smart object is a vector or text graphic. I guess you could set your Photoshop preference interpolation before doing each transform.
The second way to resize a smart object is by editing it in Photoshop and use Photoshop Tools. You do this be double clicking on the smart object icon in the smart object layer in the layers palette. When you do this Photoshop or ACR will open the embedded smart object in Photoshop as a temp work document in ACR the raw file with its current ACR settings applied. Use the tools approbate to resize. For example if the embedded smart object was a PSD file use menu Image>Image Size. Check resample the size and interpolation. Text and Vector layers will be resized using vector graphics or change font size raster layers will be resized using the method you set. When you commit the resize In ACR or use menu File>Save in Photoshop the embedded object in the smart object layer doubled clicked on will be update with the changes you made.

Replace smart object script

Disclaimer: I do not know how to script, but am willing to learn and am looking for advice.
I need to replace the text in a smart object from a data list then save the updated file using the smart object text. Is there an existing script that will do this?
I cannot use a straight text layer because I'm performing a free distortion warp on the smart object that does not work on straight text. Using variables seems like a logical solution, but the only variable type for smart objects is "visibility".
Plan "B" is to "replace smart object" with a series of PSD files containing the appropriate text. This works great, but I don't know how to automate it. I can easily create the series of PSD files using variables, but don't know how to automate their insertion into the template containing the distorted smart object.
I'm looking forward to learning something new!

I took a quick look at your script.
I do not know where the the displacement map come in,
The script seem the be replacing the object content of the current smart object layer.
That layer can have had all sort of photoshop functions associated with it and has an associated transform. All smart object layer have an associated transform and may have smart filters and filter mask as well.
I see no code to handle the smart object size and make the replacement object have the same size or insure the replacement object is the aspect ratio and size. Replacing a smart object content does not change the current layer's associated the transform that transformed the original object. If the replacement object is not the same size as the original object the transform may not work like your expecting.
An associated displacement map may come into play because of smart filters on the smart object layer. Displacement maps content are either for the layers content or for lower layers content to make the current layer to conform to lower layers contours.
In fact I create a four image picture package template that used a smart object for the image. Added CS2 for a file type that could be used to replace the image in your script and ran your script. It did pop up the ACR dialog if I select a raw file but it worked perfectly for my portrait cr2 files are the same size and aspect ratio. Ast the object.
And a jpeg was saved to my desktop.
When a different size landscape orianted portrait image is selected here is the result

Original filename for Smart Objects in CS6

After processing a camera raw image in ACR, I want to open the image in CS6 as a Smart Object.
Then I want to run a java script that depends on the original filename. Where in the metadata can I find the original filename?
Background: I have a script that executes very well if the file is opened in CS6 as a regular layer. However, when I open a file as a Smart Object, the script fails, complaining about an invalid filename.
The problem is associated with my favorite time-saving script and I am very keen to resolve the problem.   :-(
Thank you for your assistance.
BA

rj acton wrote:
After processing a camera raw image in ACR, I want to open the image in CS6 as a Smart Object.
Then I want to run a java script that depends on the original filename. Where in the metadata can I find the original filename?
Background: I have a script that executes very well if the file is opened in CS6 as a regular layer. However, when I open a file as a Smart Object, the script fails, complaining about an invalid filename.
I think the the only reason it works when you open them as a regular layer is because of your work-flow and habits. Try opening it twice as a normal layer an see if it works.
When you open a RAW file through ACR as a normal layer and as a smart object layer there is no backing file associated with the open document yet.   I feel you problem is you script is using something like the document name.   If you look at the title in the image floating window or tab you will see that Photoshop has assigned a name the first time you open it as a normal layer you will see something like filename.cr2 @ 25% (RGB16) the second time you will see filename-2 @ 25% (RGB16) when you open as Object you will see filename as smart object-1 (filename, RGB16). These title will change when you save the document to a image file type the title will change to the associated backing file you just saved.
I you look at Photoshop File info you can see all the image metadata and you can find the RAWFileName you want here a text file I wrote using a Photoshop script
It is enev in small jpef file saved from raw conversions if you don't strip mete data
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c011 66.145661, 2012/02/06-14:56:27        ">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:xmp="http://ns.adobe.com/xap/1.0/">
         <xmp:ModifyDate>2010-08-16T22:47:35-04:00</xmp:ModifyDate>
         <xmp:CreateDate>2009-04-25T15:20:46</xmp:CreateDate>
         <xmp:Rating>0</xmp:Rating>
         <xmp:MetadataDate>2010-08-16T22:47:35-04:00</xmp:MetadataDate>
         <xmp:CreatorTool>Adobe Photoshop CS5 Windows</xmp:CreatorTool>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:dc="http://purl.org/dc/elements/1.1/">
         <dc:format>image/jpeg</dc:format>
         <dc:creator>
            <rdf:Seq>
               <rdf:li>McAssey</rdf:li>
            </rdf:Seq>
         </dc:creator>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:aux="http://ns.adobe.com/exif/1.0/aux/">
         <aux:SerialNumber>237498</aux:SerialNumber>
         <aux:LensInfo>300/1 300/1 0/0 0/0</aux:LensInfo>
         <aux:Lens>300.0 mm</aux:Lens>
         <aux:LensID>142</aux:LensID>
         <aux:ImageNumber>48302</aux:ImageNumber>
         <aux:FlashCompensation>0/1</aux:FlashCompensation>
         <aux:OwnerName>McAssey</aux:OwnerName>
         <aux:Firmware>1.2.3</aux:Firmware>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
         <crs:RawFileName>LO2G5037.CR2</crs:RawFileName>
         <crs:Version>6.1</crs:Version>
         <crs:ProcessVersion>5.7</crs:ProcessVersion>
         <crs:WhiteBalance>Custom</crs:WhiteBalance>
         <crs:Temperature>5350</crs:Temperature>
         <crs:Tint>-22</crs:Tint>
         <crs:Exposure>0.00</crs:Exposure>
         <crs:Shadows>5</crs:Shadows>
         <crs:Brightness>+65</crs:Brightness>
         <crs:Contrast>+25</crs:Contrast>
         <crs:Saturation>0</crs:Saturation>
         <crs:Sharpness>25</crs:Sharpness>
         <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
         <crs:ColorNoiseReduction>0</crs:ColorNoiseReduction>
         <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
         <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
         <crs:VignetteAmount>0</crs:VignetteAmount>
         <crs:ShadowTint>0</crs:ShadowTint>
         <crs:RedHue>0</crs:RedHue>
         <crs:RedSaturation>0</crs:RedSaturation>
         <crs:GreenHue>0</crs:GreenHue>
         <crs:GreenSaturation>0</crs:GreenSaturation>
         <crs:BlueHue>0</crs:BlueHue>
         <crs:BlueSaturation>0</crs:BlueSaturation>
         <crs:FillLight>0</crs:FillLight>
         <crs:Vibrance>+21</crs:Vibrance>
         <crs:HighlightRecovery>0</crs:HighlightRecovery>
         <crs:Clarity>0</crs:Clarity>
         <crs:Defringe>0</crs:Defringe>
         <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
         <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
         <crs:HueAdjustmentYellow>0</crs:HueAdjustmentYellow>
         <crs:HueAdjustmentGreen>0</crs:HueAdjustmentGreen>
         <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
         <crs:HueAdjustmentBlue>0</crs:HueAdjustmentBlue>
         <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
         <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
         <crs:SaturationAdjustmentRed>0</crs:SaturationAdjustmentRed>
         <crs:SaturationAdjustmentOrange>0</crs:SaturationAdjustmentOrange>
         <crs:SaturationAdjustmentYellow>0</crs:SaturationAdjustmentYellow>
         <crs:SaturationAdjustmentGreen>0</crs:SaturationAdjustmentGreen>
         <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
         <crs:SaturationAdjustmentBlue>0</crs:SaturationAdjustmentBlue>
         <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
         <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
         <crs:LuminanceAdjustmentRed>0</crs:LuminanceAdjustmentRed>
         <crs:LuminanceAdjustmentOrange>0</crs:LuminanceAdjustmentOrange>
         <crs:LuminanceAdjustmentYellow>0</crs:LuminanceAdjustmentYellow>
         <crs:LuminanceAdjustmentGreen>0</crs:LuminanceAdjustmentGreen>
         <crs:LuminanceAdjustmentAqua>0</crs:LuminanceAdjustmentAqua>
         <crs:LuminanceAdjustmentBlue>0</crs:LuminanceAdjustmentBlue>
         <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
         <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
         <crs:SplitToningShadowHue>0</crs:SplitToningShadowHue>
         <crs:SplitToningShadowSaturation>0</crs:SplitToningShadowSaturation>
         <crs:SplitToningHighlightHue>0</crs:SplitToningHighlightHue>
         <crs:SplitToningHighlightSaturation>0</crs:SplitToningHighlightSaturation>
         <crs:SplitToningBalance>0</crs:SplitToningBalance>
         <crs:ParametricShadows>-25</crs:ParametricShadows>
         <crs:ParametricDarks>-13</crs:ParametricDarks>
         <crs:ParametricLights>+13</crs:ParametricLights>
         <crs:ParametricHighlights>+25</crs:ParametricHighlights>
         <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
         <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
         <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
         <crs:SharpenRadius>+1.1</crs:SharpenRadius>
         <crs:SharpenDetail>25</crs:SharpenDetail>
         <crs:SharpenEdgeMasking>27</crs:SharpenEdgeMasking>
         <crs:PostCropVignetteAmount>0</crs:PostCropVignetteAmount>
         <crs:GrainAmount>0</crs:GrainAmount>
         <crs:LensProfileEnable>0</crs:LensProfileEnable>
         <crs:LensManualDistortionAmount>0</crs:LensManualDistortionAmount>
         <crs:PerspectiveVertical>0</crs:PerspectiveVertical>
         <crs:PerspectiveHorizontal>0</crs:PerspectiveHorizontal>
         <crs:PerspectiveRotate>0.0</crs:PerspectiveRotate>
         <crs:PerspectiveScale>100</crs:PerspectiveScale>
         <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
         <crs:ToneCurveName>Strong Contrast</crs:ToneCurveName>
         <crs:CameraProfile>Camera Faithful</crs:CameraProfile>
         <crs:CameraProfileDigest>07AA307EAF63019A907C3A103EC361D0</crs:CameraProfileDigest>
         <crs:LensProfileSetup>LensDefaults</crs:LensProfileSetup>
         <crs:HasSettings>True</crs:HasSettings>
         <crs:HasCrop>False</crs:HasCrop>
         <crs:AlreadyApplied>True</crs:AlreadyApplied>
         <crs:ToneCurve>
            <rdf:Seq>
               <rdf:li>0, 0</rdf:li>
               <rdf:li>32, 16</rdf:li>
               <rdf:li>64, 50</rdf:li>
               <rdf:li>128, 128</rdf:li>
               <rdf:li>192, 202</rdf:li>
               <rdf:li>255, 255</rdf:li>
            </rdf:Seq>
         </crs:ToneCurve>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/">
         <photoshop:DateCreated>2009-04-25T15:20:46</photoshop:DateCreated>
         <photoshop:LegacyIPTCDigest>C919DE8C578CC777664AB2BCEBAFE2ED</photoshop:LegacyIPTCDigest>
         <photoshop:ColorMode>3</photoshop:ColorMode>
         <photoshop:ICCProfile>sRGB IEC61966-2.1</photoshop:ICCProfile>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
            xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
            xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#">
         <xmpMM:InstanceID>xmp.iid:53B401F530A9DF11A629E42CB0F33EB0</xmpMM:InstanceID>
         <xmpMM:DocumentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</xmpMM:DocumentID>
         <xmpMM:OriginalDocumentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</xmpMM:OriginalDocumentID>
         <xmpMM:History>
            <rdf:Seq>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:E719AF78E386DF1185EABAB6DC507A64</stEvt:instanceID>
                  <stEvt:when>2010-07-03T16:42:18-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>converted</stEvt:action>
                  <stEvt:parameters>from image/tiff to image/jpeg</stEvt:parameters>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>derived</stEvt:action>
                  <stEvt:parameters>converted from image/tiff to image/jpeg</stEvt:parameters>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:E819AF78E386DF1185EABAB6DC507A64</stEvt:instanceID>
                  <stEvt:when>2010-07-03T16:42:18-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:52B401F530A9DF11A629E42CB0F33EB0</stEvt:instanceID>
                  <stEvt:when>2010-08-16T22:47:35-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:53B401F530A9DF11A629E42CB0F33EB0</stEvt:instanceID>
                  <stEvt:when>2010-08-16T22:47:35-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
            </rdf:Seq>
         </xmpMM:History>
         <xmpMM:DerivedFrom rdf:parseType="Resource">
            <stRef:instanceID>xmp.iid:E719AF78E386DF1185EABAB6DC507A64</stRef:instanceID>
            <stRef:documentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</stRef:documentID>
            <stRef:originalDocumentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</stRef:originalDocumentID>
         </xmpMM:DerivedFrom>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:tiff="http://ns.adobe.com/tiff/1.0/">
         <tiff:ImageWidth>2336</tiff:ImageWidth>
         <tiff:ImageLength>3504</tiff:ImageLength>
         <tiff:BitsPerSample>
            <rdf:Seq>
               <rdf:li>8</rdf:li>
               <rdf:li>8</rdf:li>
               <rdf:li>8</rdf:li>
            </rdf:Seq>
         </tiff:BitsPerSample>
         <tiff:PhotometricInterpretation>2</tiff:PhotometricInterpretation>
         <tiff:Orientation>1</tiff:Orientation>
         <tiff:SamplesPerPixel>3</tiff:SamplesPerPixel>
         <tiff:XResolution>2400000/10000</tiff:XResolution>
         <tiff:YResolution>2400000/10000</tiff:YResolution>
         <tiff:ResolutionUnit>2</tiff:ResolutionUnit>
         <tiff:Make>Canon</tiff:Make>
         <tiff:Model>Canon EOS-1D Mark II</tiff:Model>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:exif="http://ns.adobe.com/exif/1.0/">
         <exif:ExifVersion>0221</exif:ExifVersion>
         <exif:ColorSpace>1</exif:ColorSpace>
         <exif:PixelXDimension>400</exif:PixelXDimension>
         <exif:PixelYDimension>600</exif:PixelYDimension>
         <exif:DateTimeOriginal>2009-04-25T15:20:46</exif:DateTimeOriginal>
         <exif:ExposureTime>1/1000</exif:ExposureTime>
         <exif:FNumber>56/10</exif:FNumber>
         <exif:ExposureProgram>2</exif:ExposureProgram>
         <exif:ISOSpeedRatings>
            <rdf:Seq>
               <rdf:li>800</rdf:li>
            </rdf:Seq>
         </exif:ISOSpeedRatings>
         <exif:ShutterSpeedValue>9965784/1000000</exif:ShutterSpeedValue>
         <exif:ApertureValue>4970854/1000000</exif:ApertureValue>
         <exif:ExposureBiasValue>0/1</exif:ExposureBiasValue>
         <exif:MaxApertureValue>3/1</exif:MaxApertureValue>
         <exif:MeteringMode>5</exif:MeteringMode>
         <exif:Flash rdf:parseType="Resource">
            <exif:Fired>False</exif:Fired>
            <exif:Return>0</exif:Return>
            <exif:Mode>2</exif:Mode>
            <exif:Function>False</exif:Function>
            <exif:RedEyeMode>False</exif:RedEyeMode>
         </exif:Flash>
         <exif:FocalLength>300/1</exif:FocalLength>
         <exif:FocalPlaneXResolution>3520000/1136</exif:FocalPlaneXResolution>
         <exif:FocalPlaneYResolution>2342000/756</exif:FocalPlaneYResolution>
         <exif:FocalPlaneResolutionUnit>2</exif:FocalPlaneResolutionUnit>
         <exif:CustomRendered>0</exif:CustomRendered>
         <exif:ExposureMode>0</exif:ExposureMode>
         <exif:WhiteBalance>0</exif:WhiteBalance>
         <exif:SceneCaptureType>0</exif:SceneCaptureType>
      </rdf:Description>
   </rdf:RDF>
</x:xmpmeta>

Smart objects generate huge ( 10 GB) temp files ??

Similar Messages

Maybe you are looking for