PS 14.2 Smart Object Bug

A quick screencast demonstrating a bug in Photoshop where it gets confused between two instances of the same Smart Object, in two different documents.

Hi,
This has been reported and we're investigating a fix. As you've noted, this bug happens with copied Smart Object layers (even in the same document).
Sorry for the introduction of this bug.
regards,
steve

Similar Messages

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". ;-)

Smart Object Bug?

When I edit Smart Objects in CS5.5 they open in their own window; meaning I only see the smart object in my new window when I chose to edit. In CS6 I am seeing the actual document I made the Smart Object from, as well as the Smart Object when I edit the Smart Object, AND it has its own rounded border that when saved out, does not appear - it is taking that from the original for no reason.
Windows 7 Pro 64 Bit only. I did not install 32 bit.

Hi Zeno,
Thanks for the suggestion. Resetting the temp directory to another location is a good workaround. I was having the same problem with another program, CuteFTP, and changing the temp dir fixed its problem too. I had previously tried running in Compatibility mode, Administrator mode and both together but none of those modes helped.
It would still be nice to know why Windows 7 denies access to its own temp directory but at least now, I can get back to work.
Thanks,
David Salahi

Smart Object woes!

Most serious users have been greeted by Smart Object bugs. They're frustrating.
Check this one out.
http://feedback.photoshop.com/photoshop_family/topics/smart_object_rendering_bug?rfm=1
Ever happen to you? What causes it?

Photoshop's real power is in its ability to combine many features and functions modally that lets you get just what you want done.
Photoshop's real power to confuse is in its ability to accumulate modality in various places that cause something undexpected to happen.
Yep, we've all done it.
Glad that was an easy one.
-Noel

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.

Bug or feature: opacity and blend-if values wiped out when convert layer to smart object

I had some unexpected results in an action I put together. As I was stepping through it, I found that conversion of a layer to a smart object reset the opacity to 100% and removed any blend-if adjustments, though the blending mode was retained. This is certainly an unexpected effect--is it a bug?

Smart objects are always created at 100% and will wipe any other blending, the blending still exists WITHIN the Object, itself. This is the most logical and sensible way for it to work - you will realise this if you think it through. Blend modes on the other hand are sometimes copied from the source layer or Group, this is possible and its a kind of shortcut.
To get the original blending into the Smart Object layer - Open the Smart Object, right click on the layer with the correct bending Choose "copy layer style". Now Back in your master document you can "paste layer style" into the Smart Object layer.

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.

Possible bug when opening NEF-images as Smart Objects in PS CS3?

In architectural images I often apply lens corrections (Rotation, Distortion, vertical Transformation) to my RAW (NEF) images.
When I open such an image in PS CS3 as a PSD all is fine, that means all the lens correction is applied.
But when I open the same image in PS as a Smart Object the lens correction is not applied, i.e. PS shows the image with all LR-editing (such as color temperature, exposure, contrast, etc) except for the lens correction data.
What is wrong here?
I'm running LR 3.2 and PS CS3.
Thank you for your input.
ErnstK

Thank you for your answers.
It occurred to me - and Ian's post seems to confirm this - that PS CS3 is not fully compatible with LR3.2.
When I chose <Edit in CS3> (to open the image as PSD) I get the message that my Camera Raw plug-in is 4.6 and it gives me the choice to <Open Anyway> or to <Render by LR>. I usually chose the latter and I assume that this is technically an Export.
When I chose <Open as Smart Object> it just opens the image in CS3 without any dialog in between.
I guess it's time to upgrade to CS5.
Thank you all.
ErnstK

Bug in Smart Objects?

Dear Community!
I stumble over the following problem and hope, some of you might be able to help me.
Scenario: Several layers (art and text) are forming one element that is then converted in to a smart object. Seen as smart object, there is a part of the original content missing (see attachment). It appears to me, that Photoshop is cropping the elements of the smart objects to the smallest size possible. Therefore I included a background layer, which is slightly larger than all the other layer contents. Still PS does cut some of the content. Why and how to avoid?
Thank you for digging in to this. I'm happy to read your smart answers.
Andreas

Please repost in the Photoshop forum.

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?

How to Turn Off "Open As Smart Object" ??

Help ! I am using PS CS3. I opened a JPG file as Camera Raw using "Open As Smart Object" just to see what it was all about. Now, when I use just "Open As" to open a JPG as Camera Raw, at the bottom of the CR dialogue, instead of "Open Image" it continues to say "Open Smart Object" even though I did not specify that I wanted to Open As Smart Object. How do I get back to just Open Image in the CR dialog. I have the latest version - is it me or it a bug ???

Links do not seem to have a high discoverability in a software.
A drop down list would not take much more screen real estate, I wonder why they got scrapped in favor of hyperlinks.

Illustrator Application Window Resizes When Opening Smart Object from PSD

Hi All, I've taken a vector graphic created in AI CS4 and pasted it into my PSD CS4 doc as a smart object. When the original AI file was created the application window was set as I preferred it, filling my screen. When I double click the Smart Object in PSD to edit it back in Illy, the window that contains the application has been switched off of the fill screen mode and is quite a bit smaller. I know it's small but now I have to click the maximize icon in the application bar to get Illy to fill the screen again. It wouldn't be so bad once, but the application window resizes itself every time I punch back into the smart object from PSD.
Any ideas on how I can get the AI environment from switching around on its own??
Win 7, CS4, all patches current, Dual 22" montiors
thnx,
jeff

I just want to point out that when you open the smart object of course it is not the same file as the original but an embedded copy of it.
That might also have something to do with this issue and might also be a photoshop issue with the smart object and one reason might be that Photoshop is see the image as resolution and Illustrator sees it as a dimension and the teams might be able to do something about this but might not actually be aware of it unless you file a report even if it is not a bug it would then be a feature request.
They might not be able to do anything about it but then there might be a clever engineer with an idea, so it might be worth the report.

PS CC Video Layer Smart Object error

I think I have found a bug, I'd like to see if it's reproducible for others. I don't know what the actual error is, but the error message says 'Photoshop could not complete the request because of a program error' (which I'm guessing is just a general error message that could be any number of things). To cause the bug, create a new blank video layer, and draw something on a few frames. Convert the layer to a smart object, and make a copy of the object on the timeline. Add transform key frames to each layer. Save the file. At this point, the file should still be able to play what is on the timeline (for me it does). Close the file, and attempt to reopen. PS should be unable to open the file.
Additional Info:
Whether the Smart object is composed of a single layer, or multiple layers, the error occurs.
I've only tested it so far with scale/rotation transformations, may happen with opacity and position
Altering the opacity and position of the second smart object without setting key-frames doesn't cause the error (just altering the opacity from the layers panel for example, or moving the video layer with move tool).
Timeline frame rate doesn't seem to affect it one way or another.
A few times when I didn't cause the issue intentionally for testing, I was still able to open the file, but attempting to start playback would then cause the error, which would crash Photoshop altogether. In those cases, I was able to find that one of the smart object layers in particular would crash photoshop when visibility was enabled/disabled, so I was able to drag all the other layers into a new file, only loosing one layer.
EDIT: Just to add, my question was: Can other people reproduce this bug?

I can also reproduce this bug.
It is also reproducible by creating a regular document.
Add a few layers with content.
Convert a few of those layers into a smart object.
Animate the contents of the smart object.
Everything works as expected. Timeline plays. Looks good.
Save: Get PS error "Photoshop could not update smart object because of a program error"
Save the animated file as it's own PSD just in case.
Close.
Re-open: Nothing works. Cannot scrub timeline, cannot save for web, cannot play timeline, cannot move objects.
Everything results in the error: "Photoshop could not complete the request because of a program error"
I have inadvertently lost a few hours of work a couple of times now due to this bug. It sucks because the work is there right in front of me but none of it is accessible to me.

PS 14.2 Smart Object Bug

Similar Messages

Maybe you are looking for