Imported PSD files don't show layers

Hello Touch-Community,
Via Creative Clouse, I imported several PSD files on my iPad3 who consist of several layers. However, independ which file I import these PSD files open without layers. That is, they open displaying the layers who were enabled (visible) when they were saved in Photoshop.
Does this means I only can create layers in Touch, but not work with already existing layers from non-Touch PSD files?
Thank you,
Michael

Correct. (Kinda sorta.) You can export PS Touch projects as PSD and PSDX files into Photoshop CC/CS6 and have their layers preserved, but if you import a PSD file into PS Touch, the layers will be flattened. I imagine this was done as a failsafe mechanism. (PS Touch works with 12 layers max, versus the thousands of layers available in Photoshop CC/CS6.)
Oddly, once you open a PSDX file in Photoshop CC/CS6, you cannot save it as a PSDX; you're forced into saving as another compatible format like PSD. (I'm thinking this was another failsafe mechanism since PS Touch does not support features such as adjustment layers.)
PSDX files can be uploaded and downloaded from Creative Cloud to PS Touch and have their layers preserved.

Similar Messages

Layers of imported .psd files are cropped?

Hi, when importing .psd files the images on layers are cropped...?
In Photoshop an image on a layer is moved across the visible portion of the document as if it is animated, through the use of comp layers (each new comp layer the image is move a little bit). However after importing the .psd into After Effects only a portion of the image is visible...it is impossible to recreate the animation roughed out with Photoshop comps because some of the image on the layer being moved is cropped.
I hope that makes sense...how can .psd files be imported into After Effects without cropping? Thanks

Thanks so much for such a prompt reply...the single .psd file with many layers is imported using:
Import Kind: Composition
Layer Options: Editable Layer Styles; Life Photoshop 3D (although there are no 3D layers in the .psd...so I'm unsure if this default is needed?)
Oh!! Never mind...I just tried Import Kind: Composition -- Cropped Layers and the layers were not cropped...kind of counter-intuitive since I would have thought "Cropped Layers" would crop the layers rather than the other way around.
Thanks for your help...if you just reply to this post I'll mark your reply as the answer, thanks for suggesting the direction to look for a solution, cheers!

Imported PSD Files Are Being Erroneously Resized in Captivate 4

I am trying to import PSD files to use in my Captivate 4 project. I verified that the PSD image size is 800 x 600, and my Captivate project dimensions are the same 800 x 600. But when the import process completes, the layers are erroneously resized to smaller dimensions. I have tried the same thing on two separate installations of Captivate 4 on two separate PC's with the same results.
Here is a screenshot of the PSD file in Photoshop (image size = 800 x 600):
Now here is a screenshot of what the imported PSD file looks like in the Captivate project (screen size set to 800 x 600):
When I do the import, I'm selecting: File --> Import --> Photoshop File..., then I select the "As Layers" option, and do not check the box next to "Scale according to stage size" (I have tried using this option as well with the same results, although I don't believe I should have to rescale when the PSD image size and Captivate project size are the same.)
Any help with this would be greatly appreciated.

Thanks so much for such a prompt reply...the single .psd file with many layers is imported using:
Import Kind: Composition
Layer Options: Editable Layer Styles; Life Photoshop 3D (although there are no 3D layers in the .psd...so I'm unsure if this default is needed?)
Oh!! Never mind...I just tried Import Kind: Composition -- Cropped Layers and the layers were not cropped...kind of counter-intuitive since I would have thought "Cropped Layers" would crop the layers rather than the other way around.
Thanks for your help...if you just reply to this post I'll mark your reply as the answer, thanks for suggesting the direction to look for a solution, cheers!

FCP 7 - PSD file in BIN shows diff than layer properties

steps to reproduce this issue, please confirm you have it too before I submit a bug report:
1. FCP 7
2. Photoshop CS5 Extended - setup iPhone 4 size file (640 x 960 at 326 ppi)
3. create multiple layers
4. import the PSD file into FCP 7
5. setup BIN columns to display file resolution
6. notice that BIN shows 640 x 960
7. double click PSD file - shows in TL
8. navigate to PSD in TL, pick any layer
9. right click Item Properties, Format - will show at 640 x 964
Ive tried recreating a PSD from scratch - a test scratch file if you will, and the problem persists.
Tried restarting this Mac - persists.
Tried software update - there's nothing left to update

sorry I might have misread your post. To clarify: yes the sequence and PSD files are both SHOWING IN FCP as 640 x 960
The issue came to light as after importing additional a layers, I noticed that they appear wider when 2x clicked on from the TL versus the BIN.
Further, the layers will also "stretch" to the layer's size even though the (text) data within the layer is far smaller than the layer itself. This "stretching" phenomena I swear Ive seen before somewhere years ago... cant quite recall the details.
The layers in my PSD mostly only have text on them, the text bounding box will stretch to layer boundaries as if the matte background werent part of the layer. This behavior is also incorrect, the matte matters....

Error when importing psd files into Premiere Pro

I am using Adobe Premiere Pro CS4 and Photoshop CS4. Whenever I attempt to import a psd file I get this error message: "File format not supported". I have tested it with different file sizes and properties. My files are RGB and 8 bits/channel. Is there any way to resolve this problem? I am also using Adobe After Effects and importing psd files works great with it.
Thanks

Welcome to the forum.
The RGB and 8-bit take care of two possible causes, so thanks for getting those out of the way early on.
Does the PSD file contain Layers? Are any of them mostly Transparent, with just a few pixels, such as a small logo? Those have created issues.
What is the exact version of CS4, that you are running? Seems that there WAS an issue with PSD's in an earlier version, and that a later update fixed that.
There is another element with PSD's, that has caused issues, but my feeble mind is suddenly blank on what that was about. Seems that Colin Brougham commented on it not that long ago. I'll see if I can drege up one of those threads, but you might aslo want to do a Search on "PrPro" and "PSD," though the forum Search might still be broken. Maybe Google, and also look for replies from Colin. I'll do the same too. IIRC, one had to Open the offending PSD in PS, and just do a Save_As with a short file name, and a short Path (not buried deeply inside a sub-folder structure), and all was good, but do not recall any other details at the moment. I would also eliminate any spaces in the new file name, just to eliminate any issue there - use the _ like in the old DOS days, though do not think that one had to adhere to the old 8.3 structure.
Good luck,
Hunt

Why does Premiere Pro CS3 no longer import .psd files?

Over in the German forum, BjoernG has already asked this question as of this past June. He's gotten no answer, so let's try it here. Like Bjoern I use PPro CS3. Mine is on WinXP with all updates. I import PSD files as keying masks. I've never had a problem until this evening (27 Aug 2014). I tried to import a mask I've used many times before. And it has always worked before. Tonight PPro refused to recognize .psd as a supported file type, so it didn't show in the import folder file list. When I told PPro to show "all files *.*", it showed the file. When I selected it, PPro even showed the "import file" window, then displayed the "File Import Failure" window with Error Message: File format not supported. See the picture.
This is a file I've imported into many previous projects with no problem whatever. In fact, I started with a project file from last year which showed the mask file in the project assets but offline! Even though the file had not been moved.
If PPro CS3 is as obsolete as Adobe claims it is, then who's been messing with it? And how can we get it "unmessed"?

I couldn't imagine what any of those steps would do for my problem – but I didn't have a better idea so I tried them:
> If Premiere is acting weird, restart computer.
It's a laptop, so it was off all night. I turned it on this morning.
> Hold down shift+alt while opening Premiere.
If I hold down shift-alt before clicking the desktop icon, all it does is select all icons from top left to the Premiere icon. It does not start Premiere.
If I press and hold shift-alt immediately after clicking the icon, Premiere displays every tiny module it loads rather than summarizing. I held shift-alt until Premiere was fully up and idle.
> Then empty all media cache.
I did that. As I write, Premiere is busy reconstituting all of that.
Then finally, the acid test: Try to import a .psd file. Bzz-z-zt! Still claims it's an unknown file type.
> jpegs do not have transparency. You can save as png instead.
I'm using it as a track matte key, so white is equivalent to transparent. I do have to select "matte luma" instead of "matte alpha" in the effect. I'll save your advice in case I ever do need transparency.
Follow-up: I checked my other licensed copy. It accepts .psds just fine. I checked Help About for both; they're identical: 3.2.0 (374). So the problem must be in an internal setting, an external influence, or a defective module. And remember, it's not just me, Björn in Germany reported the identical problem in June.

Importing PSD files create a black line to the right of some images

I am importing PSD files into Framemaker 11 and they keep giving me a vertical line on the right side of some images. I already know that other image file formats don't cause this, but I prefer the practicality of PSD files and not having to deal with duplicate files of the same image. I figured that native Adobe files that are supposed to be cross platform compatible should work without any issues. I get lines when converting to PDF documents and when I print them out also. I’m getting ready to publish our catalog and would like to prevent the printer from cleaning them up again. Does anyone know how to fix it or if Adobe is currently addressing this issue ? Who can I contact to let them know about the issue, since it has been around from the time Frame started accepting PSD files?
Thanks,
Tomas

Hi ais007,
This is gonna sound really crazy, but this happened to me a couple of years ago. Below is the answer....hope it helps for you!
Found the answer to this in the framers digest mailout (framers Digest, Vol 71, Issue 9). Hopefully it wll help you too.
I am not sure about the Illustrator files, but for Photoshop, resize your images so that the last number is an even number. (example: change 3.25 to 3.24)
This worked for me! I couldn't believe it!
If you don't receive these emails, below is the link to subscribe...they are really helpful. I hope that is the correct link, it has been a while since I signed up.
http://lists.frameusers.com/mailman/listinfo/framers
http://forums.adobe.com/message/3945090#3945090

Importing psd files into AN

I have been using Edge Preview since the beginning. last time I used the app was 4 months ago. Now I see the newer version 1.0 is out. I got quite used to the older previews but it's been 4 months so I need a refresher course. While I do that and re familiarize myself please correct me if I'm wrong but I could have sworn that the older Edge previews allowed you to import .psd files.
Am I right?
R

So is it possible to import .psd files now or not? I have not found the way.
You can export to Edge Fireworks files with an add-on - see here: http://johndunning.com/fireworks/about/EdgeAnimate
It would be great to have the same capability with psd files.

FLV file don't show on iPhones, iPads, etc.

I'm on a iMac with a 3.06 GHz Intel Core i3 processor running 10.6.8. I build websites using Dreamweaver CS4 and all my media files are FLV files. I've noticed that none of the media shows on a iPhone, iPad, etc. Is there a media file format that I can use that works for browsers and will show on iPhones, iPod, etc.? I also noticed that SWF file don't show either. Any direction would be helpful.

Those are Flash content types. Flash doesn't exist on iOS, and won't exist on any future mobile platforms, according to Adobe.

When I import PSD file then Catalyst stopped working why?

HI,
When I import PSD file then Catalyst stopped working .why? it's a BUG?
Please find the attached image

I'm an a mac, and I haven't had the problem, so I'm not the best for advice. That said, I am sure FC on the pc can import .psd file. I would check the psd for anything "abnormal". If it is a complicated file, simplify as much as possible, flatten effects especially.
**Upload the psd, I could try to import it and upload a fxp

When I open a psd file in photoshop I don't see the layers. When I opened a psd file in elements the layers would show up.

When I was using elements and I opened a psd file that I wanted to re-edit the layers would be visable just as when I last closed the image. Now that I upgraded to photoshop and I open a psd file it opens with only the background layer. What am I doing wrong?

System info? Versions? Exact settings? PS only opening the merged view could indicate that the file contains data unique to Elements which it cannot interpret.
Mylenium

Importing PSD files with layers.

Sometimes when I import Photoshop files that have layers,
I can double-click them, and they open as multi-layer sequences where I can control the opacity and blend modes of the layers. Sweet.
But then sometimes they don't, so I have to go back to PS and render .png's of the layers that I want.
So I ask: What am I doing wrong when it doesn't work as expected?
FCP 6.0.6
Best regards;
E.

PSDs from Windows machines will not open up as layers inside FCP. This has been an issue since the first days of CS.
Open those PSDs in Photoshop on a Mac, and then resave as PSD. They will then open up fine in FCP.
Andy

Background of imported .psd file showing grey green rather than black?

Hi, the background of a .psd file imported into FCP is displaying a dull green background rather than black...do I need to coordinate the default FCP color profile with Photoshop or...?
Thanks
(Oh...and, just out of curiosity, what does a person gain by having earned points from answering questions?)

(Oh...and, just out of curiosity, what does a person gain by having earned points from answering questions?)
When you reach a million points Apple sends you an email that explains the meaning of life.
Really...
As you gain points by giving people good answers the number of coloured bars under your user name increases. In theory, this lets others know how much knowledge you have on the subject and therefore how much they can depend on your replies.
rh
Message was edited by: Randy Holder

After Effects CC freezes when importing PSD files

Version 12.2.1 of after Effects no longer imports Photoshop's PSD files (Photoshop 14.2.1 x64).
The last project I worked on was on 7th March 2014. Today is the 28th March 2014. What could have happened in the intervening three weeks I wonder?
An update to AE I'm guessing...
Is this a known problem?
Is there a fix?
How do I report this to Adobe?
Thanks in anticipation.
James

Hi Rick,
I made sure the images are RGB, but I don't know what simple means. Nor do I know how to make them the same size as the comp (composition?). I saved the images as Tif and PNGs and they imported without crashing. I literally have just opened to the first chapter of After Effects: Classroom in a Book, so please bear with me.
When I first imported a Photoshop file, AE crashed with this alert:
After Effects Alert
Last log message was: <140735304074000>
<SyncService> <4> CheckConnection: 3.
Generating crash log, which may take a few minutes.
(Updated errors below)
As I mentioned, I'm following the instructions for lesson 1 in the Adobe book, After Effects CC: Classroom in a Book. The first few steps are to import a group of files. I import the footage files first, then when I try the .psd file, AE crashes.
Here are my specs:
AE CC 2014 Version 13.0.2.3
OS X 10.9.4 (13E28)
iMac 21" late 2009
3.06 GHz Intel Core 2 Duo
12 GB RAM
NVIDIA GeForce 9400 256 MB (I installed the CUDA driver on another account of this iMac--should only need to be done once, no matter whose account, right?)
Connected over wifi to a Belkin router.
UPDATE:
I switched my wifi connection to the 5 GHz band and tried again (since some online searches seemed to indicate this error message had to do with TCP) and got a new error when trying to import the .psd file:
<ALOG> <5> PSL AE Interface Cache Cache
created: /Users/[myname]/Documents/Lesson01/Assets/bgwtext.psd.
UPDATE:
Switched to ethernet, got the same <ALOG> <5> PSL message, switched back to 2.4 GHz wifi and still get the same message. I cannot replicate the first SyncService error message.
The Adobe Creative Cloud is connected to the Internet and can download other Adobe applications, however Photoshop Elements 6 shows a "No Internet connection" message when I try to update it. Adobe Acrobat Reader updates fine. I have also tried to import the file in with Root enabled, but to no avail.
Crash report for AE below:
Process:         After Effects [2898]
Path:            /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/MacOS/After Effects
Identifier:      com.adobe.AfterEffects
Version:         13.0.2 (13.0.2)
Code Type:       X86-64 (Native)
Parent Process: launchd [275]
Responsible:     After Effects [2898]
User ID:         504
Date/Time:       2014-08-19 10:51:10.888 -0400
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 49A8B52B-C8C4-7C01-564E-1B8E1298696F
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
VM Regions Near 0x10:
-->
    __TEXT                 0000000100000000-0000000100004000 [   16K] r-x/rwx SM=COW /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/MacOS/After Effects
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.adobe.psl                 0x000000010e6f45c9 0x10e485000 + 2553289
1   com.adobe.psl                 0x000000010e67bb2e 0x10e485000 + 2059054
2   com.adobe.psl                 0x000000010e8c636d 0x10e485000 + 4461421
3   com.adobe.psl                 0x000000010e71f469 0x10e485000 + 2729065
4   com.adobe.psl                 0x000000010e749fa0 0x10e485000 + 2903968
5   com.adobe.psl                 0x000000010e816595 0x10e485000 + 3741077
6   com.adobe.psl                 0x000000010e72d261 0x10e485000 + 2785889
7   com.adobe.psl                 0x000000010ea3026f 0x10e485000 + 5943919
8   com.adobe.psl                 0x000000010ea2d6ed 0x10e485000 + 5932781
9   com.adobe.psl                 0x000000010ea344f4 0x10e485000 + 5960948
10 com.adobe.psl                 0x000000010ea2a9c4 PSLGetImageDuration + 36
11 PIN.dylib                     0x00000001021d4f55 AdobePSL::Image::GetDuration() const + 53
12 PIN.dylib                     0x000000010212a064 D_PS3p_InitPSL + 4644
13 PIN.dylib                     0x0000000102128b4e D_PS3_NewSeqSpecFromFile + 1166
14 PIN.dylib                     0x000000010207a95c PINp_NewSeqSpecFromFileSpec + 6188
15 PIN.dylib                     0x0000000102079c2a PINp_NewSeqSpecFromFileSpec + 2810
16 PIN.dylib                     0x000000010207e7ee PIN_NewSeqSpecFromFileSpecH + 270
17 com.adobe.AfterEffectsLib.framework 0x0000000100227411 Egg_PINImportFileCBX(FILE_Spec*, AE_FIM_ImportOptionsTag*, int, BEE_Item*, AE_FIM_RefconTag*, PIN_NewSeqSpecInfo*) + 721
18 com.adobe.AfterEffectsLib.framework 0x0000000100227a9e Egg_PINImportFileCB(FILE_Spec*, AE_FIM_ImportOptionsTag*, int, BEE_Item*, AE_FIM_RefconTag*) + 446
19 com.adobe.AfterEffectsLib.framework 0x00000001002cabb9 FIM_DoImport(FIM_ImportSpec*, BEE_Item*, int, BEE_Item**, int) + 1241
20 com.adobe.AfterEffectsLib.framework 0x00000001007128d8 CProject::DoCommand(int) + 7640
21 com.adobe.AfterEffectsLib.framework 0x000000010070b93e CPOutlinePano::HandleDoubleClick(ae::egg::MouseEvent const&) + 302
22 com.adobe.AfterEffectsLib.framework 0x000000010032aaed CView::DispatchMouseEvent(ae::egg::MouseEvent const&) + 349
23 com.adobe.AfterEffectsLib.framework 0x000000010032aa12 CView::DispatchMouseEvent(ae::egg::MouseEvent const&) + 130
24 com.adobe.AfterEffectsLib.framework 0x000000010032aa12 CView::DispatchMouseEvent(ae::egg::MouseEvent const&) + 130
25 com.adobe.AfterEffectsLib.framework 0x000000010035e334 CDirTabPanel::UI_DoMouseEvent(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&) + 820
26 com.adobe.AfterEffectsLib.framework 0x00000001006d7634 non-virtual thunk to COutlineDir::UI_DoMouseEvent(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&) + 52
27 com.adobe.dvaui.framework     0x0000000103a4e1fc dvaui::ui::UI_Node::UI_DoPointerEvent(dvaui::ui::UI_Node*, dvaui::ui::PointerEvent const&) + 44
28 com.adobe.dvaui.framework     0x0000000103a4a533 dvaui::ui::UI_Node::UI_DispatchPointerEventToLeaf(dvaui::ui::UI_Node*, dvaui::ui::UI_Node*, dvaui::ui::PointerEvent const&) + 243
29 com.adobe.dvaui.framework     0x0000000103a4a040 dvaui::ui::UI_Node::DispatchPointerEvent::operator()(dvaui::ui::UI_Node*, dvaui::ui::UI_Node*, dvacore::geom::PointT<float> const&) const + 128
30 com.adobe.dvaui.framework     0x0000000103a518da std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchPointerEventTowardsLeafT<dvaui::ui::UI_Node::DispatchPoint erEvent>(dvaui::ui::UI_Node::DispatchPointerEvent&, dvacore::geom::PointT<float> const&, bool) + 154
31 com.adobe.dvaui.framework     0x0000000103a518c2 std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchPointerEventTowardsLeafT<dvaui::ui::UI_Node::DispatchPoint erEvent>(dvaui::ui::UI_Node::DispatchPointerEvent&, dvacore::geom::PointT<float> const&, bool) + 130
32 com.adobe.dvaui.framework     0x0000000103a518c2 std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchPointerEventTowardsLeafT<dvaui::ui::UI_Node::DispatchPoint erEvent>(dvaui::ui::UI_Node::DispatchPointerEvent&, dvacore::geom::PointT<float> const&, bool) + 130
33 com.adobe.dvaui.framework     0x0000000103a518c2 std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchPointerEventTowardsLeafT<dvaui::ui::UI_Node::DispatchPoint erEvent>(dvaui::ui::UI_Node::DispatchPointerEvent&, dvacore::geom::PointT<float> const&, bool) + 130
34 com.adobe.dvaui.framework     0x0000000103a49201 dvaui::ui::UI_Node::UI_DispatchPointerEventTowardsLeaf(dvaui::ui::PointerEvent const&, bool) + 65
35 com.adobe.dvaui.framework     0x0000000103a488c2 dvaui::ui::UI_Node::UI_DispatchPointerEventToTarget(dvaui::ui::UI_Node*, dvaui::ui::PointerEvent const&, bool) + 194
36 com.adobe.dvaui.framework     0x0000000103a48752 dvaui::ui::UI_Node::UI_DispatchPointerEvent(dvaui::ui::PointerEvent const&, bool) + 66
37 com.adobe.dvaui.framework     0x0000000103ac4f40 dvaui::ui::OS_View::UI_DispatchPlatformMouseEvent(dvaui::ui::MouseEvent const&, bool) + 608
38 com.adobe.dvaui.framework     0x0000000103ac4ab8 dvaui::ui::OS_View::UI_DispatchPlatformMouseClickEvent(dvaui::ui::OS_Event const&) + 600
39 com.adobe.dvaui.framework     0x0000000103ac2e69 dvaui::ui::OS_View::UI_DispatchEvent(dvaui::ui::OS_Event*) + 121
40 com.adobe.dvaui.framework     0x0000000103ac2dc6 dvaui::ui::OS_View::UI_HandleOSEvent(dvaui::ui::OS_Event*) + 22
41 com.adobe.dvaui.framework     0x0000000103ac4549 dvaui::ui::OS_View::UI_HandlePlatformEvent(NSEvent*) + 57
42 com.adobe.dvacore.framework   0x000000010330340c int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 28
43 com.adobe.AfterEffectsLib.framework 0x0000000100282bf4 Get_NAB_BUILD_SYNC_SETTINGS_HIDDEN() + 1780
44 com.adobe.dvacore.framework   0x0000000103303558 void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 136
45 com.adobe.dvacore.framework   0x00000001033048f5 void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 165
46 com.adobe.dvaui.framework     0x0000000103acf81a -[DVAMacContainerView mouseUp:] + 122
47 com.apple.AppKit               0x00007fff8c33a145 -[NSWindow sendEvent:] + 781
48 com.apple.AppKit               0x00007fff8c2db5d4 -[NSApplication sendEvent:] + 2021
49 com.adobe.dvaui.framework     0x0000000103ac8d6b -[DVAMacApplication sendEvent:] + 603
50 com.adobe.AfterEffectsLib.framework 0x00000001000abfec GetAECocoaApplication() + 1404
51 com.apple.AppKit               0x00007fff8c12b9f9 -[NSApplication run] + 646
52 com.adobe.AfterEffectsLib.framework 0x00000001003131e1 CApplication::Run() + 65
53 com.adobe.AfterEffectsLib.framework 0x0000000100281bce MainMain(bool, bool, bool, bool, bool, bool, unsigned short const*, bool, void**, int, int, int) + 894
54 com.adobe.AfterEffectsLib.framework 0x000000010028181b EggMain(bool, bool, bool, bool, bool, bool, unsigned short const*, bool, int) + 59
55 com.adobe.AfterEffects         0x000000010000333e main + 1838
56 com.adobe.AfterEffects         0x0000000100002c04 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib         0x00007fff8ec26662 kevent64 + 10
1   libdispatch.dylib             0x00007fff82cfd421 _dispatch_mgr_invoke + 239
2   libdispatch.dylib             0x00007fff82cfd136 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib         0x00007fff8ec25e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8cdfcf08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8cdfffb9 start_wqthread + 13
Thread 3:
0   libsystem_kernel.dylib         0x00007fff8ec25e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8cdfcf08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8cdfffb9 start_wqthread + 13
[etc. etc.]
Thanks,
Tom

Importing PSD files from PC

I have been trying to import layered .psd files from a PC. When I import them into DVDSP they show up as a QuickTime Picture with only one layer, instead of a photoshop file with multiple layers. Anyone else encounter this issue?

Ask if they're saving the PSD with the compatibility mode selected. I can't recall exactly what it's called, but there's a preference for saving a "compatible" version of the file. What it actually does is save flattened version of the file along with the regular layers, for apps that can' read Photoshop's layers. Perhaps the file's been saved this way and DVDSP is reading the flattened portion instead?

Imported PSD files don't show layers

Similar Messages

Maybe you are looking for