Skip to main content

Why should you edit your photos?

In my initial phase of digital photography, I was one of those who believe that editing an image is cheating the viewer. I took pride in my untouched photos and thought it was upto me to take a good shot each time I clicked the button and editing should not substitute my abilities as a photographer.

To some extent, I was correct. Technology should not, actually it can not, substitute my abilities as a photographer, however it can take my photos to a higher level. And if you thought touching your photos is 'cheating', consider having an orchestra at your command but you insist on using just the synthesizer! A digital photo is like creating music, a note here, a symphony there and you come up with a completely new tune. Similarly a little deeper tint, a little brightness and your photo can become a piece of art.

Composition is a very important aspect of taking a photo, one which can affect the perspective of your photo like no other. Sometimes it is not in your control to place your subject in the desired spot in the frame or you may not be able to keep yourself at the suitable distance from the subject. You take the photo and you find that there is a lot of unnecessary detail in the photo and your subject is getting almost obscured or at least it doesn't seem to be the 'subject' of the photo. Or most common example, you took a scenery but there are electric wires!

What do you do now?

Try 'cropping' your photo. In simple terms, remove the extra parts of the image from the sides. If your photo is sufficiently large, cropping the image will enlarge the subject and remaining parts of the image. Here is an example.


In this photo the stone pond is my subject, but there is so much more on top of the image that pond does not attract the attention immediately.

After cropping the photo becomes:


Now there is lot lesser clutter in this image.

Cropping is only one of the many ways you can edit the images. Almost all the photos of models/actors/actresses you see and drool over are touched up professionally in Photoshop. Professional photographers color-coordinate their photos to make those sceneries look like heaven or those wild-life shots come alive!

How to edit your images? Most photo-management softwares give you options to do simple editing of photos. I use Picasa which gives you one click touch-up in terms of brightness, contrast and lighting. Other actions like cropping and straightening too are very simple. You can even add effects in your photos. You can download it from here and install it.

If you don't want to install anything, you can do online image editing on Flickr.com.

This article should get you started with basic understanding of editing of your photos. Try playing with your images, you will definitely create something new and hopefully something better.

Comments

Tushar said…
Well said Asty Reay!
You hit on the mark about us the 'cheating' aspect. I suffered from this guilt fro some time. And like you, I have started using Picasa for the past few months. The resutls have been amazing. Using the "I am feeling lucky" option to edit improves your images dramatically. More so, if you are an amateur photographer. I have found the utilities like adding light very useful for images which have been taken in dim light and when I didn't want to use the flash.

Keep clicking.

Tushar

Popular posts from this blog

How to upload to Google Cloud Storage buckets using CURL

Signed URLs are pretty nifty feature given by Google Cloud Platform to let anyone access your cloud storage (bucket or any file in the bucket) without need to sign in. Official documentation gives step by step details as to how to read/write to the bucket using gsutil or through a program. This article will tell you how to upload a file to the bucket using curl so that any client which doesn't have cloud SDK installed can do this using a simple script. This command creates a signed PUT URL for your bucket. gsutil signurl -c 'text/plain' -m PUT serviceAccount.json gs://test_bucket_location Here is my URL: https://storage.googleapis.com/test_sl?GoogleAccessId=my-project-id@appspot.gserviceaccount.com&Expires=1490266627&Signature=UfKBNHWtjLKSBEcUQUKDeQtSQV6YCleE9hGG%2BCxVEjDOmkDxwkC%2BPtEg63pjDBHyKhVOnhspP1%2FAVSr%2B%2Fty8Ps7MSQ0lM2YHkbPeqjTiUcAfsbdcuXUMbe3p8FysRUFMe2dSikehBJWtbYtjb%2BNCw3L09c7fLFyAoJafIcnoIz7iJGP%2Br6gAUkSnZXgbVjr6wjN%2FIaudXIqA

Running Apache Beam pipeline using Spark Runner on a local standalone Spark Cluster

The best thing about Apache Beam ( B atch + Str eam ) is that multiple runners can be plugged in and same pipeline can be run using Spark, Flink or Google Cloud Dataflow. If you are a beginner like me and want to run a simple pipeline using Spark Runner then whole setup may be tad daunting. Start with Beam's WordCount examples  which help you quickstart with running pipelines using different types of runners. There are code snippets for running the same pipeline using different types of runners but here the code is running on your local system using Spark libraries which is good for testing and debugging pipeline. If you want to run the pipeline on a Spark cluster you need to do a little more work! Let's start by setting up a simple standalone single-node cluster on our local machine. Extending the cluster is as easy as running a command on another machine, which you want to add to cluster. Start with the obvious: install spark on your machine! (Remember to have Java a

java.lang.IllegalArgumentException: Malformed \uxxxx encoding

I was getting this exception during build while running ant. Googling didn't help much and I was flummoxed because the same code was running fine till now. My code reads a text file and does some operations on the basis of values read. It was only when I saw the text files I understood the error. I had copied the text in wordpad and saved it as .txt file. Wordpad had put lot of formatting information before and after the content. Also there was "\par" after every line, which was giving this error. So moral of the story: if you get this exception check your properties file (or any other file that your code might be reading.)