Archive for the ‘Workflow’ Category

Digital Photography & Workflow Thoughts – Part 4

Wednesday, April 9th, 2008

I was reminded on one of my own rules to live by when it comes to principles of use of a digital camera when I put my Olympus C730UZ into the hands of my 9 year old, so while it was fresh in my mind I figured I’d relay some observations and opinions about some points to ponder.

DSLR

1. Spend plenty on large denominations of storage media whether CF, SD, MS or xD. Read on for the reasons. A corollary to that is buy plenty of rechargeable batteries. If your camera uses a proprietary battery buy at least a second one and keep it charged/rotated.

2. Always shoot in the highest quality/resolution JPEG possible (native resolution, not interpolated as some cameras have, that’s a farce), or RAW if you have a DSLR and will be using an advanced workflow that handles RAW well (Aperture, Lightroom, Photoshop, or asset management.)
Because… You never know how timeless, unique or otherwise valuable the images that you (or your family) capture may be. You can always throw them away after the shoot if you determine otherwise, which is a parallel to point #3. If the only purpose for your images will be 4X6 prints, maybe you can ignore that point… Maybe.

3. SHOOT! When in doubt, shoot! The only real soft expense involved in shooting more than less is the potential time it may take to wade through the images after the shoot. The main hardware expense involved in this philosophy is a one-time investment in larger media than you maybe would buy if you were far more conservative (…and hard drive space.) For just around the house use, not factoring in trips or remote events, you can probably do fine on 256MB. But the second you walk out that door, the thing you have to realize is, you can’t go to the corner gas station and buy a roll of “film” (but you can go to WalMart and buy more media :) , so you have to plan ahead and make sure you’ll have enough media to capture the event or trip. Which leads to point #4.

CF Media

4. Keep your media cleared off. Don’t leave images on your card for months or even weeks. This does 2 things; helps you properly file or tag your images when you import them because the event is only a few days or a week old and you’re less likely to look at an image and have no clue what it is. The other thing it does is help you get the most mileage possible out of the media you do own because you will most likely have all the space available when you go to that event.

5. Backup your images on CD and some other form of live media i.e. a secondary and/or dedicated hard drive (besides wherever you have your primary library stored) or website or something, CDs are not reliable as the sole backup of your life images – do not trust them. They may make a fair off-site backup, which is another strategy to seriously consider – storing at least CDs of your library at a family members house. With the cost of media, it’s very affordable to (and inexcusable to not:) have off-site backups, which means unless your entire town is struck by a natural disaster, you should have something to fall back on if a major catastrophe befalls your dwelling.

6. Keep the time and date set correctly on your camera. Metadata is only good if it’s accurate. When is as important to me as what and where. If you are using rechargeable AA’s this is a real factor to stay on top of. If I don’t use my C730UZ within 7-10 days, those NiMH batts are prone to running dead on me and then my clock is reset and I’ve added another 50 images with the date of 01/01/00 and time of 12:00 am.

Audio Batch Processing With Amadeus Pro

Thursday, March 20th, 2008

I was on the warpath today for batch processing options, as I have been many times before. Amadeus Pro ($40) is not an app that I remember getting a hit on before when doing these searches, but I hit it today. I already had Amadeus Pro in my toolbelt, thanks to Geoff Hankerson, so I thought I’d check out these features (honestly since I have Peak I just didn’t do much exploring to start with.) As I mentioned in this post, I have a workflow I follow to generate the two different quality Mp3 files for my churches sermon downloads. I’ve been looking for a way to cut Peak out of the picture, just for the sake of doing it. Today I think I hit on another option, all things being equal. I discovered the batch processing options in Amadeus Pro. Here are some screen shots of the setup I used, the -a arg in the LAME window forces mono (even though my source files are mono I had to do this to get Amadeus to recognize and output as such, there is no option in the main encoder section for number of channels.) This also means that the bitrate selection appears to be of the output file, after channel conversion, whereas in my example with iTunes, all bitrates are stated as stereo, you just do the math to pick the one for the desired mono bitrate. Translation; I wanted 24k mono, so rather than setting it to 48k (and divide by 2) like I would in iTunes, I set it to 24k.

Batch processing in Amadeus

Encoding options showing the LAME command line args.

Batch processing in Amadeus

Adding an AudioUnits plugin to the action list, my parametric EQ setup as a high pass.

Batch processing in Amadeus

The parameters in the Parametric EQ.

There are a ton of things you can do in batch mode. After I researched the command line args for LAME I added the -a for mono conversion so I didn’t have to do it as a stereo to mono conversion though you can do that as an action item too. I also experimented with normalizing, there are a couple options there including RMS normalize and fixed percentage (or dB) normalize. You can retain the input file format, however if you want to change the bitrate of a source MP3 file, you have to specify MP3 as the output format and set your encoder options there as shown. There are more expensive options ($70) as well for the hardcore production user, unfortunately the demo does not allow batch processing so I couldn’t “let the machines speak” for themselves. Comparing it to my Peak & iTunes workflow it took 1:22 to process my test file – open in Peak, apply Parametric EQ (as low cut), export as AIFF, re-encode with iTunes. Using Amadeus Pro it took 2:38 for the same source file and the same operations. This is on the same MDD 2 X 1.25GHz G4, 10.4.11, 1.75GB RAM machine. Based on sheer speed, Amadeus was not a runaway winner. But for a large group of files and a persons sanity (or schedule), Amadeus Pro is a viable option. Granted this is an extremely narrow test (I didn’t set out to do a review, just to find a better mousetrap), other functions may be faster, and if there were more gyrations to be done that had to be done serially in Peak I wonder if Amadeus wouldn’t show a gain there as well. Tests were done on the latest version 1.2.1. Bottom line; if you’re on a budget and need to do production-like processes with audio files, Amadeus Pro has a lot to offer, especially for the money.
Some additional how-to pages on Amadeus.

Of Audio Encoders and Bits

Thursday, March 20th, 2008

LameBrain has been my MP3 encoder of choice. Today I discovered Max, yet another audio encoder, but more than that a batch converter and CD ripper. It’s free, like LameBrain, but has multiple encoders including Ogg, FLAC, WAV and many others. It allows you to queue up multiple encoding options for a group of files – which is great for production type workflows where you need multiple versions of a file, though I haven’t yet discovered a way to do multiple variants of the same encoder type i.e. two different bitrate MP3 files in the same batch (it overwrites the previous version with the last version.) It can do tagging, add the output files to your iTunes library, and embed album artwork. I found it via Google for batch encoding, and that it does, like LameBrain. I did a quick speed comparison, only one file, one format and came up with LameBrain in the lead with 29 seconds vs. 34 seconds for a 2:31 stereo AIFF to 192k high quality MP3 (on a MDD dual 1.25, 10.4.11, 1.75GB RAM.) And on the same machine encoding to AAC (m4a) iTunes 7.6.1 bested it by 2 seconds on the same source track, 17 secs vs. 15 secs but this was with Max set to highest quality for AAC where iTunes gives you no choices. In Max at lowest quality AAC 128k it managed it in 8 seconds, yet for some reason iTunes says the same for all three versions – “Low Complexity”, can somebody show me a way to do high complexity?! And it’s not all about speed, there are some nice batch processing features in here for the production-minded, for free!

(Some) Church Sound System Essentials Part 2

Monday, March 10th, 2008

Topics for this post include Subgroups and AUX busses on mixing consoles. Subgroups can really simplify managing the mix, especially if your services are very dynamic. AUX busses are a necessity as well if you are running your monitor mixes from the same console as the FOH, and I will also elaborate on how I use AUX busses for my record mix.

Current Version of SR32.4

Subgroups are smaller (sub – below a full mix) mixes within the main mix generally. Here’s how I use mine (on a Mackie SR32.4) and why: I assign my vocal mics (for singing) to subgroup 1 by first depressing the button on each vocal mic channel labeled 1-2, then turning the pan control to the left which narrows the scope of the signal down to subgroup 1. I assign my two speech mics to subgroup 2 by again depressing the 1-2 button and turning the pan control all the way to the right. I assign my instruments to subgroup 3 by depressing the 3-4 button and panning all the way left, and lastly I assign my six drum mics to subgroup 4 by depressing the 3-4 button and panning to the right. What this allows me to do is run most of the service with 5 or 6 fingers. Once I have established the balance of the vocal mics (by pressing the solo button on the Subgroup 1 master channel strip) I can adjust vocals as a whole with a single fader. Same with my instruments on subgroup 3, the speech mics (for speaking, a wireless Shure LX series handheld with SM87 head, and an old AT W series with 831c lav), and the drums on subgroup 4. Because of the way I have my record mix setup (or should I say I setup my record mix this way because) I can tweak the speech mic level going to the record mix by adjusting the channel fader for that mic, and while watching the level meters on the PMD570 recorder simultaneously trim subgroup 2 to maintain the appropriate level at FOH. If the voice (person) leading a given song changes I can always trim up that channel’s mic to bring it out in the mix, and I may pull back subgroup 2 as well, depending on what kind of level we’re already at and if the other vocalists will be coming in at all. But you get the general idea: make your fine mix adjustments with the individual channels (by using the solo button on the associated subgroup master channel strip), then make the coarse adjustments with the subgroup. And again, note that this allows my record mix through the AUX busses to work out the way I want which I’ll explain. One thing that I know generates confusion about AUX busses is the whole “pre-fade” and “post-fade” thing. What this means is that the signal feed to a given channel’s AUX 1 control (being pre-fade, for instance) is pulled from the channel before the channel fader. Which means what? You can jack the channel fader around all you want and the level of that channel’s signal going into the AUX 1 mix (presumably a monitor mix) will not change. Which is how we want it 99% of the time; we don’t want to mess up the person’s monitor mix when we make a change to the FOH mix. Post-fade is the opposite, the feed to that channel’s AUX buss 3-6 (on the Mackie, and 3-4 is switchable) comes after the channel fader. Which now means that it doesn’t matter how high you hack the AUX 3-6 send on that channel, if the fader is all the way down, the most you’re going to get is maybe a smidge of crosstalk. Post-fade sends (tech speak for AUX buss) are used for effects such as reverb and delay, and also for record mixes (at least in my setup.) My theory on this is that if I need to trim a vocal channel or the speech mic for the house, then I would also want to trim it for the record. The trick is getting the AUX level set for each channel so that that relationship works for both mixes within tolerance. But that’s also the beauty of it – I can setup a different mix for recording than I use for live, which means I can use ambiance mics for the record and just not assign them to the FOH mix. And I feed the PMD570 into the tape in on the console so that I can monitor the record mix from the console as well – including the processing I’m doing between the console and the recorder, a Behringer Ultramizer (which I wouldn’t recommend to anyone.) It was a good idea in theory, but the hard compression that this unit applies means all it’s good for is a fancy limiter. Being 2 bands it does allow you to reduce some of the brutality by setting the crossover point just high enough that thumps and bumps and heavy low end don’t bring the entire mix to its knees. And why am I doing all of this? So that when I get home with the flash card I can have a good solid recording that only requires some simple edits in Fission, final MP3 encode and it’s ready to upload. See what you think of the results, our sermon downloads are here and here. Low bitrate versions are encoded with iTunes using this workflow. So, back on the main highway here, a very general guide is that you use pre-fade AUX busses for monitor mixes and post-fade busses for effects (but not processing devices such as compressors since in general they’re meant to be inline devices, not mixed in in a parallel fashion (as you typically would with reverb or delay), and to feed recording devices and/or even distributed sound speakers in the nursery or bathrooms. Our distributed feed is tapped off the output of the Ultramizer, which is feed by AUX 5 and 6. Which brings me to the last thing I want to cover, using a pair of AUX busses to generate a stereo mix for your recording device. I’d love to run a multitrack recording of our services, at least in theory, but that’s not a real need now and just another way to burn up 8 more hours of my precious time. So, for a time I was using AUX 5 and 6 for Left and Right channels, respectively, to generate a stereo mix for recording. What you do to “pan” a voice or an instrument is adjust the AUX 5 and 6 controls differently, for instance; to pan hard left you only turn up the AUX 5 control for this channel, and leave AUX 6 all the way down (and then feed AUX 5 to the left channel of your recorder, and AUX 6 to the right.) To pan in the middle just adjust 5 and 6 to be the same. And for somewhere in-between adjust one AUX slightly higher than the other. That’s the down and dirty way to pan. When we regularly had 2 guitarists playing it really added some nice width to the soundstage of the recording to pan each one fairly hard to one side and the other, and of course panning the cymbal mics and toms, and the vocals.

Working With MPEG2 (.MOD) Files

Sunday, February 10th, 2008

So you’ve got one of those hard disk based camcorders and you want to do something with the .MOD files the thing generates. They’re MPEG2 files, and you have to say the magic word to do anything with them. This free app which is a wrapper for this MPEG2 codec will get you home, on the Mac. It will allow you to do all sorts of magic with MPEG files, not just MPEG2.

MP3 Reunion – AppleScript to Join MP3 files

Wednesday, January 30th, 2008

I know I just blogged about how cool Fission by RogueAmoeba was, and the purpose being to split MP3 (and other audio) files. But… I found myself still needing to re-join some of them later on in rare cases – but after they were already re-encoded and potentially edited. So, a few minutes on Google and I had found a free option using the “cat” UNIX command that I figured I could wrap an AppleScript around to make even friendlier. The result is “MP3 Reunion”, a “plain vanilla” AppleScript that has been tested on OS X 10.3 and 10.4, so it should work right out of the gate for you. This script allows you to drag and drop multiple MP3 files onto it and it will use the cat shell command to concatenate them together, in the order you specify via a simple list dialog. You are prompted to select the sequence one file at a time, as you select an item, on the next dialog that file will no longer be listed making it easier to keep track of where you are in the sequence. This allows you to specify non-incremental sequences. The (extremely fast) result is a concatenated file named “New.mp3″ in the same root location as the source files (well, the first one in the file list that the script builds.) At this time it is mainly intended for joining/re-joining MP3’s files, it does not work with .M4A (AAC) files. It will even join files of differing bitrates… not sure if that’s a feature or not. I also found this shareware app that does the same thing (and more.)

Digital Photography & Workflow Thoughts – Part 3

Thursday, January 24th, 2008

My goal in this post it to highlight what I think is an oversight by most digital camera manufacturers, except Olympus. And then to offer a free tool that may be helpful for making the most of your images for the sake of a more intuitive workflow. I also want to highlight a piece of software that I use in my workflow that really streamlines the task of previewing and rejecting bad images.

UPDATE
So, I live under a rock right? It was brought to my attention that Adobe Photoshop Elements does a bunch of whiz-bang stuff like this and more and will soon be available for both platforms in version 6. I don’t live under a rock, but since I already have a working solution I haven’t been on the lookout for other solutions, especially for a fee. If I had the $$$ to throw at it I would likely purchase iView MediaPro.
END UPDATE

So here’s the rub: if you don’t buy into using the camera manufacturers workflow, meaning, you don’t use their software to get the images off the camera but instead use either your own filing system or iPhoto or Aperture on the Mac or something like iView MediaPro (now owned by Microsoft and named “Microsoft Expression Media”), in a short amount of time you end up with 50 files named “IMG_001.JPG”. A completely useless file name, no idea what (or more important to me is when) it was, and it’s only a matter of time before you overwrite one of them with a different image named the same thing. However, my first digi-cam was an Olympus C-2020Z. Olympus is the exception to this naming debacle, and IMO they get it. They use a file naming convention that tells you the date the photo was taken. Right off the bat you have meaningful data just in the file name, and secondly you have far fewer opportunities for file name collision – though I have had it happen, which is the reason for a feature of the tool I’m going to offer here for free. It’s an AppleScript which runs under OS X 10.3 and 10.4, and may run under 10.2 as well. It does require this free OSAX (think of it as a Plug-in for AppleScript), but can be wired to not need it without a marked reduction in functionality. Olympus’ file naming works like this: P5171289.jpg would tell me it was taken in May (second digit, which uses 1-9 and A,B,C for the 12 months) on the 17th (characters 3 and 4.) I am at a loss for why they wasted one character on a “P”, so it’s a photo… like the .jpg extension didn’t hint at that already, whatever. And then 4 digits that rollover after varying points, depending on the camera (1289 in this example.) I think the C-2020Z rolls over at 1600 or something like that, my C8080 goes higher I think. First I set out to add the year as a prefix to all file names to virtually guarantee I wouldn’t have a file name collision. So P5171289.JPG becomes 07_P5171289.JPG since it was taken in 2007. Secondly, I started working with other cameras that weren’t Olympus’ and decided that prefixes such as IMG_, _MG_, IM000, IM00, IM0, DSCF_, DSCN_, DSCF, DSCN, CRW_ were an insult to me as a user and then added the ability for the script to re-format all those names into the Olympus format, minus the “P”. This does allow me to see at a glance which photos were taken on my Canon vs. my Olympus’, but it was just the idea of a letter that meant nothing to me so I left it off. So _MG_0087.JPG becomes 07_5170087.JPG assuming it was taken on the same day as our previous example.

How it works: Copy your photos onto your hard drive – and I recommend using a media reader, then drag and drop them onto the script. You will be prompted with a dialog that allows you to specify what you want done. I made the default to just add the year and conform names to the Olympus format by just hitting Enter on this dialog.


File Renamer

If you select “Prefix” it will re-format to the Olympus format, no year, and then prefix that with whatever you enter in the dialog and an underscore. If you click “Both” you get prefix _ year _ file name.extension. This script will work on JPEG, TIFF or RAW formats, it retains whatever the extension was in the original file name.

This does bring up a caveat that all digital camera users should be paying attention to anyway: make sure you keep your clock set correctly on the camera. Otherwise you’ll end up with a bunch of files that start with 00_101 – 00 for the year 2000, 01 for January and 01 for the 1st, at least that’s how my Olympus’ behave. Something like this could be written in .NET for Windows if you know anyone that programs in .NET or good old fashioned VB Script.


rule

Another vital part of my image workflow is PhotoReviewer by Stick Software. I am still using v1.4 for it’s straight-forwardness and sheer speed (MDD G4), but the current version is 2.1. Here are the controls in v1.4:

PhotoReviewer v1.4

You can use it for numerous things including making copies of specific images based on review, doing a scan through new photos off of your camera (the main purpose) to quickly delete the duds. I did experience a known bug under OS X 10.3 with a memory leak over time, which requires a reboot to purge. It behaves better in 10.4 though I don’t think it’s perfect. I highly recommend it especially for the price. It’s worth a hundred times that for the hard drive space it will save you that would otherwise be consumed by unusable or indifferent photos.

Speech Processing with EQ, Multiband Compression

Tuesday, January 8th, 2008

Here’s another article of mine on using Macintosh Audio-Units based processing on speech to give the track some guts.

Digital Photography & Workflow Thoughts – Part 2

Saturday, January 5th, 2008

Here’s a tidbit related to resolution and pixels and what it all means. A mistake that can be made in Photoshop when resizing images is, if you’re just looking to change the resolution from 72 dpi to 300 dpi, then here’s how it should be done. This does not actually add more data, it just re-arranges the sizing information, which allows you to directly see what size your image is (height and width) at 300 dpi resolution, making it simpler to tell what you’re going to have in the end, if you need a 300 dpi image. For offset print (i.e. use in QuarkXPress or InDesign) you should be re-sizing your images to the desired print resolution anyway, and then scaling them to the correct print dimensions (by checking the “resample Image” option) even though RIP performance is light-years ahead of what it was in the early days of PostScript, this is still best practice. So here are some screen shots in Photoshop showing what happens when you use the proper method to re-order an images resolution, note the chain linking the inch dimensions to the resolution – and that the pixel dimensions are locked – they won’t be changing. This is done by un-checking “Resample Image”.

Our first example is at 72 as it came off the camera:

72 DPI in Photoshop

Now, changing the same image to 300 dpi:

300 DPI

Lastly, just to illustrate that all we’re doing is defining the number of pixels in an inch – converting from pixel dimensions into inches (in this case) – 1 dpi:

1 DPI

See what happens? The inch dimensions match the pixel dimensions, because, we’ve told it that there’s 1 pixel in 1 inch.
Another thought along this line, when shooting in RAW mode, and using Adobe’s RAW Import (or any other camera RAW software for that matter) there’s an area where you can define the resolution, that does not magically create more pixels, it just does the very thing I’m illustrating in these screen shots – re-ordering the dimension information. When done correctly, this operation is absolutely instantaneous. You’ve done it wrong – typically fabricating pixels, if you see a progress bar or it takes a few seconds. To change resolution, then scale an image you will use this dialog twice, the first time with “resample image” turned off, the second time with it turned on.

Digital Photography & Workflow Thoughts – Part 1

Saturday, January 5th, 2008

In just the 2 hours I’ve been writing posts for this blog I’m convinced Blogging is an out-growth of the spreading of A.D.D. in our world. It’s soooo easy to just throw some thoughts and images up on the web (which is the whole point, duh…) But, given that fact, here are some really quick thoughts on digital photography and the associated workflow, which to me is the crux of the whole topic.

If you are only planning to make basic 4X6 prints and the occasional 8X10 – or use them on a website, anything over 3 megapixels is enough for you – but hang on for some heavy math to help you figure that out for yourself ;~)

If you want to be able to submit photos for a school yearbook or anything involving traditional offset lithography (a.k.a. four color printing on a real printing press) then you’ll need at the very least 3 megapixels, and if you want to be able to print these (in said yearbook) larger than 4X6 then I’d recommend 6 megapixels or greater, and those figures don’t leave you with much room for cropping. Here’s how the math works to figure this out: For traditional screening (a.k.a. AM – the most common, still) you need twice the resolution of the line screen your printer (as in a printing company, not your desktop inkjet) is printing at. For the sake of discussion the most common is 133 lpi, so figure 300 dpi (literally; 2 X 133 = 266 dpi), at the print size. So, if you want to print a 4X6 image at 300 dpi that’s 4 X 300 for the width, and 6 X 300 for the height, in pixels. That translates into meaning you need 1200 X 1800 pixels to print said image at 133 lpi in offset print (up to 150 for best quality, 175 would be allowable.) In megapixels that’s (1200 X 1800 / 1,000,000 = 2.16) – 2.11. So, back to that 8X10 print. I’ve gotten varying answers from photo labs, but from experience I’ve gotten good results from both the Fuji Frontier systems (Walgreens, Wal-Mart and Sams) and Kodak systems with as low as 150 dpi. Translate that; 4X6 would have to be at least 600 X 900 pixels (4 X 150, 6 X 150.) Understand that regardless of what resolution your photo editing app (or camera software) is set for, if the image is 600 X 900 pixels, it’s good to go. How pixel width, height and resolution (depth) relate is for another post, but all you need to really know is the actual pixel dimensions. 8X10 would require 8 X 150 = 1200, 10 X 150 = 1500 (1200 X 1500 pixels), which comes down to 2.11 megapixels, minimum. The one photo finisher in town told me basically 200 dpi, so that would mean 1600 X 2000 pixels for an 8X10, which is 3.2 megapixels. What he said was 3000 X 2000 pixels was the max on the Fuji system, and that would be for a 15X10, equaling 200 dpi.

That’s all pretty straight forward, except; Most point and shoot digi-cams shoot using a 4:3 aspect ratio, the same as standard video. So, for the typical 2.11 mpcamera, with 1600 pixels wide (that’s the 4 in 4:3), if we divide by 4, we get 400, then 400 X 3 = 1200 (which is the 3 in 4:3.) That’s the resolution of a typical 2.11 mp cam like the Olympus C-2020Z. So, back there on our calculation for an 8X10, needing 1500 pixels for the 10 part of the 8X10 (that’s 4:5 aspect ratio) that would mean there would be next to no room for cropping – you got 100 pixels to throw away on the one dimension, none on the other – and that’s only for the bare minimum, IMO, 150 dpi. Some point and shoot digi-cams offer a 3:2 aspect mode, such as the Olympus C-730UZ. That’s a 3.2 megapixel camera, so at 3:2 you get 2048 X 1360 pixels, or enough data to do 13.65 X 9 at 150 dpi. In 4:3 mode that camera yields 2048 X 1536 pixels. 3:2 is the same aspect as 35mm film, and the same aspect of a 4X6, though to be correct in page layout speak that would be a 6X4 since the first number is always the width, and the 3 in 3:2 represents the width. As always YMMV, especially with inkjet printers.

This illustrates one other point I’ll make in closing; give just a little forethought to how you compose a shot. If you know you only want it for 4X6 prints, then drive on. But, if you want to make sure it will work for multiple sizes/aspect ratios, then be sure to leave some room in both directions, in other words, don’t crop the shot to tight (like me.) It simply means this; when cropping an image shot at 4:3 aspect for use on a 4X6, you will be cropping off material on the top and bottom of the image (assuming landscape orientation in both cases.) If you shoot using 3:2 aspect, and want to use it for video at 4:3, the reverse is true – you will be cropping off the left and right of the image. These examples are assuming that you want to use the entire image right up to the edges.

Here are some visual aids for this concept. This image was shot wide enough that it will work at almost any aspect, but note the last example where, if shot at 3:2, and you want an 8X10 out of it, how much width you lose, the source image is always 600 pixels wide before “cropping.”

Original 4:3 Image

Here’s the original 4:3 image (above).

Cropped for 3:2 - 4X6

Now cropped to 3:2 for a 4X6 (ghosted areas show what would be cropped.)

Cropped to 8X10

Now cropped for 8X10 (ghosted areas show what would be cropped.)

3:2 Original cropped for 8X10

Lastly, here it is shown as if it was shot at 3:2 originally, then cropped for 8X10. Hopefully this gives you some idea how these all relate to each other.

So much for the quick blurb and A.D.D..