What determines length of imported PSD comps?

I just imported a PSD comp and noticed the duration was 00:16:27, which is kind of an odd length. If I lengthen the duration after the fact, I have to go through each precomps and change the length and layer output.
Where is the length of imported comps set? I have still frame imports set to 1:00:00.

> Know of a script that would let me lengthen my PSD comps (and go through all my pre-comps to lengthen also)?
from "Composition settings", in After Effects Help:
"Jeff Almasol provides a script on his redefinery website to set the frame rate and duration of the current composition and all compositions nested within it."

Similar Messages

Best way to import layer comps as states in Catalyst?

Is there a native way in Catalyst to break the layer comps into separate states?
Right now it seems my only recourse is to manually export layer comps to separate images from photoshop and then arrange them as states in Catalyst. Of Course this way I lose my layers and other psd information. Having a proliferation of psds will become unwieldy very quickly.

Automatically converting Photoshop layer comps to States in Catalyst is not within the scope of version 1.0. However support for individually identifying layer comps and importing them is. In Beta 1, there's a bug that keeps this latter functionality from working correctly. So be on the lookout for a fix in the next beta build. You can spot this feature in the Advanced Photoshop import dialog (click the Adv. button at lower left of the basic Import dialog). In the Advanced settings, you'll see a drop down menu of available comps is presented. But due to the bug, Beta 1 doesn't pay attention to what you choose in this menu.
Once we fix the above bug, for 1.0 the suggested workflow is: Import the initial application state's layer comp using the Advanced dialog; then generate a new blank state in Catalyst and import the next layer comp/appearance state there. Currently, hidden artwork is always ignored via the Advanced dialog, so you won't end up with duplicate objects after importing multiple comps.
A couple of additions that should be helpful in future builds: a) Rather than always ignoring hidden layers in the Advanced dialog you'll be presented with a choice to either preserve or ignore them, b) when importing, we'd like to compare the artboard's dimensions to the dimensions of an incoming file and subsequently align the two if they match. This function coupled with Catalyst's pixel snapping should ensure that artwork in each layer comp is properly aligned with that which exists in another application state.
-Eric
Catalyst QE

Report Generation: what determine row height?

When using the standard report generation vis, and I append a table, what determines the height of the rows? You can set the column width, but even down into all the vis, I don't see any way to control this.
This is in Labview 8.5.1
Message Edited by remenakb on 04-21-2008 12:53 PM
Brad Remenak
Certified LabVIEW Architect

I have a Zebra printer I am trying to print to and it seems like the row height is determined from just the text length. Even if the column width is plenty wide enough. But if I send it to a regular Canon printer the table seems to print fine.
Brad Remenak
Certified LabVIEW Architect

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!

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!

After Effects CC crashing on importing PSD (ae.blitpipe error message)

Hi guys,
I hope you can help me, Adobe Support couldn't so far.
I recently installed After Effects CC on my MacBook Pro 13" (2012), 16GB RAM, Mountain Lion 10.8.4.
I cannot import PSD files into AE. Everytime I try, it crashes with the following message:
Zuletzt protokollierte Meldung: <140735306359168> <ae.blitpipe> <2> Making New Context
It doesn't matter, what kind of PSD file I try to import. But to be sure, I created a new PSD file, 1920x1080, 72 dpi, RGB, just with a background, no effects, flattened, just that single background layer. It won't import, AE always crashes.
I'm also running After Effects CS3 on that MacBook. Importing PSD files there works perfectly here.
I tried these troubleshooting procedures:
- trashing preferences
- uninstalling every single Adobe Product
- cleaning with the Creative Suite Cleaning Tool
- Reinstalling just After Effects CC (still wont import PSD files at this stage)
- Reinstalling Photoshop Elements 11, creating a new PSD file, still doesn't work.
I don't know what else to do right now. I want to avoid reinstalling the whole operating system because I'm working on projects at the moment (with Final Cut Pro X).
You have an idea?

Process:         After Effects [856]
Path:            /Applications/Adobe After Effects CC/Adobe After Effects CC.app/Contents/MacOS/After Effects
Identifier:      com.adobe.AfterEffects
Version:         12.0 (12.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [287]
User ID:         501
Date/Time:       2013-08-26 09:11:26.282 +0200
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version: 10
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/Adobe After Effects CC.app/Contents/MacOS/After Effects
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.adobe.psl                           0x000000010dd6b419 0x10db03000 + 2524185
1   com.adobe.psl                           0x000000010dcf339e 0x10db03000 + 2032542
2   com.adobe.psl                           0x000000010df33fbd 0x10db03000 + 4394941
3   com.adobe.psl                           0x000000010dd95ba9 0x10db03000 + 2698153
4   com.adobe.psl                           0x000000010ddbf290 0x10db03000 + 2867856
5   com.adobe.psl                           0x000000010de86585 0x10db03000 + 3683717
6   com.adobe.psl                           0x000000010dda2fac 0x10db03000 + 2752428
7   com.adobe.psl                           0x000000010e098718 0x10db03000 + 5855000
8   com.adobe.psl                           0x000000010e095dd6 0x10db03000 + 5844438
9   com.adobe.psl                           0x000000010e09a61a 0x10db03000 + 5862938
10 com.adobe.psl                           0x000000010e08dcfe 0x10db03000 + 5811454
11 com.adobe.psl                           0x000000010e08dbb1 PSLGetImageLayer + 33
12 PIN.dylib                               0x00000001020cb42d AdobePSL::Layer::Layer(AdobePSL::Image const&, int) + 61
13 PIN.dylib                               0x000000010201bb5d PSL_AE_Interface::BuildLayerIDList(AdobePSL::Image*, std::vector<PIN_LayerID, std::allocator<PIN_LayerID> >*) + 141
14 PIN.dylib                               0x000000010201c225 PSL_AE_Interface::DoLayerDialog(PIN_SeqSpec**, int*) + 357
15 PIN.dylib                               0x00000001020189b1 D_PS3_NewSeqSpecFromFile + 1009
16 PIN.dylib                               0x0000000101fbd22d PINp_NewSeqSpecFromFileSpec + 6173
17 PIN.dylib                               0x0000000101fbc215 PINp_NewSeqSpecFromFileSpec + 2053
18 PIN.dylib                               0x0000000101fc07dc PIN_NewSeqSpecFromFileSpecH + 268
19 com.adobe.AfterEffectsLib.framework          0x0000000100225581 Egg_PINImportFileCBX(FILE_Spec*, AE_FIM_ImportOptionsTag*, int, BEE_Item*, AE_FIM_RefconTag*, PIN_NewSeqSpecInfo*) + 369
20 com.adobe.AfterEffectsLib.framework          0x0000000100225a2f Egg_PINImportFileCB(FILE_Spec*, AE_FIM_ImportOptionsTag*, int, BEE_Item*, AE_FIM_RefconTag*) + 111
21 com.adobe.AfterEffectsLib.framework          0x00000001002b912d FIM_DoImport(FIM_ImportSpec*, BEE_Item*, int, BEE_Item**, int) + 1085
22 com.adobe.AfterEffectsLib.framework          0x00000001006c31d6 CProject::DoCommand(int) + 10198
23 com.adobe.AfterEffectsLib.framework          0x00000001006bcb34 CPOutlinePano::HandleDoubleClick(ae::egg::MouseEvent const&) + 308
24 com.adobe.AfterEffectsLib.framework          0x0000000100318da6 CView::DispatchMouseEvent(ae::egg::MouseEvent const&) + 310
25 com.adobe.AfterEffectsLib.framework          0x0000000100318f4e CView::DispatchMouseEvent(ae::egg::MouseEvent const&) + 734
26 com.adobe.AfterEffectsLib.framework          0x0000000100318f4e CView::DispatchMouseEvent(ae::egg::MouseEvent const&) + 734
27 com.adobe.AfterEffectsLib.framework          0x000000010034c8a7 CDirTabPanel::UI_DoMouseEvent(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&) + 855
28 com.adobe.AfterEffectsLib.framework          0x000000010068ac94 non-virtual thunk to COutlineDir::UI_DoMouseEvent(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&) + 52
29 com.adobe.dvaui.framework               0x000000010388ed83 dvaui::ui::UI_Node::DispatchMouseEvent::operator()(dvaui::ui::UI_Node*, dvaui::ui::UI_Node*, dvacore::geom::PointT<float> const&) const + 291
30 com.adobe.dvaui.framework               0x0000000103894f03 std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchMouseEventTowardsLeafT<dvaui::ui::UI_Node::DispatchMouseEv ent>(dvaui::ui::UI_Node::DispatchMouseEvent&, dvacore::geom::PointT<float> const&, bool) + 163
31 com.adobe.dvaui.framework               0x0000000103894eeb std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchMouseEventTowardsLeafT<dvaui::ui::UI_Node::DispatchMouseEv ent>(dvaui::ui::UI_Node::DispatchMouseEvent&, dvacore::geom::PointT<float> const&, bool) + 139
32 com.adobe.dvaui.framework               0x0000000103894eeb std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchMouseEventTowardsLeafT<dvaui::ui::UI_Node::DispatchMouseEv ent>(dvaui::ui::UI_Node::DispatchMouseEvent&, dvacore::geom::PointT<float> const&, bool) + 139
33 com.adobe.dvaui.framework               0x0000000103894eeb std::pair<bool, dvaui::ui::UI_Node*> dvaui::ui::UI_Node::UI_DispatchMouseEventTowardsLeafT<dvaui::ui::UI_Node::DispatchMouseEv ent>(dvaui::ui::UI_Node::DispatchMouseEvent&, dvacore::geom::PointT<float> const&, bool) + 139
34 com.adobe.dvaui.framework               0x000000010388e3cf dvaui::ui::UI_Node::UI_DispatchMouseEventTowardsLeaf(dvaui::ui::MouseEvent const&, bool) + 63
35 com.adobe.dvaui.framework               0x000000010388dc54 dvaui::ui::UI_Node::UI_DispatchMouseEventToTarget(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&, bool) + 1124
36 com.adobe.dvaui.framework               0x000000010388d7b5 dvaui::ui::UI_Node::UI_DispatchMouseEvent(dvaui::ui::MouseEvent const&, bool) + 69
37 com.adobe.dvaui.framework               0x0000000103905f4a dvaui::ui::OS_View::UI_DispatchPlatformMouseEvent(dvaui::ui::MouseEvent const&, bool) + 666
38 com.adobe.dvaui.framework               0x0000000103905aad dvaui::ui::OS_View::UI_DispatchPlatformMouseClickEvent(dvaui::ui::OS_Event const&) + 477
39 com.adobe.dvaui.framework               0x00000001039043a8 dvaui::ui::OS_View::UI_DispatchEvent(dvaui::ui::OS_Event*) + 120
40 com.adobe.dvaui.framework               0x0000000103904306 dvaui::ui::OS_View::UI_HandleOSEvent(dvaui::ui::OS_Event*) + 22
41 com.adobe.dvaui.framework               0x00000001039055a9 dvaui::ui::OS_View::UI_HandlePlatformEvent(NSEvent*) + 57
42 com.adobe.dvacore.framework             0x00000001031d6a74 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 68
43 com.adobe.AfterEffectsLib.framework          0x0000000100274557 Get_NAB_BUILD_SYNC_SETTINGS_HIDDEN() + 1815
44 com.adobe.dvacore.framework             0x00000001031d6b0c void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 140
45 com.adobe.dvacore.framework             0x00000001031d867d void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 125
46 com.adobe.dvaui.framework               0x00000001039105da -[DVAMacContainerView mouseUp:] + 122
47 com.apple.AppKit                        0x00007fff8868e5d6 -[NSWindow sendEvent:] + 7053
48 com.apple.AppKit                        0x00007fff8868a644 -[NSApplication sendEvent:] + 5761
49 com.adobe.dvaui.framework               0x0000000103909aae -[DVAMacApplication sendEvent:] + 622
50 com.adobe.AfterEffectsLib.framework          0x00000001000b63ec GetAECocoaApplication() + 1420
Adobe Product Version: 12.0
Adobe Product Build: 404

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

Importing PSD's into Flash

I'm using Flash 8, and have just started importing PSDs into
Flash. I actually found the import PSDs feature in CS3, and
discovered that you can import PSDs to Flash 8 as well.
The problem is, there is a color shift-the PSDs imported into
Flash appear lighter than they do in PS, or than a JPEG of the same
image appears when imported into Flash. I have noticed the same
problem with PNG's as well. They also appear lighter than a JPG of
exactly the same image when brought into Flash....
Does anyone know of any fix for this? Is it something to do
with color-profiles in PhotoShop (of which I know little about)?
Thanks!

How was the original art created? Was the original RGB or CMYK? What is the resolution of the Photoshop file? Flash only works well with RGB and 72 pixel per inch resolution. If your original art is not set this way, then Flash will attempt to convert it as it imports it. Flash uses the sRGB color space. You'll get the best color translation if your Photoshop file is using this color preference.

DL or import AEFX comp - pros & cons

I am exploring DL workflows.
Previously I was bit more of a fan for the simplicity of intermediates but Win7 , MPE, 64-bit etc has made me include DL in my workflow
If someone can give me some thoughts on this question please.....
Is there an advantage using DL ? (ie for an AEFX comp in a PPRO sequence)...
over...simply importing the comp into PPRO as an asset.
This "importing workflow" reflects any saved changes to the comp so I am wondering why I would bother with DL
Appears to me there are a number of ways to skin this cat. I am trying to understand them all.

When you import a Premiere Pro project into After Effects, elements of the Premiere Pro project have to be converted into their nearest equivalents in After Effects. In many cases, this conversion is... um... imperfect. In many more, no conversion happens and you just get nothing for that element.
The conversion that is done for importing a Premiere Pro project is exactly the same (i.e., uses the same code) as that for copying from Premiere Pro and pasting into After Effects. Therefore, these tables for the results of copying and pasting are also useful for knowing the details of the importing workflow.
Internally, we consider that path to be the less desirable path, and so less attention is paid to it than to Dynamic Link. Dynamic Link tends to get the new features and polish these days.
So, what about Dynamic Link?
Dynamic Link has 100% perfect fidelity, with no conversion problems for image data. (Well, it should, anyway.) Why? Because there is no conversion happening for image data. In the case of linking from Premiere Pro to After Effects, a "headless" version of Premiere Pro runs in the background, rendering frames and giving them to the After Effects client as needed.
So, what's the downside? Well, you have at least one extra application instance running when you're using Dynamic Link, and that headless application has to be processing and handing off frames for every linked sequence or composition, so the performance hit can be serious in some cases. This got a lot better in CS5.
Of course, the simplest method (though the one that eats time and disk space) is rendering and exporting intermediate movies. I still do that in some cases.
There's more about the ways to move data between these two applications here.

Cc 2014 - Nothing shows in inport window when importing AE comp.

So I'm trying to import a comp and there's nothing at all in the window

We found what the culprits were, but I don't know why they'd cause these error messages.
To recap, I have a piece of HD video that I've duplicated 39 times with a different triangular mask on each layer to re-create the whole frame (moving the anchor points of each layer as needed). The idea is that I then rotate those layers in 3D somewhat randomly, revealing a different video clip on the back side. To create the "B-side" video for the back sides I duplicated the original 39 faceted layers and parented each to its corresponding "A-side" piece. I created some opacity expressions to make the A-sides disappear halfway through their rotation with the B-sides appearing at the same point.
My plan was to vary the mask shapes on the A-sides to create variations on the transitions, so I enabled an expression on the masks and pick-whipped the mask shapes on the B-sides to their A-side counterparts. That seems to be the problem. Here's the expression (applied to layer 26B):
thisComp.layer("26").mask("Mask 1").maskPath
I repeated this for all 39 B-side layers. Then I duplicated that comp and inserted new video into the transition. At some point some part of the software decided some layers were missing or something, creating the above error messages. The comps still worked as designed; it was just error messages that I had to repeatedly dismiss. Once I deleted all of these mask expressions the error messages stopped.
Before deleting those expressions we tried renaming the layers (1-39) so they were unique within each comp (Train1, Rail1, etc) but that didn't work.
Feels like a bug.
Shawn Marshall
Marshall Arts Motion Graphics

Importing PSD or PNGS? (Transparent)

Since Flash CS3 imports PSDs, should I continue importing
PNGS and JPEGS?
I am importing Transparent PSDs and find the published file
swf size is a little smatter than when I import transparent PNGs.
What is the rule of thumb with Flash CS3 and importing?
Thanks for your help.

there is no rule of thumb - the PSD import wizard is an added
and welcomed feature if you are
working with layered PSD files and Flash - but if you have a
single PNG then that's fine to import
on its own also.
As for file size - there may be a difference between a PNG
and the same PNG in a PSD file - I have
never tested it.
Chris Georgenes
Adobe Community Expert
www.mudbubble.com
www.keyframer.com
www.howtocheatinflash.com
FlashRenaissance wrote:
> Since Flash CS3 imports PSDs, should I continue
importing PNGS and JPEGS?
> I am importing Transparent PSDs and find the published
file swf size is a
> little smatter than when I import transparent PNGs.
> What is the rule of thumb with Flash CS3 and importing?
>
> Thanks for your help.
>

Color discrepancy with imported PSD between Motion and FCP

I've got a Motion project with an imported PSD file as a background element (the PSD was created in Photoshop CS2 for Windows, running under Parallels).
The PSD file consists of two overlapping curved shapes, one blue, one green (part of our corporate look). The colors (RGB) match our official guidelines.
I imported the Motion project to FCP and placed it on the timeline, on V1. In FCP, I then used a color generator to create a small blue rectangle which would serve as a border for a slightly smaller thumbnail image that would get overlaid later on. The rectangle is on V2. I used the exact same RGB values for it as I did in Photoshop for the curved shape.
Trouble is, the blue color in the shape that got imported into FCP inside the Motion project doesn't match the generated color.
See this screenshot, in FCP:
http://elamaton.no-ip.com/~jarkko/colordiscrepancymotion.png
Three blues: leftmost, the color generator resized to a small rectangle; on the center, the shape that I created in Photoshop and imported into a Motion project, dropped into FCP; rightmost, an instance of Photoshop CS2 running in a virtual WinXP in Parallels Desktop. You'll notice that the blues of the generator and Photoshop match, but the middle shape that travelled the CS2->Motion->FCP route is a different shade.
Narrowing it down further, I decided to import the PSD file directly into FCP (just to see if it'd match - it needs to go through Motion for the final product). Here's a screengrab of Canvas this time:
http://elamaton.no-ip.com/~jarkko/colordiscrepancy_motion2.png
Again, from left to right: the generated rectangle, the directly imported PSD, the PSD in the imported Motion project. The first two match, but something in Motion or the Photoshop->Motion route screws up the colors of the blue-green shape (as well as the Työterveyslaitos logo on the top left, also a PSD, in the same Motion project). The blue shade is also incorrect in the Motion canvas, pre-import to FCP.
What's going on here, and how can I fix things?
The project settings are PAL DV in both FCP and Motion. No rendering has been done, I'm importing the .motn into FCP as-is.
Any help is greatly appreciated, deadlines loom...

First, double-check that your PSD is in RGB, but I suspect it it or it wouldn't even work in FCP. I suspect a gamma issue moving between the apps:
http://docs.info.apple.com/article.html?artnum=93794
You might try setting the colorspace in FCP to RGB or adding a gamma filter in Motion to adjust.
Mark

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.

What determines whether the Label name and/or Caption appears in the context help window but in other cases, both the label and caption appear in the context help window?

I am trying to polish an application, and find that I cannot seem to reliably control which of the label or caption text appears in the context help window because I don't understand what rules are in place to determine which should appear. It seems like if I reate a named constant, then use it's right click menu command "Create Indicator" I get a control with only a Label (as long as I don't add a caption). This then appears in the context help window as the label name followed by the description text (after entering some description text). But if I add a caption, the label name is shown in bracket
s which is a 'feature' I would like to avoid, because I have certain controls where I would like to use a descriptive variable name on the block diagram side without using so much space on the front panel. It seems like there is no way to avoid showing the Label name in the context help for a control/indicator. Is this true?
I thought the purpose of having a seperate caption was to make the text that appears with a control programmatically controllable, but if that control is not extended to what appears in the context help window, it limits the usefulness of the caption and forces me to re-consider some Label names. However, the problem goes deeper than that because then even when I make the label and caption exactly the same, or if I delete (via a select caption text-backspace or select caption text- delete key .. sequence) the caption for a control, the label name in the context help window still appears in square brackets!
Can I have complete control over the context help fo
r a particular control (or has anyone found a third-party context help solution that functions compatibly with LabVIEW 7 in a built application that they will be so kind as to recommend?)
I have used LabVIEW for three years, and I am now using LabVIEW 7.0.

Sorry for that.. I was changing the text of my question and didn't read carefully enough in the preview stage. I wanted it to read "What determines whether the Label name and/or Caption appears in the context help window?"

What determines how a PDF or EPS file is opened??????

Hi I was wondering if anyone can tell, what determines how a PDF or EPS is opened in Photoshop.
If I open a PDF in photoshop, the first thing that pops up is the settings for which you want it to open. i.e., color mode, resolution, you choose what you want and then open.
I always thought that how the file was created determines the initial settings in which photoshop displays in that little dialogue box. (for example, if I open an illustrator eps file that I created in photoshop, it always prompts the correct settings (300dpi, CMYK) I click open and it works great.
But when I open a PDF in photoshop it always displays the color mode as RGB, not cmyk. Which i find odd, because I know there is no RGB color space in the PDF.
Today something weird happend, I created an Ad in Indesign, every image I am certain was 300 dpi, and the rest are vectors. Exported it to PDF with high resolution settings, but when I opened it up in Photoshop, the settins dialogue box promted it as 72dpi, which again I find odd because I know each image is 300, the rest are vectors, and I know the PDF preset to which I exported it creates high res images.
Does anyone know what determines how a PDF or eps file is opened in Photoshop and why photoshop is rendering a PDF in which I am certain is hi res, to a low res?
Thanks for any help. Kevin

>Hi I was wondering if anyone can tell, what determines how a PDF or
>EPS is opened in Photoshop.
Nothing, really. EPS provides this info openly in its header, but it is not always right, so PS cannot even assume it would be correct to use that info. For PDF it's a different story. PDF is a container format that can contain any number of items in mixed resolutions and colorspaces, hence PS cannot assume anything. Likewise, you can have multiple pages, links, multimedia content, all of which may influence the result upon display or rasterization...
Mylenium

What determines length of imported PSD comps?

Similar Messages

Maybe you are looking for