View allAll Photos Tagged workflow

Pic from the inside of my truck. Yes, I'm actually a real Trucker! 😃😁

a workflow chart describing general content creation process as shared by professional media and hobbyist bloggers alike.

IOGraphica overlaid on my photoshop document for 31.5 minutes. I've been working on this for a few hours, so this is an incomplete mouse track.

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]

You can download this workflow from David Allens website: www.davidco.com/pdfs/gtd_workflow_advanced.pdf

or you may try the D*I*Y Planner Templates, which is a collection of very good templates, includying the one you liked: www.diyplanner.com/templates/official/classic

 

There are also other great gtd workflows that are similar to this one:

smerino.bol.ucla.edu/gtd/gtd-1.html - Collection

smerino.bol.ucla.edu/gtd/gtd-2.html - Daily Reviews

smerino.bol.ucla.edu/gtd/gtd-3.html- Weekly Reviews

elementkstaff.com/Student_Course_Materials/bnu/images/gtd...

blogs.salon.com/0002007/images/workflow_diagram3.gif

My new photo project about workflow of my friend and fashion designer Alena.

 

Best viewed on black

 

© All Rights Reserved

Coffee and photography, a good way to start the day. I'm thankful to the Lord for both. :~)

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).

I just constructed the cheapest standing desk ever, inspired by my coworker Jordan's setup.

Edited with Adobe Photoshop Lightroom 3.

Not sure how to proceed with a task? Use this handy flowchart.

Workflow

 

Photographed in Hospers, Iowa

Friday, June 6, 2025

Juniper SRX Process Flow

Le Suquet is the old quarter of Cannes, probably best known to tourists as the climbing, winding cobbled lane lined with local restaurants, Rue St Antoine. Le Suquet contains a clock tower and church that sit high facing east overlooking the Bay of Cannes and Cannes itself. At the bottom of Le Suquet on Rue Dr. P. Gazagnaire is the Marché Forville, where the market is held in the mornings and early afternoon.

 

This area is the original fishermans' residential area of Cannes. The houses are all very old. The streets were laid out at least 400 years ago. It is a 5-minute walk from the beach and is full of restaurants around the Rue Saint Antoine and the Rue du Suquet. A lot of the area is pedestrianised and is a major tourist attraction for visitors to Cannes.

 

The rue du Suquet is the original main road into Cannes. It came in below the walls of the castle (for defence reasons). It is a pedestrian street again and has plenty of restaurants [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

What is ECM and Document management workflow-...

  

Updating my workflow so more of the steps in publishing a podcast episode are done automatically.

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

+ vimeo.com/71165098

+ 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

Part 3 of 3

  

Then I do the same for the water area. Note that at this point this image is very similar to by 0EV capture—no surprises there. This was what I saw when I photographed this photo. I do HDR not for effect, but just so that I can have some details on the shadow area.

  

At this point you see that really there is not much color to this scene. In fact, they stand to distract the overall image, so I removed it. Here since I have been working in Lab mode I just quickly removed the color channels or just removed the color saturation. If I work with images filled with color I usually would use the channel mixer in RGB mode or use the black and white tweaking modules inside Lightroom. But as you can see there is not much color in this image to start with so I can simply just remove the color saturation.

  

After importing back into Lightroom, I tweak things further as I feel that I can still get some more details in the shadow area. If I were inside Photoshop I would do a image-wide shadows/highlights tweak but since Lightroom version 4 there is this new Clarity parameter which works very well in manipulating local contrast so I used it.

  

And that’s it. But remember, every single image is different. This is not a recipes. There are no rules. Now go have some fun!

  

Cheers.

  

# Full video

+ vimeo.com/71165098

+ 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 3 of 3 / SML Tutorials

/ #SMLPhotography #SMLTutorials #SMLEDU #SMLUniverse

/ #HDR #photography #workflow #tutorials #video #edu

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).

1 2 ••• 4 5 7 9 10 ••• 79 80