Photoshop: Render Video ignores Smartobject transform in Timeline frame

  • 1
  • Problem
  • Updated 2 years ago
  • (Edited)
Recreate bug.
1. Create Timeline with Frames2. Create smartobjects3. Duplicate smartobjects and transform them (flip horizontal), moving them on different frames
4. Select File, Export, Render Video, sequence (jpeg)
5. Smartobjects in the rendered jpegs do not match the view in Photoshop, they are flipped the wrong way
Solution: select smartobject, Timeline, Match layer across frames, Position.This is the only way to ensure they actually match what you see in each Timeline frame.A time consuming process if one has multiple smartobjects.
It seems as if Render Video uses the orientation of the smartobject on the first frame (even though the object may not be visible there) and applies that transform to each following frame where the object appears, rather than using the actual transform of the frame in the Timeline.
Photo of Marten Lundsten

Marten Lundsten

  • 12 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 16406 Posts
  • 2615 Reply Likes
Can you post a PSD along with a resulting video file that exhibits this problem? (dropbox or Creative Cloud)
Photo of Marten Lundsten

Marten Lundsten

  • 12 Posts
  • 0 Reply Likes
Hi Jeffrey,

thanks for the quick response.

I've uploaded the sample PSD to Dropbox

It has Timeline Frames and Smartobjects that turn out wrong when rendered as a Video.I noticed that it occured when I duplicated and already duplicated smartobject (copy #2). But not with the first copy. Perhaps that's a clue?
Image 03 differs from what the frame looks like in Photoshop. The arrow should be pointing up, not down. It seems as if the vertical transform is ignored.

If choose Timeline, Match across all frames, Position, it renders correctly. But this extra step is a pain, and doesn't help if you want the position to be different between frames with the same smartobject.

Let me know if you're able to replicate the problem, and hope it will get included in a future bugfix.