Ae/Ps .psd workflow

Hi.
I'm somewhat new to Ae and am starting to comp some of my shots for my stop-motion film. A lot of the shots will require set extensions and I was wondering if I could use layers that are .psds and import them in a way that when I update the .psd in Ps the new edits automatically update in Ae. Sort of like when you send a clip to Ae from Pr. There will be a lot of these long vista shots so I need to tweak colors and foliage ect. If someone knows of a better way to do this then you can gather from the image attach please chime in.
Thanks in advance!
~Scott

Yes, if you change any source item (whether a .psd file or anything else), changes will be incorporated when the project is opened or any time that a footage reload is triggered---e.g., when you switch back to After Effects from another application.

Similar Messages

Jpeg Displays pick up Raw file sxif info when displayed

After creating a jpeg images as the last part of a raw -> psd workflow I noticed that the jpegs were not displaying correctly in CS5's bridge.
This can be corrected by opening the jpeg in RAW, setting everything to 0, and clicking on DONE. This erases the info about how I processed the CR2 file - but is a REAL drag.
Am I missing some setting somewhere to fix this oddity?

By the way I spelled Exif wrong.
What I mean is that, if e.g. I increase an image's exposure by 1 stop in raw, process the image, then the final jpeg is displayed overexposed by 1 stop.
It displays correctly (i.e. like the psd file it was created from) if, as I say, I reload the Jpg and UNDO the saved info (that the file was processed with a +1 exposure in raw).
Thanks for your interest.

IPhoto 08 and Photoshop - suggestions on workflow and managing PSD files

Hi Everyone,
I'm a long-time Photoshop user, and a recent convert to Mac (BTW - I love my new Mac), therefore I am also new to iPhoto 08. I must say that I actually enjoy how iPhoto manages my pictures, as it is not all that different from how I've been managing my pics manually for years (by year, by event, etc.). I've read the various discussion topics on how to set up and use Photoshop as an external editor from iPhoto, and have not had any problems up to now.
I'm now looking for suggestions on workflow and managing my PSD files. I apologize if this is a little long, but I want to make sure I explain the problem clearly. Here's the scenario:
- From iPhoto, I choose to edit an existing JPEG file in the external editor, Photoshop.
- I perform my edits (including advanced edits with layers etc.)
- I do both a "Save As..." and a "Save". That way, I "Save" the flattened JPEG back to my iPhoto library properly, and "Save As..." a PSD file in case I want to do further edits on the image later (days, weeks, months later).
I'm looking for suggestions on where to put my PSDs. For now, I am saving the PSD to my desktop (using max compatibility), and then importing the PSD into my iPhoto library (into the same Event as the original JPEG). However, this leaves me with 2 copies of the same picture: 1 JPEG, and 1 PSD.
The problem is, I now want to go back and do more tweaks on the PSD, the end result of which will make the JPEG version out-of-date. I can either
1) Open both the PSD and JPEG versions at the same time, tweak the PSD, then copy and paste the flattened layers on top of the JPEG version and "Save"
2) Open only the PSD, tweak, and save a copy as a JPEG onto my desktop and re-import into iPhoto.
Although a little tedious, both options seem to work. Are there any other options? What do you suggest? I'm curious to see how others manage this.

I don't have a solution for you (sorry) but I'd like to comment because I'm in a similar boat. However instead of saving PSD files to the desktop, I've been advised to save these to TIFF format in Photoshop by a professioal photographer friend of mine (I think he feels its a more universal file format than PSD for archival purposes). The downside is the files are huge.
I imported high resolution jpegs into iPhoto. I then use Photoshop to edit and save the flattened jpeg version back to iPhoto (thankfully, keywords are preserved this way). I recently realized that I need to save a copy of the edited file in a lossless format like TIFF or PSD. Unfortunately when I save the file to TIFF and import it back into iPhoto, keywords are lost. This is a drag.
What I am trying to figure out is how I can retain my keyword info in the edited archival version. Any tips?
I'm beginning to question whether I should import my photos in to Photoshop (or PS Bridge) first, save the original for archival purposes, do the majority of editing and save a TIFF/PSD file and then import this file into iPhoto for keywording, further editing, downsizing, etc.

Need Help. PSD corrupted in middle of workflow.

I have no idea what happened to my psd. I have never seen this before and am hoping I just pressed some keys.
I closed photoshop restarted computer and nothing happened. All these are supposed to have images I was on my last layer & wasted 2 hours.
Has anyone had their psds corrupt like this? If so How did you fix it? I am on a deadline. Also how can I prevent this problem from happening again.
PLEASE HELP!

I hate to tell you this, but you are probably out of luck. We see this once a month or so, and people seldom manage to retrive anything worth while, but it is unusual to see this happen mid workflow. It usually seems to happen when saving, or is discovered when attempting to open a file.
You mave have something in the recovery folder if Photoshop consideres itself to have crashed, but I don't know what OS you are using. (Allways best to upload your entire screen at full res so people can more information).
You may be able to use one of the PSD recovery apps found on the Web, if your last save is also corrupted. I'm assume you save often? It is also a good idea to increment file names every 15 to 30 minutes in case of this sort of situation. A lesson the regular posters here have learned from other poster's misfortune.
Good luck, but my gut feeling is that you are probably not going to have any.

TGA/PSD w/Alpha proper workflow?

I have Targas with pre-multiplied alphas which I need to load as symbols into Flash CC.
As Flash has no .tga support I've saved them as .psd which still have the alpha channel.
When importing them into Flash they do not use the alpha channel, just show as normal graphics in a big white rectangle.
What am I doing wrong?
regards, R

Can you try importing the Targa files in illustrator and then import into Flash.,

Workflow question- psd - tiff- jpg

Here are the submission rules I need to follow:
* Convert your image into a 8 bit Tiff file (save as, Tiff)
* In an image editing program such as Photoshop, upsize the image to a minimum of 48MB. (If you make your longest side 5200 pixels and keep it in proportion to the shortest size, this should give you a file size of just over 50MB)
* Make any alterations as needed, inspect the image carefully at 100%
* At the very last step save your image as a Jpeg and send us that Jpeg. Remember, the Jpeg is the compressed size so this will typically be between 3MB-15M
Here is what I am doing, starting with .raw to 16 bit .psd :
Flatten finsihed final psd
Change image size to approximately 2x original to 96-104 Mb (5200 = 51.6Mb) using bi-cubic smoother
Change mode to 8 bit color (reduces file by 1/2)
Save as tiff
Save tiff as jpg highest quality
My question:
Is this the best flow to use or should I be editing the tiff, or going 8 bit at a different point in time? Should I be using something other than bi-cubic smoother? Or...?
Thanks for the help.

Actually sound like you are following some really out of date advice for up sizing for
Alamy or some other agency with a minimum file size requirement.
With the LR Beta 3 this can be done easily enough directly from the export dialogue. With LR 2 it is best done using LR/Mogrify in the export dialogue. The setting for LR/Mogrify to up size with size and quality that will be acceptable by them are
File Settings TIFF, no compression, 16 bit sRGB
Image sizing, and sharpening off
Mogrify Image Processing Options resize to fit total number of pixels 16.1 automatic algorithm
Mogrify Format Options change format to JPEG, quality 95%
The jpg so outputted will meet the requirements of Almay in terms of size and quality every time.
There is also the Alamy plug in which you may want to use, that makes this even easier if it is specifically Alamy you are uploading to

Workflow how - convert psd to jpeg...

Ok so in automator I have the "get specified finder items" and I have my 4 .psd (photoshop files) and then I have the next action be "convert image to... jpeg" now what is the next step to put these in a specified folder and place? What action would that be?
sorry I am sort of new...
thanks
TM

Are you using an action you've downloaded specifically for Photoshop? The Preview Automator action (which is installed by default) won't convert from PSD. The action is designed to ignore unrecognized file formats, so it wouldn't have thrown an error to tell you this. Oddly enough, Automator is fully capable of converting PSD and a variety of other formats that the action's author must have been unaware of. Check out this recent thread on the subject:
http://discussions.apple.com/thread.jspa?threadID=389497
You'd just have to swap out TGA for PSD.

TIP: Photoshop Workflow that WORKS (for me)

Been thinking about this for a while and have figured out a workflow that integrates photoshop(PS) editing quite well with Lightroom (LR).
My goals.
*Export to PS in TIF PSD or jpg.
*Autoimport back to library for stacking with original once edited
*Avoid excessive browsing while exporting and importing.
Solution involves use of Autoimport to a 'SORT' folder.
It is mainly for use with single images that I want to pay extra attention to.
Here are the steps.
1. Create 2 new empty folders somewhere accessible. This can be done with the '+' key in the Folders panel. I have mine in my root photo directory. Call them Develops and 1ASORTBOX (the 1A means your sortbox will be at the top of your folder list in LR).
D:\Develops
D:\1A SORTBOX
2. File>Auto Import>Auto Import Settings...
- Set Watched folder to D:\Develops
- Set Destination to D:\1A SORTBOX
- Set Subfolder to Misc
- File naming :filename
3. Find a RAW file that needs photoshopping. Develop.
4. Export to destination D:\Develops
- choose format etc. FILENAME can remain the same!
- EXPORT
You will now see your file appear in the 1A sortbox/misc foler at the top of the list. Develops folder stays empty.
I created the Misc subfolder so that I can specify subfolders in the future if I want. In the meantime, they all go to misc, but I view them by selecting the top level 1Asortbox folder (all subfolder items remain visible) and sort from there.
5. select the image in the sortbox - then ctrl-E to edit in PS.
you can also automatically open the file in PS by selecting that option during export - but you end up with 2 files when you save - this works because PS tries to save the file in the develops folder which is then autoimported)
- edit the original.
- Edit in PS and save.
6. Drag the edited file to the same directory as it's parent RAW and stack it there. (I keep my edited one on the top of the stack becuase that is the one that will be exported when I do a batch export) It can be the same filename as the original. (I wish we could stack across subfolders)
This method speeds things up a bit for me.
I avoid having to select an output directory every time I want to export a PSD for editing. The export directory is always set on D:\Develops. It is so handy to have the file autoimported with all metadata intact (including heirarchical keywords). Much easier to drag the images from the sortbox folder destingation folder than to find and reimport single images manually.
I then use the Ctrl-E edit in PS function if I want to edit these files further. Choose edit original - save will overwrite your PS edits. If you want to keep the original edit, then edit as a copy or create a virtual copy first.
Hope this helps those struggling with the whole PS integration thing. Sorry its so long - it find it hard to explain these things.
Any suggestions to improve this would be fantastic.
Cheers
KEv
PS still trying to get my serial email. Grrr.

I have used this workflow for developing a few shoots and it has been working a treat. Makes lightroom a pleasure to use for me now.
The automation results in a RAW and jpg in the same folder with same name. Good for stacking and keeping a clean reference system.
I discovered a bug that occurs with the samename RAW/jpg in the same folder. Posted a thread here:
http://www.adobeforums.com/cgi-bin/webx/.3bc3493d
Basically if you rename the jpg, the RAW gets renamed too. And you can move the jpg around in grid mode properly. If you don't need to rename or move the jpgs around then the workflow is fine.
So I've made a slight adjustment to the workflow which auto renames the developed jpg.
The steps are now:
1. Export from LR to watched folder d:\develops
- in the export dialog, make sure you select 'open in photoshop' in the dropdown menu.
After this step you get a jpg (or whatever format you choose) in the sortbox with same name as the RAW, and the file open in PS.
2. Edit and ctrl-S in Photoshop
- photoshop will save the edited image to the develops folder (because this is where it opened the image from). LR then auto imports to the SORTBOX folder. Because there is already a jpg with the same name in the sortbox, LR will automantically rename the jpg with filename_2.
3. Delete the original export jpg from the sortbox and move the edited filename_2.jpg to the destination RAW folder for stacking.
The filename will be different and not be affected by the bug described. Still very quick and easy, possibly better if you don't mind the changed filename.
Kev

Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,, Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"

Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,, Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"

Sorry for the late reply. My email firewall has become a little over zealous & sent a lot of my emails straight to my junk email folder, so I have only just now discovered your reply in my junk mail folder.
The only "don't open files exceeding xxx megabytes" instruction I can find in my Prefs, is in the Bridge Prefs for Thumbnails, & mine is set at 1000mb. The biggest files I handle are bigger than 200mb so I should be able to open a few, not just one.
However, this doesn't explain why I can open a psd format file of 180mb, close it, but then can't open a RAW format file of only 26mb immediately after.
I can open the RAW file only if I restart my computer - very annoying!
However, thanks for the advice about the video card & memory.
So, I'm still stuck as to what the issue is.

Editing Plug In Workflow

This is a follow up to a previous question. Firstly i know it's not not possible to add new plug ins to the internal adjustments within aperture which is a shame.
So i've tried using an external plug in, specifically Magic Bullet Photo Looks because i use the video version as well and like the results.
However is it me, or just this plug in, or is plug in integration with aperture really lame? These are the issues i've encountered, if someone knows a way around or can tell me i'm wrong that would be great
- when you edit with a plug in a 14MB RAW file is first turned into an 80MB tiff file (and at 8 bit too)
- that generates a new master, and then that starts the adjustment workflow anew basically from an 8 bit source now.
- i make adjustments then leave the plug in
- if open the image again any information about those adjustments have gone, there doesn't seem to be any storage of meta information so i cannot tweak. Like wise i'd expect some of the aperture adjustments to happen before the plug in is applied because they're more to do with source RAW conversion.
In reality i'd expect a plug in filter to be applied within the adjustments chain. So that it's live and can be tweaked. I'd also expect aperture to be able to send a screen resolution preview to the plug in or at least the image data aperture is working with rather than create an intermediate huge file.
Is this just the way it is or am i doing something wrong (please!)
cheers
paul

Like wise i'd expect some of the aperture adjustments to happen before the plug in is applied because they're more to do with source RAW conversion
That's exactly how it works. When you send a file to an external editor or plugin Aperture creates a TIFF or PSD file with all your adjustments applied. You then work with this rendered file and save it back into Aperture with whatever plugin effect applied.
that generates a new master, and then that starts the adjustment workflow anew basically from an 8 bit source now.
Or 16-bit. This is a choice in preferences.
if open the image again any information about those adjustments have gone, there doesn't seem to be any storage of meta information so i cannot tweak
Not if you work with Photoshop. You can save layered PSD files and go back in to change things from Aperture.
In reality i'd expect a plug in filter to be applied within the adjustments chain
It would be great to keep everything non-destructive. But right now it's simply not possible. In any DAM.
I'd also expect aperture to be able to send a screen resolution preview to the plug in or at least the image data aperture is working with rather than create an intermediate huge file
If you send a screen resolution preview, you're working with a screen resolution preview - not good. And for Aperture to share its image data, third party apps would need to be able to understand it. What you see in Aperture isn't an image: it's a set of instructions within an xml file that are applied in realtime. This is not trivial. It's code, just like each app or plugin has its own code. It's not something that can easily be shared universally.
Your wishes are pretty much what we all wish. But it's not yet reality.

Large Still Images into PE - One Workflow

Everyone wants the highest quality that they can obtain when doing their videos. It’s natural to want the best. Well, when dealing with still images, bigger is not necessarily better, for two reasons. First, overly large still images can really tax a system and second, one is limited to the frame size of the video, so these have to be resized somewhere - this resizing can be in the NLE (Non Linear Editor) program, or in an image processing program like PS (Photoshop), which does a better job anyway. Doing this in PS, or PSE, will result in better resized images, and they are easier for the NLE to work with. Quality is as high as your Project’s Preset will allow, and you are more efficient, with fewer crashes, slowdowns and hangs. It is a win-win situation.
Here is my normal workflow when dealing with still images. This workflow is for NTSC 4:3 720x480 with a PAR (Pixel Aspect Ratio) of 0.9. If your Project’s Presets are different, use those specs to resize to.
Since I shoot my still images in RAW, I Copy my files from the CF card to my system and catalog these images by location, subject and date (if necessary). I’ll do a quick conversion and Save_As Adobe DNG for backup. I then process these RAW images in PS with the ARC (Adobe Raw Converter), correcting them and then doing a Save_As PSD into a sub-folder. All of this is in my still photo library.
Normally, I will edit these PSD’s to find the images that I wish to use in a Video Project, and will Copy the selected images to another folder. You’ll see that I work with a lot of Copies, so my original files are always untouched and stored elsewhere. This guards against anything happening to them.
At this point, I’ll decide how I wish to use these selected images in my Video Project. Let’s just say that they are all horizontal images, and are still full-size from my camera. As stated, my Video Projects are DV-NTSC 4:3 720x480 PAR 0.9. [Remember, your Video Project may vary, so you will need to plug in the dimensions for YOUR Video Project in that case.] I also will have done my Cropping on each image individually, to get them to 4:3 Aspect Ratio. I do this my eye and by hand, rather than via an Action, because I want full aesthetic control.
In PS, I have a set of Actions for Video. An Action is like a Script, but less powerful and less involved in the writing. As I have already done all of my image enhancements and additional processing before I did my Copy to the selected folder, I only have to worry about my Action resizing these selected images for use in my Video Project. My Action here is to resize to 720x480 with a PAR of 0.9, and I normally use the Action that does this with a particular resizing algorithm, Bicubic-Smoother (though I also use Bicubic-Sharper on occasion).
For the next step, I go to my folder structure (remember, this folder contains copies of my selected still images in PSD format), and create a new sub-folder "[Project Name]_720x480." Back in PS, I choose File>Automate>Batch. Here I set my Source Folder, my Destination folder and the Action to perform. In my case, it’ll be the Destination Folder, that I just created, [Project Name]_720x480, and my Action will be my NTSC 4:3 720x480 Smooth. I check to have the Open command by-passed, because I do not need to see this take place on my monitor. When I hit OK, PS grabs all files in my Source Folder, runs the commands of my Action and does a Save_As for all files into my Destination Folder. I can process hundreds of large images down to a great 720x480 PAR 0.9 via Bicubic-Smoother interpolation, in moments. Now, I’m ready to go. Last, I Copy my Destination Folder to my Video Project’s folder hierarchy (usually on another HDD), and then Import these processed stills into my NLE.
What if I need to pan on one, or more of these images, while they are zoomed out completely? I don’t have enough pixels in my horizontal dimension to do this. I am just filling the frame with my still. Well, if I find that there are such images, I go back to my folder with the full sized images in my still images library, and select the ones that need to be larger. I run another Action on these, but it’s one that resizes to something larger than 720x480, say 1000x750. Now, I have another Destination Folder with the name [File Name]_1000x750. I’ll Copy this over to my Video Project, and Import these into the NLE. Here, I can go to Project Panel and remove the 720x480 versions if I so choose, but since a Premiere Project file (.PRPROJ or .PREL) is only an XML database, I may just leave them. It does not contain any media files, just links to where they are on the system and to what operations are performed on them.
By doing my resizing in PS, rather than in Premiere, I have accomplished two things:
1.) I have better quality resized images, using the algorithms in PS, plus have a choice of several interpolation methods to work with.
2.) I have lessened the processing load on my NLE and on my system, while doing the editing
I get higher quality and lower resource overhead - hence my reference to "win-win."
Now, back to my aesthetic control. I do not do any automatic zooming or panning. If one allows the NLE to do this, then they will want to probably process all of their images to 1000x750 (remember, this is for an NTSC 4:3 Project, so you will need to calculate what YOUR Project will require).
The two programs that I use are Photoshop and Premiere Pro, but Photoshop Elements can do the same things, though the exact commands might be different. Premiere Elements will handle the resized still images, just like Premiere Pro and the only difference will be the terminology used when one wishes to Import the still images.
I also keep all of my images in .PSD (the native format of PS), and do not convert to JPEG, or other. If one’s camera shoots only JPEG, I suggest writing the Action to do the Save_As to .PSD, as another JPEG compression will cost one quality. Yes, the JPEG’s will be smaller, but remember we are looking for the ultimate quality, so larger file sizes are just part of that equation.
One does not have to deal with all of the Copies, as I do. However, this allows me to go back to the originals, or to the processed full-sized .PSD’s at any step along the way. There is only one thing worse than not being able to go back to an intermediate version with full Layers and Adjustment Layers, plus any Alpha Channels, and that is finding out that you’ve lost your original RAW and DNG backups! That’s why I do a lot of Save_As and also work from Copies all along the way.
Hunt

Your workflow looks good. I do similar, but use PS, in lieu of LightRoom. I also do DNG's for my archives.
Provided that one chooses a JPEG compression algorithm setting that does not do too much compression, I doubt that anyone, but the most very critical, could tell the difference in Video. Most of my tests on PSD vs JPEG have been for print. There, one can more easily detect the differences. Video "hides" some of that.
To date, I have not had a Project where the Asset size differences between equally sized PSD's vs JPEG's caused any slowdown, or problem. There could be a resources savings with the smaller JPEG files, but there is a tiny bit of overhead dealing with the JPEG compression. I have never tested this, so can only guess that the smaller Asset size of the JPEG would trump that overhead - just a guess on my part.
For me, keeping the images in PSD does save a tiny bit of work in my Action (basically one less operation to perform), but I doubt that one could measure that time difference, even over the automation of hundreds of images. Besides, it's only one additional line in the Action. My feelings on JPEG vs PSD is firmly based in my print experience, and I am probably being too critical with images going to video. When I move up to HD and BD authoring, I need to apply a very critical eye, to see if I can tell the differences on an HD TV. So long as one does not apply too much JPEG compression, the differences should be very slight, at the worst, and maybe not even noticed, at best.
I do minimize the impact of many files on my Project by sizing to what I need. If I will not be doing any pans on zoomed-out images, I size to my Project. For pans on zoomed-out images, I calculate just what I will need for those pans, and might end up with several groups of sizes, to accommodate each. Still, the vast majority will be sized to exactly what I need for the Project - very few extra pixels.
In my case, and yours too, I have my RAW, my DNG, my working Layered PSD's, and then my sized output. I always keep all working PSD's, as I might change my mind, or my client might change theirs, and I do not want to have to go back and redo work, if I still have those working files. I also do as little destructive editing, as I can, using Dupe Layers, and Adjustment Layers, whenever possible. If I can, I never Flatten, or Merge Layers, so I can make any/all changes at any time, and only have to do the resizing via the same Actions. That is basically a "one-button" solution, once I have made the changes required.
Good luck,
Hunt

Creating a new title template from a .psd file

We weren't happy with any of the lower thirds that Premiere had for us, so I got one of the people in my office to create a lower third that would look nicer, but now I've just got this .psd image that I don't seem to be able to get into title form.
Its just an image of a thought bubble that says "science tips" and then a darly shaded rectangle with blue text inside of it, but when I try to import the .psd image as a logo in the titler screen it comes up with the thought bubble very washed out and see through ( the thought bubble is white on the inside in the .psd file) and the darkly shaded area doesn't show up at all.
I fell this may be a photoshop error on my part as likely as anything else, but mostly, I'm wondering if bringing it in as a logo is the right way to go?
-Dan

Ann,
I like that workflow.
I handle my "custom" Lower-Thirds (or similar) just a bit differently. I create the artwork in PS, and then Import that as an Asset. I'll then do a regular Title for just the text, placing it above the PSD of my graphic. My workflow does mean that I will need to Import that PSD into each Project, but I put a copy into my Common Assets folder, for ease of Importing, as is required. I can also individually animate each element, as is needed. If I wish to animate the Layered elements of the graphic, I'll Import as a Sequence, keeping my Layers, but with Lower-Thirds, I usually end up animating both the graphic and the text as a unit, i.e. the same Keyframing for each of those elements.
Your method will all one to do a full Save_As a Template, and allow for easy changes of the text, as the graphic is but a logo. Neat!
Thanks,
Hunt

Problem while starting on a workflow

Hello,
I am using SharePoint 2013 online.
I have one site collection, that I am the owner of him, and I have full control on all sites.
I have a workflow that create a new item In a form library, and when I am trying to activate him it always failed.
the internal status is:
RequestorId: b1bc1314-d192-a837-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 401 {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access
denied. You do not have permission to perform this action or access this resource."}}} {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["55"],"SPRequestGuid":["b1bc1314-d192-a837-b1bb-5c1835644592"],"request-id":["b1bc1314-d192-a837-b1bb-5c1835644592"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["16.0.0.1810"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Wed, 07 Aug 2013 00:56:41 GMT"],"P3P":["CP=\"ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT
NAV ONL PHY PRE PUR UNI\""],"Server":["Microsoft-IIS\/7.5"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]} at Microsoft.Activities.Hosting.Runtime.Subroutine`1.SubroutineChild.Execute(CodeActivityContext
context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
executor, BookmarkManager bookmarkManager, Location resultLocation)
The work flow have no problems when I checked him In the SharePoint designer.
What should I do?
Thanks
Tamir Maimon

Hi,
Base on the description, you fail to start workflow thought you have full control on all sites .
I suggest you to add you to the site with edit permissions. This ended up being a permission for the user initiating the workflow though they had permissions to edit the entire site adding them to the site with
edit permissions (directly and not through an AD group) fixed the problem.
I also suggest you to create User Profile Service Application and then you need to create Sync connection and run full sync. All SharePoint 2013 workflows must be started from real users, not system
account.
Here are some similar threads for you to take a look:
http://sharepoint.stackexchange.com/questions/63041/how-do-you-track-down-workflow-errors-in-sharepoint-2013
http://www.sharepointviking.com/system-unauthorizedaccessexception-when-running-sharepoint-2013-workflows/
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/fe78502c-9e49-4ad6-9e0c-40a439c54e57/workflow-cancelled-with-a-sharepoint-designer-2013-workflow
In addition, this thread seems to related to SharePoint Online. You’d better to post your question to the forum for Office 365:
http://community.office365.com/en-us/f/default.aspx .The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read
the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Best Regards,
Linda Li

Please help me Automate an Aperture/Photoshop workflow

I'm trying to streamline the process of exporting a RAW file from Aperture to Photoshop for editing and then re-importing it into Aperture. I have zero experience with Automator, but someone else on the Discussions site was kind enough to share hte Automator process he uses for this.
Problem is, I can't get mine to work (or I don't know how to make it work).
I created a folder called "Photoshop-IN" where I would export the RAW files from Aperture that need editing. Then I created a folder called "Aperture-IN" where the completed Photoshop files would be exported for re-import into Aperture. Then I created this workflow:
http://homepage.mac.com/chriskresser/PhotoAlbum16.html
I think the workflows are correct, but I don't know what to do at this point. The original poster said something about making them "watched folders", but I have no idea what that means or how to do that.
To test the workflows, I tried exporting a RAW photo from Aperture to a "Photoshop-IN" folder. Then I opened Automator and clicked the play button for the designated workflow. It tells me it executed properly, but nothing happens. The CR2 file wasn't opened in Photoshop, is still in the folder, and didn't get moved to the trash.
I also tested the other workflow (getting PSD file back into Aperture), and that doesn't seem to be working either. With this workflow, I get the following message. "Aperture got an error. Some parameter wasn't understood. (-1715)".
What am I doing wrong? I realize that this might be pretty far off topic, as it is more a question of how to use Automator and possibly AppleScript. But any help would be appreciated, including direction to some resources where I could learn more about Automator (the help section is woefully inadequate!)
Thanks again,
Chris
G5 2.0 dual-core Mac OS X (10.4.3) 17" Apple LCD, iSight, Bluetooth Keyboard & Logitech Cordless Laser Mouse

Your PS-in workflow is too complex, all it needs is a Finder action to open in PS:
http://www.azurevision.co.uk/aperture/open-in-ps-action.jpg
Then File>Save as Plug-in..., choose 'Folder Actions' and then where it asks what folder to attach it to, navigate to your folder. Now, every file that is copied, moved or saved into that folder will be opened in PS.
The import into Aperture workflow is mostly OK, but you are passing a folder from the first action, not files. Try adding a 'Get Folder Contents' action just after the first action. With a bit of jiggling around and using the two actions of that workflow you should be able to save it as a folder action.
A couple more threads using a slightly different approach:
http://discussions.apple.com/thread.jspa?messageID=1292903
http://discussions.apple.com/thread.jspa?messageID=1372571
Basically these export a RAW file out to a watched folder (as you are trying to do), but instead of saving it out and re-importing into Aperture, a duplicate file is made in Aperture by using 'Open in external editor' and saving the converted file into that.
Ian

PSD (and AI) thumbails in Windows 7 64 bit?

Does anyone have a fix for the missing Photoshop (and Illustrator) thumbnails (CS3) in Windows 7 64 bit Explorer?
Something easy to implement that doesn't involve purchasing and running an additional 3rd party commercial solution?
Please don't answer "Bridge". I should not be forced to use an extra resource hogging application to simply view my files in my normal workflow.
I used to use the psicon.dll and aiicon.dll workaround in XP without any problems whatsoever. I know there are people here that claim these caused information loss and other nonsense like that but they worked perfectly fine. However, I had to recently upgrade my OS and unfortunately this workaround doesn't function properly in Win 7 64 bit because of the different directory structure.
I'm sure these could be made to work by rejigging the registry edit files to point to Programs (x86) but I'm not that confident in my abilities there. I've searched high and low to see if anyone else has done this yet but haven't come up with anything promising.
I was also wondering if CS5 corrected this problem? Can anyone tell me if they are able to see their PSD and AI thumbs in Win 7 64 bit Exploer with CS5?
Any help would be greatly appreciated! Thank you.

FYI, .psd thumbnails do not show in Windows 7 x64 Explorer with Photoshop CS5 either. Edit: Oops, I see that was already answered.
There's a psicon.dll file in the 32 bit Program Files (x86) subfolder, but none in the corresponding 64 bit area.
Anyone got a direct link to that discussion between Adobe and Microsoft?
-Noel

Ae/Ps .psd workflow

Similar Messages

Maybe you are looking for