Showing posts with label Photography. Show all posts
Showing posts with label Photography. Show all posts

2008-06-21

Chicago

Patrick and I did eventually make it to Chicago. Fully six hours after we were supposed to, and after nine hours of bus ride, dehydrated, with a headache, and completely exhausted, we got off the bus, found our luggage, let Meghan (Kate's daughter) know we were there. After Meghan picked us up, we all went to get an awesome frozen yogurt treat, and we then went to (Kate's sister) Becky's house. We had some pizza, watched The Day After Tomorrow, then went to bed. It was a fold-out couch, but it was such a relief, and a good night's rest after havinng been on the train and buses for so long.

The next morning, we decided to head out to see some of downtown, Millennium Park and one or two other things. It was great fun, seeing the Chicago skyline, the giant reflective bean thing, and the giant water fountain faces. We had lunch at a little place called the Corner Bakery Cafe, then went back to the car to get our stuff, and head to the train station.

I knew were running later than we should have, and that the cause for it was an error in my own memory, saying that we needed to be on the train at 3:20, when our actual departure time was 3:00. So we rushed back to the car, only to have some shoe shining guy take my brother against all of our will, and dob this "interesting" white shoe cleaning material on his feet. The crosswalk had just told us we had permission to cross the street, and here we were, having to wait for some maniac to finish with my brother's shoes. All the while I'm screaming about how "the train is at three o'clock! we have to go!" and my brother's shoes, which already had the exact appearance he wanted, are being visually altered against his will, by some maniac who has the gall to charge him $4 per shoe.

So it was at that point that I decided we were late. Most of my readers know about CoryTime, and it went absolutely crazy today, as we walked into Chicago Union Station at about 2:45 p.m. (CDT), which was just fifteen minutes before our train was scheduled to leave. Luckily, Meghan and Sean saw us all the way into the terminals, and we got on the train just in time. Not to be outdone by my schedule, I still managed to snap a few hundred photos of downtown.

So now we're on the train, heading to Lapeer, Michigan, where we'll see our grandmother. I'm pretty excited for our travels to nearly be over, and for our vacationing to start.

2008-05-25

Flatcat

Today, after sleeping until noon, Meaghan and I went to the Black Bean, a small Mexican restaurant inside a little nook of Flagstaff I would never have seen unless someone had taken me there. Luckily, Meaghan was there to show the way. The food was great.

flatcatAlso part of our adventure was a trip around downtown, including some shops like the Blackhound Gallerie, where I got flatcat, my new dorm pet. When I get my printer back at the beginning of the next semester, flatcat will be assigned to protecting that, but for now she (or he or it) is assigned to protecting flatdell.

All told, Meaghan and I spent about 4 hours walking around today. I got about 160 frames in with the D300, and there would've been more if I had brought more than one memory card. Today's Photo365 image is pretty great. There were some very awesome shots of Meaghan, but for today, the train picture won.

We're probably going to make these particular event a weekly thing, because we found out that downtown Flagstaff on a Sunday afternoon is a very fun place. Live music, shops, and great photographic opportunities. Next time I go to downtown, I am definitely bringing all of my memory cards.

2008-04-29

Photo365

Last night Megan linked me to an article on the PhotoJojo site, detailing a project that anyone can do called Photo365. If you've been looking at my flickr feed, you're probably fairly well-aware of the fact that I use my iPhone to take photos and post them online quite often.

Although, I wouldn't mind a good excuse to carry around the D300 a bit more often. And it sounds like there's gains abound to be had while participating in the Photo365 project -- Especially the part where...
Taking a photo a day will make you a better photographer. Using your camera every day will help you learn its limits. You will get better at composing your shots, you’ll start to care about lighting, and you’ll become more creative with your photography when you’re forced to come up with something new every single day.
Although I can't really start right now with it, I'd really like to start this summer, and hopefully be able to keep up with it next school year. Although I've been pretty good at blogging every day, I know that taking photos sometimes becomes difficult for me, because it's not really something I can do during classes. (Although between-class photos are better anyway.)

So I intend to start the project over the summer, I am probably going to either get Flickr Pro, or set up my blog on the U60, but that's a project for the summer, rather than posting every image to Blogger or Flickr. Things to consider later on, anyway.

2008-04-27

The Shot

Earlier this morning, I finished watching the VH1 show I downloaded from iTunes, The Shot. In The Shot, eight or so people competed to become the next big fashion photographer.

The production values of the show weren't that great, even in the last episode I was distracted by a few audio problems, but I don't necessarily think high production values were the goal of the show. As a show about photography, I think it succeeded as a show about photography, although I don't think it was necessarily meant to appeal to people actually doing or studying photography, except as a general broad-strokes type of thing. It's intended audience really probably was "people who watch VH1." Although I'll admit that one of the biggest reasons I liked it was the drama, and because that first episode was free on iTunes.

Anyway, my favorite of the contestants ended up winning, which was cool. I think this was the first time I kept track of a "reality" show from beginning to end (albeit after the fact, I think the show is a year or two old by now.)

2008-04-23

Engineering Building

Today was the first time I dared to venture into the Engineering building. After my trip to the Lab Sciences building the other day, I was feeling confident that I could go and get some compelling images of the fairly newly remodeled building.

I got a few great outdoor shots of the building, and a few other random things on South Campus, but I don't feel as though I've done that beautiful building justice. I need to work on both the Engineering building and the College of Business Administration this summer, because I think I can get much better images than what I think I got today.

Although the adventure into the Engineering building did afford me an interesting opportunity to take a look at some of their systems. They've got a bunch of Sun Ray 2 thin clients hooked up to a little farm of terminal servers, and you can select at the machine whether you'd like Windows, UNIX, Linux or just a web browser (which I presume is firefox coming in at full screen off of a Linux system, but I didn't check.)

The setup they're using, with terminal servers and the thin clients is pretty clever. In theory, your thin clients stay modern for a very very long time, and they're extraordinarily low maintenance. Add to that, the fact that you can terminal into different systems, I think the thin client setup, especially in the College of Engineering where it's fairly quick, is a good winner. The only problem I can see is that there are a few instances where network bandwidth isn't really good enough to support a lot of thin clients. The W.A. Franke College of Business Administration has some problems with it's SunRay clients because, I suspect, of high server loads or slow network connections. The size of the display may also have something to do with it, as the CBA runs very large 24-inch monitors on it's thin clients, while the thin clients at the Engineering building were running at 1280x1024.

One of the only negative things I can think of to say about the thin client situation is that I would really like it if Apple or some third party Mac vendor were to get everything set up so that Mac systems can be used by thin clients.

Ahwell, just dreams I suppose.

2008-04-19

Impending Switch Canceled

Well, I'm just not sure what to say. For about three months here I've observed a very huge difference between Adobe Bridge on my Mac and Adobe Bridge on my PC. For quite awhile, my impression has been that Adobe Bridge runs better on Windows than it does on the Mac. My guess at why was mainly as a result of how Adobe must work in order to maintain the same code base on Windows as well as the Mac. Unfortunately, while working on keywording some of my older images earlier this morning, I found out that I was terribly terribly wrong.

It turns out though, that what's actually happening is that either version of the program starts to become erratic and unpredictable in it's behavior with keywords once you've started to add some keywords to your keyword database.

I am both severely disappointed, and quite happy about this. First off, it means that basically I've been complaining needlessly for the past several months. The PC and Mac versions of Bridge suck equally! The great thing about this though, is that it doesn't necessarily rule out Mac OS X as a computing platform for me in the future. I had no serious plans to run out and replace the iMac in the next year or two, but in the past month or two, but I had been giving serious consideration to making my next new desktop computer a Windows PC, and I'd been researching the various vendors of Windows hardware, and preparing myself for the cost of a decently well-configured Windows-based computer, based on today's systems.

I'm not ruling out a Windows machine as my next computer, nor am I ruling out continuing to test Adobe CS on Windows as well as the Mac, but it just makes a switch to Windows much less necessary.

I'll end this post with this one last statement: GAH... Really, Adobe? Really?

2008-04-12

Switching to Bridge

This is "Part three of an unknown number of parts" in a series I'm calling "Cory talks about how he manages his images." In Part One, I described the history of the schemes I used to manage my photos, including some of the rationale behind each of my switches to a new management system. In Part Two, I ponder the affects of various systems which I could use for photo management. It's also worth noting that I sat on this draft for a very long time, so some of the time is messed up.

This is no giant shock, because it happened several months ago, but I've recently switched to a workflow featuring Adobe Bridge for organizing photos. One of the main features of this system is a heirarchy of folders and Adobe DNG files that consist of my master images, Photoshop PSD files that have files that have been changed at all, and images I've already prepared for output.

Adobe Bridge is what we'd like to call image browsing software. It's capable of interpreting Camera RAW data, building little previews of almost all types of files in any given folder, and things like assigning keywords, ratings and other metadata properties to files. It's somewhat less efficient in some of these processes (particularly rating and keywording) than a few other options available for the Mac, but on the PC, it works great. (More on that later, I'm sure.)

One great side-effect of this system is that I can actually access my files from any computer that doesn't have Bridge or Photoshop installed. Another cool aspect of Bridge is that it doesn't even require I be using a specific type of computer, or accessing my files in a particular way. Because there's less overhead involved in using the files, I can feel confident hooking them up to a network server, or leaving them on a FAT32 formatted drive and using them with my mobile Windows PC as well as my Macintosh at home.

After using the iMac to convert just over thirteen thousand images to DNG format, then split the files into the four gig buckets specified by my workflow, I started using it to give keywords to the images in the first bucket of images, from when I got my first digital camera several years ago.

One thing I noticed at this point was that while Bridge "worked" it definitely wasn't the smoothest possible solution on the Mac. it lagged when loading any significant number of images, and during the process of keywording, something that's specific to the Mac version prevented it from being able to actually add a keyword to an image unless you follow a strange set of keystrokes for each image.

But alas... as a result of PHO382, I was switched to Bridge permanently.

Well that's enough of Bridge for now, but stay tuned for the next article in this series about digital workflow management, or whatever it is I'm calling it as you read this.

2008-04-11

Blogging as a Career.

Recently there was a very interesting article on ZDNet, talking about the high-stress world of blogging for pay. The focus of the article is on the instantness of the Internet as a publishing medium, and the stress that's caused by the fact that anybody can get to any given story, and he who gets to the story first gets the most clicks.

One of the main points of the article is how there have been two fairly recent and fairly well-documented cases of bloggers having health problems, potentially related to the stress of their profession. It's great that blogging is now considered to be a very legitimate form of journalism, but it's unfortunate that in order to be successful at all at it, you need to be awake all hours of the day so you can be the blog that has the information first.

This is one of the things that admittedly makes me quite happy that I'm not really blogging for pay, or for another website where I'm stuck to someone else's publishing schedule. Although I'll admit I've had a few moments where I wasn't really sure I'd be able to get a post up onto the blog on time (my main goal is one per day, I haven't been strict with exactly when that post shows up, and sometimes a post will show up a few hours early or late, but since spring break there has been one post that corresponds with each day.

One thing I wonder about this relates to my intent to become a professional photographer. If this is what it's like to do freelance writing on the Internet, do some of the same stresses apply to being an independent or freelance photographer? Or will I find some job where I've got a predictable, reasonable schedule for shooting and delivering?

Maybe I'll start or be a part of a successful photo-blog. That would be cool.

2008-04-08

Jack Dykinga / Wind on Campus

Jack Dykinga is basically the photographic hero of my PHO382 instructor, and today instead of class, we got to go hear him speak. On one hand, it was a pretty awesome way to spend some class-time, especially with the high amount of stressful stuff we've been doing in my other classes. I've still got an essay due Thursday, and I had an exam or two today.

Ah well, the blog must go through!

At the very least, it was a good revenge for the Wednesday night class, which had Ami Vitale the week before, and was already a week behind.

On another note, it's been very windy on campus today. It's almost that "right before a big storm" kind of windy that I experienced a lot last semester, where I knew something was coming, just not exactly when.

2008-04-04

Color Accuracy

This is mostly just a note to let everyone know that my color calibrator arrived! It's an x-rite i1 display 2, which is a long somewhat confusing name, but I think overall the thing's a fairly solid middle of the road offering, and I'm really happy with it. Especially since bhphotovideo sells it for $250, and I got it for $175 from MAC-On-Campus.

I've just got to say, I'm really happy with it. It's not something that I can really use every day, but it really is something that's already made a difference. Looking at my photos is now a better experience, and I think I'll be able to get better output from RA-4 process wet labs that use machines like the Fuji Frontier. (and Target, which uses Kodak's competitor to the Frontier.)

Right now I've got my iMac, which is a bit over a year old, set to remind me to calibrate every two weeks, and my ThinkPad, which is just under six months old, to remind me every three weeks. So even though I can't use it daily, I intend to be using it biweekly at least for the next few years. I don't know if these things ever wear out, but if they don't, then I can't imagine myself really needing to replace it -- although if it does wear out I hope someone lets me know.

2008-04-01

Scanning Negatives

I had some other crazily awesome blog entry planned for today, I think. Although I've completely forgotten what it was, and although the draft for it is probably in my other computer, that's not where I am right now, and I'm feeling like I'm in a pretty good writing mood, so here I am, working on a post in Blogger's web mode.

Today I'm just hanging out here in the School of Communication open lab, preparing for my PHO382 midterm, and we're finally scanning files for Megan. I'm not sure exactly how much quality we need, so I've gone ahead and tried to give us as much extra quality as I possibly can. This way, even if we end up outputting 640px jpegs for the web, we'd have as much latitude and data to work with as posible, which is awesome. Only real problem is that it seems like the process of scanning these 300 megabyte TIFF files is very.. umm... well, intense. The computer hates me ow, basically. The protip of the day is that 300 megabyte TIFF files make computers very angry.

The open lab here at the school of communication consists of all Macintosh computers of various ages. I suspect some of the machines in this room, set up and able to be logged into on titan are nearly a decade old, such as the old PowerMac G4 systems with their 15" ADC displays. The very ones I remember Apple unveiling in 1999 or 2000. What workhorses. On the other hand, we've got a lot of pretty modern systems in here too, a bunch of the latest 20" iMacs, and G5s of various types (iMacs and PowerMacs.)

This iMac performed very well at first, and I bet that as a standalone machine, or a machine in an environment with a much faster network, this thing would rock so hard, it wouldn't be funny. Similar to those 2.0GHz/2GB Dell OptiPlex 755 systems in the College of Business Administration, except the iMacs here have bigger displays and webcams. Oh, and there's the whole thing about how the School of Comm only has one file server, but that's actually a post for another day.

SoC Lab iMac
The only thing I can really purport to not love about this iMac is the keyboard, at first Apple's newest keyboard is a little bit off-putting. It's so low on the desk, and it's somewhat difficult to get used to the idea of a laptop keyboard like this on the desk. It was also difficult for me to find an appropriate position for the keyboard, where I felt like I could start typing on it at full speed and not have it fly out from under my hands, or have my fingers start feeling weird as a result of the odd positioning and shape of the keyboard. After a few hours of typing this blog entry and chatting in Meebo and Mibbit however, I'm feeling much more confident with this keyboard. While I'm not going to run home and buy one tonight, I would feel confident in ordering and using one if both of my previous-generation Apple Keyboards died, or it came to be that I ordered a newer Mac and didn't have a different keyboard to use with it.

2008-03-24

Reliability, Nikon D300

I write about reliability far too often. It's sad but true, for some reason, the products I use seem to be horribly horribly unreliable. The iMac since getting it in December 2006 has been in twice, once to have it's motherboard, optical drive and hard disc replace, and once to just have its hard disc replaced. Most recently, my new camera, the Nikon D300, which I purchased exactly one month ago today, has been having a weird little problem.

Specifically, when I make exposures under very specific conditions, the camera displays "ERR" in the viewfinder and on the top LCD. The particular conditions are "any ISO, any shutter speed, any F-number above the minimum for the lens." That might not mean anything to any of my readers, but I'll sum it up in a user-friendly way. "about 95% of all photographic situations."

So the other day I opened up a service ticket with Nikon's online knowledge base system. The response I got back earlier today was that I should try to charge the battery, and make sure I was using a supported memory card and lens. If those hints didn't help, that I was advised to go ahead and send in the camera.

So now I've printed out a repair form and shipping label, and all I need to do is find suitable packaging for the thing and send it in. With luck, that won't be too extraordinarily challenging, because I'm not actually too interested in sending the camera in, let alone finding my own packaging and paying my camera's way to Nikon's facility in El Segundo, CA.

Although, for the people who have told me about how the value of a repaired D300 outweighs the costs of getting it repaired (in my case, just the time without the D300 and the cost of shipping it) I'd like to mention that I've had the D50 nearly three full years without ever having a hiccup with it, and that the D50 was Nikon's cheap model a few years ago. So I don't think I should have to send my brand new camera into the manufacturer in order to be able to get use out of it.

Anyway, with luck and skill I'll have the D300 sent out by this time next week, hopefully to be able to get it back before going on my trip to Michigan this summer. It seems depressing to me that I should say something like "maybe in two months I'll have it back and it'll be useful" but I've never experienced Nikon's send-in service before, and from what I've read online in the past, there's a good chance that it's not as efficient and well-thought-out as AppleCare's send in service is. (in AppleCare, for a laptop, they mail you a box free, you put your product in and mail it back free, and they have your computer back to you in less than a week.)

And with that, this is the official opening of the Nikon category of my blog. Things pertaining specifically to Nikon, such as the rest of this saga, will be put into said category. It'll be epic.

2008-03-23

Nature Sounds (video)




Today Jim and I heard some nature sounds from our room! I decided it would be cool to make a video about it.

Also Today I've been doing some of the bookkeeping and keeping up in general with my camera, that's been experiencing a weird problem at high F numbers like sixteen and twenty two. It worked fine last night when I only needed to go to F/4 once, (I was hanging out at 3.5 all night because it was, well, night.) So right now I"m charging the battery, which was one of Nikon's reccomended steps. I've alreayd done the two-button reset, and I'm afraid that if this continues even after I've fully recharged the battery, Nikon is going to have a quite unhappy Cory on their hands.

2008-03-17

Quiet Day

It's very quiet today at the helpdesk. I haven't gotten an actual call yet today (knock on wood) and a bit ago, the chatter of the full-time staff mysteriously stopped. I don't know whether it's relaxing, or creepy.

At any rate, I've just been here writing blog entries and working on some photography stuff. I'm getting some of the base adjustments on some of the additional images for my photo class, and finding other images I want to work on. I really should start working on rating and keywording some of the older images too. I can't wait to (whenever it finally happens) to just have that done.

So, I'm just hanging out here, writing blog posts and working on photography. I'll probably hang out here with Meaghan a bit when she comes for her shift later on. She's got some images on which to play Photoshop too.

2008-03-16

Nuclear Winter Will Never End

Let me begin by saying that I really admire people who actually find time to write on their blogs every single day. Even if it’s something small. I tried yesterday, to write and post something, but once I got to Peter Piper to start writing my blog entry, and Megan and I had finished lunch, they decided to let Megan go early, thus cutting my writing time short. (Although I’m very appreciative of the time spent with Megan.)
At any rate, today’s blog entry is about what I’m calling Nuclear Winter. Basically, it started snowing in November or December of last year, and it hasn’t stopped since. It was definitely cool for the first month or so, and the first cumulative foot of snow, but after awhile it really prevented me being able to or wanting to go out and do anything other than that which I was required to, like classes and work. I even went through a period this semester where I was eating significantly less because I was never willing to take a trip to the store to just get some food.
Luckily, Megan and I went to the store yesterday and I stocked up for spring break, but the fact that it’s snowed worries me for other reasons. My dad was supposed to come up for a visit sometime over this break, and if I have to say to him “oh, it’s just snowed last weekend” then he is unlikely to want to come visit.
The other bummer is that I wanted to get out and take some photos with the D300, but I’m not super comfortable walking around outside with it in the snow. Plus, I’ve got a lot of other unattractive snow pictures. I really just can’t wait for it to be July or August again. Flagstaff looks amazing at that time of year.

2008-03-10

Horrible Horrible Disillusionment

The good news is that my PowerBook G3 isn't actually dead. It's just that my power adapter has died. The bad news is that even though my G3 is now once-again alive, I'm coming to the end of a horrible horrible disillusionment about the state of the Mac as a computing platform.

In short, especially with Windows Vista, there's almost no advantage any more to owning and using a Macintosh computer. Even for photographers, web designers, and graphic artists.

This is where in previous blog entries, I would've tried to reassure you by telling you I'm not thinking about switching to Windows. But the truth of the matter here is that I've already got a great mobile Windows computer, that happens to run Adobe Bridge better than my desktop Mac computer.

To better explain the situation, I've got to ruin my next blog post and let the world know that I've officially taken my photography workflow to Adobe Bridge. It's probably a permanent move, and I'm overall quite happy with it. Even poorly behaved Bridge is fairly productive, and I've already got the first group of four gigs worth of DNG images keyworded, and I have been working on the second group. The workflow in question provides a clear path toward archiving things on DVDs, and it's a cross-platform solution.

In order to take advantage of the cross-platform nature of the Bridge workflow, I recently "acquired" Photoshop CS3, and installed it on my ThinkPad R61i. When I loaded some images into Bridge and started keywording a more recent set, I was surprised at just how fast everything goes. I don't wait for application of metadata, or for keywords to show up on images, I just work through the set, rather quickly actually, and all of the keywords are applied. The program doesn't start behaving oddly, and it can keep going for hours.

What a gyp! on my iMac, Bridge starts behaving very poorly after only about twenty minutes of keywording, and the whole program becomes unstable while it builds caches, applies metadata, and does anything other than sit idly. (Actually, I've also experienced extremely unreliable idle sitting Bridge. That was fun.) To use a trite expression, and to add insult to injury, the PC I'm running Bridge on is a low end business laptop with a slow processor and a slow connection to the external hard disc. It's got one gig more ram than my iMac, but the Macs at the School of Comm also have that extra gig, and they're just as bad at Bridge as my home iMac.

I've also noticed that I've got almost zero other Mac-only software. I like iChat and Mail, but Pidgin and Thunderbird have been doing a great job on my Windows machine. I browse the Web with Firefox, even on my Mac, and the other things in my dock are either not needed on Windows, or are available on Windows easily (like the whole Creative Suite group.)

So... while I'm not about to run out and replace my iMac this week, I'm really going to be looking at Windows desktop PCs and workstations when it's time to buy my next computer. I'm also going to be looking really hard at the Windows version of Adobe CS4, when that comes out, because as it stands, I can run Windows software very easily on my existing Mac hardware.

Such disappointment.

2008-03-09

Dating Photography

Yes, I know it's not timely. Ohwell.

As per a thread on the 68kMLA Forum about the total cost of owning a computer, I'm currently merely dating photography. In order to extend our relationship to marriage, I need to go and meet photography's parents: the darkroom. Not only, of course, have I been in the darkroom for nearly three years now, but I'm fairly certain that photography just doesn't care if I meet her parents. Also, I'm apparently not fit to even be allowed to view the 68kMLA forum, because of my affinity with things like "getting my schoolwork done" which can't be done on something with a 68k processor. Well, let me just say, rude newbies. I'm not worthy, really. Luckily though, Photography and I have talked it out and we're fairly comfortable with our open relationship, I'm also dating German, Megan, CIS, and History.

2008-03-04

Photo Management.

This is "Part two of an unknown number of parts" in a series I'm calling "Cory talks about how he manages his images." In Part One, I described the history of the schemes I used to manage my photos, including some of the rationale behind each of my switches to a new management system.

I struggle with managing my images constantly. It seems like the photos I come out of my camera are always either receiving really esoteric naming schemes, or are being put into some trendy new piece of photo management software. On the other hand, images I download from the Internet, or are sent to me by people are stored haphazardly in an ill-conceived folder structure that tries to separate "pictures of friends" from "pictures of trains" and "pictures that are random."

My main problem with my personal photo collection at this point in time is the fact that it's poorly organized. Even when I find a great piece of organization/management/processing software such as Aperture, which is where my images are right now, I have problems with the actual tasks of applying metadata, coming up with a naming scheme, and deciding where in my library to put each image. It looks organized, but because I've got images from two or three different eras of management, and even a bunch of images that simply don't have good naming applied to them, it's difficult to decide where an image goes, or to find an image once I've put it in its place.

The answer, quite simply, is that I need to beef up my use of metadata and keywords. The thing I need to decide really quickly here, as I continue working on gathering even more images, is whether or not I want to continue using Aperture for my images, or if I want to look into other Mac-only programs, or switch to Adobe Bridge.

Enter Photography 382. This class is pretty amazing so far, the instructor is very energetic about the subject, and does a great job of explaining thing, which is awesome.  The focus of PHO382 is preparing digital image files for output, and the beginning of this is setting up a good workflow for acquiring, storing, backing up, and organizing digital images. The main tool for the class so far is Adobe Bridge CS3. We've been learning about batch renaming, applying metadata templates, and adding keywords to images. I expect we're going to continue learning various things about Bridge and picking things up about it as the semester progresses. So now, I just need to decide if I want to switch to it for managing my images, and when I want to do that.

I'll admit that Aperture isn't the best solution for everything I do, especially when my photos are considered, because Aperture lacks an equivalent on the Windows platform. I can't just copy my library or my folder structure out to a file server or onto a FAT32 disk and open it on a Windows computer, like the ones at work, or even my mobile computer. In addition, it's more difficult than it needs to be when I copy images from my mobile computer to my Mac, because the images are still in an unprocessed form, I have to apply my naming convention and do my organization when I get back home.

Another advantage of finding some other system by which I can organize my images is that I am not necessarily tied to the Mac as a platform. I love my Mac dearly, but I'm simply not sure if I'll ever buy another mobile Mac again, and I may not even buy another desktop Mac, depending on what Apple ends up doing in the next few years. Chances are very high that I'll have a Mac as my next desktop, but just in case, I like the idea that my option to switch to Windows is open. (In fact, I once needed to do just that, during my first semester at NAU my G3 PowerBook was always on its last leg, so I moved my then-Bridge-based collection of photos onto the Dell OptiPlex machines I'd gotten from surplus sales. The transition was really quite easy. Oddly enough, that Pentium III/933 machine got better SETI@Home scores than my 1GHz PowerBook G4 ever did.)

The main problem with having that multi-platform solution for image management, of course, is that I have no large-capacity storage areas that work with both Macs and PCs. FAT32 would almost be acceptable, except I doubt that a 750 gig fat32 drive is going to work too well. Add to that, I don't have Photoshop CS3 for Windows anyway. I may need to do research on software that lets Mac OS use NTFS drives, or software that lets Windows use HFS+ drives, because sharing drives tends to be a general problem for me, not only a photo management problem.

A big disadvantage I can see of using Bridge for my photo management is that it's not the best app ever for actually searching for things I need. Even the PHO382 instructor I have mentioned that he uses a piece of image cataloguing software, instead of only using  Bridge. I'm going to investigate this more as an opportunity for how I use Bridge (and maybe Aperture!) because I like the idea of having Bridge for setting up a lot of the metadata, naming, etc, as well as having Aperture if I want to search/catalog and do some of the things at which Aperture is great.

So I haven't actually made my decision yet, but there's a good possibility that I'm going to be moving my photo operations back to Bridge. Stay Tuned however, for Part 3 of the first-ever Strapped to a Desk multi-part series, on "how Cory manages his photos."

2008-02-25

Nikon D300

Well, I've gone and done it, I suppose. I've impulse-bought a new camera. It's not a half-bad camera either, I got the Nikon D300, and an "AF-S Nikkor 18-135mm 3.6-5.6G ED DX" lens for it, along with a filter for the lens, and a fast 2 gig CF card. I bought it at Ritz Camera after Megan and I had dinner at Ruby Tuesday's.The D50, sitting atop the D300's box. The images in this post should link up to full-resolution versions of the images that came out of the camera. I did minimal work on them using the included Nikon Capture NX software. Unfortunately though, my ThinkPad's display is not calibrated.

I decided to buy it at Ritz because the D300 is new enough that it costs just about the same amount of money everywhere, and because it was a situation where I could have it and start using it right away. And right away did I start. The very next morning after my shower, I unpacked the D300 and its lens. What an exciting feeling, that of unpacking a new piece of equipment and starting to use it. I carefully removed the D300 and the lens from their boxes, taking care to take a variety of hopefully-interesting photos with the D50.NAU's new Applied Research & Development Building.

So far, the difference is rather amazing, especially in the lens. The lens isn't that different from my old Quantaray 18-125mm lens, except for the fact that this one seems much sharper so far. I haven't used under all of the same types of conditions as the Quantaray, but I'm sure it'll be less than a year before I can tell whether or not I really think this lens is a better lens. I can tell you now though, I think this is a better lens.

The body is extremely well-built, its heftiness, speed and overall build quality show that it's a higher end camera than the D50, which in and of itself is an excellent piece of imaging technology, from a usability as well as a quality standpoint. The difference in the amount of pixels is readily apparent, especially on my mobile computer, which has been suffering performance problems as of late anyway. The other most apparent differences are in the speed of shooting, which is immense. I have always thought of my D50 as fast, but this thing can rapidly fire off nine or ten shots without even blinking. Said images will be properly focused too, because the AF system on this body is amazing. The other immediately noticeable difference is the review screen. The review screen on this camera is nothing short of amazing. It's significantly larger than that of the D50, which back in 2005 and 2006, I remember saying was very large and bright.It's Tracy!

I took it out for a test drive after unpacking everything and getting used to controlling it. (Not to say that I'm very good at it yet, but I'm getting used to it.) My initial reaction to shooting with it is that I feel like I'm getting the shot I want, when I'm framing and shooting, even if I'm shooting something I didn't expect to be, or if I'm walking around and I happen to see some people I recognize, such as the image above of Tracy. The only bad thing I've got to say about the body is that when I was setting it up and hooking up the camera strap, I did so in a retarded way, and while walking around,

I took it to the overnight too, and although it's not necessarily as great a low-light performer as the D300, I'm sure that between the onboard flash and the Nikon SB600 I've got hanging around, I'll manage. I used the SB600 on the image of the D50 at the top of this post. Although even at relatively high ISOs, the D300 does still procure nice images. The image of the Dell OptiPlex in the SLAC was shot at ISO1000. (The D300 supports all of these weird ISO numbers I've only ever seen on Olympus cameras before.)

One of the things I think some people may now be thinking is "what about that non-full-frame sensor?" Unfortunately, that was one of my biggest desires for the camera upgrade, and it's the one thing I didn't get. I'm not too terribly sad at this point though. For one thing, getting a full-frame sensor requires either saving a few additional years to be able to afford the Nikon D3, or a switch to Canon.Dell OptiPlex GX270 in the SLAC.

I was seriously considering that switch to Canon too. However, the thing about that is that I've already got four different Nikon lenses, the Nikon flash, the off-camera Nikon flash sync cord, and in general, I'm pretty decent at using my Nikon stuff. The other thing is that the currently-available Canon full-frames are the 1Ds-Mark II, the 1Ds-Mark III and the 5D. None of which can be had new for less than $2000. BH has the 5D for $2100, compared to the D300's $1800, and the lens I wanted for the Canon was just shy of $1300. That's a pain in the wallet. And really, being that the 5D was released in 2005, it's out of date and due for a replacement. A replacement that will most likely cost significantly more than the 5D's current price anyway. Aside from the sensor thing, for the savings, the D300 is a significantly better camera in nearly every way.

Although, they say that what makes a great camera isn't necessarily the megapixels or the image processor or the brand or the size of the sensor. It's the ability that the camera has to let the photographer create an image. And while I think that one of my talents as a photographer is to be able to get the results I want out of nearly any piece of equipment. The D300 just happens to let me be even more sure of the images I'm making, and it lets me make them a little bit faster.

2008-02-19

History of Management of Cory's Photos.

When I got my first digital camera (A Kodak EasyShare CX6220, for those of you who want to make fun of me for having owned a Kodak), I just imported my images into iPhoto. It worked well for the first thousand images, and I always thought of it as being fairly speedy. I painstakingly named and even added descriptions to many of the images, and some of my best, I posted to deviantArt. After awhile, and a trip to Michigan, iPhoto became unstable. Unstable enough that I actually lost what I think amounts to about two or three hundred  pictures I'd taken while I went to visit my grandmother in Michigan. I was, of course, unhappy, and to this day I still go on random searches for those images. They never turn up.

Then, in Fall 2005, I got my first taste of real photography, in Kate's Photo I class. I used dad's Canon AE-1 film camera for that class, and subsequently decided that I really needed to do more photography. I was, you could say, hooked on film. That Christmas, dad, knowing that I now intended to do more photography classes, and possibly even use it as a career for my real life, gave me the Nikon D50 I use to this day. It was a great camera, and it remains so, but it had something I didn't know anything about yet: Camera RAW, and more specifically, the Nikon Electronic Format.

A month or two earlier, Apple had released an exciting-looking new photo management application geared toward the needs of professionals, called Aperture. It looked like a super exciting program, with the ability to do most of the stuff I needed with my photos right in the interface of the program. I eagerly downloaded and watched tutorial videos, wanting to know more about its functionality. I decided it was the program I needed for my photos, since iPhoto had already failed me a few times, and I didn't have a modern enough version of Photoshop hanging around.

I downloaded Aperture, but realized I couldn't use it until I upgraded my computer to Mac OS X 10.4. This is an entirely separate debacle, but after getting and installing 10.4, twice, I finally got Aperture 1.0 working on my below-spec G4 PowerBook. It was an amazing program, I spent most of my time waiting for it, but it was amazing nonetheless.

Of course though, later on I decided that Mac OS X 10.4 and the speed of Aperture were unbearable, so I "found" a copy of Photoshop CS2, exported my photos out of Aperture, and installed 10.3 back on the PowerBook. At this point, I'd also acquired my first laser printer, and the solution seemed clear, I started right away creating my second photo organization scheme.

Using a MacBook Pro at the high school, I renamed and exported all of my images to one big folder. I then started using Adobe Bridge to rename the images a certain way. PIC_XXXXX.ext where XXXXX was a unique number I assigned to each image based on the date it was taken. Starting at folder zero and working my way through about two hundred folders' worth of images (at least that many) with thirty images per folder, I organized all of my images into neat little buckets of images, perfectly sized for printing contact sheets using Photoshop CS2. The idea was pretty good, I thought. I print out a bunch of contact sheets of my images, and it takes me less time to findt he image I want. Then, I pull the image out of my collection, do whatever to it, and save the derived file to a separate place. It turns out, I wasn't actually all too far off with this sytem.

Although soon, I was separated from my contact sheet binders, and since I'd gotten the much faster iMac in December, 2006 anyway, I decided I could safely move back to Aperture. And move I did, which was amazing because Aperture is very speedy on that iMac, I found myself tagging and naming and describing and sorting, until I stopped, which was cool, I guess.

Organizing photos is a difficult thing, and I'm currently not sure what exactly I am going to do in the future, with that. I'm currently in a class called PHO382, where one of the first things we're learning is all about managing images using Adobe Bridge CS3. At this point I haven't changed from Aperture, but in the next few weeks, I am going to try to decide whether or not I want to use Bridge or Aperture for my photos. This will be a permanent decision, and as I now have almost thirteen thousand images, it's a pretty important one. I'll keep the blog posted, so definitely consider this to be "part one, of an unknown number" in a series of "Cory talks about how he manages his images."