Cooeee, Its me, I’m back
Well almost. I’m shooting again and, while it’s great to be behind the camera again it, makes it that much harder to remain dedicated to the day job. The software is still not out. The beta testers love it but are finding little things for me to fix. The website is nearly done, but I have about 190 pages of documentation to write and about 20 video tutorials to shoot. Its not as much fun as shooting naked women. Actually, it’s not as much fun as shooting the dog! But it has to be done if we are going to eat.
Anyway, Last week I shot the lovely Lisa “Lil Mummy”. Great session and I took about 130 pictures which I’ve whittled down to 50 or so that make the grade. Tried some experimental stuff (for me) and they came out well. You’ll see them in the blog over the coming weeks.
Now when processing the images I previously used Photoshop CS2 and have a bunch of javascripts and actions tied together and put into droplets to create the 3 images sizes I use for the web and blog and also add the frames and labels to the web sized images. This worked really well … until I upgraded to CS3.
The first time I ran the script on CS3 it started its resize operation and the memory usage immediately went to 2GB. That’s right, it maxed out. Everything I tried maxed it out. Eventually I broke out the script debugger and started to go through the lines one at a time until I found the problem.
I normally resize my images for the web to 600 pixels max for height and width. In order to maintain the correct aspect ratio the script calculates the current aspect ratio then sizes the dimensions appropriately to maintain the ratio in the resulting image. Unfortunately the default setup in CS3 was inches not pixels, That’s right, I was trying to resize my images to 600 inches wide at 300 dpi, that’s a 50 foot wide picture. No wonder it gobbled all the memory. Knowing what the problem was made the fix easy. I changed the ruler scale to pixels rather than inches and off went the scripts. Problem solved. Hurrah.
And this is what I have produce, the first of the finished images shot with Lisa and put through the CS3 processing. I hope you like it.
It’s a week and a half to my next shoot, just time to finish the rest of the photos from last weeks shoot and get some day job work done.
Anyway, Last week I shot the lovely Lisa “Lil Mummy”. Great session and I took about 130 pictures which I’ve whittled down to 50 or so that make the grade. Tried some experimental stuff (for me) and they came out well. You’ll see them in the blog over the coming weeks.
Now when processing the images I previously used Photoshop CS2 and have a bunch of javascripts and actions tied together and put into droplets to create the 3 images sizes I use for the web and blog and also add the frames and labels to the web sized images. This worked really well … until I upgraded to CS3.
The first time I ran the script on CS3 it started its resize operation and the memory usage immediately went to 2GB. That’s right, it maxed out. Everything I tried maxed it out. Eventually I broke out the script debugger and started to go through the lines one at a time until I found the problem.
I normally resize my images for the web to 600 pixels max for height and width. In order to maintain the correct aspect ratio the script calculates the current aspect ratio then sizes the dimensions appropriately to maintain the ratio in the resulting image. Unfortunately the default setup in CS3 was inches not pixels, That’s right, I was trying to resize my images to 600 inches wide at 300 dpi, that’s a 50 foot wide picture. No wonder it gobbled all the memory. Knowing what the problem was made the fix easy. I changed the ruler scale to pixels rather than inches and off went the scripts. Problem solved. Hurrah.
And this is what I have produce, the first of the finished images shot with Lisa and put through the CS3 processing. I hope you like it.
It’s a week and a half to my next shoot, just time to finish the rest of the photos from last weeks shoot and get some day job work done.
posted by Richard at 9:34 AM
0 comments
links to this post
