Showing posts with label software. Show all posts
Showing posts with label software. Show all posts

Saturday, February 1, 2014

Project365 - At the Game

Introduction
OK - let's try this again. I have recovered from the shock I had yesterday of discovering the forgotten last pictures of our Mother... I have always wanted to tackle the challenge of taking photos at the hockey games. Unfortunately, the Scotiabank Saddledome has a policy which prohibits "professional-looking" cameras. But not photography in general. If you use your phone's camera or your "point & shoot" camera, that's completely acceptable ! I know, right ? Bizarre...

So I took the "point & shoot" camera to the game, to see what I could capture. It's a Nikon Coolpix L122 - I don't understand the model numbers, but hey - It's a camera.

The Setup

Nothing to write home about... It's a Nikon Coolpix "point & shoot" camera. Everything is fully automated, with the exception of being able to disable the flash. It saves all images as JPEGs, so there's little opportunity for post-processing. It has a digital zoom feature, which allows it to get a little closer to the action, but it is slow to change.

The Photos

There is a significant delay between when I depressed the shutter, and when the photo was captured. I always felt like I was missing the shot - because I was !


I can't say that I am thrilled with the White Balance on this camera. Look how yellow the ice is ! Remember, the Saddledome has bright white phosphorous lighting. This should have been almost blindingly white.



Since the camera runs on a fully automatic setting, I was disappointed at how MUCH blur there was. Set manually, I would've had these at 1/500 of a second or faster. These were all shot at less that 1/80 ! No fast-action shooting here !




Overall, I was remarkably underwhelmed by this camera. Frankly, it makes me appreciate my DSLR a whole lot more. Perhaps that's WHY the Saddledome permits "point & shoot" photography - they know the photos will be Sh!t !

Lessons Learned

In photography, you truly do get what you pay for. Using a cheap "point & shoot" camera will get you mediocre photos. If you want better quality - you need to pay for it. Please note: this is NOT a comparison of Canon vs Nikon - that would be an unfair comparison. Both manufacturers build excellent DSLR cameras, which can produce some stunning images. This is merely an entry-level, consumer grade device. Which, when put in the hands of an advanced novice (me), fell way short of my expectations.





 

Monday, January 27, 2014

Project365 - Vertoramas

Introduction
As always, I like to experiment with new techniques. We are in Cornwall, visiting family, and thought it would be great idea to get pictures of the bridge to the USA before it is pulled down. So, mixing technique with opportunity, I thought I'd see what I could capture.
A panorama photograph is typically created when the subject of the photograph is wider than the lens can capture in a single frame. Special software is used to stitch together two or more frames. A vertorama takes the landscape orientation & runs in portrait, top to bottom.
The challenge is having enough overlap between the photographs to be able to stitch them together into a single realistic image. There are also other challenges, usually related to light. As you pan across the image, the intensity of the light changes.
The Setup

Since I want to capture a lot of scenery, my trusty Canon 60D has my Canon 24-40mm f/4 wide-angle lens mounted on it. Since this is a really cold day - 18 degrees BELOW 0C ! - I think I'll give it a go without setting up my tripod. Equally, it is a very bright, sunny day - no need for secondary lighting.
The Photos
Creating a vertorama starts by taking a number of images vertically, such that about a third of the photos overlap each other. Then the photos are turned 90 degrees so the panorama software can stitch them.
The first photo, including a lot of the base. Many tutorials suggest that you start shooting with your toes in the image & work your way up !


















Here, much of the original photo is still in view. I wanted to make sure there was lots of opportunities for the stitching software to find identical points.













Now we are starting to point upwards I would guess at about a 75 degree angle. For the entire shoot, my feet never moved. Nor did I change any camera settings.













This photo is looking almost vertical now.



















I'm starting to lean over a little backwards - but my feet never moved ! :-P
















In this, the final photo of the series, I am leaned way over backwards. Pat was quite sure I was going to fall over !





























So those are the raw photos. In the perfect world, I would have been tripod-mounted, with a rig which makes the tip of the lens the pivot-point. Given I am not expecting to become a professional vertoramist (I think I just made up a word !), I elected to forego such an expense, and thought I would try to shoot it handheld, and see what needs improvement. After all, this IS about learning and experimenting...

This is the output of the stitching program. As you can see, it stretched and turned some of the perspectives in the raw source photos, in order to align the reference points.


































After cropping and straightening the output photo, I did a couple of quick touch ups. Finally, it was watermarked.














































Lessons Learned
In a future attempt, I'd like to shoot from the tripod. I think it would render a better product, especially in terms of the alignment of reference-points in the stitching software. Also, I would like to shoot a venue where I have more control over the lighting. As you can see, the sky in the final photo gets progressively darker as I shoot towards the sun.
I like this technique a lot. It is fun to shoot, and creates an interesting photo. Although I am starting to appreciate why most vertoramists shoot inside large buildings - like churches and railroad stations ! But that will be another day's shoot ...

Project365 - Out and About

Introduction
We were traipsing around Cornwall, and found so many interesting things to photograph. I had decided to use my wide-angle lens, to see what effect it would have on the feeling my photos.

The Setup

As always, I was shooting with my trusty Canon 60D. On it, I had mounted my Canon 24-40mm f/4L series lens.

The Photos

Some photographers like to take pictures of running water with long exposures. This smooths the flow, making it look soft & silky. Here, I was hoping to capture the crusty nature of the ice. That crustiness is also seen in the concrete wall, and the swirling water - I hope !



This is the bridge between Cornwall, ON and Messina, NY. I wanted to shoot it before it gets torn down. The very bright sunshine (flare in the top right corner) makes the bridge look dark & foreboding. Maybe this should have been shot in HDR, but I like the hard shadows.



The sluice way at the power dam posed a challenge. The fence you see creating leading lines is also cutting right in front of me. I opened up the aperture wide, and hoped that any incursion would be invisible. It almost was - a little cropping saved the photo.



Lessons Learned

This shoot was an "out and about" series. I had not scouted any locations previously, so I had no idea what challenges I would face. Equally, the brutal cold made me push to be just a smidge faster. Prepping the camera settings in the car beforehand really helped !

 

Tuesday, January 21, 2014

Project365 - Explaining HDR

Introduction

Over the past few entries, I have dabbled a little with High Dynamic Range (HDR). I've had a couple of people ask me what it is, so I thought I'd pause for a moment and explain it. So this blog entry will be a little different.

The Setup

As usual, my camera is a Canon 60D, and I am using a 70-200mm f/4 L for the lens. I SHOULD have used a tripod, to insure the images were framed identically, and free of camera shake. I compensated for the potential shake by driving up the shutter speed to about 1/1000th of a second. I would have to let the HDR software deal with any misalignment.

Many DSLRs have a setting called Automatic Exposure Bracketing. On my camera, it is adjustable in the settings. It will automatically set up three exposures - one at the correct exposure (0EV), and then two more - one under-exposed and one under-exposed. In my case it was 1 and 1/3 stops. So my settings were -1.3EV, 0EV and +1.3EV.

My camera body also has the ability to shoot about six frames per second. So I set it up to shoot multiple images with a single click of the shutter, in high speed succession. So I could take all three pictures required for the HDR software in one shot.

The software, Photomatix, can take up to nine source images to create the final image, but three is sufficient for basic work.

The Photos

Here is the first photo at -1.3EV. It is very dark, and shows a bit of contrast.

 

 

At 0EV, we have a properly exposed image, which looks a little flat !

 

 

 

At +1.3 EV, it's very bright, but we start to lose the shadows & contrast.

 

 

 

The final photo, produced with an application called Photomatix, blends the three images together. You see all the details of the darker areas, while maintaining the contrast and details of the brighter areas.




Lessons Learned

I'm not sure I like HDR in landscape photography. As we have seen, it makes a final photograph look faked. I do like the process, and how it really accentuates architecture, for example. Once again, I got caught between always having a camera nearby, but not my tripod. But when an opportunity presents itself, you just gotta make the best of it ! Maybe I should just carry all my gear with me - I'd get a workout along with the photographs !

 

 

Sunday, December 1, 2013

Cloud - Platform as a Service

This is part three of a continuing discussion of The Cloud. In Part 1, we discussed how people perceive the cloud, and where these perceptions come from. In Part 2, we looked at Software as a Service (SaaS). Now let's look at what was the next logical evolutionary step - Platform as a Service (PaaS).

In discussing PaaS, we first need to understand a couple of other major milestones in computing history - virtualization and clustering. Virtualization has a big name for a simple topic. These days, almost anything can be virtualized: applications, operating systems, even hardware. We use the term "virtualization" to describe a method of abstraction. For example, a company called VM-Ware has made a business out of PC hardware abstraction, allowing them to virtualize the operating system of a computer. This allows them to run multiple instances of operating systems on the same compute platform, simultaneously.

A computer's operating system (OS) is responsible for "talking" to the hardware. For example, it interfaces with the hard-drive, so the applications we use don't have to know how to write the data to the disks. It interfaces with all of the various components, including the microprocessor, the random access memory (RAM), the hard disks, the network interface cards, and so on.

Then the virtualization layer comes into play, called a hypervisor, abstracting the hardware from the OS. Acting like a translator, it says "don't worry what KIND of processor or RAM" you think I'm supposed to have, I'll translate your queries & responses in a way that you will understand. This abstraction layer means that the OS can be deployed onto any piece of hardware, running the same hypervisor ! The underlying hardware layer becomes unimportant.

The first way this became important was in the area of Disaster Recovery. Since the OS and it's applications were now encapsulated into a computer file, and hardware-specific drivers were no longer important, moving the OS from one hardware platform to another became trivial. If a systems administrator could move the OS across the computer room, why not across town ? Or across the country ? Suddenly, disasters weren't catastrophic to a business.

Another key element to PaaS is the concept of the server cluster. Prior to virtualization, server clustering allowed PC-based servers to perform two duties - 1) scale the load of a single application beyond the hardware capabilities of a single server (aka a "node"), and 2) allow redundancy in the event of maintenance or a hardware failure. Google's famous search engine runs on many multiple server clusters, which are in turn load-balanced across different data-centers, so that new search requests go to less busy servers. So when a query comes to the virtual address of the cluster, the cluster-manager software determines which node to send the request to. The decision can be based on any number of criteria, such as how busy the nodes are, or the relative distance from the originator of that request.

Now that we have a hardware-independent hypervisor, and the ability to cluster our hypervisors, we can now discuss how to deploy PaaS. When an IT Department needs to set up a service, say a web-server, they can skip the phases of hardware and OS procurement, the phases of assembling the hardware, installing the OS and hardening it for security purposes. They skip ALL of that by simply logging onto their cloud-provider's management web-site & making a few choices and pressing the "provision" button. Then all they need do is install & configure the web-server and connect it to the data source. Clustering is important for making the OS Guest redundant across the provider's data-centers.

The main advantage of such a configuration is that it allows the service to be deployed in an elastic fashion. That means it can grow and shrink according to actual demand, rather than having to guess in advance what demand might be. Since the IT group doesn't need to buy new equipment for each new node, there is a shift from capital expenditure (CAPEX) to operational expenditure (OPEX), as well as potential savings related to the delay in time it takes to procure and deploy the new server hardware. Obviously, the cloud isn't free. Providers of PaaS typically charge for their service according to a number of metrics, including compute cycles, amount of disk-space required, and so forth. The positive is that the IT Group only pays for what they use, on an ongoing basis, rather than guessing and paying for it up front.

Again, we are seeing a shift in the business model. Now, the deployment can be very rapid, eliminating the acquisition phase altogether. The provider supplies the hypervisor and the operating system, and the client need only deploy the application. This allows the IT group to be agile in providing the services that its business requires, while having predictable costs associated with operating the service.

 

Saturday, November 30, 2013

Cloud - Software As A Service (SaaS)

One of the first ways in which the Internet started transforming itself into "The Cloud" was through software. In the early days of computing, software was a big deal. Teams of software engineers would spend days, weeks or even months deploying their software into a client's computing environment. In those days, the big packages ran on mainframes - huge, wildly expensive, monolithic compute platforms, typically owned by banks and insurance companies.

Later, as the PC era dawned, companies like Microsoft and IBM recognized just how popular these systems would be. So they encouraged development of PC-based software by marketing their development kits. A footnote in history is that IBM missed this eary trend, and chose to try to generate revenue from their software development kits. Developers abandoned IBM's OS/2 platform in favour of Microsoft Windows, as Microsoft gave their software development kits away for free at Developer Conferences. Suddenly, there was all kinds of software available for the Windows platform !

Software became a consumer product - shrink wrapped boxes sold at big-box office-supply stores like Staples and Office Depot. Early on, these were merely "single use" copies of packages that consumers had gotten used to using at work. Titles like Microsoft Office and Lotus 123 were popular. Soon after came games and other amusements. And with the rise of PC popularity came the rise of malware. By giving away their software development kits, Microsoft unwittingly opened the kimono to early malware developers ! And so followed the rise of utility software, such as Norton AntiVirus and PC-Doctor.

In those days, the Internet was still in its infancy. Typically accessed via dial-up modem, and through a University or College campus, it was still very much a novelty. Slow & cumbersome, it was not really the Internet we think of today at all ! But as the Internet became commercialized, and cable or telephone providers brought the Internet into our homes & places of business, the demand for ever-higher data speeds increased. This was critical to the development of Software as a Service. Interestingly, the notion of paying for a product or service via the Internet was born about the same time. The sordid side of the story is that it was pornographers who pioneered the methods for accepting credit card payments online !

Apple hit upon the idea that the device (laptop, tablet, mobile device) was merely for consumption. And so they started with iTunes - building a business model whereby the device was the access-point to the Music Store. Following this model, the "App Store" was born. Apple didn't want to include the middle-man. Why not have the consumers directly download their software from Apple. They even went so far as to remove optical media devices (DVD/CD-ROMs) from their hardware.

Other companies had similar business models. SalesForceDotCom (SFDC) believed that the web-browser should be all a client needed to access their popular Customer Relations Management software. Previously, CRM was the domain of big enterprise customers, and was implemented by a team of software engineers. Requiring a high degree of customization, CRM providers like SAP and Siebel generated high revenues through their professional services teams. But SFDC changed that model. Being web-based, and easily available via the open Internet, SFDC makes it's revenues on a subscription model, similar to a magazine or a newspaper. But without requiring dedicated, on-premise hardware, large up-front software purchases and implementation teams, companies of all sizes flocked to SFDC.

SFDC's new subscription-based software service became the model many companies want to emulate. Microsoft now provides Office365 on a subscription basis. Adobe provides their image-editing software on a subscription basis. So when you start thinking about "The Cloud", think about Software as a Service. Stated even more plainly, think about a subscription-based business model.