PS CS3 - Smart Objects are "Jaggy"

I've been trying to copy/paste some vector art from Illust CS3 into PSCS3. Regardless of what option I select (Smart Object or Pixels), the artwork comes in jaggy. Tried the same thing in CS2 and had no problems.
I checked the clipboard prefs in both apps, and tried a search on this forum w/o luck.
What am I missing?
Thanks in advance!
Bryan

Hello,
I am having the exact same problem with CS3 - did this get resolved? What does 'trashing' your prefs mean and does any one have settings for correct pref for PS and AI - I would love you forever if someone could sort this for me, bloody deadlines and technology
Much love.x x

Similar Messages

LR 2.1 Softproofing with CS3 Smart Object

I have seen Jeff Schewe use a duplicate of the image to smart proof at least until Adobe gets this in LR (Can't Wait!) but some discussions say edit in a smart object.
What advantage does this have over the way Jeff does this and is it done the same way with a duplicate image?

My problem might be of a similar origin.
I have also posted it on a different thread http://www.adobeforums.com/webx/.59b6903c
I use mostly Hebrew characters for Keywording (the file names are in English) after opening in CS3 and saving, the keywords are converted from Hebrew fonts to accented fonts like åäöÅÄÖ.
This didn't happen in LR1 and does not happen if I use CS3 as my secondary editor (not using the new LR2 edit in CS3 functionality)
Shai

PS CS3 - Smart Objects resizing when updating resolution! Help!?

My company has built many multi-layered files using Smart Objects in CS2. When in the past we have made resolution changes to the smart objects and updated them in the parent file, they have stayed at the same size, with only the resolution changing.
Now, when opening in CS3 and performing the same action, the Smart Objects now re-size to match the parent file's resolution and the height and width changes!
Has anyone else experienced this?
It is quite disturbing that this feature has changes since we have come to rely on it in CS2.

Yes I've tested this in both CS3 and CS4 - you are right, the problem you describe happens in both. Your problem was very well described.
Duplicating linked layers has always been a little odd in the way it behaves (ever since grouping and nested grouping was introduced) - it seems to be that it can't hold complex linked relationships when duplicating the layers.
No solution at present I'm afraid

Pasted smart objects are distorted in CS6

Any time I paste an object from AI into PS, it's getting horizontally squashed. Here's an example:
1. 12x12 pixel circle in Illustrator, aligned to pixel grid.
2. Pasted into Photoshop as a Smart Object, it's visibly distorted (12x11), but the W/H is inaccurately labeled 100%.
3. After pasted, if I select Edit > Transform > Scale, now the starting W/H are shown with the accurate distorted values.
This is driving me nuts. Can anyone suggest a fix, or is this a bug?

You could be correct that the bad AA is a Mac-only Ps problem. We need more participants to see if any Windows user is affected.
An Illustrator-saved AI or PDF placed into Ps results in the very same bad rendering as a paste. A slightly different but similarly bad AA arises when the placed file is an Illustrator-saved EPS.
The AA bug appears to be related to Photoshop's rasterizing of vector files rather than something to do with the clipboard.
There is no improvement by pasting into a new document created with clipboard dimensions. I had already tried that and I've rechecked now.
Here's an example comparing Ps CS5.1 and CS6 using the same clipboard content. The very same results happen when placing the design as a vector file in the two versions of Ps.
1. Object in Illustrator CS5.1 that's copied to clipboard.
2. The transformation opportunity of the paste into Ps CS5.1. The height is short by a pixel.
3. After correcting the height and committing. A perfect rasterization.
4. The transformation opportunity of the paste into Ps CS6. The height is correct.
5. After committing. A terrible rasterization with gray pixels which should be white.
Other examples will result in the height being initially wrong in Ps CS6 and the height being initially correct in CS5, which is the opposite of this one, and the rendering being differently bad in each version of Ps.

Illustrator Smart Objects are "Linking" to each other in PS file.

This strange behavior started after I upgraded to the latest PS CC which includes the "linked" vs "embedded" smart object feature.
When I edit previously created PS files that contain mulitple linked Illustrator smart objects, an edit to one smart object will update a different smart object within the same file. These are not duplicates of a single smart object layer, they are completely independent smart objects, containing different graphics.
Has anyone else seen this? Is there anyway to break the link between all Illustrator graphics within a document so this won't continue to happen?

Here'a link to the original file. http://adobe.ly/1d6uwA1
This was created with PS CS6. I recently had to do some modifications to it, and that's when I noticed the strange behavior with SO. Of course when I tried to duplicate the weirdness this morning, I was unable to do so. I know for certain though, that on two different occasions I updated one SO layer and the it replaced the contents of a different SO layer.
I did notice some other oddities while playing with this today. Here's what I did.
Open the file, and save with a new name to make a copy.
Edit a couple SO layers with Illustrator
Close the file and save
Open the file back in PS and again edit a SO
This time when I save the SO I get this message "This file has been modified outside of Illustrator. Do you want to continue". I say yes to save it. I only get this message after I have closed the file and reopened it for more edits.
Another oddity; if I leave a SO open in Illustrator by just saving without closing the file. Then close the Photoshop file linked to that SO. When I open a new Photoshop file and try to open a SO within it, PS thinks the SO that was left open is the one I want to work on. I have to close out the previous SO to get the new one to open correctly.
I work with a lot of Illustrator SO's in PS. So I will continue to monitor what happens, and try to pay very close attention to what steps I took if and when the weirdly linked SO layers happens again.

CS3 - Placed objects are duplicated to temp

hi,
I am placing a PSD document into my document. And PS CS3 creates a copy of my document in App data / temp.
I had pointed to a document in my project folder, but it is not linked with the original anymore.
What is the problem?
thnks!

Photoshop placed document support doesn't link to the original file - it embeds the original file.
And to edit that embedded data, you have to put it on disk somewhere (like temp).

CC 2014: are creation and editing of smart objects multiple cores cpu operations?

anyone knows it for sure?
thanks everyone
sam

Chris Cox wrote:
Creating and updating smart objects are mostly just saving and loading files - which is a pretty serial operation.
If you have a transform or filter applied to the smart object, then those steps will be accelerated as the transform or filter normally would be.
Chris that is interesting. We were talking about Smart Objects reducing image size in RAM, and from what you are saying, creating a Smart Object saves it's details to hard drive. Judging by the resulting image size as stated in the Status Bar, the Smart Object uses similar memory to an equivalent raster layer. How does it work if the containing document has not yet been saved as a PSD? I imagine that saving the PSD file must contain the Smart Object information?

Switching off layer in smart object causes it to move in photoshop

Dear all. I am stumped. I have piece of packaging artwork that I’m using in my 3D software.
Smart Objects are great for this as all I have to do is go to Photoshop, double-click the Smart Object, then in Illustrator turn off the layers I need etc and update the Smart Object back in Photoshop and save back out for my 3D software. Only problem is that when I switch off the layer in illustrator and go back to Photoshop to update, the Smart Object jumps half way up my Photoshop file as if I’ve moved it but it also crops it so I can’t even just move it back down as there’s nothing there when I do.
The layer I’m switching off (not deleting) is the die cut for a pizza box, it is still in the Smart Object just not visible. I have tried this in both CS3 and CS4 and it happens both times. I have searched everywhere on the internet for similar problems but can’t find an answer which makes me think I’m doing something wrong. Although I’ve used Smart Objects many times before and this has not happened. I have attached some screen grabs to help with the explanation.
Any help would be greatly appreciated.
Icegiant.
My specs are CS3 (and CS4)
MacPro 2 x 2.8 Quad Core Xeon,
4 GB ram,
512 mb graphics card,
Mac OS 10.5.6

You need to set up an invisible Bounding Box in the Illustrator file. This will be outside the Die cut. This Cropping area can be defined as a Cipping Mask. In Illustrator Object/clipping mask/Make - Command 7. I haven't really experimented with the ins-and-outs of this, and it may also be possible possible with a simple transparent bounding box. But the clipping mask (different to Photoshop Clipping Masks, same term, completely different function),always seems to work in keeping the defined area from moving when you update the Smart Object
Its happening because the outside perimeter of the Smart Object is changing somehow when you delete the object. Photoshop always defines how its going to sample/render the Smart Object based on this perimeter.

Blending Effects + High res. = Nightmare. Smart Objects don't do justice.

When Smart Objects debuted in Photoshop I tried them out and was content to find that there is now something which can scale my styles/blending effects while I resize the object. Previously I'd've had to resize the image first (with the Scale Styles option enabled), and then copying things over to what I was working on. (Simply resizing the contents of the layer itself would not also change the layer Style, which means that it would look different.)
Anyhow; I just discovered that I have been deceived. Smart Objects are merely a raster version of their contents: vector or not. If you enlarge a Smart Object containing vector data, it will look pixelated, yet resampled/semi-smooth pixelation.
So my problem is that I made something (vector-based) on 72dpi, and for example if I want to enlarge the image as well as the resolution to 300dpi, (for print), then the style settings are maxed at their boundaries and the look of the image changes.
If for example I have an Inner Glow blending effect with the Size set to 20px, and I enlarge the image, then Photoshop would scale the Size higher and higher the more I enlarge the image, but if I enlarge it too much, it cannot of course go beyond Size 250px as that is the limit for that effect. (And at that point onwards the look of the image starts to change the more I enlarge it).
I made a 3D-looking sphere/orb using purely 5 or so circle shape layers and blending effects. Nothing else. Everything is vector. I put everything into a Smart Object and tried enlarging that instead, hoping that it would somehow know how to render the layer styles/blending effects no matter how large. So as it turns out, the Smart Object is not even vector. *sigh*.
So what's the solution? Am I using the wrong platform for these kinds of things altogether? Should I be using something else entirely like QuarkXpress and start all over from scratch?
I'm using Photoshop CS3 by the way.... 10.0.1

But I have a concern that if I break it down to 300 images (6 seconds of footage) then stack then flatten the stack until its dont the whole 30 mins then use these flattened ones to create a new stack it would affect results as it will then be working with images like the above.
That should be easy enough to test (if maybe not exactly proof) – for Range it seems to make no difference, for Variance it seems to do.
Also why use 16 bit image mode?
To reduce the accumulated effect of the necessary rounding of pixel values.

Smart object within another smart object

I'm running photoshop cs3. I created two different smart objects. Within each of those smart objects, I want to include another smart object. However, when I update the embedded smart object, only the partent SO is updated, the other SO seems to have a different child. here is the setup visually:
canvas -> SO1 -> SO3
canvas -> SO2 -> SO3
so when I update SO3 from within SO1, only SO1 is updated - SO2 stays the same. is there any way to have updates to SO3 affect all its parent SOs?
thanks

Bart Cross wrote:
Smart objects are not really that smart after all. Yes PS uses a version of the original object, not the object itself.
Furthermore, I would add they they aren't even OBJECTS!
The very concept of an object is that changing it would affect all instances of that object, no matter where it is included, intended to save development time on complex projects.
http://en.wikipedia.org/wiki/Object_(computer_science)

Photoshop document with smart objects changed when I apply color profile. Why?

I work in Photoshop with smart objects. When I apply color profile smart object are changed. For example change filter or change size. I dont now why?
See image

Yes, fortunately, I am a Windows user, but I don't want to start a religious war here And it is also possible to run multiple versions of Adobe products simultaneously under Windows - why shouldn't that be possible? Currently I have CS3 and CS4 and somtimes use CS3 when CS4 is just too buggy to get the job done. Before that I had CS and CS2 on the same machine.
But I wouldn't keep all versions back to PS 6.0 or CS, that would be a bit too chaotic and I'd had to spend days of installing if I get a new computer. I expect those programs to be a little bit backwards-compatible, so I don't have to use many different versions. And for Photoshop, this is mostly the case. It's just very tiny details like Smart Object resizing that seems to work differently.
Otherwise I'm really happy that in CS4 I can finally link Masks to smart objects and apply warp and perspective on them, that's a big plus!

NEF file opening in CS5 as a smart object

My CS5 recently started opening up all my Nikon raw files as smart objects. I don't want that. How do I make it stop? This never happened before nor am I aware of me changing any of the settings. Any help would be great. Thanks

I never changed anything in my preference that i'm aware of. I don't even
know what smart objects are. Nor did I want it in the first place.
To clearify. I usually open a folder containing NEF files and then drag and
drop the file over the CS5 program in my dock. Then it brings me to the
Camera Raw menu and I click open and then it opens the file as a smart
object. TIA

Linked Smart Objects from Photoshop CC

Hi
I have a Photoshop file which makes use of the new Linked Smart Objects (introduced in the last major CC update). If I create a Reflow Project out of this .PSD the Linked Smart Objects are not being converted.
Am I doing something wrong or is it simply not implemented yet?
Cheers

If that's the case then keep the main grid container at 100% and then just add two boxes inside it. The outer one also stretch to 100% and have the inner one stop on column on either side and set the max-width on that. You could also just have the inner one strech to 100% with a max-width and have the underneath one show on the side only when it get really wide. I know it feels a little akward to use the grid like that, but we only have one container that the grid is on right now so this is what we can do. Here's an example using yellow for the outer container and red for the inner.
Hope that helps and thanks again for using Reflow!
Chris

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

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

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

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.

PS CS3 - Smart Objects are "Jaggy"

Similar Messages

Maybe you are looking for