This content has been marked as final. Show 4 replies
Simple: AE will use a higher precision than Photoshop even in the 8bpc/16bpc modes, let alone 32bpc. Photoshop will surely use the same values internally, but it doesn't display them. Dunno why, but PS being the old dog it is, I'm not really wondering... More of a question for that forum for sure. Could of course also be a problem with different color profiles/ color space settings between the apps, so this might be worth checking. Maybe you are using an outdated version of a profile in one of them... A simple solution inside AE would be to simply nail down those values with expressions, e.g.
Otherwise: Stay away from the evil Photoshop. ;-)
If the problem is that the manually entered integer values are slightly different from the more precise values stored in the keyframes, then why not just copy the start keyframe and paste the copy at the end? Then you're guaranteed for the start and end values to be identical. Also, the copy-and-paste operation just seems like it would be more efficient and less error-prone than creating a new keyframe, clicking in its property values in the Timeline panel, and typing some numbers.
"Copy and paste keyframes"
Thanks for the replies.
Workarounds really aren't the problem. Although it can be an issue, it is usually easy enough to track down the item that isn't looping correctly.
This was more of a wonder as to why it is the way it is with PS and AE both coming from Adobe.
One would think / hope they would handshake properly.
In a way they do, in another they don't really. In several areas AE surpasses PS (in strict geeky technical terms, of course it lacks e.g. useful stuff like custom brushes etc.), which is part of the reason for these issues. If you will, AE is doing too good a job at some things... ;-)