Action sequence with Aperture 2?

I would like to do a snowboarding sequence edit with Aperture 2, but i dont know how? I know it is possible with the layers with photoshop. Can anyone help me please!

Aperture is a photo editor, you can't do any kind of "sequence editing."

Similar Messages

How can I stop an action sequence with another

Hi,
I am quite new to flash catalyst. I made a side with an office where you can click the phone to go to the status "phone". In there you should be able to call some virtuell people. I made buttons with names that trigger different action sequences with showing the name of the called person in the display and playing a sound file that sounds like a call. Now my problem is when I am clicking a different name while it is still in one action sequence, the other one shows up over the first and both sounds are playing at the same time.
How is it possible to tell the action sequence to stop all others when it is started?
Thank you for your help.

Sorry, I'm a bit confused now. Just to clear this out:
WDDOBEFOREACTION is for validating user inputs BEFORE Actions and HERE you can prevent actions from happening
WDDOAFTERACTION is called JUST WHEN an action is happening for all visible Views (it's to prevent redundant code which would be equal for all event handlers)
WDDOBEFORENAVIGATION is AFTER Actions and BEFORE navigation.
Check the chart in the following Link (sorry it's german, english version seems not available, but the chart is in english nevertheless)
http://help.sap.com/saphelp_nw73/helpdata/de/49/b8c706c7c26d7ce10000000a421937/content.htm
In my opinion put an if clause into WDDOBEFOREACTION, check whether the respective field is filled; and in case it is filled, execute your method; if not, don't.
That's why I am confused, you kind of answer your question within your question itself )) or I still don't understand what you want to accomplish.
best regards, hope this helps you (if not, try to explain it even more detailed for me ;-D)
Lukas

Using the same action sequence with multiple buttons and exclusive conditional interactions

Hi all,
first of all, pardon me for my english and if I post questions already answered, but I can't find anything about that.
I'm new to flash and I decided to use Flash Catalyst to speed up the building process of a multimedia presentation for university.
I have a menu with 10 buttons that change a text box on rollover (I converted it to a button label) and I need to reset the name of the current page on RollOut. Since the action sequence for it is the same of every button on one page, is there a faster way to apply the sequence than repeating it for every button? (I had to do it 10x10=100 times... and what if I made some mistake? )
Another question is I want to disable the interaction of the menu button of the current page, but conditional interaction let me choose only an "if in state" condition an not a "if not in state". How can I do this? should I simply disable the button on that page?
Thanks a lot for the help!
Cheers from Italy

I answered to myself by grouping buttons and disabling the button in his state.
Thanks anyway!

Action sequence using PS Elements 10

Hello Group, first post here anyway, I am trying to make an "Action sequence" picture using PS Elements 10, example: I took a few pictures of a guy surfing and what I would like is to merge 3 or 4 shots into one picture (I hope I explained this right) SO what I would end up with would be a guy surfing on the same wave but it would show him on it in 4 different places although its just the same wave.
Thanks, James

I am using Windows 7. I think that the best path might be a third party conversion program. Do you have a recommendation?
Thanks,
Fred Czerner
<mailto:[email protected]> [email protected]
M: 703-909-9001 (Preferred)
H: 703-329-0098
F: 703-329-0099
NOTICE: This message is for the designated recipient only and may contain privileged or confidential information. If you have received it in error, please notify Fred Czerner immediately and delete the original. Disclosing, copying, distributing or taking any action in reliance on the contents of this e-mail by other than the designated recipient is prohibited.

Got action sequence to "loop" but it shows in all states - conditional statement to fix it?

Using Flash Catalyst & Notepad (to open and alter the code in the "Main" MXML file) I'm able to "loop" an action sequence on the home state for my swf by changing the code as follows:
ORIGINAL CODE
<s:Parallel id="Sequence3">
ALTERED CODE
<s:Parallel id="Sequence3" effectEnd="Sequence3.play()">
The desired effect is a sequence (of 4 images) that loops whenever a user is viewing the home state. It is activated "On Application Start"
The PROBLEM is that the loop continues in all other states (it appears in the background - behind the objects that are supposed to show up on the other pages and only begins to show up in each state when the sequence begins another loop).
I am assuming I need a conditional statement --- something along the lines of:
while (condition){ statements;}
...in other words, ONLY while currentstate = "Home" it should loop the sequence. What would be the correct code for this conditional statement and where would the conditional statement be inserted to loop the sequence as desired??? Or... is there another better way??
My current code for this action sequence is:
<s:Parallel id="Sequence3" effectEnd="Sequence3.play()">
            <s:Parallel target="{designlayer1}">
                <s:Fade alphaTo="0" duration="500" startDelay="2100"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage2}">
                <s:Fade alphaTo="0" startDelay="2100"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage3}">
                <s:Fade alphaTo="0" startDelay="2100"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage4}">
                <s:Fade alphaTo="0" startDelay="2100"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage5}">
                <s:Fade alphaTo="0" startDelay="1650"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage6}">
                <s:Fade alphaTo="0" startDelay="1800"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage7}">
                <s:Fade alphaTo="0" startDelay="1950"/>
            </s:Parallel>
            <s:Parallel target="{designlayer5}">
                <s:Fade alphaFrom="1" alphaTo="0" duration="0" startDelay="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="2650"/>
                <s:Fade alphaTo="0" startDelay="5300"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage8}">
                <s:Fade alphaFrom="1" alphaTo="0" duration="0" startDelay="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="2650"/>
                <s:Fade alphaTo="0" startDelay="5350"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage9}">
                <s:Fade alphaFrom="1" alphaTo="0" duration="0" startDelay="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="2650"/>
                <s:Fade alphaTo="0" startDelay="5350"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage10}">
                <s:Fade alphaFrom="1" alphaTo="0" duration="0" startDelay="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="2650"/>
                <s:Fade alphaTo="0" startDelay="5350"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage11}">
                <s:Fade alphaFrom="1" alphaTo="0" duration="0" startDelay="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="2650"/>
                <s:Fade alphaTo="0" startDelay="4750"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage12}">
                <s:Fade alphaFrom="1" alphaTo="0" duration="0" startDelay="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="2650"/>
                <s:Fade alphaTo="0" startDelay="5000"/>
            </s:Parallel>
            <s:Parallel target="{designlayer6}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="5900"/>
                <s:Fade alphaTo="0" startDelay="7900"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage13}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="5900"/>
                <s:Fade alphaTo="0" startDelay="7550"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage14}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="5900"/>
                <s:Fade alphaTo="0" startDelay="7900"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage15}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="5900"/>
                <s:Fade alphaTo="0" startDelay="7750"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage16}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="5900"/>
                <s:Fade alphaTo="0" startDelay="7900"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage17}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="5900"/>
                <s:Fade alphaTo="0" startDelay="7900"/>
            </s:Parallel>
            <s:Parallel target="{designlayer7}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="8500"/>
                <s:Fade alphaFrom="1" alphaTo="0" startDelay="11000"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage18}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="8500"/>
                <s:Fade alphaFrom="1" alphaTo="0" startDelay="11000"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage19}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="8500"/>
                <s:Fade alphaFrom="1" alphaTo="0" startDelay="11000"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage20}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="8500"/>
                <s:Fade alphaFrom="1" alphaTo="0" startDelay="11000"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage21}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="8500"/>
                <s:Fade alphaFrom="1" alphaTo="0" startDelay="10650"/>
            </s:Parallel>
            <s:Parallel target="{bitmapimage22}">
                <s:Fade alphaTo="0" duration="0"/>
                <s:Fade alphaFrom="0" alphaTo="1" duration="0" startDelay="8500"/>
                <s:Fade alphaFrom="1" alphaTo="0" startDelay="10800"/>
            </s:Parallel>
        </s:Parallel>
Thank you!!!!!!!!

Figured out my issue...
I had to select each layer for the 4 photo sequence and "Remove From State" for each layer. If this is done with all layers except the "Home" state, the images show only where appropriate.
So...   "Loop an action sequence" is really easy.
I've seen a lot of complaining that "FC can't do it" but with a very simple code mod, I was able to do it WITHOUT using the video timer method.
I should also mention that I've never worked with Flash at all before this project and am only self-taught in HTML (basics). I was able to make a pretty good looking Flash component for a web site and never would have attempted it without FC. I have to say, while FC is a bit limited, GUI-based Flash is a great add for Adobe and will save me over $2k per year in web admin.
To edit the document in Notepad as mentioned in the first post:
the full text can be found here http://www.judahfrangipane.com/blog/2010/09/03/flash-catalyst-jailbreak-for-flex-developer s/
Editing MXML Documents
To edit your projects MXML documents we first need to find the path to the Flash Catalyst workspace. To do this publish your Flash Catalyst project (CMD / CTRL + ENTER). Now, the browsers URL shows the path to the project workspace. So in this URL, "file:///Users/judah/Library/Application Support/Adobe/Flash Catalyst/workspace/Project/bin-debug/Main.html", the project MXML documents are located at, "file:///Users/monkeypunch/Library/Application Support/Adobe/Flash Catalyst/workspace/Project/" when on a Mac.
Flash Catalyst project files
Project Files Description
/src - location of the application source files
/bin - the location of any additional flex libraries
/bin-debug - location of testing swf
/html-template - location of the html template that wraps around your application
/src/Main.mxml - the main application file. make your application changes here
/src/Main.css - the css stylesheet of the main application
/src/components - the location of custom components and component skins
/src/assets/graphics - location of optimized FXG graphic symbols
/src/assets/images - location of images
You can edit these XML documents in any text editor. To apply the changes you need to save the file and refresh the Flash Catalyst project. You can do this by opening the changed document in Flash Catalyst code view. When we do this it will recognize the document has changed and prompt you to use the newer version of the file. Select Yes. If the project does not rebuild immediately publish it using CMD + Enter.

Syncing Folders with Aperture 3, How To?

Hi,
I was wondering how can I keep a file system folder in sync with Aperture library (Both when I add files to the system folder or when I create a new versions in the Aperture library).
I know it is not supported in Aperture. Is there some scripts or a plugin to do this?
I know that Aperture was designed to be the sole Manager for the photo library, but I need this feature. Please let us not turn this discussion into a discussion about managing libraries emoticon - smile
Any help is appreciated!

Terence Devlin wrote:
You can use
1. Folder Actions and AppleScript
or
2. Automator Actions
or
3. an app like Hazel
to watch a folder and perform certain tasks when a change is detected - like importing to Aperture.
Thank you. That is helpful. Where can I get these scripts?
However, matching versions is another matter. There is no file for a version, it's simply an entry in the database. Do you really want to export every version as a jpeg/tiff ?
Sometimes, I would like to export the versions to have them as JPEGs. I know that Aperture was designed to manage versions in an incremental fashion. But sometime, I would like to have this option (For my PS3 to see the files [I know that you can sync your aperture library] or for my wife's Windows laptop to see the files etc...).
Rather defeats the purpose of Aperture.
Regards
TD
You can use
1. Folder Actions and AppleScript
or
2. Automator Actions
or
3. an app like Hazel
to watch a folder and perform certain tasks when a change is detected - like importing to Aperture.
However, matching versions is another matter. There is no file for a version, it's simply an entry in the database. Do you really want to export every version as a jpeg/tiff ?
Rather defeats the purpose of Aperture.
Regards
TD

How to name image sequences with the convention "name.[####].extention"?

Quicktime doesn't seem to respond to the naming convention used in other programs like After Effect or Combustion for naming image sequences when you are exporting the sequence. It does let you put a space before the sequential numbering but this is no good for using image sequences in Maya for example. During the save prompt if we were to save the image sequence as AppleMovie.[####].jpg in these programs we would yield an image sequence with AppleMovie.0001.jpg, AppleMovie.0002.jpg, AppleMovie.0003.jpg, etc. Anyone know if there is a way to do this as I've described?

Open ExtendScript Toolkit this can be found here:-
PC: C:\Program Files\Adobe\Adobe Utilities
MAC: <hard drive>/Applications/Utilities/Adobe Utilities
Copy and paste the code into a new window and then save the code to:-
PC: C:\Program Files\Adobe\Adobe Photoshop CS#\Presets\Scripts
Mac:- [hard drive]/Applications/Adobe Photoshop CS#/Presets/Scripts/
If photoshop was open, close and re-start it so that Photoshop can pick up the new script.
Now you can create an action to run the script and do your save so that this action can be batched.
To add the script to your action:
File - Scripts - select the script (this will add the new layer)

Too late to start up with Aperture?

I'm aware of both Aperture and iPhoto being trashed by Apple in the near future. I have been using iPhoto on my MacBook Pro since it was introduced and usually do some additional editing as required using Adobe Photoshop Elements. But now I'm starting to shoot in RAW, and iPhoto won't even take RAW files into it's library without converting them to Jpegs. I think the best bet for me would be to upgrade to Aerture but I also know it's no longer going to be supported. In fact, I've read that Apple is no longer interested in the entire advanced enthusiast and pro photography spaces. Thoughts and advice for me? I have been spoiled by the wonderful Apple apps that work so nicely. By the way, I haven't upgraded to Yosemite, nor do I intend to. I think in my case it will take me in the wrong direction.

Reasons for migrating to Aperture of course depend upon your intended use. As pointed out here, development for Aperture has ceased. Apple has decided to migrate to another application, using cloud based back end for image storage. There has been more than one or two posts of disappointment on this course of action. In the end it's Apples decision however right or wrong the users believe that decision to be. Your best bet is to look at the features, determine if those are of use to you, scan the threads here for comments, then determine if the cost is worth it.
As opined Aperture probably has about a year of life left. After that you may be able to use it so long as you do not upgrade your operating system. But make no mistake - there will not be an Aperture 4.x. Nor, in my opinion will there be any significant (or heroic) efforts to fix what are now significant issues with Aperture.
The trade off, in my opinion is not worth it. Especially when you can get Lightroom now for a modest price. That is if you don't mind paying a monthly usage fee and really don't need facial recognition. The former being the pricing plan Adobe is moving to and the latter being completely absent from Lightroom. I don't know of any other viable professional package on the market right now. On the upside, Adobe products do support IPTC extended metadata which Apple never adopted. Understandable, it was an Adobe push - but the data stored is pretty nice. Mostly dealing with model and release information (and others, read the IPTC specs if you are interested) - if you deal with that kind of thing.
As for my experiences - Aperture use to be an incredible product. Especially with the introduction of Facial Recognition - which is now horribly broke. Here are some of my experiences.
FACES:
- Aperture now scans my entire photo library for new faces in every image every time the application fires up. This isn't a problem if you have a few hundred images. Once you start hitting about ten thousand (10,000) it becomes a nuisance. It takes about 45 seconds. Multiply that time out based on your library size.
- Aperture now rescans every identified face for a match, every time you identify a new face. Ok, I get this process. You have marked this guy as John Smith, now we are going to look for possible matches for John Smith. The only problem is that it appears to being in every face which it cannot justify as someone else.
- Aperture often double tags a face. To explain this you have to understand what the software is (probably) doing and how it records facial locations. First it applies some order of facial recognition. It looks for things which appear to be faces. Eyes, nose, mouth. It then draws a box around that area. You have the option to select that boxed area and in the upper left hand corner click on the "x" to close the box. Except when two boxes are exactly on top of each other. It's maddening. You cannot get rid of either box. Nor, can you identify the name of the person in both iterations of the box. If you understand all the places where you can name people (every software package has multiple places to do the same task) then you can select one of the boxes and tell Aperture that this area "is not a face". But since you are now telling the AI that the information contained within the defined area is not a face (when in fact it is) you are setting yourself up for a real HAL9000 moment. And if you don't get that reference, you are simply confusing the system. Especially when you leave box 2 in place and give that person a name. So is it a face or isn't it? Aperture appears to be using both decisions (is and isn't a face) in future iterations of facial identification (finding faces in an image) and facial recognition (is this face Johnny Smith or Jane Smith).
PLACES:
- A number of folks have reported problems with the geolocation of images. With the upgrade to the latest OS I have also begun to experience this problem. Images which I shot in my home studio were correctly mapped within a few feet of my home. With Aperture 3.6 many of them are not even on the same block. I actually have photographs which were previously (properly) mapped in central Maryland, that with the 3.6 upgrade are now tagged in the middle of the Pacific Ocean. Yes you can manually move them to their correct location - but again, thats great with a few hundred images. Thousands becomes a real nightmare.
This same geomapping problem has reared its head in faces as well with some users reporting the placement of the facial identification box in the wrong location on the image. Far be it from me to disparage software developers but it's almost as if the crew forgot that the image coordinates (whether for dropping a box on a photo or a pin on a map) start at 0,0 being the upper left corner of the display. /snark
STORAGE:
- A couple "upgrades" back Aperture migrated a reasonable and easily understandable storage methodology in which photos were filed (on your hard disk) in a directory architecture based on the date/time of image. So, if something horrible happened a savvy user could open the Aperture package, navigate through the directory and recover lost or damaged data. Not anymore. I defy anyone to explain the system now. It appears to have something to do with the ingest date, solar or lunar cycle and a hashed algorithm of some programmers mothers birthdate which is then translated into an XML filename. All that to say - good luck finding your photo IF you need to AND you are storing images internal to the Aperture database. But lets get serious about filing images under a directory system based on import date/time. This is great - if you import your photos on the date of the shoot. But, if you go on a two week trip of Europe and ingest all your photos the day you get home, well that's not too bad. A year later when you have to recover all your photos from a significant system failure and end up ingesting 10,000 photos on 15 May 2014 that is another story entirely. Now, good luck finding your photos on the hard disk (if you need to that is).
SECURITY:
- Apple applied the "sandbox" theory to image security. Basically in a nutshell all your photos are locked from editing by only approved applications. So don't even think you are going to download some awesome script to do some wonderful task and have it work. Sorry. It took me months of phone calls with apple support before one of those on the line even thought to walk me through my editing process and determined the script/app I was using was not apple approved and this was causing my problem. I get it, new risks in computer data and all. But there comes a point when you have taken security so far as to lock the user out of the loop.
CRASHES:
- We all have them, and they all happen at the worst possible moments. In the past 2 days I have been working in Aperture with my data and experience Aperture crashes about every 45 minutes or so. Yes, I have repaired my permissions, yes I have repaired the database and Yes I have rebuilt the database. It just appears to be another nuisance of Aperture that wasn't there a couple years ago. I have even gone so far as to completely uninstall Aperture, reload it from scratch and re-ingest all my images (that is how I discovered the whole ingest date/time versus shoot date/time storage della described above). My entire library now (in the Aperture Package) falls under a single year (2014) when previously it was spread across 40 years (from the 70's to current date). Yes, I have images from the 70's in aperture. I scanned a lot of film over the years. Regardless, I could never track down exactly why the crashes were happening. Some feedback from Apple would be nice - I have after all must have sent them a few hundred crash reports by now. My RAM is good (yup, I have tested it), drive space is fine and I have plenty of it so ..... Im left scratching my head.
Aside from all of that - I loved Aperture, while it lasted. I will be saddened by it's loss and to date I haven't heard anything yet which gives me hope about Photos. As someone who is occasionally paid, and who occasionally pays to shoot (read into that what you will) I refuse to store my image library on anyone else cloud. I have my own storage architecture which has worked fine for me. I haven't lost an image now in the many many years I have been using it. If you shoot a lot I recommend you look into Drobo. I was an early adopter and have never looked back. I have two 16TB units on my desk - one for live data, one for TimeMachine.
Cloud storage is simply too risky.
1. You are reliant on too many factors which are (a) out of your control and (b) are run by people who really don't care about your data or your business. Not to mention the constant finger pointing. If a switch goes out somewhere in Nebraska I hope you had a local copy of your data because now you can't work. But then again, that defeats the whole purpose of cloud storage doesn't it? How many Apple users signed up and put up web pages in what is now the cloud? You remember those days? You data is your data and will always be there? Until we change our ToS and now longer support personal websites.
2. Pricing. Seriously look at the pricing. The cloud tops out at 1TB for $20/month. Not bad. What do I do with the other 15TB of data I have? Oh, and after 3 months I could have purchased a Western Digital portable USB 1TB. If Moore was right (and so far he has been pretty close) that 1TB next year will only cost me $30 at the local Best Buy. If you can find it. You know 6TB drives come out this fall? Only a couple hundred dollars each. About 1 years payments on the cloud. Now I realize I might get slammed there - not everyone has $60 extra dollars for a portable 1TB drive. But I am assuming you do since you are tinkling about spending $70 for an app which is only viable for another year.
3. Cloud storage really? I don't know about you but the last time I ran an all day shoot I used up about 128GB of card space which took me a couple hours of transfer time (card to local disk). Now, how long would it take me to run that up to the cloud before I can use it. And that was on an older camera which was half the megapixels of what I am shooting now. So, 1/4 of my storage maximum being transferred up to the cloud after only one shoot. Awesome. Ill get a coffee, take a road trip, and in a couple days my images will be ready for first draft editing. Meanwhile my client will be ..... strumming his fingers? Don't worry though sir - a couple more days and your proofs will be available online. For everyone with any mad skillz to hack into. The only secure computer is one not online.
So, there are the down sides from my perspective. Yup, it's one sided. If you want to know the good stuff (and there is a lot of good stuff) just read the sales brochures. It's fine product - so long as you understand the limitations. And overall I am happy with it. And I will, again, be saddened when it leaves the market.
Aperture's days are numbered. I am past denial and isolation. I guess this places me in the anger stage. There is no use in bargaining. It is Apples decision and they have made it. Depression is next. I doubt I will make it to acceptance - unless there are some significant changes to Photos and I don't see that in the works. Apple appears to be dropping their professional line of products and pushing to the general market.

How to prevent PS from skipping steps in action sequence after encountering an error while batching

Hi guys,
Would really appreciate help. I've spent several days working on this.
What I am trying to do is a long story, but the latest problem I've encountered is that when batch running an action sequence, and when PS encounters an error in a step in that sequence (e.g. a layer X is not available), it does not process the subsequent steps in that sequence.
My action sequence involves auto aligning layers from 2 image files, one a PNG file and another a JPG file.
I am batch running the action sequence on a folder of image files. The PNG and JPG files are arranged like this:
1.jpg
1-1.png
2.jpg
2-2.png
Some steps in the action sequence apply to the first image file, by virtue of the fact that the default layer in a jpg file is named "background", while some steps in the action sequence apply to the second image file by virtue of the fact that the default layer in a png file is named "layer 0".
When I run the action sequence manually, I will just click "continue" when an error message pops up, and PS will continue processing the subsequent steps in the action sequence. i.e. the sequence works exactly as I need it to.
But when I run the action sequence through the Automate> Batch command, with the setting "Errors: log errors to file", I find that PS ignores the subsequent steps in the action sequence if an error message is encountered on a step, and moves on to the next image.
This is a screenshot of my action seq:
Is there a way to get around this? I am not proficient in scripting, hence I am here seeking the expertise of this community.
Thanks,
Jay

Use sc command to put Windows Module Installer to disabled in your script after Enabling Hyper-v Role. When the system completely restarts, change it to Manual or Automatic.
Note: I have not tested it, it is just my thought, if it does not work or something unexpected happens, it means your issue cannot be fixed this way.
Juke Chou
TechNet Community Support

Is there a way to start a Sequence with Task Manager (Windows)

Hi
Is there a way to start a Sequence with Task Manager (Windows)?

Hi,
That is too bad I can not schedule my action Wizard to run via Windows scheduler... The funney things about is that on the same machine that I have created the Action Wizard and saved to to my desktop via export, when I click on it to run it asks me you want to Import that action to your Acrobat Pro X? Okay or Cancel... That Action is already there in my action Wizard List and I have exported from this same machine and I was trying to see if I can schedule it via this command:
C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat <C:\Users\Bahram\Desktop\OCRFaxedPDFs.sequ
Regards,
Jeff P.

Printing problems with Aperture

I just switched from Windows (long story, many years) to an Intel iMac 20, with Aperture pre-installed. I had a Canon PIXMA iP 6000D printer; all prints had a yellow cast. I bought an HP Photosmart 7160; all prints have a yellow cast. I have done a format and re-install of OS X and all software. I have installed my Aperture software on another iMac 20 at the store; with my printer and the store's printer the prints had a yellow cast. I took my computer to the store and printed on their printer; all prints had a yellow cast. I get the same results printing from Photoshop CS2 for Mac or from Preview. I have tried several USB cables. My monitor is calibrated with a SpyderPro 2. Prints directly from a memory chip in the printer are fine. I've tried all the adustments in the print setup; no help. I'm working on the sliders now, but with seven sliders with 100 possible settings on each I think that's seven to the 100th power possible settings. Both printers work fine with my Windows computers.
I've exhausted all the available Apple support. Anyone have any ideas?
Arthur
iMac 20 Mac OS X (10.4.8)
iMac 20 Mac OS X (10.4.8)

Well, to reiterate, I am using the HP printer as there is only room for one printer on my desktop. I am using HP paper, the "Advanced" type which is bar coded so that the printer recognizes the paper type and sets the appropriate defaults. I have also tried other HP papers, and selected them from the printer dialog. I have tried setting the paper type manually with the "Advanced" paper. I have tried printing with all the defaults left alone.
When I said that I had tried every print option in the printer dialog sequence, I meant that in the printer dialog I had tried each of the paper types, each of the color options, each option under HP Colorsmart, several types of HP printer paper with the proper option selected. Under ColorSync, there are only two options here. One is "Standard" and the other is "in Printer" which is greyed out.
Go down the print dialog. I have tried every option. Under "Paper Type, Quality" I have tried every option for paper type, quality, and color. I have done this systematically, using all available combinations.
I don't know how else to describe the process Apple and I have tried to use to try to repair my problem. Name an option--I have printed using it.
I tried the "sliders" as a possible way of altering the output from the computer to the printer, as I had exhausted all other possibilities, and if I could find the magic combination I could set it as the default and all my prints would be
affected by those settings and print correctly. They appear in the printer dialog from Aperture. My photos print correctly if I copy the file to a Compact Flash chip and place it into the printer slot and print directly.
Pardon me if I seemed snappish. I bought the iMac specifically for photographic work, have had it for a couple of months, have made several hundred prints, have exhausted support from Apple, and am grasping at straws. I have 8 GB of photos from my last trip which remain unprinted. Shortly before the trip I did two wedding shoots which were quite successful, printed from Photoshop CS2 under Windows. All my current photos print acceptably on this printer from my Windows computer. They are not acceptable printed from Adobe CS2 for Mac.
Can I be more specific in what I have tried? Do you have a suggestion for something for me to try? Apple and I are grasping at straws, and would appreciate any help you can give.
Arthur

Nikon D2Xs NEF not working with Aperture

This is so shocking. I should have researched more..... but I cannot believe that Nikon and Apple do not have it together on Aperture??
I just switched from the Canon 1DS, which worked like a charm with Aperture, to the Nikon D2Xs and Apertrue will not support NEF files from the camera. Frankly. I am pretty stunned. What's the deal? I find a lot of chatter in the forums about other Nikon model NEFs that are not working.
Since there are only 2 serious top of the line pro-digital SLR manufacturers out there, I would have thought that they would both be supported fully.
Nikon Tech support said that their plug-in developer kit has been available for a long time, it is up to Apple to take advantage of it.
Am I out of line here - ranting on..
Does anyone know of a solution to this issue, other than dumping Aperture and moving to Nikon's Capture NX (when they get to finally release it) and Photoshop?
Many thanks for you help in advance,
NIck

So you switched from Canon to Nikon. I decided to do
the switch vice versa. What were your reasons to pick
Nikon?
The EOS and the D2x are both very excellent cameras. Some things I find better with the D2x:
Image quality.
First off, as far as I know prints from Canon's best and Nikon's best are similarly excellent. In spite of the EOS's ~50% higher cost and additional pixels it does not provide significantly better prints. Nikon worked some pretty good engineering to achieve that.
Price.
Most photography involves price tradeoffs with faster/better lenses, etc. costing more. In the case of the D2x the arguably equal and in some ways better camera actually costs $thousands less.
Speed.
The D2x shoots RAW at 5 to 8 fps versus the EOS 4 fps. When you are trying to capture the "perfect" instant of a rapidly changing scene higher frame rates increase the likelihood of catching the perfect moment. Or if you are auto-bracketing, faster speed captures your bracketed images before the scene changes. The concept of shooting a burst of 5-20 frames just to catch the very best pic is new to most photogs, because with film it was impractical. With cameras like these DSLRs new photo workflows may evolve. [Edit: My workflow has evolved. I now shoot almost all dynamic shots and many group shots as a burst of 2-5 pix at 2-5 fps.]
8 fps Crop Mode.
The D2x will shoot 6 megapixel images taken from the center of the frame at 8 fps. So if one wants to shoot tele action shots like sports it is ideal.
Buffer capacity.
IMO a much bigger issue than fast frame rate is the buffer capacity at that fast frame rate. The D2x captures about twice as many pix (~22) as the EOS does before the buffer fills.
Card capacity.
Canon built a slower camera with 30% more pixels and that leads to less images per card, slower file transfers, etc.
LCD size.
The D2x LCD is more than 50% larger than the EOS. The larger LCD changes everything as far as the ergonomics of DSLR workflow are concerned. Just try a D2x side-by-side against the much smaller EOS LCD.
Exposure Compensation (used constantly in DSLR workflows).
+/- 5 EV for the Nikon versus +/- 3 EV for the Canon.
Weight.
Being a 200# male with large hands I don't worry about size and weight too much. The Canon does weigh almost a pound more. Dimensions are pretty similar, with the Nikon a few mm larger. If size/weight are issues the Nikon D70s and Canon 20D are much smaller but sacrifice pro features like good viewfinders.
Self-timer.
Nikon has choice of 2/5/10/20 seconds whereas Canon is only 2 or 20 seconds. I find 2 seconds is sometimes not enough to let the camera settle down on the tripod if it is extended, so typically I use 5 seconds. Using 20 seconds as a cable shutter release substitute would drive me crazy. Often this is moot because I almost always have a cable shutter release with me.
Framing.
Some folks prefer a DSLR to be the same lens factor as 35mm film. Other folks do not. Quality superwide lenses are achieved at a $500-$1500 cost while supertelephoto is a $5000-$15000 cost; personally I prefer the 1.5 factor since it extends the expensive telephoto range. However, 1:1 versus 1:1.5 is a matter of personal preference rather than one being "better" unless print quality were to suffer.
The high end EOS does beat the Nikon D2x hands down in lower noise at ISOs of 800 and above. I am not familar with the high ISO performance of the D2xs, however.
-Allen Wicks

Tethered Nikon Shooting with Aperture?

Is it possible to attach my Nikon D2x to my mac via firewire and then as I shoot, the images are transfered to Aperture? How do I do this?
Kevin Hawkins

Well, the D2x doesn't have Firewire (big Bronx cheer to Nikon), so you'll have to use USB 2.0. For cable lengths over 15', you need a "booster" cable that has a powered signal repeater on one end. The only brand I'm aware of is IOGear. You can get their 16' USB 2.0 Booster Cable from B&H for $25.
http://www.bhphotovideo.com/c/product/357445-REG/IogearGUE216_USB_2_0_BoosterExtension.html
You can daisy-chain up to four of these if 16' isn't long enough for you.
As for using Aperture, you'll need Nikon's Camera Control utility, which Nikon sells separately (another Bronx cheer) to control the camera from the computer and transfer the files to the hard drive. Note that when shooting tethered with the D2x or D200, the camera will not save the files to the CF card in the camera (third Bronx cheer), so a backup strategy on the computer is important. FYI, Canon gives the option to save to CF or not when tethered.
Now, you'll want to download two files from Apple. One is Aperture Hot Folder.
http://www.apple.com/downloads/macosx/automator/aperturehotfolder.html
This is basically a folder script that watches a folder and sends anything added to it to Aperture. When you launch this, it prompts you to select the destination folder you've designated in Camera Control and a project in Aperture. Then, it runs in the background.
Performance will be best if you turn off auto generation of previews in Aperture and tell Hot Folder to import the images as referenced rather than managed files. Even so, data transfer from the D2x to the hard drive is painfully slow, so you'll find the buffer filling and all shooting grinding to a halt after shooting a few dozen images in a minute or two. Ya just gotta wait for the buffer to clear. Another Bronx cheer for USB.
As for backup, there's an Automator action called Duplicate Files to Folder 1.0.
http://www.apple.com/downloads/macosx/automator/duplicatefilestofolder.html
This watches a selected folder and automatically copies any incoming files to another folder (preferably on another hard drive). I haven't actually tried this one yet.
I've used a tethered D2x with Aperture on portrait sessions, and it works smoothly as long as you shoot slowly. Start blasting away at 12MP, though, and you can expect the buffer to inspire curses you didn't even know you'd forgotten.

Copy and paste action sequence?

i have an action sequence set to play on application start, but i also want to set it up to play whenever a user navigates to that specific page

Hello.
You can't copy-and-paste action sequences yet.
But you can if you were to open it in Flash Builder, but this would require a lot of 'fiddling about' with.

Problem trying to run photoshop roundtrip with aperture/automator

i have been trying to install photoshop round-trip to use with aperture but it is not working.
first, i created a folder called automator in the main library and drag the "start photoshop roundtrip.action" file.
second, i copied the photoshop action pack to my photoshop cs2, inside my application folder
third, i restarted the computer (aperture loves quit and restart).
now, i am trying to run photoshop round-trip from my aperture menu from automator, but i dont see the option for photoshop round-trip.
what i am doing wrong?
thanks for your help.
eric

Can you please provide the code for a sample procedure and the string you are passing it for me to try out?

Action sequence with Aperture 2?

Similar Messages

Maybe you are looking for