10.2.1 & Photoshop file update issue. Is it solved?

Hi all.

I am out on assignment and unable to test right away, but has anyone tried . Psd or tiff files to see if they update correctly in 10.2.1 with new update when changes are made to original files?

I will love you forever if any of you could check and pnce I return to studio I'll do the same.

This would be awesome if this finally got sorted out.

Jonathan

Jonathan Levin wrote: Hi all.

I am out on assignment and unable to test right away, but has anyone tried . Psd or tiff files to see if they update correctly in 10.2.1 with new update when changes are made to original files?

I will love you forever if any of you could check and pnce I return to studio I'll do the same.

This would be awesome if this finally got sorted out.

Jonathan

Well, FWIW, I just made a tiff in graphic converter with some text and dragged it to a timeline in X. Back to GC and made some changes, saved it, and it updated in FCP. Don't rent photoshop so not sure about psd's....

Thanks plysat.

Thanks for that. Were you having the update issue prior to the new update? And what version of Photoshop are you using? I am working with CS 6.

Jonathan

I rent Photoshop CC and it works for me. Didn't realise it was broken but I'm doing a job with 10's of PSD files and TIFFs edited in place with Photoshop without problem. Panasonic AVCHD files 25p - now that was a whole 'bag of hurt' in 10.2. Fixed in 10.2.1 but I'm thinking of sending Apple my medical bills!

Hi all.

Well after running many tests with 10.2.1 and Photoshop CS 6, I can tell you that the problem with the PSD and TIF file update is still not working, and in fact, it may be a little worse.

I've run just about every test I could think of, but no luck. This is a big problem for me because I always update the original PS media and need it to update in FCP.

What a pain and disappointment.

Jonathan

I have the same issue with Photoshop CS 5 and CS 6. Where layers and there names become out of whack.
So it seems there is a issue with older version if it works in CC.

I guess we will have to wait until Apple addresses this unless Adobe will fix it.

I stopped trying to use layered Photoshop files in FCP X. It's just too much hassle and I don't find it's all that helpful anyway. Updates to FCP X usually caused issues also.

I keep a layered file as my working file and just configure the layered file as necessary, duplicate, delete unused layers and export either a PNG if I'm using transparency or a high-res JPG if it's full screen.

If I need to make a change I go back to the layered file, make the change and export as necessary. I don't have any graphics problems doing it this way. The reason I use the PNG is I find that PSD files with transparency in FCP X have color shifting.

This does not take any longer and is more reliable in my experience.

Thanks guys.

I am just surprised that this something as important and needed as this has not gotten more attention.

And who knows if it's an Apple or Adobe issue.

If I knew that for sure it worked with the Adobe Photoshop CC, I'd actually consider switching, even though I hate Adobes pricing structure. The reason I've stayed with CS 6.

Jonathan

I don't use Photoshop, I use Pixelmator, and I don't have any issues with layered PSD files at all. Just FYI.

BenB wrote: I don't use Photoshop, I use Pixelmator, and I don't have any issues with layered PSD files at all. Just FYI.

you must be lucky. I get the same result with a PSD file from Pixelmator.

Appleguru,

I forgot to mention that the layers getting out of whack were also part of this issue. If I have a layered PS file with four layers as an example, named A, B, , C and D and I delete layer C, in Fcp it appears to rename (incorrectly) the remaining three layers. Weird.

I'm willing to call Apple support on this, if only I was sure that it was an apple or adobe issue.

Does anyone with a Photoshop CC subscription have this problem? Or is it just CS 6 and lower?

Jonathan

OK - I tried the following with Photoshop CC and FCPX 10.2.1 - Yosemite 10.10.3:

Created a 6 layer PSD in Photoshop CC inc. 1 layer of text and saved to Desktop.

Created new library and project in FCPX and imported the PSD - leaving it in place.

The PSD file came in as a layered still as expected.

Placed the clip in the timeline and opened it up by double clicking. All layers present and labelled correctly.

Deleted layer 2 in FCPX - all other layers remained - no labels corrupted.

Loaded the source file back into Photoshop and desaturated a layer and increased the text size on the text layer and changed the text itself. Saved it back.

Changes immediately reflected in the timeline and the browser.

Re-loaded source file into Photoshop and deleted layer 4. Added a new layer (layer 6) above the text (Layer 5) and created a filled shape on it.

Saved it to the Desktop.

Changes immediately reflected as before but the Text is now incorrectly named Layer 4 and the new layer (called new layer in the PSD file) is now called Test type layer 5 in FCPX, which is wrong. The layers are all correct but the labels are not.

More worrying - the filled shape on the new layer is in the wrong x and y position - too high and too far left.

Created a new event and imported the file anew. All layers correctly labelled and positioned.

So, it seems that there is no update mechanism present in FCPX to refresh the metadata relating to layer labels and other attributes when the underlying file changes. To prove this I added an extra layer to the source file and both clips in FCPX ignored it. So you can change existing layers but you can't add new ones. Deleting layers in the source file does not delete them in FCPX but it does delete the content in those layers - because they are no longer in the source. Adding layers back into the source with new content appeared back in FCP in the old left over layers - incorrectly labelled of course.

I haven't tested this but I would assume that PixelMator PSDs behave in the same way as the issue appears to be that FCPX has no code to refresh the structure of these layered assets when they change. Thinking about it I'm not sure that it would be wise to implement this as it would overwrite any animation etc. that you have done in, possibly, multiple instances in multiple projects.

Anyway - don't invest in Photoshop CC as a way to make this work as you want it to - 'cos it won't.

Hope that's helpful.

Ian.

Ian et al,

Thank you so much for that detailed report. So much appreciate that you spent the time looking into this. It seems that this problem is spread across current versions of PS. CS5, CS6, and CC. In some permutation or another.

What is clear from your tests and other comments is that working with layered PS files is problematic. Now to find the right ears to make a formal report.

I've sent feedback a cew times to Apple. But who knows.

It almost seems like there is something wonky with symlinks not updating since everything is "linked" in FCP.

I will try and call Apple support next week and ask for an advance level of support (if they'll do that) and see if I can have them reproduce the problem.

Jonathan