Smart object conversion- fonts required?

I've converted two type layers in CS5 to smart objects. If I send the layered PSD to a vendor for printing, will the vendor need the fonts, or is this the equivalent of "converting to paths" in Illustrator?
Thanks in advance for your thoughts.

Thanks again for your time, but is it correct to say that there's no way to directly convert type to a vector layer in Photoshop then?
(It'd be easier at this point than going through Illustrator.)

Similar Messages

Keynote 6.0 vector smart object conversion to Photoshop CS6

Hi,
I upgraded to OS 10.9 and Keynote 6.0. In the previous version of Keynote, I was able to easily paste Keynote content (words, shapes, charts) into Photoshop CS6 & Illustrator CS6 as vector objects, of which the elements could be independently manipulated by releasing the clipping mask.
However, with Keynote 6.0, it appears the content mentioned above pastes into CS6 software as .tiff files with no option to convert to a vector smart object? Is there a way to force a vector object placement or does this new Keynote version no allow (and if so why eliminate such a convenient function as vector smart objects)?
Thanks for the help...

Hello thanks for your answers,
i posted this when i was upset because it was a very frustrating situation. I create Vector art in Illustrator and most of the times i just copy and paste them into Photoshop. I dont use Illustrator Cs6 because some Issues with the color Picker and because i Use Scriptographer alot. So i use Photoshop CS6 and Illustrator CS 5.
Somehow recently i noticed this strange behaviour. When i close Illustrator completely and doubleclick the Layer in Photoshop it works fine.

Smart Object Workflow Suggestion/Question

Sorry if this is a noob comment/discussion I have been looking around for more info on this stuff and can't find it.
I really love using smart objects to help me organize my workflow. But I am frustrated at the lack of control I have over how to save my smart object conversions.
There are no settings, that I can find, in preferences where I can tell CS5 this is where I want my smart object conversions automatically saved to. (it currently uses the temp cache folder? I believe thats where it places them.) I would like set the save location in my preference.
It would also be nice to organize the smart object psb files in a folder system similar to the layers in my PSD file. keeping that consistency will allow me to go through my folder system in the same manner I go through my layers.
Sorry if this workflow already exists. I'm having trouble finding any in depth information on saving psb files. hitting export on every smart objects is very tedious.
Here is an example of what I mean
PSD FILE:
FOLDER1
>SubFolder1>
>> image
>> image
>> image
>>>Sub_Subfolder2>
>>>>> image
>>>>> image
>>>>> image
Convert each folder to Smart Object
SmartObject_FOLDER1
>SmartObject_Subfolder1
>>>SmartObject_SubSubfolder2
PSB SAVED LOCATION:
USER SETS LOCATION
C:/whereever/smartfolders/
autosave
files structure:
Directory
SmartObject_FOLDER1.PSB
SUB DIRECTORY
>SmartObject_Subfolder1.PSB
SUB SUB DIRECTORY
>>>SmartObject_SubSubfolder2.PSB
I know I can export each smart object individually but is there a preference function to do this automatically?
Does this exist and I just don't know it?

Check out the PS links panel here:
http://ps-scripts.com/bb/viewtopic.php?t=3045

Automating RAW file conversion to Photoshop with Smart Object Layer

Hi
Can anyone tell me if it is possible to automate an action (and the steps) to open a series of photos from their raw file state to a Photoshop file with a smart object layer. I have tried **** this... recording an action without success... it ends up creating a photoshop file with a background layer, no smart object layer.
Am i missing something obvious? Thanks for your help!
Regards bruce

Hi
Can anyone tell me if it is possible to automate an action (and the steps) to open a series of photos from their raw file state to a Photoshop file with a smart object layer. I have tried **** this... recording an action without success... it ends up creating a photoshop file with a background layer, no smart object layer.
Am i missing something obvious? Thanks for your help!
Regards bruce

Documents with Smart Objects - Very slow to open and Save - CS6 Photoshop

When opening and saving documents with smart objects photoshop freezes the adobe PS loader (circle dots) is replaced and the system loader (multi colored wheel of death) spins for 30 seconds or more.
What I've tried so far based off looking at various posts.
Photoshop Preferenes
Save in Background off
Maximise PSD and PSB file compatability never
Cache Tile Size: 128k
Advanced Graphic Processor Settings: Basic & Normal
Layer Panel options: No Thumbnail
Observations and workthroughs to date
The file size and amount of smart objects effects the file expotentially i.e. The more smart objects you have the worse it gets
These files worked perfectly in PS CS5
It also happens on files natively created in PS CS6
The CPU is maxing out at 100% while PS loads
Closing or opening suitcase has no effect.
System:
iMac 27-inch, Mid 2011
Processor 3.4 GHz Intel Core i7
Memory 16 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6970M 1024 MB
Mac OS X Lion 10.7.5 (11G63)
Suitcase 4
Anyone got any ideas? This is making me go nuts!

A solution!
It turns out the problem in my case was in fact Suitcase. Previously, I'd tried turning it off, but that didn't fix the problem, so this time, I uninstalled it completely and the problem disappeared. I then began re-adding it (installed 15.0.1, upgraded it, etc.) and the problem resurfaced with the addition of the Photoshop-specific plugin. Deleting that plugin solved the problem. So it seems that "disabling" Suitcase by stopping the TypeCore doesn't seem to actually disable all of the tentacles it sticks into your system.
You can find the plugin here: Applications / Adobe Photoshop CS6 / Plug-ins / Automate / ExtensisFontManagementPSCS6.plugin
(After a restart, I also had to delete the font cache, as described here http://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop-cs5.html but your mileage may vary.)
Alternately, if you don't want to delete the plugin, disabling it from within Photoshop seems to work as well. To do that, go to File > Automate > Extensis, click Preferences..., then deselect Enable Suitcase Fusion 4 Auto-Activation.
Fortunately, the plugin doesn't seem necessary at all to use the the core functionality of Suitcase (enabling and disabling fonts) in Photoshop. I didn't even know what these app-specific plugins did until researching this problem, and I still don't quite understand the point of them. I guess they allow you to let the apps for which they're installed do a little bit more of their own management (enable a font via Suitcase that isn't enabled system-wide), but that seems like more control than I need--if I'm enabling a font, I want all my software to be able to use it.
Anyway, the problem seems to be completely solved on my system now, though I just did all this, so more testing over the next few days is required. I'll post here if any issues crop up. I'm interested in hearing if this solves it for anyone else as well.

RGB and Smart Objects

When I place separate images into my CMYK master document, should I be placing them as smart objects and preserving their RGB values? Is there any benefit or detriment to doing that? I imagine it's good to preserve the RGB values, but if I am always going to print to a CMYK press with that particular document, then does it benefit me in any way? I've shied away from keeping the RGB values because I feel like they give me a false view of what the CMYK doc will turn out to look like. Any suggestions?

Stephanie:
I am not being unkind but there is SO much more to this subject than you currently begin to comprehend.
Let's start with your Color Management settings:
(gballard's web site, to which we directed you in your other thread, will be a great help to you in getting a better understanding of this subject.)
You simply MUST start with a properly calibrated and PROFILED monitor. That is non-negotiable so buy a spectrometer (Puck) if you don't already have one.
In your CM settings you have a selection of choices but if you are sending work to a Press, it is absolutely essential that you choose a CMYK Profile which is targeted to the KIND of Press and the type of Stock on which your job will run.
And of course you can, and SHOULD, create your document in a recognized RGB working space (either ProPhoto or Adobe RGB but NOT sRGB) and embed that Profile into your document because you then have the flexibility to CONVERT that RGB file to the correct CMYK Profile for the job.
And your Printing Company has some terms of reference, and the means of rectifying your file, if your CMYK conversion does not meet the requirements of their Presses.
Next, you need to learn to use Soft Previews.
You should set your proposed CMYK Profile as your Preview Profile (in Photoshop's View menu/Proof Set-up/Custom) making sure that you have checked "Simulate Paper Color".
If you keep "Proof Colors" checked, you can work in RGB while getting a very clear idea of how your colors will actually print when the ink hits paper on the Press.

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.

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.

Smart object colormanagement

When I place a psd file as a smart object in Dreamweaver CS4
I get a much darker images than the original or the exported jpeg
file from photoshop.
Any tips on where I can change the
colormanagement/conversion?

What are the color settings you are using in
Photoshop?

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>

DISGUSTED! ImageReady functionality lost for producing smart objects in GoLive!

It is ABSURD that the rollover/layer-based slice capabilities feature of ImageReady was eliminated and instead replaced by way of mediocrity using manual copy and paste functionality within Dreamweaver. What kind of step-backward mentality is this? I am beyond disappointed and feel betrayed by Adobe, not to mention unbelievably, inconsiderately inconvenienced. Does the title "industry standard" require bowing to irrational development or is this mere laziness on Adobe's part?
Previously I had been able to develop multiple series of rollovers within Photoshop using layers and then switch to ImageReady in order to automatically produce rollover code for a set of images...AS ONE IMAGE FILE. These images could then be placed into GoLive (another hot-button issue!) as SMART OBJECTS - gee, what a concept! - where the targets, if necessary and not already entered within ImageReady, could be linked to any page within the the site folders. Now I can't access the secondary image anywhere at all. It appears that the only solution for us lowly GoLive CS2 users is now to be required to TRIPLE THE AMOUNT OF WORK AND place multiple objects within a page layout, leaving (no pun intended) room for pixel space errors and requiring multiple manual page adjustments when the work was ALREADY DONE IN PHOTOSHOP! Layer-based slices are a work of genius, but NOT without the added capability of automatic rollover detection. How am I supposed to work this out in GoLive?
NOW, only NOW am I discovering that this "merged capability" within Photoshop is missing one of THE MOST INGENIOUS FEATURES EVER and now I am scrambling to find some garbage workaround in order to capacitate the need for a string of visual interface objects. This is the kind of move I EXPECT from Microsoft, but NEVER have I been this put out with Adobe. NEVER.
Is this the only solution? Bend to the will of the Dreamweaver cabal and join the ranks of the Microsuck copy-and-paste zombies? Not only is the new CS3 series "upgrade" cost-prohibitive for most anyone that isn't within the realm of the design elite or corporate ladder-climbing ranks of internal design group budgets, the tools appear to force anyone without the time necessary to learn the intricacies of manual HTML tagging to create nothing but the same garbage website in an infinite spectrum of ineptitude.
Is the new GoLive 9 supposed to accommodate this ridiculous shot-in-the-foot move or am I REALLY going to have to resort to a complete reload of CS2?

Dave and Buko, that's my entire point...I shouldn't have to be using CS2 after purchasing CS3. I have full versions for both thankfully and for this very reason but I don't know if I can install CS2 in addition to CS3 without causing some system file issues. I did briefly read about someone else trying that in another forum.
IR does indeed work great with GoLive CS2. My issue is that the rollovers in the extended Photoshop CS3 do NOT work and don't export code at all. It's damn frustrating that after making the purchase, I feel duped.
And Buko, no, I never even bothered with Dreamweaver. I attempted to learn it several times and was just put off completely. I previously owned both Macrodmedia Studio Professional and the complete Adobe CS2, but the upgrades for the combined product sets which made sense for me and didn't break the bank like purchasing the "Master Suite" didn't even include things like Fireworks, which supposedly has some sort of workaround for rollovers when setting multiple targets in an image file.

Photoshop smart object layer will not open in ACR when I double click

I have a raw file opened up in photoshop, duplicated it, made them smart objects, when I click the smart object icon on the file, i get another copy of the file in photoshop, the file doesn't open up in acr, is there a setting i'm missing?
Message was edited by: Rodwf

If you dupe that smart object layer you still have one smart object change one the other also changes. If you want two smart object for the save image so you cab have two versions of raw conversions you need to use menu Layers>smart Object>New smart object via copy..

Photoshop CC 2014 - Stack Mode Disabled - Load Image Into Stack Has No "Convert To Smart Object" Option

Hi,
I have just installed Photoshop CC 2014.1 and I have "Stack Mode" command disabled.
Also, I have no option to convert layers into smart object when I run "Load Image Into Stack" command.
Can you please tell me how to enable these features?
Thank you very much.
Luca

The 512 MB are a minimum requirement, not some optional thing. Without it, 3D will never work.
Mylenium

PS opens vector smart object all pixilated

I have this problem when using graphics from Illustrator as vector smart objects in Photoshop. I have followed tones of heated discussions on this but I haven't got any further. So here is what I do following the steps on the PS help: I copy graphics in AI and paste them in PS as smart object. A layer will be added that even has the name vector smart object but the graphic itself is all pixilated. Now the size of my PS-file is 150X150 Pixels with a resolution of 300. I need this size because I want to implement the file into my website and the layout requires this size for all my graphics. I would say it doesn't matter much what size the file is anyway since according to the PS help whatever vector smart object I place in Photoshop it won't change image quality when transformed. Therefor I'd say that not even the small file should be a problem here. But obviously there is something not working... because even when, to compare, I paste the graphic as pixel it shows the same result. Strange enough that I have used this vector smart objects before and it worked just fine... So I tried to paste the graphic in different ways, saving it as pdf in AI and then placing it in PS, insert it directly as smart object, making sure the file handling and clipboard references are adjusted, and finally after no success trashing the preferences in both applications. Still not closer to a satisfying result. I attach the graphics (first the AI graphic, then the vector smart object from PS) to show the difference and maybe there is someone out there that can tell what I am doing wrong. By the way I just converted the files to jpegs to post them here so the sizes might not match on the screen...

One other thing to check...
Are you viewing the display at 100%?
Photoshop's OpenGL-based image resizing algorithms are smoother and fuzzier than they used to be (or than they are with OpenGL disabled). What I'm getting at is that you may be perceiving fuzziness in the display that's not really there in the image.
How does the fuzziness look if you zoom in a lot?
-Noel

Photoshop CS6: Pros and Cons of Using Smart Objects

I haven't had Photoshop CS6 for that long, and have only just got past feeling uncomfortable with using Curves, now I've learnt how to use them properly.
My concern is - I am currently learning about Smart Objects. The concept, at first, seemed like 'the best thing since sliced bread', being able to non-destructively use filters, Shadows/Highlights command, Unsharp Mask, endlessly scale using Free-Transform etc etc, without harming pixels at all.
However, the more articles I read about their use in Photoshop, the more I am afraid to start using them in my workflow.
I understand that when you convert to a Smart Object, this process is non-destructive, i.e. I can perform as many readjustments to a filter, for example, and Photoshop will always work from the embedded container file (which has had no filter adjustment made to it) to adjust the filter to your most recently adjusted settings. If you later decide you don't want to use a filter at all, and rasterize the Smart Object back into a regular layer again, is this process non-destructive as well?
Then there is this article, which I struggle to understand properly:
http://bjango.com/articles/smartobjects/
Please see the part 'Smart Objects Created in Photoshop'. It seems to say I can't scale with a Smart Object without causing interpolation and blurry edges. Please can somebody clarify what the writer of this article is trying to get across, because it is well documented that Smart Objects can be endlessly rescaled non-destructively.
Please understand I use Photoshop primarily for editing photographs.

There is much modern focus on "non-destructive" editing, but keep in mind if you don't overwrite or destroy the original file there is no destruction at the highest level. Put in layman's terms, you could always start over with the raw file.
That thought segways into my next one: Non-destructive editing makes sense if you need to use the same information for a variety of somewhat related purposes, or if the work product may need to change (e.g., to suit the whims of a fickle client).
But at another extreme, if you're editing for a particular purpose - say creating the best possible print from an exposure - sprinting right for the finish line by changing pixel values directly and being done with it can be an extremely effective approach. This requires that you get things right the first time, and that takes practice.
Some folks do their Photoshop work by building up layer after layer and using smart objects, smart filters, etc., and this can be effective but no computer has yet been built that can composite all that stuff in real time with a big image. So there IS a cost to doing it. What you might gain by being able to re-do things, you might not have needed to gain if your control responses were instantaneous and you could tweak the intermediate result at every step very easily. Note the number of posts about how slow Photoshop CS6 is/was at editing deep documents, some by people using 2012 computers.
As with most things, it's horses for courses. It's good that Photoshop gives us rich tools and choices for how to work.
Regarding your specific question, bear in mind that what's communicated to the parent document from each of its embedded Smart Objects is a flat, rasterized image. Think of the embedded smart object kind of like going off and opening another document, making the changes you want, saving the document, then flattening it and pasting the pixels into your parent document.
In the very first example in the linked article, they show how the smart-object-rasterized image of a vector circle, subsequently scaled by resampling the parent document in which the Smart Object is used, becomes fuzzy as it is scaled up. Once you understand this you realize that of course you could scale up the smart object itself, e.g., to a size equal to or larger than what's ultimately needed by the parent document, and then it could be crisp in the parent document where it's used.
Of course, having all your smart objects at a size larger than you need takes up even more resources.
-Noel

Smart object conversion- fonts required?

Similar Messages

Maybe you are looking for