How would you edit for story telling? (persistently)
I primarily shoot and edit lifestyle in the form of documentary. As an output, several sequences of pictures are published in very specific orders, to tell narratives.
I'm looking for a workflow to maintain different narrative sequences based off of the same variants.
Let's say right out of camera, 200 pictures A > B > C > D > E > F > G > .... are imported to C1 in that order.
1) Creative decisions lead to a manual ordering of 50 variants : C > D > A > ... > E > F > G > B (full story.)
2) Shorter excerpts are required by clients depending on target publications : C > A > E > G > B (medium story)
3) and A > F > B (small story)
How would you recommend to maintain sequences 1) 2) 3) in Capture One simultaneously and persistently ?
Current limitations that I face:
- manual sorting is not persistent
- no functionality to duplicate an existing album
- renaming files will work only for 1 story at a time.
Thanks, CHRIS
-
Chris,
I think the best option would be to create output files in the required format and load them into some software dedicated to the task or tasks you want to undertake.
Grant
0 -
Grant,
Thanks for the feedback.
In my mind this would mean to maintain several sidecar JPEGs and TIFFs attached to a each single RAW files. Is there a piece of software out there to do this with a tight integration to Capture One ?
Regards, CHRIS
0 -
Hi Chris,
My initial thinking would suggest output of completed images and then work with those to save the complexity of always going back to the original RAWs.
Is a one size (dimensions) output OK or are multiple sizes required?
Assuming it helps use something additional to file name numbering inconventions to obtain a sort order and assuming there is a logical "A" to "ZZ" (or equivalent) order that can be defined AND used for selection as well as order for each one of the Story sets, then manually sort them and apply the requered "Selection Identifier" to an otherwise unused IPTC Metadata field. That can be become your selection field and included in the Output process to populate the metadata for other selection programs to read. If you can use numbers they can be added allocated and automatically to output file naming but a metadata field may prove more useful.
Reordering the selection by story line is a different sort of need. That is where I think I would look to an external organiser application to group and sort the output images without bothering C1. (If at all possible).
One could extended the Metadata usage concept but It may be easier and more effective to do something else.
IMO.
Grant
0 -
Hi Grant,
" Is a one size (dimensions) output OK or are multiple sizes required? "
> two sizes for each storyline.
Thank you for the second take on this problem. I've investigated this closely in past days. Do I understand well from your suggestion that the "selection id" would have to be inserted manually in an IPTC field for each single variant ? If yes, from my perspective that is an acceptable workaround for a one time job.
For a repeat workflow like mine (once/twice per week) there's a need for a flexible and error-free solution. As a result I've decided (reluctantly I must say) to fork my workflow out of COP and give these downstream tasks to an external cataloging system:
- create and update multiple story lines from a single set of TIFF files
- become the launch pad for optional edits in Luminar
- create JPEG outputs with or without watermarks, and in multiple sizes
- track project progress (apply color flags as indications of project steps/completion)
Looks like someone is off to write an enhancement request to C1 support team soon... :)
Have a good day,
CHRIS
0 -
Hi Chris,
"Do I understand well from your suggestion that the "selection id" would have to be inserted manually in an IPTC field for each single variant ? If yes, from my perspective that is an acceptable workaround for a one time job."
Based in the way I am envisioning your requirement at the moment and assuming I have thought of all of the key needs, the answer is yes for every variant that you need to use i the output. However once you have identified the group of variants required for an particular narrative you can simply update one of the variants with the identifier in the preferred IPTC field and then copy that entry to the others. There are a couple of methods for copy - one being copy of course but also if you have the chosen field displayed in a filter (Filter tool) you can simply drag the file or selection of files to the required entry and "copy" in that way.
Once you have the chosen field populated you can use smart albums to select the variants required.
For an image that appears in multiple narratives a single field could be used to contain multiple selection identifiers BUT that might need more interaction when adding the identifiers since copy the contents of a field would be inappropriate in that situation. Keywords, however, would work well.
I think all 4 of the items on your list could be achieved in C1 but whether in a way you would be comfortable with I can;t be sure.
The multiple story lines requires some identifiers - primarily which sotry line and the position of the image in the story as a minimum.
C1 supports the use of external editors.
Creation of jpgs (or indeed TIFFS, etc.) via the Output Recipes option with appropriately created presets to select from should deal with point 3
Applying colour flags is certainly possible in bulk to a selection of variants but if you are thinking of something that should happen automatically as the result of a successful process step then the nearest one can get (that I can think of) is a "Processed" identifier on processed variants. Non-automated options are plentiful However having some sort of publisher package that can take the files and manage the specific final publishing steps sounds like it could be beneficial for your purposes.
HTH.
Grant
0
Post is closed for comments.
Comments
5 comments