View allAll Photos Tagged Workflow
We kept the primary workflow extremly simple.
Verify is the fastest way to collect and analyze user feedback on screens or mockups. We talk more about Verify and our other products on the ZURBapps blog.
ZURB is a close-knit team of interaction designers and strategists that help companies design better (www.zurb.com).
Just experimenting with a some little video clips that show a before and after and how my workflow gets me where I want to go...
Single in September 2017
Pentax M50/1.4
Day 7
The dust mask, especially the N95 version, an essential piece of PPE when dealing with cargoes such as grain and iron ore.
I thought I'd present this as an example of a workflow. It's not necessarily the best for this photo, or any photo, but it gives a representation of steps of getting from one place to another. I did it for The Photoshop Support ground here on flickr.
REALLY LARGE If this is small on your browser drag it to your desktop and you should be able to zoom in.
Cannes is a city located on the French Riviera. It is a commune located in the Alpes-Maritimes department, and host city of the annual Cannes Film Festival, Midem, and Cannes Lions International Festival of Creativity. The city is known for its association with the rich and famous, its luxury hotels and restaurants, and for several conferences. On 3 November 2011 it hosted the 2011 G20 summit [Wikipedia.org]
It all starts with contributes uploading or creating a new document for collaboration. A collaborator is a group or people responsible for selecting the appropriate document from “uploads” folder, store them in them in “working-document” folder and work on them. Once the document is ready to be published document is sent to the “request for approval” folder where an approving authority is notified.
Approving authority can approve or disapprove the document. It may go back to the “working document” if disapproved with a notification to the collaborator(s). If approved the document moves to the “Approved version” folder and can be published in a desired format (pdf/doc/html) and location (published folder/intranet site/social networking site) as per the predefined rule set.
All these roles and workflow can be re-fined and redefined based on the business process. This is an example workflow and was created for basic understanding of a document workflow.
Find the full blog at
I am a huge fan of Adobe Lightroom - Other than its excellent workflow solutions it is, for me, a sketchpad for creative processing ideas. Which I enjoy as much as making/capturing the initial image. This image was processed in just a few minutes and while I could go back and re-edit it in photoshop with a little more finesse - I'm quite happy with it as it is. And in a time when I find myself questioning what other people think about my work I have to keep reminding myself to focus on me and what I enjoy. Because within that is the fuel that should be driving my photography not the other way around. Wow - got a bit serious there.
THE SHOT - best clicked to view full size on black.
I like getting to know the people I photograph, it's not always necessary but more often than not it can help when trying to capture something that conveys some emotion and character. I dislike asking people to look and smile at the camera etc. and instead try to elicit different looks from our interaction. And while this shot is a bit of a cliched pose, I captured this frame in-between our conversation on the joyous news of conception after many years of what can only be described as 'challenges'. It's natural and though i would have liked to slow the shutter down to capture her rubbing the tummy/baby, it works for me.
I wish the couple (2+1) all the very best of luck and a continued happiness. As always, it's an honour to be asked to photograph a person and to capture a part of their story.
Thanks for looking - and reading if you got this far.
Part 1 of 3
This presentation briefly goes through the steps of how I processed a high dynamic range image of a cloudscape during stormy season in Hong Kong.
High dynamic range images or HDR, is the process of combining multiple low dynamic range captures into a single image, when a single capture does not afford the necessary range for what is intended.
Three captures were made for the making of the final image. All three images share the same ISO, the same aperture value, and the same focal length. They differ in shutter speed, and the result is shown here, with one normal exposure (0EV), one 3 stops down (-3EV) and one 3 stops up (+3EV).
The image on the left was exposed for the overall intent: the clouds and the reflection on the sea. The image in center was exposed for the highlights, which provides some tonal details in the sunlight in this case. And the image on the right is exposed for the shadow areas, where the buildings on the horizon are now correctly exposed, and you can see the patterns on the water surface.
After importing my RAW captures into Lightroom, I have exported them to merge to HDR via Photoshop. I used to use Photomatix for this but lately I have been using Photoshop because it was easier for my workflow.
The important bits to note here is that you should be focusing on extracting details from the captures, and not trying to create the final image.
# Full video
+ youtube.com/watch?v=0N9RWxVO5gw
# Presentation PDF
+ www.slideshare.net/seeminglee/hdr-process002
# Final photo
www.flickr.com/photos/seeminglee/9370400032/
# Notes
Hope this is useful for some…
# Media Licensing
Creative Commons (CCBY) See-ming Lee 李思明 / SML Photography / SML Universe Limited
HDR Photography Workflow: Part 1 of 3 / SML Tutorials
/ #SMLPhotography #SMLTutorials #SMLEDU #SMLUniverse
/ #HDR #photography #workflow #tutorials #video #edu
I'm back from my wilderness excursion. This is the first of many rolls of film to come...pretty heavy workflow in my bathroom right now. I only have so many shower curtain rings to dangle film from...
Quite unfortunate that light leaked. The pinhole camera is usually pretty good about not doing this, but I find that if I walk around a bunch or jump around when there's film in it, it'll come unspooled a bit. So when I pull the top off to get the finished roll of film out (and I'm NOT in safe light), sometimes I exclaim "SUMMBITCH!!!!" and shut it real quick....damn loose spools.
This was taken on the second portage of our trip. 140 rods (that's 2240 feet) off of Crab Lake. Probably the coolest portage of the trip, the wind was shaking the pines that were all around. No post processing has been done to the bottom picture, that's just the movement of the trees during the 12 second exposure.
AI artwork generated with Stable Diffusion AI v1.4
Prompt: "abstract art of a black hole, solid shapes, neotokyo colors, muted colors, geometric, depth of field, tilt shift, film grain, noise, detailed textures "
Seed: 5345452
CFG usually either 7, or 14
Upscaled with Topaz Gigapixel AI:
- Upscale: 2x
- Mode: Standard
- De-noising: 0
- Blur Reduction: 20
- Face recovery: 10
My Workflow:
- Generate hundreds of 10-20 step "rough draft" images in Google Colab
- Grab the seeds of the good-ish ones
- Rerun in Google Colab with 50-100 steps using the seeds
- Send the good images to Gigapixel AI, export with Standard Mode settings
- Finally, send them through Sharpen AI, often with "Too soft - Normal" and 30-70 added grain. This step isn't that crucial, but it does help a tiny bit.
- Post to flikr with JS scripts to automate this description :)
- Probably about 1%-5% of AI generations get posted to Flickr. It depends a lot on the prompt, different prompts run into different issues. Bust portraits tend to be more successful since hands, arms, and legs almost always come out wrong.
Start creating right away with the official Stable Diffusion web UI: beta.dreamstudio.ai/
You get 200 free credits. Alternatively, find a Google Colab to make images at a cheaper rate. My personal one is too personalized to publicly share.
Join the Stable Diffusion community on Discord: discord.gg/stablediffusion
Almost all generations use v1.4 Stable Diffusion. However, a couple anime-related images may instead use the anime-trained Stable Diffusion model, "Waifu Diffusion".
This is an image I processed using original narrowband data from Telescope Live. In my processing workflow, I used the Hubble Palette for the narrowband color mapping.
There are two open clusters and associated emission nebulae shown in this image - IC 2944 (the Running Chicken) and IC 2948. They are found in the southern constellation Centaurus.
In the image above, IC 2944 is centered on lamda Centauri, the 11th brightest star in the constellation. This is the bright star towards the lower right. IC 2944 and IC 2948 overlap. IC 2948 is positioned in the upper left and IC 2944 is at the lower right of the image.
Lambda Centauri is about 400 light years from Earth. IC 2944 is estimated to be 6,500 light years away.
IC 2948 includes small dark nebula known as Bok globules. These small nebulae contain dense cosmic dust and gas and may be where star formation takes place.
Telescope Live Information:
Observatory name: El Sauce Observatory
Location: Río Hurtado, Coquimbo Region, Chile
Coordinates: 30.472529° S, 70.762999° W (Google maps)
Elevation: 1525 m
Average seeing: 1.3'' - 1.8''
Date of capture: April 13, 2021
5 exposures per filter (Astrodon Sii, Ha and Oiii)
Total exposure time: 2.5 hrs
Telescope:
Officina Stellare RH200, a 20-cm F3 reflector
Aperture: 200 mm (8 inches)
Focal Length: 600 mm
F-ratio: 3.0
Mount:
Astro-Physics 1200GTO Equatorial Head Specifications
Minimum elevation: 32 degrees
Camera and Filters:
Camera Model: FLI ML 16200
Pixel Size: 6 μm
Pixel Array: 4500 x 3600
Pixel Resolution: 2.06 arcsec/pixel
Cooling: -20 degrees
Field of View: 2.58 x 2.06 degrees (155 x 124 arcmin)
Filters (50mm square): Astrodon LRGB 2GEN, Ha (3nm), SII (3nm), OIII (3nm)
Workflow: I created the larger object in the background with Blender. I wanted to use Mudbox to retopologize and since MB requires a "clean" mesh, I exported the object into Maya. Performed "cleanup" and smoothing in Maya, then to Mudbox for re-topology. Finally imported back into Blender and rendered the scene using Luxrender.
This may initially look complicated but this is the photography workflow that I currently use including the route from initial captured image, through ingestion and processing, distribution and eventually to archiving.
INGESTION: Through Adobe Photoshop Lightroom, images are copied to a working internal hard drive on my PC. During this "ingesting" stage, I set keywords, add copyright, apply any preset editing and add these images to a subfolder named, "originals". I also automatically copy the images to an external drive purely as a backup. I call this drive the redundant drive.
SORTING: Next I quickly go through and determine which images are rejects and I mark them for deletion. I don't delete them yet because I might always change my mind later after I see what can be done with the editing.
NON-DESTRUCTIVE EDITING: I adjust the camera calibration. This is a very quick and flexible way to change the major balance of the photo and effect all of the colors at once. I do additional white balance tweaking, black clipping, whatever is needed. If specific changes to the content of the photos are needed such as removing an exit sign or cloning over a name tag, I export to Photoshop from Lightroom and make those changes on a copied layer. Then I save a PSD, go back to Lightroom and make any final changes there. Finally, I add individualized keywords (people in the photos, specific details about the photos).
RENAMING: The first step before exporting is to look at the files marked for deletion. If they really are no good, I delete them. Next, I rename all of the files so that they are easier for people to read. Usually I follow the pattern of "name of event - 001.extension". Some photographers and editors don't do this step preferring instead to use whatever file name is generated by the camera. But to me, with the power of modern search engines in Lightroom and Portfolio, I think it's best to rename the files so non-technical people aren't intimidated by all of the numbers and strange letters.
EXPORTING: Next I export for print and web size, each to a separate subfolder. For print, it's a full resolution jpg export at 300 ppi with the same name as the original filename. I also retain the Adobe RGB color space that I shoot in as it's best for printing (though I personally prefer the look of ProPhoto color space). For web, 72ppi jpg, sRGB color space (for browser compatibility) and 1024 x 768. Other photographers prefer TIFF but I think a full resolution jpg looks just as good as a full resolution uncompressed TIFF. Maybe I'm wrong, but my photos have been printed rather large on two page spreads and they look good to me. Plus, an uncompressed TIFF is rather huge in terms of file size. And when sending dozens of files for a magazine, JPGs are much easier for people to handle and transfer.
I also have export presets for facebook, LinkedIn and any other social media sites I distribute to. However, for Flickr, I just publish straight to the site from within Lightroom. No need to export anything separately.
DISTRIBUTION: Depending on the needs and capabilities of the client, I'll use our or their FTP sites to distribute print or web size jpgs. If they don't have FTP capabilities, I'll send photos via YouSendIt.com. If that isn't a possibility (if I am sending huge amounts of data for event photography for example), I'll burn a DVD and mail it to them. For internal distribution within the company, I'll place the print and web files onto the shared drive along with a PDF preview I make in Bridge (step not pictured). Some people have had the picture preview function removed from their computers by the IT department, so the PDF preview is unfortunately a necessary step.
ARCHIVING: The first step before archiving is to convert all of the raw files to DNG. This reduces the file size by about 20-40% and is a lossless compression. It also combines the raw file and associated sidecar file into one file which makes the folders cleaner. Over the course of many thousands of images, this makes a huge difference and makes the IT department slightly happier about storing ten versions of a headshot when to them they all look the same.
Next step is to transfer the whole working folder which contains the originals, print files, web files, PDF preview and PDF scanned copies of consent forms to the shared drive. This network drive is on a standalone server and is backed up every night to tape which is stored at a separate location. The shared drive is also in a separate building, so if my building ever had a disaster and was destroyed, the photos would be backed up in two separate buildings.
DATABASE MANAGEMENT: I currently am using Extensis Portfolio to look at the photos stored on the shared drive. When Portfolio runs, it searches for new photos, changed photos, removed photos, etc. and while it's updating its catalog (database), it extracts keywords from the files and creates keywords depending on the folder name, file name and location on the server. This catalog can then be searched by anyone with Portfolio Browser as it's stored on the network (the program and the catalog). Extensis Portfolio is very buggy and crashes all of the time, so I'm currently looking for another solution that is more reliable and user friendly to non-professionals.
FINAL STEP: Once the photos are edited, distributed and archived, this is usually when I delete the photos from the CF cards (if I haven't done so already to make room for another shoot).
With kind permission from Paul Fisher, visualisation with GraphViz.
A version of this workflow is available at www.cs.man.ac.uk/~hulld/workflows/paul_fisher_complex.xml