Problem with Photoshop transparency file

Question

Level 10

151,149 points

Problem with Photoshop transparency file

I made some single layer Photoshop files with transparency using Affinity Photo and Pixelmator Pro.

I make the files as HD 1920x1080 with transparency. I paint something on the layer and export in PSD format.

When I bring the PSDs into FCP, the content of the file is usually offset and not in the correct place. FCP says the file is 1920x1080. I make a project with a 1920x1080 file; FCP gives that as the size. When I put the PSD files in the project, info still shows them as 1920x1080, but they don't fill the frame. They smaller than the frame. Spatial conform is set to none, and the images aren't scaled in Transform.

Could someone try this and see if they are having the same results? I don't use Photoshop, so it's possible the problem is in the graphics application, though surprising that the two are producing similar behavior.

Thanks very much.

MacBook Pro, macOS High Sierra (10.13.2), Late 2016 15" 2.7 GHz i7 16 GB RAM

Posted on Dec 20, 2017 9:30 AM

Reply

Answer 1

Dec 20, 2017 11:03 AM in response to Tom Wolsky

There is something not working well if the psd file has a single layer.

This is a shot of the browser with two psd files. They should look identical, but don't.

The second one has two layers and shows correctly (an orange border with transparency in the middle). The first has a single layer and comes out as above (in the browser and in the viewer).

(Note: I just added an empty layer to make the second file from the first)

Reply

Answer 2

Tom Wolsky Author

Level 10

151,149 points

Dec 20, 2017 11:05 AM in response to Meg The Dog

Tried in 10.4 in Sierra and got the same results.

Pixelmator Pro PSD file in the project viewer

Affinity Photo PSD file in the project window

They come placed in the lower right like this when appended. Notice the bottom of the AP file is clipped, and the bottom right of the Pixelmator file is clipped.

Weirdness they look clipped in the browser as well, but the content is centered

if I skim over it the content drops into the lower right corner

Reply

Answer 3

Dec 20, 2017 8:47 PM in response to Tom Wolsky

unfortunately, have to confirm your observation PLUS things are even worse:

my example, in Pixelmator…

exported as png = all fine:

but in psd format:

A) shrunk, B) off axis!!

I can repair that by manually resetting x/y to 0 and scale to 200% 😟

now, just for fun, I created another project, selecting 150dpi instead of 72dpi…

(yep, I'm the loudest&first yelling "no such thing as dots per inch in video making!" but …)

that is the 150 dpi psd, and that …

arrghgh!! Different off-values!! Depending of dpi settings!

And, diff. topic, but perhaps a coincidence:

A friend told me about issues with some pdfs due to a new internal pdfkit of OS since Sierra …

ahh, and to mention:

exported the same file from within PixelmatorPro = same issues.

Finally, indeed, adding an (empty), 2nd layer = no misbehaves …

forgot to mention: macOS HS, FCPX10_4 …

hmmm? something seriously kaputt …

Reply

Answer 4

Meg The Dog

Level 6

13,567 points

Dec 20, 2017 10:06 AM in response to Tom Wolsky

I can't replicate your issue with either a Photoshop originated psd or an Affinity Photo originated psd file.

FCP 10.4 on Sierra 10.12.6.

In Affinity Photo, using the export preset PSD (Final Cut Pro) if that makes a difference.

MtD

Reply

Answer 5

Dec 20, 2017 10:21 AM in response to Tom Wolsky

Tom, I ran the test and have no problem. Created a document in Photoshop Elements: 1920x1080, transparent background. Imported to a FCP 10.3.4 project, spacial conform is None. The file fills the frame and is positioned as expected.

Reply

Answer 6

Dec 20, 2017 2:11 PM in response to Kurt Lang

I have had issues with PSD files in FCPX for a long time, especially when FCPX was upgraded. I have done entire projects where everything was perfect and then when I went back to them after an update everything was screwed up. I started using png files for transparency and jpg for full screen and I have not had any issues since. It's easy enough to retain a PSD file as the working file and just export it to the necessary format.

Reply

Answer 7

Tom Wolsky Author

Level 10

151,149 points

Dec 20, 2017 2:14 PM in response to Nick Toth

Interesting. Thanks Nick. Both Pixelmator and Affinity have there own file formats that get saved as the master graphic as it were, from different formats like PSD, PNG, JOEG can be exported. I usually work with PSD files for transparency or layers, but I'll rethink that going forward.

Reply

Answer 8

fox_m

Level 6

12,268 points

Dec 20, 2017 7:13 PM in response to Tom Wolsky

PSDs are a proprietary file format and Adobe can change the details of it at any time. There is an option in PS preferences to Maximize Compatibility of saved files. This helps with other outside applications that can "open" PSDs (100% compatibility can never be guaranteed but they generally work). Have you checked that yet? Your other apps (Affinity and Pixelmator) are using that compatibility mode file format (it's their only option).

Reply

Answer 9

Dec 29, 2017 3:33 AM in response to Tom Wolsky

just stumbled by incident on this Option in Affinity Photo, when you select psd as Export format:

an extra FCPX_compatible psd format…

What do the folks at Serif know, what we don't? 😉

Reply

Answer 10

Tom Wolsky Author

Level 10

151,149 points

Dec 20, 2017 10:27 AM in response to TheRealJG

Thank you both very much. I'll have to test further and see why this is happening for me.

Wondering now if it's an HS problem, though I don't see why the OS would have an effect on this.

Reply

Answer 11

Dec 20, 2017 10:38 AM in response to Tom Wolsky

Forgot to mention: I'm running Sierra 10.12.6.

Reply

Answer 12

Tom Wolsky Author

Level 10

151,149 points

Dec 20, 2017 11:07 AM in response to Luis Sequeira1

Thanks Luis. This is troubling. Single layer with transparency is a very common format. I guess the workaround is to add another layer to the file. I'll try that.

Reply

Answer 13

Dec 20, 2017 11:11 AM in response to Tom Wolsky

Tom, do you also see the problem with png files? I read something about that (perhaps at fcp.co) but for me a png version of the same file works fine.

Reply