Reuters:
Adobe profit up 21 percent on sales of design software. I’m extremely happy with my purchase of the CS3 Creative Suite. Early next year, I should be able to show you some dramatic before/afters in my personal portfolio.
For the photographically curious,
I just finished my ‘large project’, so I felt safe in trying the Lightroom 1.2 update again (for those who don’t know, the update twanged my desktop, but installed fine on my laptop). It went without a hitch. I have a feeling that one of my other programs’ automatic update features decided to install at the same time I was updating LR. Lesson learned. This install seemed terribly anticlimactic.
Adobe CS3 update, 2:
This would have been posted sooner, but I’ve been busy. Working and learning. I should explain. Adobe gives you a ‘free gift’ with a Creative Suite purchase. I chose the discount on the “Classroom in a Book” series, figuring it would be the most cost-effective of gifts (as long as I order all the books I want at the same time; it’s a one-time only discount). In the meantime, I went ahead and signed up with Lynda.com (video instruction) on the monthly plan, to get myself back in the saddle as swiftly as possible. I’m even sticking out the most basic of software function explanations (something I disdain), but such patience is paying off. I’ll rate Lynda.com another time.
Normally I comp websites in Photoshop. Taking a cue from the CS materials, I decided to try Fireworks for a recent set of websites. FW has turned into a very nice mix of Illustrator (vector) and Photoshop (bitmap) features, with the already-there web-centric capabilities. To refresh your memory, I left FW at version 1.0, and I’m surprised to find much of my knowledge is still applicable. In crossing from one Adobe program to another, though, it can get confusing. Keyboard commands and the layers palette functionality, in specific. FW has always felt clunky to me ... now it feels like a turbocharged Studebaker pickup truck. Lotsa power, needs aesthetics. I’m confident Adobe will introduce more of their trademark elegance to the interface in the next couple of upgrades.
I’m happy to say that in actual use, FW saved me time. Those wonderful vector features, the ease of editing gradients, interop, interop, interop. Getting vector text and artwork from my partner, and being able to maintain layers, edit colors, edit text ... great. I imported complex AI hand-drawn icons with layers, changed colors of elements, resized, grouped, named, layered, done. So nice. Each time I didn’t have to dump out of FW to do edits made me happier and happier. I came up with some dynamite designs much faster than normal, with even more current design sensibility. Most importantly - it made my clients ecstatic. You still want PS and AI for truly discursive creation - but as a gatherer of editable graphic skeins for web output, FW is pretty darned nice.
The next challenge is taking the FW comps to CMS (likely my preferred Expression Engine) and CSS. FW outputs as CSS, but I believe it’s all left-just, absolute positioning (basing on my 1.0 knowledge). I hope to find a simple way to fluidize and/or center elements. Expression Engine will let me create static template files, which I can then set up to access from Dreamweaver. I’m looking at standardizing on this scenario ... FW > DW > EE. In theory, this could make changes very swift. I’ve been busy setting up some of my favorite CSS and XHTML boilerplates, EE code snippets in DW in anticipation.
One request to Adobe for a FW update: “Save Page as PDF” in the FW pulldown menu, at print resolution for quick and easy printing of good-looking comps. I like to present color comps on boards to clients, so they can chew over design elements without needing a ‘net hookup. New Mexico still doesn’t have the fastest of broadband, and wifi cafes can be jammed and slow. I know web graphics are 72dpi, and print resolutions have nothing to do with what the client will get on the web ... however, in my experience they perceive print quality on the ‘net, nevertheless. Showing them printed 72dpi type is always asking for trouble (“Is it really going to look that mushy?”). I thought saving as Illustrator format might allow me to cheat to high rez, but some of the graphics didn’t translate well. So ... “Please, sir, can I have some PDF?”
nerd.of.steel
has a nifty method of using Fireworks to create a CSS grid overlay for positioning.
CS3 update.
I did a bit of HDR and 16-bit work in Photoshop today. Shot a home at 10:30, finished at 12 (staged furniture, posed flowers, etc. etc.). Started processing files for HDR (window details in sunlight) at 2, done with the masking, general processing and sharpening stages at 3:30. It usually takes me much longer. HDR pops right up, processes much faster than in CS2. The 16-bit files opened almost as quickly as 8-bits. The Lens Distortion filter has no startup lag anymore. Liquify filter also starts immediately. The speed of CS3 continues to delight me.
Upgrading to Adobe Creative Suite 3, Master Collection.
I have used Illustrator, Flash, Dreamweaver, Photoshop, Premiere, Acrobat and others at different stages of my career, but their prices of late had sent me searching into the world of alternatives ... open-source and shareware apps ... while letting my commercial versions age. I dare say there’s a certain cachet to brag that one uses open-source equivalents, as a sort of badge of gear-headed expertise. I’ve tried, as others have, to replace the functionality of Photoshop with Gimp, Illustrator with Inkscape, Flash with SwishMax, Acrobat with PrimoPDF, and other lower-entry-cost software for others. Little interoperability, reduced feature sets, differing interfaces, inconvenient file formats, and more ended up eating away mountains of time ... and for a small business, time is money. Your ‘free’ time disappears in managing all the little incompatibilities, all the ‘special requirements’. Debugging recent installs of certain open source software has wasted immense amounts of my spare time; charged at my hourly rate these hours represent a pile of cash bigger than that which full list price versions of comparable commercial software would require for purchase.
No more. I’ve come to the hardened conclusion that this ‘cachet’ of alternative software is ridiculous in a for-profit business, especially in this economy. Hobbyists, fine. Business, no. Purchasing this Creative Suite, for me, is an investment in saving money and time, while improving the quality of my output. I might still use one of the open-source or shareware alternatives I own for a specific effect ... but I will not, in the foreseeable future, ever again base any business upon them.
So let’s get down to brass tacks on the Adobe Creative Suite 3 Master Collection. I had been hankering for the MC, because my skillsets bridge print, web, video, audio, 3D and more. Obviously, getting the Master Collection puts me on track to a lower-cost upgrade each version change, rather than chasing down individual package upgrades that would result in higher costs over time. Choosing the suite gives me the interoperability and consistency of interface that will free up headspace for creativity. I can set the toolbars across multiple programs to be identical, color palettes sit in the same locations, etc. etc. I can drop the ‘Trivial Pursuit’ (remember dozens-of-different-interfaces and their vagaries) mindset the alternatives imposed.
My experience with the major packages in MC:
1. Illustrator ... Highly skilled with Version 9.0 on Macintosh.
2. Photoshop ... Highly skilled with CS2.
3. Flash ... Middlingly skilled with Version 5. I knew Macromedia Director very well, the translation across has been a little rocky at times; I still fight my Director reflexes. I intend to concentrate on updating my Actionscript chops to current accepted levels of expertise.
4. InDesign ... I knew Quark Xpress 5 very well on Mac, churning out production magazines. I’ll have to change over. My Pagemaker to Quark transition didn’t take long, I don’t expect this one to take long either. I have a skilled individual in-house to help me.
5. Premiere Pro ... Used Premiere Standard on my year-old VAIO install, created a couple of pieces. Most of my experience is on physical offline and online editing machines. Learning to be done. Additionally, my VAIO needs a little debugging over video inputs (they apparently only work with Media Center open, and I don’t use or start the Media Center services), so getting video footage in is going to be a challenge for a bit.
6. After Effects ... I used Version 1.0 extensively for a while. The interface looks a little familiar, but much learning to be done.
7. Dreamweaver ... I am a skilled XHTML/CSS hand coder, and never really liked DW much. Admired the ease with which skilled DW individuals can churn out completed websites, disliked the weightiness of the generated code. I’ve built templates in previous versions, but have never used them in conjunction with Contribute. I prefer CMS output for most sites of size, through Expression Engine. Curious to see if the CSS interface has improved; it used to reek. The interop with other software intrigues me here, so I’ll give it another go. If nothing else, I’ll use it for that nifty ‘tree view’ of an entire site.
8. Fireworks ... Version 1.0 I knew well. The CS3 interface still looks familiar. Shouldn’t be a problem.
9. Soundbooth ... Never used. Audacity has been my recording environment of late.
10. Encore ... Never used.
11. Acrobat ... I’ve used Professional frequently on the Macintosh platform, CS2.
The fun in all this, is tracing out a schedule and plan for getting back to speed on the current CS3 versions. The first thing I’m going to tackle from a production perspective is a Flash/video piece for delivery via internet in the next month ... and I’m really looking forward to it. I prefer immersions with deadlines. Nothing like it for learning.
There’s one point of perceived ‘weakness’ in the Suite, where some will point up the popularity of Final Cut Pro [Mac only]. I know, it’s ostensibly the more popular package for video wonks, at least when you hit the HD video mags. I find the video edit interface paradigm is pretty standardized across platforms and software. The bread-and-butter aspects of video editing are usually obvious and easily transferred, if ever necessary. I’d rather judge the suitability to intended purposes myself, anyway. The fact that After Effects sits in this Suite is a kicker. I used to create some really edgy things in the 1.0 version, when combined with form*z/Electric Image 3D renderings, years ago. It was a bizarre little piece of software, able to do online effects without the costly equipment. I can’t wait to work in this new version, and in combination with Premiere Pro, judging its power vs. Apple’s offerings. An HDV camcorder and Blu-ray recorder is in a future hardware budget.
Well, enough of my thoughts and plans. On to the product. Most reviewers give you details on the packaging. Faugh. It’s a box. It has disks inside. You install the disks. A couple of handy pamphlets to help you get familiar with the interfaces and specifics of interoperability. It’s all very pretty, well-designed and minimal. The first install disk has a Read Me file. Be sure to read it, not just gape at the link and press “Install.”
My installs tend to be rather meticulous. Windows can be finicky, so I like to clean things up before, during, and after installs. I have recently performed disk checks and optimizations, so this is what I did to get a flawless install:
1. Backed up vital work files (in heavy production at the moment).
2. Cleaned up the registry (I’d been lazy about this.)
3. Restarted the machine.
4. De-installed Photoshop CS2, Bridge 1.0, the Sony install versions of Premiere Standard and Photoshop Elements. I retained my current version of Adobe Reader.
4. Cleaned the registry again.
5. Restarted the machine.
6. Confirmed that my previously-installed Photoshop Lightroom didn’t lose any dll’s (it didn’t), and that it was still fully functional (it was, kudos Adobe Install/Remove programmers).
7. Installed the Creative Suite [4 DVDs].
8. Restarted.
9. Rapture.
I use Rose City Software’s Registry First Aid to clean my registry, but it’s just one I found years ago and have had good luck with. YMMV; compare reviews of other registry cleaner software. I like that RFA automatically creates restore points and registry backups on each repair. I clean the registry religiously before and after software installs/deinstalls, and my Windows issues have been minimal. I will, at a later time, run defrag/optimisation to kick the loading and operating speeds up further. I’ve been fooling with Raxco PerfectDisk of late, with better results than Norton SpeedDisk or Windows built-in defrag.
The first MC program I opened was Photoshop CS3 Extended. I got two screens while trying to start up this ‘first opened’ program: one for product activation, and another for registration. Both worked as advertised. I filled them out, they processed in less than two minutes.
Now, if you’ve read here long, you know I’ve bitched and moaned about my machine (dual core Pentium D 830) being slow to load and run Photoshop CS2 and other programs. I upped the RAM, bought a new video card, optimised both 7200rpm 250 GB HDs till I was blue in the face, with middling results. PS CS2 still took a minute and a half to start, every time I loaded it ... pausing forever on loading gradients. Well, I have to tell you that PS CS3 loads faster. Much faster. First load is just under 25 seconds, subsequent loads in SIX SECONDS. In operation, it is now snappy as all get-out. I haven’t yet opened any of my 16-bit multilayer HDR creations, but I’ll let you know if the snappiness is still apparent. Zipping multilayer TIFFs is a little pokey, a little slower than CS2. Saving a TIFF with no compression [8MP output from my 20D and Lightroom runs in the neighborhood of 24 MB] doesn’t even bring up a ‘wait’ icon. It seems instantaneous.
My style of working might not be yours ... I like to run programs with lots of RAM headroom, so I tend to open and close programs rather than keeping a half-dozen open at a time (old habit from the early ‘multitasking’ Macs). I found this opening and closing speed, for an updated and obviously larger and more capable program, simply astonishing. I’m used to updates being slower than their predecessors, when installed on the same machine.
The new CS3 interface is mildly different. I find myself having to pay attention to my cursor, because I’ve gotten in the habit of knowing where my palettes are on my screen real estate. I think I’ll prefer the tall single-icon toolbar over the double, adding screen real estate until I invest in a nice Dell 24” LCD. I’m getting used to the new palette area on the right, and I believe I’ll like it better. In playing with the new Brightness/Contrast panel, I can tell you the rumored improvements are completely true. It works so much better, I gasped. The more I play with the new PS, the more I want to re-convert all my RAW photos with the improved tools. I’m not adding my third-party plug-ins back until I review all the comparable filters in CS3 for quality.
Bottom line: If you’ve been on the fence about upgrading to Photoshop CS3, I wouldn’t wait any longer. I find even these few aforementioned improvements worth the price of upgrade.
Other than Photoshop, I opened and did a little fiddling in each of the installed programs to verify that they all work properly. Not a single install-related issue.
Bodes well for the future. I have a slew of production on my to-do-today list, but I thought I’d write this up right away. I’m particularly interested in delving into the interoperabilities within this Suite, and how that will affect my time/creativity. If you’re interested in my journey, let me know ... I’ll make a separate category, and continue to do weekly updates on my impressions, learned lessons, and overall progress.
