uberfoto avatar ...such is the life of a designer & photog

Posts about my thoughts on photography and other things I find useful and want to share.

 

Internet Explorer 6 (IE6) Can Suck It.

Monday, October 19, 2009

I'm done supporting it. In fact, I don't even officially support IE7.

If you're wondering why my site looks broken or funky, update your browser.

I recommend one of the following:

Safari Firefox Chrome



Please update your browser and stop using Internet Explorer (or more commonly known as Internet Exploder) so that the web can get better. Internet Explorer is NOT the Internet. It is just ONE of many more capable Internet browsers.

Newer, faster, more standards-compliant browsers mean better, faster, and more interactive websites. Internet Explorer (IE) is holding all of us back with poor (and slow to implement) standards support. What does all this mean? It means IE it is not capable of recognizing and properly displaying website code that makes sites look and function better. New developments (HTML 5) allow interaction almost on par with your desktop applications. Where Safari, Chrome, and Firefox support most or all of these new programming languages, IE does not. If you are using IE, you could be missing out on valuable internet tools and the websites you view are likely not rendering as intended (they look bad!).

Join the cause. Do your part to speed up web development. Use a more capable browser.

Labels: , , , ,

Aperture 2: Max Supported File Size

Ok, this is ridiculous. I found out from an Apple support agent that Aperture currently has a supported file size limit of 250MB.

This is why I have been getting the maroon, "Unsupported Image Format" error all the time. For now the workaround I have come up with is to restart Aperture and switch to view Previews ONLY.

I guess the way it works is, Aperture only uses the video card RAM to load images into for viewing/editing. Quitting Aperture dumps the memory and switching to "Quick Preview" (P) helps prevent Aperture from filling up the video RAM so quickly. At least this way I can export the needed images and keep working.

Rant follows:

250MB. This is a joke. Most RAW files are 10-50MB each depending on MP and compression. That's not bad. However, anybody that has round-tripped a file through Photoshop knows that once you create a multi-layer PSD and lose the camera maker's compression on that RAW format, a 12MP file starts around 150MB. Now add a few adjustment layers, sharpening and some touch up and you're about 220-300MB. Some of my files hover around 1GB+ and the panoramas are almost always 1GB+. ALL of my Hassy H3D stuff is north of 100MB before I even open them. Forget about medium and large format transparency scans. They're out of Aperture's league (and honestly, I am probably expecting too much with the LF transparency scans).

I want to ask the guys at Aperture this:

How, with almost ANY 35mm SLR file that has been round-tripped through Photoshop being over the 250MB cap, am I supposed to use Aperture for my "Professional" photography workflow?


Currently running the most up-to-date (at this time) Aperture 2.1.4, Photoshop 11.0.1, Nikon D3 RAW workflow.


Everybody needs to submit feedback to the Aperture team to let them know, this MUST change! Do your duty.




Oh, and I updated my website again. It was sorely needed IMO. I also fiiiinally got around to editing my blog template to match the site. Feedback (good and bad) always welcome. See you next time.

Labels: , , ,