Smart object / Auto save bug

MacPro 1.1, OSX 10.6.8, PSCS6 Beta
Came across the following, which I think is a bug.
I have two ducuments: D_test_00042.psb and D_test_00052.psb.
Each were build using a few layers and a group "Retouch", and then converted to Smart Object. So both files contain a (different!) Smart Object called "Retouch".
If I open both files, and doubleclick the first SO, then go to the other and do the same, all works more or less as expected:
However, if I open one file, and doubleclick the SO, then close the original file (to save on system recources), thén open the second document and doubleclick the SO in it, I get a warning "The disk copy 'Retouch.psb' was altered since you last opened or saved it. Cancel / Update":
Cancel obviously won't open the second SO, Update updates the SO that's already opened (which belongs to the other document)
(History palette in the top center, shows "Update from file")
Message was edited by: Rene-) for exact workflow and screenshots

Follow up: PSCS4 (11.0.2) behaves the same, so it is probably something I never noticed before (which is surprising, since I didn't alter my workflow) and has nothing to do with Auto Save…
I'll make it a feature request then: Fix this. Use unique names 'internally' for SO's.
I want to be able to open a SO from an older document for instance to be able to copy paste from one SO to another.

Similar Messages

How do I disable linked smart-object auto-update/refresh?

Working in the CC3D features, I am constantly making changes to my bump map. Every time I step-backwards, or make a significant change to the bump texture (smart object?), CC auto-saves the layer. This specific file is a very very large document (3 gigs in the bump texture layer alone), and the 3D layer has lots of lights and is very complex. This auto-refresh/update really bogs down the time that it would take me to make my changes. I have a very fast machine (I know it's fast, I dont need to list my specs), and I have all shadows disabled.
How do I disable linked smart-object auto-update/refresh?

If you do not like a feature like smart objects there is nothing forcing you to use it. Use some other features to do what you want. Please don't ask Adobe to introduce bug into smart object support.
You could work on your bump maps textures in external files. When your done some time in the future you could edit your project with the smart object layer and use replace smart object. Only then will all smart filters be applied to the smart layer with the replaced smart object.
Or if by CC Auto save Layer you referring to CC Generate feature you can disable that feature.
I have no idea what your referring to when you write "CC auto-saves the layer" being a feature. I know CC Generate will write layers out as web files but that more a Web feature then a 3d feature. Where do you see your layer being saved?

FURIOUS! Warning: Undo Bug and Auto-Save Bug

So I'm pretty ticked off right now. I generally liked FCPX and its changes contrary to many others' opinions, but I just came across a bug that ultimately was worse than I thought.
During my editing process, at some point I was unable to undo changes. It was greyed out in the toolbar, and Command+Z wasn't working. It was annoying, but I didn't think much of it or bother to restart FCPX because I was in the zone and didn't want to stop. Eventually, I decided to restart FCPX to see if I could fix the bug with a lull in my edits. It closed out as normal.
When I re-opened FCPX, I found out that my project was at an EARLIER state. From what I can guess, when the undo bug happened. So, during that period of time, NOTHING was being saved. Since you CANNOT auto-save (I know you can duplicate a project, but Im not interested in that, I just want to save a copy manually), there is no way I can recover my edits. I lost about an hour or so worth of edits. Since FCPX doesn't support "versions" yet either, there is no way I can retrieve it.
I do not know if this is a bug due to 10.7, nor do I really care. I sent a bug report because this needs to get fixed. I consider you do the same but AT THE VERY LEAST, be mindful of this bug. If you suddenly can't start undoing, either STOP IMMEDIATELY or duplicate your project (maybe that would work). I'd hate to have someone else go through this problem too.
Sorry if this message is written poorly, like I said, I'm pretty ****** that this key function (Apple's ONLY way to save) failed.

Thanks guys for the tips. Unfortunately though stuck, I don't know if the finder trick will work. Remember, I never really had the file LOST, the changes were simply not writing to the actual .fcp file. So if I copied it in Finder, I think it would just copy the .fcp file which is currently not getting saved to anyway. Maybe duplicating the project in FCPX would work, but again I think that just takes the .fcp file and duplicates it. If it's not writing to it, then its a moot point. Oh well.
As with anything that frustrates anyone, I've cooled off haha, and doing the re-edits actually seemed to turn out easier and better then second time (you know, as theu naturally are I suppose haha). Obviously all sorts of problems happen with technology, its just a shame that its a bug that revolves around the ONLY save feature haha.
HOWEVER. I think I have replicated the problem, and MIGHT know the source of it. Or at least one. If someone wants to try this and confirm this? I'm running OSX 10.7 and FCPX 10.0 (obviously), however I encourage someone with 10.6 to try it too.
I noticed the "undo bug" (and thus the auto-save bug) happens when I took one of the "fader handles" (I don't know the actual name, but its the little marker-like icon found at the start and end of audio tracks, which when dragged, let you easily make a fade in or out. If you take a fader-handle, an drag it ALL the way BEYOND the length of the clip, it should get stuck. Youll notice you cant easily make a change to it again, and you can't undo it. I think this is what causes the problem, as I think this happened twice to me.
If this is it, I hope I can find a way to flag this for Apple so it can get fixed! At the very least we can be concious of it.

FCPX undo / auto save bugs + RAM Hog - Possible Fix?

Hi there FCPX users,
I have a 8-core 2010 Mac Pro with 16GB Ram and the stock GPU running Lion 10.7.2
I have been using FCPX since day dot, and have been overall very pleased with its super fast work flow and realtime capabilities.
I have completed over 100 3-4min edits with average project size of 50GB, and a bunch of wedding edits with approx 150-200GB project sizes. The issues I had with 10.0.0 - 10.0.1 were mainly FCPX quitting unexpectedly.
And now on 10.0.2 I have expereinced the well known auto save / greyed out undo bug. I have gone through all the steps via apple care which included:
Trashing the Prefs, repair permissions, check drive space / correct format, new user account and clean install of lion / Final Cut X.
I am still experiencing this issue. So yesterday I purchased another 16GB Ram totaling now to 32GB Ram, and I monitor the RAM usage via "Free Memory".
I Noticed that if my RAM is running low, I "free Memory" without quitting FCPX and continue to work as normal, and so far I have not yet experienced the issue again.
Dont know if this is a temporary fix, but it has worked for an hour long edit (approx 6-7 hrs without restaeting FCPX).
Also, I have noticed FCPX will eat up 16-20GB RAM quite easliy.
Not sure if this problem is related to RAM...
My 2 cents.

You have to really be conscious when you start a new project and how and where you manage your footage.
No one has complained more than I have about FCPX's quirky behaviors and it can be frustrating. I have worked with FCPX since day one, even tried to get a refund but couldn't. After using it for a while now, it is very easy to get used to how fast some elements are in editing and reviewing a lot a footage. But several things you have to make sure of that will keep the rendering speed up and less crashing happening.
First make sure that you can see how much space you have on your drives by right clicking in the main window of you screen and make the necessary clicks form the drop down menu. Make sure any drives you have been doing projects with lately are hooked up and do a secure empty trash. Its cool to see how much space you regain. 2) make sure that FCPX, Motion and Compressor (if you have those are installed on your boot drive).
3) Create a FCPX Projects folder on an external (FW800) with at least 75% of its drive space available if you do not have secondary drive installed in your computer. (Its very important to note that any drive you use for any aspect of editing should never be more 75% full, especially your boot drive.) This is where FCPX will log all of its operating files for all of your projects.
4) Either copy all of the other FCPX files from your main hard drive and paste then into the new folder you created. Then delete all of those files, as well as any Motion files too! (Do the same as you did for FCPX in the previous step)
5) If you need to move all of your music files to another drive as well. If its iTunes, you will have to tell iTunes where to look for the new files and it will populate accordingly. This will free up a tremendous amount of space. Make sure to delete them form the main drive.
6) Remove any junk programs form the boot drive (main) or move them to another drive if possible.
7) Now do another secure empty trash and watch your drive space return.
8) Now open up FCPX and make sure you only create projects on your new drive by clicking on that drive in the project window. Any older projects you can simply pull them to the other drive and you will be prompted on how to duplicate that project and all its files to that drive. Delete the other ones.
9) Only capture footage to you external drives. Save it there until you need it.
10) Create all new projects on the secondary drive and pull any footage you are working with on that drive as well. By keeping it all off the Boot drive FCPX will run much smoother and faster, especially if you have at least 16g of Ram, which I recommend.
So to re-cap:
1. Keep your boot drive lean. Delete anything you can move to another drive. Do not set up events and or projects to it...never!!!
2 Use you secondary drive for your project files and the video you are working with in your events.
3. Store raw footage on a FW800 drive ready to move to your secondary drive.
4. Use secure empty trash after all editing sessions when you are certain of your trash contents.
Doing these things have greatly increased much more consistently faster render times and much fewer crashes.
iMac 27 - 3.5gh - 16GB Ram - Quad i7 - 250SSD/1TBesata - External FW800 Drives
Good Luck

Problem when extracting Smart Objects

I am having a problem when extracting Smart Objects.
I work for a small pre-press company. We are working on several computers using one Job Server. Some of these computers have different versions of OS.
For one of our clients the company uses Smart Objects as a precaution for moire issues. The child file stays a certain size, while the parent file is sized down for print. Our client has started to request the larger Child size image for their use. For the volume of images requested, I have made an action out of Photoshop to open the smart object and save out a flat tif of the larger child file image. Here is the problem...
At times the smart objects child file does not retain the name of the smart object layer as its being extracted. What could be causing the lost connection between the parent file name to the child file name, and is there a way to prevent it in the future?
Thanks for your help:)
DVan

Hello,
I have noticed that. The true problem is that the child files name starts out as the parent layer name, but then somewhere down the line it turns wonkie, starting to be named things like 12.psd etc. Please see attached. Your can't re-save the name of the child file either because all that does is save out a named temp file that does not get linked back to the parent file....so what is making the name change?

Replacing smart object content using Droplets ???

Hi,
I have a .psd with a smart object as one of the layers.
I could easily go to Layers>Smart Objects>Replace Contents...
but I have a couple of thousand files to replace.
Is there a way to create a droplet so i can just drop the files into it
and it automatically replaces the content of the smart object
then saves out a new file for me?
This would help me tremendously.
I would appreciate any help.
Moo...

In my opinion this task will need some Scripting unless the Layer-names and Layer-structure are identical in all the files.
One should be able to include the Script in a Droplet, but one might just as well use a dialog within the Script itself, I guess.
If you should find no other option you might be able to get some help in the Photoshop Scripting Forum.

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.

Bug? Camera Raw Smart Object Can't Be Edited

I have a problem where a raw file placed as a smart object can't be re-edited in CS3. Here's how to replicate the problem:
1. Open a JPEG or TIFF as a Smart Object (may happen with other file types).
2. Go to Layer > Smart Objects > New Smart Object via Copy.
3. Double-click the top smart object and make changes in Adobe Camera Raw.
You should now be able to hide/show the top layer (the final)
to see the bottom layer (the original.)
4. Double-click the top smart object layer to see that it properly opens Camera Raw allowing you to make edits (this works for now but will stop working when we encounter the bug in a moment).
5. Save the file and close it.
6. Re-open the file and double-click either of the smart object layers to edit them. Instead of Camera Raw dialog opening, the image in the window changes to the original unedited version. This is a bug and doesn't happen on every image, but it always happens on at least some of my images.
There have been times when it works, but the next time I open the file it stops working. Some of my files allow editing later without problems. Truly weird. Has anyone else had this problem? Is there a workaround?
I have applied all updaters, so that means I am using Photoshop CS3 10.0.1 with Camera 4.4.1 on Mac OS 10.5.2. I have also trashed preferences for Photoshop and Adobe Bridge. I've also Purged the Adobe Camera Raw Cache in the Bridge. This happens on both my Mac Pro (3GB RAM) and MacBook Pro (4GB RAM) so it's not just one machine.
Thanks in advance,
Dan

Hi Daniel,
Stumbled on your post while searching on a similar issue. I'm not sure if I precisely understand yuour problem, but here's my experience when dealing with TIFFs and JPEGs embedded as Smart Objects in CS3...
If the Smart Object layer contains a TIFF or JPEG that has already been edited and saved in Camera Raw (i.e., the embedded file has Camera Raw XMP metadata in its header), then Photoshop will open the Smart Object's contents in Camera Raw... with one provision. You have to make sure that in your Camera Raw preferences, under "JPEG and TIFF Handling", that both boxes are checked for "Always open JPEG/TIFF files with settings using Camera Raw".
If those boxes aren't checked, when you try to edit the contents of a Smart Object layer containing a TIFF or JPEG with Camera Raw settings in its header, instead of opening the embedded file for editing, Photoshop seems to simply revert to displaying the layer without the settings applied. I'm unsure whether this is a bug or intended behavior, but it seems to be one of the symptoms you describe.
On the other hand, if you make a Smart Object layer from a JPEG or TIFF that does not already have Camera Raw settings in its header, Photoshop CS3 will never open that layer's contents in Camera Raw, regardless of what preferences you have checked. Instead, the contents are opened in a separate window as a temporary .psb file. The only way I've found to do Camera Raw editing in these cases is to export the layer, edit the exported file in Raw, and then re-import it via Replace Contents.

Photoshop bug: Smart Objects overwriting other Smart Objects when edited and saved in Illustrator

Experiencing issues when working with a large number (over 200) vector smart objects brought into Photoshop CS4 from Illustrator.
Things seemed to be going along nicely; if I needed to edit a Smart Object, I could double-click it, it would open in Illustrator and then I could edit and save it. Return to Photoshop and the Smart Object is updated. Swell and dandy. The issue started happen when I hit a large quantity of either vector smart objects (remember, over 200) or the many layers and groups within Photoshop (must be over 500). When I would double-click, open, edit, and save the vector Smart Object, the Photoshop Smart Object I was working on would update AND another/several other Smart Objects would update as well. Which, of course, would ruin the artwork, as suddenly I was seeing several instances of the same object. If it hadn't have been for ForeverSave, I many not have recovered the work.
It's rather hard to isolate the issue to see what's causing the problem. Here are some of the possible causes:
Running Snow Leopard on Mac
Many, many Smart Objects in file, perhaps enough to ruin the naming convention and cause bugs when Photoshop referenced the temp file
Many, many Photoshop layers and groups
Illustrator vector files copy+pasted from several different files (affects the naming convention perhaps?)
Some groups/layers in Photoshop are duplicates
To help make it a little clearer, you should know:
Running the most updated software / OS (that is until CS5 comes out)
Smart Objects showed no error until I had actually opened, edited, and saved the referenced temp file (i.e. VectorSmartObject1.ai)
Files saved and worked on from Dropbox (network folder)
Not looking for much of an answer to this question; I just wanted to see if anyone else had come across this bug. Also, Adobe PLEASE look into this as you begin testing for the next update. I have the file(s) if you need to replicate the issue. My best guess is that the naming convention of Vector Smart Objects has an odd character limit so when Vector Smart Object 200.ai is saved, Vector Smart Object 2.ai gets overwritten.

Have you tested this with Photoshop CS5 and Illustrator CS5? (the current versions, that came out last month)
If you duplicated a smart object layer, both layers refer back to the same file content. So when you change the file, both layers would be updated. That is intentional and explained in your manual. If you didn't realize this, that could explain what you are seeing.
If you placed separate files, then they should not be updated at the same time, because they will refer to separate files.
Yes, Smart Objects only update when you save the file.
You would need over 4 billion smart objects in one document to get Photoshop confused about which one refers to which file. And since the layer limit is much less than 4 billion, I doubt that is the cause.
There is no naming convention involved. We don't limit the filenames (except to platform standards and to include a file type extension).

Smart objects uneditable -- bug ?

When I try to edit smart objects via right-click>>edit contents (or double-click on the smart oject layer icon for that matter) this happens:
A.) if I disable [preferences>>file handling>>prefer ACR for JPEG files], PS calculates some seconds with intense HDD activity and then nothing happens visually, no window opens-up for editing, but the history log has the usual new entry "edit contents". Repeated tries result in repeated "edit contents" logs, but no visual changes.
[[In one instance the raster grahpic encapsulated into the smart object got enlarged by 200%-300%. But again, no window opened up for editing. I hit "edit contents" 3-4 times and I could always reproduce this. But ever since that day, it never happened to me again).
B.) if I enable [preferences>>file handling>>prefer ACR for JPEG files], ACR launches and displays the raster graphic the smart object is based on. Upon closing ACR, no window opens-up for editing the smart object.
I have been working with smart objects for some months now and everything worked fine. This bug started occurring some 3 weeks ago, but as I said, sometimes it works, sometimes not. I cannot find any regularities as to what could lead to this malfunctioning. The only regularity I found so far (but could be a coincidence) is that the smart objects affected by the bug were always (at least I don't remember any other case) .jpeg files that I opened in Photoshop(CS3) with abovementioned preference set so that ACR launches upon opening a .jpeg file. In ACR I alt-clicked the open button so that it says "open objects". So the smart objects were always based on a single layer .jpeg raster graphic opened in ACR.
My best bet would be that there is something that ACR writes into the smart object that isn't 100% identical to the way Photoshop would write smart object if I:
1) open the .jpeg file in ACR
2) click open/open copy (not open object)
3) convert the raster graphic to a smart object inside Photoshop itself.
But that's only a guess. I have quite a lot of work to do currently, but I hope to be able to provide additional information quickly enough if need be.

OK, going back to the issues I was (a bit incorrectly) describing in my OP:
I’ve been monitoring CS3’s behaviour for the past couple of months and I’ve tried to summarize my observations in a table (see attachment). As you can see, jpegs handling inside smart objects is far from uniform, given the different jpeg-opening possibilities and the interference of different “prefer ACR for jpegs” settings.
I think it’s okay the way it is, but I can also imagine people finding all these combinations a bit confusing and wishing for a more consistent handling (in this regard see also footnote 5 and the bugs).
I hope the table is rather self-explaining. Basically I combined different opening methods with different “prefer ACR 4 jpegs” settings.
For example, the fifth line reads means: disable “prefer ACR 4 jpegs” ==> open a jpeg file in ACR via file>>open as>>filetype:Camera Raw ==> make adjustments in ACR ==> click on “open object” ==> open a new document ==> drag&drop the SMO there ==> transform the SMO ==> enable “prefer ACR” ==> edit contents of SMO ==> ACR opens ==> make adjustments ==> click “OK” ==> SMO is updated ==> check if one of the two bugs occurs
OK, what are these bugs now? I’m not quite sure, but I doubt that it’s by design. Concerning what I’ve called the “auto-resize-bug” (for a lack of a better word): In the second and third case presented in the table, the SMO is updated according to the ACR color modifications but also …. resized! (always downsized as far as I’ve seen).
The “transform-resize-bug” is a problem that occurs from time to time, but I haven’t found a way to reproduce it. Once a smart object is affected by the bug, you can still move it around as you wish, but once you use “edit>>free transform” it mysteriously shrinks in the same way as observed in the “auto-resize-bug”. For some users it might not be a big deal, as you can just enlarge the SMO again as you please, but it can be quite annoying if a SMO has been precisely fitted into the document and you have to redo all the fitting (the values like width/height % won’t help you, because they’ve stayed the same, for example 180%, whereas the SMO has shrinked to a quarter of its size).
If not already fixed in CS4, I guess it would be important to look into this for future releases.

Photoshop CC 14.2 Smart Objects Bug

Hey,
While updating to the latest Photoshop CC 14.2 (today, 17.01.2014) I've found a huge bug with the traditional smart objects behavior.
I recorded a video. Please, take a look on it.

SG... wrote:
Hi Herbert2001,
What do you mean by 'smart objects do not update in realtime'? Can you outline steps to exhibit the behavior?
regards,
steve
Suppose you wanted to create a mirrored setup with two or more smart objects, or your project consists of multiple smart objects that are used throughout the design as repeatable patterns (let's say jewels, or textures).
So you open the contents of the smart object in a new window, and arrange both windows horizontally. Now draw in or change the smart object's contents - nothing happens in the main project. The user is forced to save the smart object first before the changes are applied. In effect a new separate file is generated.
Very cumbersome. Even more counter-productive is that the user cannot edit a smart object's content in place in the original file, and that Photoshop opens a new window instead. (I understand that external files like Illustrator cannot be edited in place, but Photoshop elements should really have that option.)
All of this severely breaks the workflow. An alternative workflow is presented in Photoline: the user is able to create virtual clones/instances of any type of layer, layer groups, and layer masks, and when the source layer is edited in some way those changes update in real time cascading throughout the project. No need for the content to be opened in a separate window. Also worthy of note is that the changes are applied while the user draws or changes the vector shape(s) - which makes it incredibly useful for mirrored painting, to cite just one example.
Flash also offers this type of functionality: double-click a symbol, and the user can edit it in place. Changing the object automatically updates the other instances. Unfortunately even Flash does not update in "real time", only after you made the changes does it update the instances.
All in all, dealing with smart objects in Photoshop is a bit of a pain compared. Just not a very well thought out feature, in my opinion, and in dire need for an update - the externally linked content is a step in the good direction, but the actual implementation of "smart objects" is rather "dumb". ;-)

Blurry smart objects in Photoshop Save for Web jpegs

I create graphs, etc in Illustrator, place them as Smart Objects in a master Photoshop file before outputing Save for Web jpegs to use as PowerPoint slide backgrounds. Everything created in Illustrator or Photoshop through that process (Quality 80 or 100 with any of the SfW options on or off) Save for Webs are blurry when imported (at 100%) into PowerPoint. The only way I have been able to get anything crisp in PowerPoint was saving a Photoshop pdf. However, that was only the text created in Photoshop. The Illustrator Smart Object part was still blurry. Anyone have any idea on the best process to combine Photoshop and Illustrator files into one file for import into PowerPoint as a clean, crisp background? At this point I am open to all suggestions.

There are parts that are being added in Photoshop, hence going from Illustrator through Photoshop as a Smart Object and then onto PowerPoint. If I wasn't 5 months down the line and just nearing deadline, I would recreate everything in Illustrator. Assuming that I have to continue at this point down the Illustrator through Photoshop line of working, how do you designate pngs or jpegs to be 220ppi. Jpegs have a 1-12 quality (and 12 is still blurry).
Note regarding PowerPoint, I embed the full-page image into the background so others that are using this can't move (by accident or on purpose) the background.

I cannot open a file from LR5 into CC2014 unless it is a smart object. also will not save back to LR at all it gives me an error message "Line: 1 - photoshop.notifyLightroomDocClosed ('lightroom-2.0', 'B53AFA39-A49B-4709-A9BD-0B6467C175C3', 'Macintosh H

I cannot open a file from lightroom into CC2014 unless I open it as a smart object. CC opens, just will not display my image. i am given an error code when I save an image, and can only save to my desktop or other locations, not automatically back into my lightroom.
I am using LR5 latest update, as well as CC2014
Below is the error message:
Line: 1 -> photoshop.notifyLightroomDocClosed ('lightroom-2.0', 'B53AFA39-A49B-4709-A9BD-0B6467C175C3', 'Macintosh HD:Users:BPexposures:Desktop:_DSC5962 as Smart Object-1.psd');

I was also having this issue, and I did some more searching and found this answer in the Adobe forums: Re: Photos from Lightroom 5 to Photoshop CC (2014) and back.... The issue appears to be caused by having not updated Lightroom to the latest version prior to having CC2014 installed (wow that's stupid). The trick seems to be to uninstall Photoshop CC2014 and to then reinstall it after having upgraded to Lightroom 5.5.

Edits to a JPG Smart Object in a layered TIFF file: DOES NOT Save to the originally placed file?

When placing a JPG as a Smart Object (and even multiples) into a layered TIFF file: If I open each layered Smart Object JPG, make changes as a JPG and SAVE the file, I expect the ORIGINAL SOURCE JPG file that was placed to also be saved- I thought that is the file I was editing!
This SUCKS! To capture my edits to the original individual files: I now have to open each layed TIF file, Edit each smart object JPG and SAVE AS to overwrite the original and capture my changes? Is this the way its always been- I don't think it has. How can I edit a Smart Object file in a layered document and ALSO update the SOURCE file?

You should edit the original jpg, and then replace the smart object. There is a utility that makes this easier, if you do many of these. Looks liek this
link_update.zip

How to save a file with smart object?

I have just created a file from LR2, by choosing 'open as smart object' in PS.
I then added a cloning layer and did my cloning.
When I wanted to save the file, instead of PS turning it in into a PSD with the same name, I now suddenly got the 'save as' pop up screen and '-2' as the recommended name. The original folder where the file came from was not shown.
I don't know what that's all about, but I'd prefer it would just save the file as a PSD and automatically show the file alongside the NEF in LR2, like it does when I don't use the 'open as smart object' feature. Is this typical for working with smart objects opened straight from LR2?
Any help will be greatly appreciated.
Marsel

Well, like this you open the file s a smart object, so if you want to now clone on a layer but want it to be a part of the smart object then you go to the layer panel and click on the smart object's icon there to edit the smart object and you hit save (command S) and it will save with that layer to your original.
then when you click the tab or the window that has the original opened as smart object those changes will be reflected, but you will not see your cloned layer active as that is a part of the smart object and you have to open the smart object to get to it.
What you say! Yes that is what I say that is what a smart object is, you are using the smart object as a part of another document( that is why you are being asked to save as, as this new documents you can now make changes which will not effect the original which is the smart object unless you rasterize it which will make it no longer a smart object.
What good is a smart object, well there are many say you are using this document or image if you wish in say five projects and the image has been retouched and it is determined it should have some more work done to it all you have to do is retouch the smart object and all five projects are updated.
You see smart.
And of course you can d things to all five projects that can be different from one another on other layers without ever destroying the work you have done to the smart object.

Smart object / Auto save bug

Similar Messages

Maybe you are looking for