This content has been marked as final. Show 7 replies
Not that I've found. I frequently import 40-50 PSDs (batch-created lower thirds and such), and rampant "OK" clicking is the name of the game. There might be some way to use an external program like AutoKey to create a macro to do this, but I don't know that for certain.
The other "solution" would be to create a multiple-layered PSD and import it as a sequence. I say "solution" because this isn't really appropriate for the number of layers you're talking about. Even if you created 10 PSDs with 100 layers each, the files would be pretty unwieldy.
Make a feature request for batch import--it's sorely needed...
Great Idea with the multiple layered psd files.
I just put in the feature request. Maybe it'll be in an update.
Never know if there is a secret "hold alt+shift then press okay on the import screen" type thing, or use Bridge...
The space bar works good for now, doesn't take too long to import them this way.
Thanks for the reply...
Wouldn't you want to treat the import as a sequence of stills? Am I missing something. Are the images all the same size/dimension?
Even if it was done that way (which I tried as well), it will still prompt you for every file being a psd file type. It prompts you to choose the type of import you would like, "merged layers" or "choose layer".
I did run them through a custom photoshop batch action, to resize them all to 720x480 .9 dv aspect ratio, and duplicate, delete the background layer (so the alpha would exist). They are numbered file-01.psd through file-1000.psd as well.
Thanks for the suggestion!
Convert to TGA. They can have alpha as well. Or PNG. Or TIFF.
You might want to check Russell Brown's Photoshop scripts. Either Place-A-Matic or Merge-A-Matic might help by taking those individual PSDs and turning them into multi-layered PSDs. Again, I wouldn't suggest making PSDs with too many layers, as I don't know how many video tracks PPro will support. Or just with one of Jim's suggestions.
An action can convert the entire folder, so I can't see a reason not to use that workaround.