This content has been marked as final. Show 14 replies
Were there perhaps smart objects involved? Layer groups? There were actually a number of bugs relating to this in CS3 and before, some of which now finally have been fixed. This may however have an adverse effect on your stuff. What does happen, if you import the PSD again? Does it look correct? Also remember, that the pixel aspect ratio calculations have been fixed to comply with ITU standards, maybe that's getting you, too, on some level...
Thanks, Mylenium. I'm testing some things and will post links with screen grabs tomorrow night or Friday. Right now it looks as though AE CS4 is misinterpreting the bounding area of a Photoshop layer. I tried reloading the footage, replacing the footage, resaving the PSD file with PS CS4 and then reloading into AE CS4 with differing results.
The most disturbing was when I moved the contents of a layer in PS and then reloaded (CTRL+H) into AE. The bounding box stayed the same size but the content was 'missing' (out of the visible area I suspect). When I deleted the footage from AE and reimported, the bounding box changed to add the distance I moved the object in the PSD file, and the contents were about where I placed them on the PS canvas. Weird, and probably repeatable. Incidentally the PS layers are text layers with a couple effects (gradient overlay and stroke).
Unfortunately I had to reinstall CS3 tonight because I had a job I needed to do and CS4 left me hanging. Disappointing.
Indeed quite disturbing news. I'll run some tests of my own to see what's up, but feel free to post your findings. Other users with similar issues will benefit from any insights.
If you could post your original CS3 project, even without footage, I'd be happy to take a look. I've not run into similar problems.
Rick, the thing is the new pixel aspect correction. Nothing else. Nothing is compatible with previous projects and other softwares.
OK, I did a little more testing and I think it is not the AE CS3 file causing the problem, but rather the way AE CS4 is interpreting the PSD.
I created a new NTSC D1 comp in AE CS4 and then a new NTSC D1 (Square Pixels) PSD doc. I created a text layer and imported it to AE with Merge Effects and Layer Dimensions. The bounding box is 530 x 160 when it should be 329 x 98. AE is creating the bounding box from 0,0 of the PSD document, rather than the live pixels on the layer itself.
I duplicated the text layer in PS and rasterized, merging all the effects. I imported into AE and got the proper sizing of the bounding box, 329 x 98, the live pixels on the layer.
Then I duplicated that layer and merged the effects to it. When I imported to AE I got a bounding box of 333 x 102, 4 pixels bigger in each dimension, but at least the content was centered in the box.
So it appears AE CS4 has changed the way it determines content position within a PSD layer and varies it depending on the layer type.
You can download the the two files (aep and psd) here to see if you get the same results: http://www.carlcarbone.com/ae_test/ae_testfiles.zip ~ 80k, but it's an easy enough setup to test on your own.
I'm very interested to see if anyone can duplicate.
Incidentally, 9.0.1 did not fix this issue, assuming it is an issue.
Please note that the presets in CS4 are just that; presets that you can easily change or ignore. If you're working with a system that dislikes the correct values; by all means use the old values when you're setting up and rendering your AE project.
The CS4 PAR values are technically correct, it's just that the industry have been ignoring the "blanking" in video for all these years.
- Jonas Hummelstrand
Can anyone please confirm?
It seems AE CS4 is reading the position of transparent text objects from Photoshop differently upon import with Layer Dimensions selected than a rasterized layer of the same position, shape and size.
You can download the the two files (aep and psd) here to see if you get the same results: http://www.carlcarbone.com/ae_test/ae_testfiles.zip ~ 80k - or try it on your own.
Adobe techs? Can you please verify?
If you think that you're encountering a bug, please file a bug report. Keep in mind that this is a user-to-user forum with no official support by Adobe personnel. (Sometimes we help out here because we're trying to be nice, but this forum isn't the best way to get information or requests directly to Adobe.)
To report bugs, send a detailed bug report (including information about the version number of your software, some details about your computer, et cetera) to firstname.lastname@example.org.
You can also submit bugs using the same form that you use for feature requests, if that's more convenient:
Thanks Todd. -Carl
I posted this issue to email@example.com and received a few workarounds until they can determine the cause:
1. Import the layered Photoshop file by setting Import Kind: Composition - Cropped Layers
This option should work, and the individual layers in the Project panel folder will appear correctly.
Once you have imported it as comp/cropped, you can import the individual layers again and they come in correctly. You can also add a layer that came in wrong to a comp, convert it to editable text, then import the layer again.
The simplest way to fix a CS3 project opened in CS4 seems to be to right click the layer, Convert to Editable text, then Ctrl-Z to Undo. That resets the layer to what it should be and matches CS3.
Also try this:
1. Open the CS3 project in CS4
2. Close the project
3. Open the same project again
Jonas, the incompatibility with cs4 and previos version cannot fix simply making another preset, the PAR is not customizable, so i cannot make a preset like PAL 720x576 (1,07) because 1,07 is not present in cs4. Thanks!
Hi Carl, Sorry, had completely lost track of this thread. It seems indeed a bug as Todd suggested. The funny thing is, though, that after you imported it for the first time, successive attempts will always yield correct results, so I would blame it on an initialization issue of the PS engine.