Aperture 3 Bulk process workflow

I'm having a work-flow issue in aperture 3 that I hope you can suggest a
way out of.
My typical workflow:
1)import
2)Stack similar images
3)Pick favorite from each stack
4)Process pick from each stack.
That all works great. But now I want to create alternate versions of
each of my processed picks. For instance, I want to offer my "client"
B&W versions of each, extra saturated versions of each, desaturated
versions of each, etc. On a one by one basis this is very easy. But
I'm looking for a to do it in bulk. I'm not looking to put a lot of
energy into these extra versions, since they are sort of bonus
versions anyway.
Some approaches that haven't worked...
1) Create another album, (say called B&W) and drag all my picks into
that. Apply adjustments to all. Problem: modifies the same versions
that appear in the original project too
2) Export picks. Apply B&W to all. Export B&W picks. Undo apply of B&W
to all. Repeat for each kind of modification I want (desaturated,
etc). Problem: Inelegant, don't get to keep the modified versions.
3)Select all the picks, duplicate version. Apply adjustments. Now I
have both the pick version and the B&W version, as I wanted. Problem:
Now the top of each stack is the alternate B&W version, not the
original pick.
What am I missing? I know lots of photographers offer clients a disk
with their pick images, plus folders of B&W, sepia, etc. How would one
do that in Aperture 3?
Thanks in advance for your help.

Similar Messages

Bulk process advice

Here my sample design of the bulk process with limit of row inserted
declare
n_rows_to_process NUMBER := 1000;
CURSOR my_cursor IS
select XXXXX
BEGIN
OPEN my_cursor;
loop
FETCH my_cursor BULK COLLECT INTO
XXXX
LIMIT n_rows_to_process
FORALL i IN 1 .. PUR_CCN_TAB.COUNT
insert XXXX
commit;
-- return;
exit when my_cursor%NOTFOUND;
END LOOP my_cursor_loop;
CLOSE my_cursor;
End;
This is only for 1 cursor select. It complete inserted the row into temp table.
So , when I put 2 cursor into this process. It wouldn't run the second cursor because the 1 cursor it already exit the process.
Here my sample design for 2 cursor
declare
n_rows_to_process NUMBER := 1000;
CURSOR my_cursor IS
select XXXXX
CURSOR my_cursor2 IS
select XXXXX
BEGIN
OPEN my_cursor;
loop
FETCH my_cursor BULK COLLECT INTO
XXXX
LIMIT n_rows_to_process
FORALL i IN 1 .. PUR_CCN_TAB.COUNT
insert XXXX
commit;
-- return;
exit when my_cursor%NOTFOUND;
END LOOP my_cursor_loop;
CLOSE my_cursor;
BEGIN
OPEN my_cursor2;
loop
FETCH my_cursor2 BULK COLLECT INTO
XXXX
LIMIT n_rows_to_process
FORALL i IN 1 .. PUR_CCN_TAB.COUNT
insert XXXX
commit;
-- return;
exit when my_cursor2%NOTFOUND;
END LOOP my_cursor2_loop;
CLOSE my_cursor2;
End;
Is there any SQL command that can used like complete the 1 loop and continue the 2nd loop?
Can we join the 2 cursor in bulk process?

You are mixing up cursor and fetch with bulk collect, forall within a loop and an out-of-scope exit.
Forget the cursor, open, loop, fetch and exit.
just do: select bulk collect and the forall.
Your second round of select should then be just fine ;)

Resolve Process Workflows

Hi All,
I've just implemented an activeSync resolve process that notifies helpdesk staff that there has been an identity collision, and includes some information about the incoming data and the clashing identities. For the time being this is adequate.
Still, Identity Manager has a tonne of power and I know that I'm not using it. What are the things that you all would normally implement to handle identity clashes during activeSync processing? Is there any sample code out there that I can look at for ideas?

Hi.
Well, in fact, the new client is a copy of another and the background data for the workflow process is already copied. I just need to re-start the workflows but I was wondering if I can do anything easier than do it manually and one by one. Maybe a migration tool to copy "in process" workflows.
Another option is to redefine sub-WF and try to put every WF in his former situation, but the logic of the original WF is very complex so this is not an option.
I know that is very difficult to do that but...who knows!
Thanks for your interest.
Ismael

Document level scripting from process workflow

Hi all,
is there some way to add a "document level" script from process workflow in Livecycle Workbench?
That is, I have a script i want to add to a pdf in my process workflow. How can I do that? Is there some service/function/script I can use to do that?
I'd really appreciate any help.
Thanks
Alessio

Not that I am aware of, could be wrong though

Migrating in-process workflows

Hi all,
New to BPM. May be using 10g or 11g (possibly depending on the answer to this question). If I'm migrating workflows from another system, and a document is currently halfway through the workflow, how easy is it to take across that document and put it in a BPM workflow at the equivalent point in the process? Is it even possible?
Thanks in advance for any ideas/suggestions!

Hi.
Well, in fact, the new client is a copy of another and the background data for the workflow process is already copied. I just need to re-start the workflows but I was wondering if I can do anything easier than do it manually and one by one. Maybe a migration tool to copy "in process" workflows.
Another option is to redefine sub-WF and try to put every WF in his former situation, but the logic of the original WF is very complex so this is not an option.
I know that is very difficult to do that but...who knows!
Thanks for your interest.
Ismael

In Process Workflow Issue after Client Copy

Hi
We have made a client copy on our training system and wish to process workflow that were created on the original client. Currently, of course, all the workflow instances have the original client. Is there a way we can change this to the new client?
Regards
Ian

Looks like there is something the basis boys ran to update these instances (and any other non workflow related thinks). It is all part of the client copy process apparently.
Cheers
Ian

TimeSheet Approval Process workflow

Hi All,
Please let me know how time sheet standard behavior of approval workflow.
I ran the timesheet approval process, I found in the event trace, the following business objects are showing for the process.
When employee requests for a timesheet approval, there is no workflow triggered ( no receiver in the SWEL), it is showing BO IDOCPACKET and event MASSINPUTFINISHED and when approval approves the request it is triggered the workflow (receiver is WORKITEM) single step type.
Please clarify me on
1. Why IDOCPACKET is triggered?
2. Why ATTENDENCE is triggered?
3. whenever a time sheet request is created by user, approver will get notifications, where these configurations have been maintained?
4. When approver approves/rejects the request, initiator will get the notifications, where these configurations have been maintained?
Thank You in advance.
Regards,
Pavan.

1 and 2) Are you sure that IDOCPACKET and ATTENDENCE have anything to do with CATS? I don't believe so. The time stamps of these events most probably don't event match with your CATS release and/or approval.
If you need to set up some kind of approval process workflow, if I remember correctly it is configured here: SPRO > Cross Application Components > Time Sheet > Specific setting for CATS Regular > CATS Regular > Set up data entry profile.
Regards,
Karri

HT3946 How do I ask Apple to update Aperture to process Olympus EM-5 Raw Files

sdff
How do I ask Apple to update Aperture to process Olympus EM-5 Raw Files

Use this link:
http://www.apple.com/feedback/aperture.html

Moving "in process" workflows to another client

Hi all.
I have a custom workflow that asks a few people for some confirmations, it has an "spaghetti" logic. My problem is that I need to move it to a new client, so the new workflows are not a problem but the instances of the workflow with "in process" status (currently running on the system and waiting for some events or confirmations for example)can not be moved as they are.
Have I to re-launch these work items in the new client? is there any other easier solution? There are a lot of these workflows (at least 4000) and launching and processing them manually, to leave them on the same situation that they were on the other client is a tedious work.
How can I do that easily?
Thanks

Hi.
Well, in fact, the new client is a copy of another and the background data for the workflow process is already copied. I just need to re-start the workflows but I was wondering if I can do anything easier than do it manually and one by one. Maybe a migration tool to copy "in process" workflows.
Another option is to redefine sub-WF and try to put every WF in his former situation, but the logic of the original WF is very complex so this is not an option.
I know that is very difficult to do that but...who knows!
Thanks for your interest.
Ismael

Finding a place for Aperture in our workflow

Hi All.
I've used it since Sunday. I've attended the demo in San Francisco and I've had discussions with other photographers who would like nothing better than to incorporate Aperture into their lives. I share that desire. This is where I am personally in my relationship with the application:
There are two distinct targets for which my images may be purposed, depending upon the kind of project and the stage of that project. Those processes are of course Proofing and Publication.
For Proofing, wether for a commercial client, corporate PR or a wedding, Apertures RAW engine is perfectly adequate. It's editing tools are brilliant. It's correction tools are crude, but convenient, and again, for the purpose of presenting proofs for selection (but not final publication) adequate.
But in terms of preparing images for publication Apertures RAW engine is not as refined as ACR's and it's color and tonality correction tools are crude by comparison with Adobe Camera RAW.
So the work flows might look like this:
Product Photography:
-Shoot.
-Review in Bridge as versions are created
-Process with color correction in ACR
-Refine for publication in Photoshop
-Deliver
In my opinion, putting these images through Aperture is bad policy because:
1) The RAW engine is going to create artifacts, sharpening, color and contrast problems resulting in an inferior file.
2) Color/tonality, noise reduction, sharpening tools available in Aperture are too crude for reproduction-quality images. Those available in ACR by comparison are more precise, consistent and trustworthy.
3) Layered files are treated and flattened on the fly in a cavalier fashion within Aperture.
4) File management in Aperture is confusing when trying to deal with a number of versions of the same image. I can't tell at a glance which version is which, either by name or other obvious tag.
Event, Wedding, Portrait, Editorial, Journalism:
-Shoot
-Review entire take in Aperture
-Edit and make preliminary selections in Aperture
-Make proof-quality color and tonality corrections in Aperture
-Process out to proofs for print, disk or web delivery to client
-Client makes selections
-Export uncorrected masters of selections to hard drive
APERTURE ENDS
Remainder of processing takes place in Bridge/ACR/Photoshop for preparation and delivery of final images.
Because Aperture should not, in my opinion, be used to produce Reproduction-Quality RAW conversions and because it is confusing, inconvenient and dangerous to use to manage layered PSD versions of files, it is currently not suitable as a one-stop Digital Asset Management application for all of my images.
I Soooo don't want to sound like I'm knocking Apple here. This is an application with amazing potential and when it's risen to the needs, standards and expectations of the professional community it may become indispensable.
Regards,
Frank
G5 2.3 Mac OS X (10.4.3)

In either process, you could do the sorting and
picking in aperture. You could possible produce web
or paper contact sheets for clients. Export the
master files (these are the original RAWS) to
Photoshop and deliver. You can always reimport the
finished files to Aperture in the same project, where
they would remain as Masters, and therefore unedited.
Richard,
I could use Aperture to sort product work, but there is no reason to.
My clients don't want proofs of product shots. I sort between only a handful of brackets to choose the frames I'm going to work on for each image at each stage. Bridge is more than adequate for this task, ports right to the superior RAW converter of ACR, maintains the file names I choose when I save versions of the file back to the working folder, behaves predictably, allows me to view multiple windows and their previews easily and (are you listening Apple?) respects the way I work.
At this point Aperture is only useful for editing and sorting large projects and creating proof-quality output. At this it is brilliant. BUT It's organizational fascism, inferior output, marginal control and capricious behavior with layered files makes it far, far more trouble than it is worth to incorporate into any part of a product photography workflow at present.
And in any case I would not want to keep finished files in Aperture anyway. If I need recourse to a file it is usually to a Layered version of that file because my client has asked me to make some change to it. If I import a layered PSD into Aperture I have to export it back out of Aperture before I can open it up again in Photoshop. Aperture will only send a flattened version of a file to Photoshop if that file was not originally saved in Aperture in the first place. Aperture only allows me access to layered files that have been savedinto Aperture, not files that were imported into Aperture.
-Import RAW into Aperture
-From Aperture, open that RAW into Photoshop, create layers and do a straight save, NOT a save as,
-Under these circumstances Aperture will allow you to then open that file into Photoshop again with it's layers.
(NOTE that it must be a straight Save. Save As will not let you save into the Aperture Library. You cannot create distinct and useful version names as you save the file.)
But if you
-Import a Layered PSD into Aperture, Aperture will ONLY send a flattened version of that file back out to Photoshop.
So I can see no advantage and very many pitfalls in allowing Aperture to touch any of my product photography at any stage. Its severe limitations mean that it can function only as a sorting table for my event, editorial and portrait work. Import Project, sort, export selects, proof, delete Project.
Like you, I desperately hope that Apple will take these concerns seriously.
Cheers,
Frank

Aperture stuck processing. Again and again.

No program like Aperture has managed to crash to the ground my faith in Apple. I was a very happy Macbook user before I trusted my pictures into aperture.
Every once in a while the program hangs with "processing ..." as a message and cannot be recovered in any way.
Last time I did some serious magic, entering the library with a command line and trying to find offensive files. That's because I had a process hogging the CPU that is related to QuickTime, used as a subprocess to visualize files not handled by Aperture itself (at least this is what I gathered with heavy googling).
Today the program crashed while I was importing pictures from my Pentax K-r. I moved around the library while waiting and stopped on a movie.
Hours later, this is what I have in my top. See a com.apple.qt scoring 133.5 percent of CPU (how can that be?)
PID   COMMAND      %CPU TIME     #TH #WQ #POR #MREG RPRVT RSHRD RSIZE VPRVT VSIZE PGRP PPID STATE    UID FAULTS
1277- com.apple.qt 133.5 06:48:26 9/2 3    259 296   1124K 31M    4276K 27M    942M   1277 1    running 502 8202
1680 top          11.8 00:06.97 1/1 0    28   29    1412K 216K   2116K 17M    2378M 1680 1667 running 0    35309+
1266 Aperture     0.8   04:48.78 49   3    463 1803 518M+ 53M    521M+ 949M   4526M 1266 250 sleeping 502 1394685+
923   WebProcess   0.8   17:40.75 12   3    290 4271+ 249M+ 66M    365M+ 588M+ 3950M+ 283 283 sleeping 502 35813170+
192   WindowServer 0.8   12:36.42 5    1    521 1296+ 11M+   54M    71M+   32M+   2879M+ 192 1    sleeping 88   2867524+
0-    kernel_task 0.7   09:50.49 67/2 0    2    1186 49M    0B     217M   50M    1479M 0    0    running 0    43842
282   Terminal     0.7   00:11.94 6    2    126 194- 9188K- 40M    24M-   32M-   2476M- 282 250 sleeping 502 3264
Kiling 1277 is no cure. I am afraid that uninstalling Aperture might be the cure. Next question is How do I get back my pictures in iPhoto, so that I can have fun trying to reorganize 10 thousand pictures in meaningful groups?
Hardware: white Macbook with Core 2 Due, software
Macintosh:Application Support mico$ uname -a
Darwin Macintosh.local 11.2.0 Darwin Kernel Version 11.2.0: Tue Aug 9 20:56:15 PDT 2011; root:xnu-1699.24.8~1/RELEASE_I386 i386

cosmic53 wrote:
Well, solved the problem the hard Unix way once again.
I suggest that your problem may not really be solved, because most of your issues probably stem from trying to use a ~2006 MB with limiting RAM, GPU and CPU. It is possible to use such a weak box (I did for years), but only with total care in optimizing workflow.
Other question: should I break my library as soon as possibile into smaller libraries? I have 10142 pictures.
No. Multiple Libraries defeat the whole purpose of having an images database. Anyway 10k pix is actually very few for a pro images database, and Aperture is not so much slowed by larger library size as it is by drives management and by workflow.
Drives slow as they fill so as a guideline keep all drives less than ~70% full and keep the Aperture Library on the internal drive. If the internal drive gets too full switch to a referenced-masters workflow with Masters on external drives.
Your Macbook's CPU and especially the relatively weak graphics will be limiting to Aperture. I do not think it will ever run particularly well. It may or may not run "well enough" for your specific workflow.
I ran (in fact still sometimes run) Aperture on a 2006 2.33 GHz C2D MBP with a max of 3 GB RAM, and it does work but it does not rock. Try doing a restart before each Aperture session and keep other applications (especially browsers and Adobe apps) closed when doing Aperture editing.
Since you are having issues I suggest before doing anything else that you make sure that good backups (as opposed to corrupted backups, which are all too common) exist on drives not connected to your setup. Also note that original image files should be independently backed up before import into Aperture.
Good luck!
-Allen

OWB Process/Workflow in third party Workflow engines

Have any of you had experience using the XPDL file generated by the Process flow component of OWB to execute the Workflow in non-oracle Commercial and/or Open source Workflow engines?
If so I'd like to hear about it. I'm attempting to do the same and think that the Oracle Workflow component is too much work.
I appreciate your responses.

Hi,
Any update on it.
Regard
Nidhideep

How to pass BindVariables to External Process (Workflow)

I build a shell script (unix) which accepts a command line parameter .... a "filename"
The "filename" is a dynamic name!
The workflow is build with a custom input parameter "filename" ... which I want to pass to an external process, which calls this shell script:
How can I do that ?
ExtProcess:
Command : Val=/bin/ksh
Parameter_List : Val=":/home/bin/myscript.sh:${Task.Input}:"
(Binding ":Filename" replaces the whole value, sorry)
Succes_Threshold: Val=0
Script : Val="" , Binding=":Filename"
... does not pass the value of ":Filename"
Script : Val="/tmp/fixed.name"
... works only with fixed names
what I really need is something simple like:
Parameter_list : Val=":/home/bin/myscript.sh:${Parameter.Filename}:FIXPARAM:"
or Script : Val=":${Parameter.Filename}:${Parameter.Param2}:${Parameter.Pram3}"
... similar problem I had with FTP, I found no way to pass dynamic filenames or other parameters (except LOCATION Parameters)
... similar problem I had with EMAIL I found no way to include PARAMETERS to the mail body (except to replace the whole body by 1 parameter)
Is there a solution or is in current version OWB 9.2 only "static" parameters supported.
I also was missing to pass OUTPUT-parameters for example of a TRANSFORMation,
I also was missing some urgent SYSTEM-parameters for self identification of the process(like "SYSTEM.TASK_NAME" "SYSTEM.EXECUTION_AUDIT_ID" "SYSTEM.ITEM_KEY" )
Thanks for all hints and best regards
Martin

Actually... After further investigation this may not be needed. I'd be interested in the answer, to understand what is possible.
The concept of passing parameters in the OWB workflow designer is rather limited, in my humble opinion. Sure, you can designate a "start" sequence that takes a parameter and you can pass that to mappings/transformations but there is no chance for feedback. Ie, if I manually (or through some rigged script) execute the flow with the "PARAMETER" then it will be able to bind. What about mid-flow. IE, select the record to be "processed", then call a "flow" with that as a parameter.
Am I mistaken? Is there a way to expose the "out" parameters of a mapping, or the return of a "transformation function" as "OUTS" in the process flow.
Of course, in a world where everything is OWB and in the DB one can leave data in tables, and pick it up on the other mappings. HOWEVER, most BI systems involve external retrievals, etc. that need a bit more "intelligence" then "run and return 1,2,3" . :)
Hope this is helpful for product feedback. If I'm mistaken on the WF capabilities please clue me in. :)
btw, I'm an OWB fan, certainly. The progress over the past two years has been excellent.

APERTURE PHOTO BOOK WORKFLOW

I'm new to Aperture (1.1) and am looking for advice on the best workflow to create Apple Photo Books. Issues include:
1. Getting the correct version of the photo into the book
2. Copying the photos in correct order with a single copy/drag command
3. Ensuring there are no duplicates
4. Not having the photo name in the Book
I had created an Aperture Album for the Photo Book. Took care to drag the best version (which is the last version) of the photo into the album (with an error here). After numerous attempts, I gave up on trying to get the correct, better version of the photo into the Book (just re-edited the version I had). Tried to manually arrange the photos within the Album in the order I wanted to have them in the Book (they are ordered by date) but was unsuccessful in re-ordering. In creating the Book I had to individually drag each photo to it's page and had to manually keep track of which ones I was using (resulting in one duplication). As I was fine tuning the Book and rearranging the photos, there wasn't a place to temporarily store the photos (this is how I inadvertently got a duplicate). Also, I had to manually remove each photo name that was attached to each photo in the Book(perhaps there is an easy option here I don't know about yet?).
Interested in any pointers to expedite creating these Photo Books. Missing some of the iPhoto Book creation tools!
PowerMac G5 Dual 2.0 GHz Mac OS X (10.4.6)

i am no expert on books, but in the one i am working on, i set the image i wanted to use as the stack pick before i made my book selections. i always manually load pages, so i can't help you there. in the browser of my book, the thumbnails of images used in the book have a red badge in the upper right corner showing how many times they have been used in the book. that should help you with duplicates.

Error in sqlplus_exec_template for executing a process workflow

Hi,
en_dev_rep_owner = owb reposittory owner owb10g2
LC_OWF = owf location
PROCESSFLOW = tasktype
WF_DIMS = Process flow (not the process package)
This is returning the following error :
SQL> connect en_dev_rep_owner/en_dev_rep_owner@en_dm_dev_test
Connected.
SQL> start D:\oracle\owb10g2\owb\rtp\sql\sqlplus_exec_template.sql en_dev_rep_ow
ner LC_OWF PROCESSFLOW WF_DIMS
Enter value for 5:
Enter value for 6:
Session altered.
Role set.
Stage 1: Decoding Parameters
| location_name=LC_OWF
| task_type=PROCESSFLOW
| task_name=WF_DIMS
Stage 2: Opening Task
begin
ERROR at line 1:
ORA-20001: Task not found - Please check the Task Type, Name and Location are
correct.
ORA-06512: at "EN_DEV_REP_OWNER.WB_RT_API_EXEC", line 704
ORA-06512: at line 12
Thanks in advance

define OEM_FRIENDLY=0
define OWB_BACKGROUND=0
l_custom_params := '&CUSTOM_PARAMS.';
l_task_type := 'PROCESSFLOW';
l_location_name := '&LOCATION_NAME.';
l_task_name := '&TASK_NAME.'; - workflow name
dbms_output.put_line('Stage 1: Source files will be loaded into Staging '||l_task_name);
:exec_return_code := wb_rt_api_exec.run_task(l_location_name
,'&TASK_TYPE.'
,l_task_name
,l_custom_params
,'&SYSTEM_PARAMS.'
, &OEM_FRIENDLY.
, &OWB_BACKGROUND.);
dbms_output.put_line('Stage 2: Task Finished');
I hope that the cut and paste didn't mess up the format

Aperture 3 Bulk process workflow

Similar Messages

Maybe you are looking for