Fireworks Auto-Kern bug: Vista issues

Adobe Fire­works is a pretty bril­liant pro­gram for rapidly devel­op­ing web lay­outs in a kind of best-of-both-worlds way that enjoys the ben­e­fits of both vec­tor and bitmap design, with­out all the frus­tra­tions that come along with smart objects. Its text han­dling is also superb, offer­ing a whole lot of cus­tomis­able set­tings that are very use­ful for mock­ing up web designs, not read­ily avail­able in either Pho­to­shop or Illustrator.

How­ever, it is not with­out its faults. On Vista, when typ­ing text in Fire­works things can occa­sion­ally go very, very wrong. The solu­tion at least ini­tially is to turn off the “Auto Kern” option in the Prop­er­ties dia­log — but this removes one of the big ben­e­fits of using Fire­works in the first place!

There are other options. The prob­lem will go away (some­times) when the file is closed and Fire­works is restarted — this is hit and miss. More per­ma­nently, dis­abling Vista’s fancy-pants Aero theme (the thing that makes all win­dow bor­ders trans­par­ent, gives that snazzy Start + Tab effect, etc.) will ensure you have a glitch-free Fire­works font experience.

The real solu­tion? Sneak into Adobe HQ and write a patch to fix the stu­pid thing!

Some numbers from Vista’s crash reporting

Win­dows Vista ships with a delight­ful tool by the aid of which it reg­u­larly digs itself a grave. Here are some find­ings after three months of use, sorted by num­ber of crashes.

Microsoft Inter­net Explorer 92
Win­dows Prob­lem Reporting 52
Appli­ca­tion Launcher 17
Win­dows Explorer 12
Adobe Pho­to­shop CS3 8
Microsoft Out­look 6
Microsoft Zune 4
Mobile Net­work­ing Wizard 4
Skype 4
Win­dows Media Player 4
Adobe Bridge CS3 3
Adobe Illus­tra­tor CS3 3
Adobe Dreamweaver 8 3
Fire­fox 3
Sync man­ager 3
Win­dows Task Manager 3
Adobe Pre­miere Pro CS3 2
Eclipse 2
Gephex 2
Win­dows Live Messenger 2
Adobe OnLo­ca­tion CS3 1
Adobe Pho­to­shop CS2 1
Dri­ver soft­ware installation 1
Filezilla client 1
Microsoft Pow­er­point 1
VLC 1

By ven­dor, that con­sti­tutes 176 crashes/hangs/‘not-respondings’ of Microsoft soft­ware to 21 of Adobe soft­ware over the same period. Now, it feels like I’m cheat­ing the num­bers here by report­ing Win­dows Prob­lem Report­ing itself, because prob­a­bly 90% of its crashes occur when report­ing on Inter­net Explorer, but hey — these are the num­bers Microsoft’s soft­ware itself gave me, so who’s complaining?

In case you think this isn’t a fair com­par­i­son for rea­sons of time spent using var­i­ous pro­grammes, exclude Prob­lem Report­ing crashes (though you shouldn’t) and the Microsoft stat comes down to 124. That is, lots.

I can’t think of a day since own­ing this com­puter I wouldn’t have used at least one piece of Adobe soft­ware, most com­monly more. To be fair, Adobe soft­ware is more likely to do weird things (like, ya know, refus­ing to save) caus­ing me to restart the appli­ca­tion rather than let­ting it ‘crash’ per se… but Microsoft’s junk is vastly less likely to give me any sort of warn­ing before flak­ing out.

These crashes are reported over a three-month period span­ning Novem­ber 26 until Jan­u­ary 25.

Vista SP1 con­tin­ues to be eagerly awaited.

Why no, vector artwork is not universally superior for lines

I’m cook­ing up a book­let for a study camp at the minute that has a sim­ple grid-lines (ruled maths paper) back­ground and ini­tially traced it with Illus­tra­tor because it looked, err, lin­ear enough to be a fair can­di­date for such work.

The trace had to be a lit­tle eclec­tic for realism’s sake, so I didn’t just do the redraw with Ctrl + D trans­form ninja skills, but let the soft­ware trace it. Big mistake.

It was one of those things that InDe­sign got a lit­tle upset about the com­plex­ity of — which is okay — and had to import as encap­su­lated post­script instead of as native vec­tor data — which is also okay. Trou­ble was, it wasn’t just bor­der­line too-complex, it was stu­pidly over the edge. I stuck it on the A-Master (which keeps me sane and the .indd file­size down) and got to work for about a week on the rest of the con­tent and so forth. As we get closer to press (I was aim­ing for today… oth­ers appar­netly have dif­fer­ent ideas) I’ve started doing the Indd->PDF shuf­fle and dis­cov­ered the absolute pain of wait­ing for it to “ren­der” (basi­cally that’s what it’s doing) the EPS onto every page as it cre­ates the PDF file.

I endured this for about two days and then finally snapped this morn­ing, went back to Pho­to­shop with the source image and processed it to make it look sim­i­lar enough before past­ing the raster scan into the A-Master in the traced thing’s place.

As if by magic, the gen­er­ated PDF size dropped from 55MB to under 4MB.

Raster images are your friend.

p.s. hope­fully I’m back here now. Am away next week with GPRS Inter­net only, then in New Zealand (with Inter­net, albeit with uncer­tainty about hav­ing a com­puter in the accom­mo­da­tion). Yes, busy as ever. On Face­book quite a lot, because sta­tus updates are more man­agable than full blog posts!

# by Josh Street on June 18th, 2007 Tags: , , , ,
| No Comments »

Firefox, straight to the front of the class

When­ever I need to find Fire­fox in task man­ager, it doesn’t ever take long. Fire­fox is the fat kid of web browsers… it’s kind of hard for it to hide. If it once were a sleek, lean fox, today it’s caught just a few too many stray chick­ens and drunk a lit­tle too much of Bean’s apple cider. It wouldn’t take any bull­doz­ers to find this fox, just a mod­er­ate sized key­board with three keys (no prizes for guess­ing the three-finger’d salute).

I haven’t had a great day with Fire­fox. Well… I spent 3 – 4 hours in meet­ings today, so I didn’t even have that much time with Fire­fox! Still man­aged to let me down twice, though.

Damn its indis­pos­able devel­op­ment tools *sobs uncontrollably*

I think I’ll switch back to Opera for all non-development Internet-related activ­ity for a while… unless any­one has any other browser rec­om­men­da­tions? I’ve seri­ously thought about IE7, but its ren­der­ing is still just a lit­tle too patchy for me to be able to live with myself as an Inter­net user.

Bleh. Let it be observed: even high-profile open source does not always lead to a good prod­uct. Its mem­ory man­age­ment is noth­ing short of repul­sive. It will reg­u­larly use more mem­ory than Pho­to­shop and Illus­tra­tor com­bined — admit­tedly, I use Pho­to­shop mostly for web pro­duc­tion and not high res­o­lu­tion print stuff (though that does hap­pen a few times a week, and it won’t often go far beyond the 350MB that Fire­fox seems to man­age fairly regularly)

I’m still using CS2, so there aren’t any mag­i­cal CS3 mem­ory man­age­ment advances that make such a claim pos­si­ble… Fire­fox just sucks :P

I’d blame Win­dows being in need of a rein­stall (it’s been run­ning since Octo­ber… more than six months with­out death :P Plus I started out not being happy with it because it’d been installed from the guy I bought the com­puter off, I just hacked it to use my CD key instead of the one he’d used to test things… so it’s never been per­fect), but really, it’s not that bad for any other appli­ca­tion. I nor­mally do a reboot once a week and things are fine… heavy duty graph­ics edit­ing, occa­sional video edit­ing, con­stant mail and occa­sional word­pro­cess­ing… and of all those things it is a web browser that can’t get it right. Per­haps I shouldn’t be so deri­sive about it see­ing as I make a liv­ing off devel­op­ing in this rel­a­tively sim­ple world… but I am.

The flip side to all of that, of course, is that I’ve been try­ing to live (more) like a nor­mal user the past few years. Essen­tially, recog­nis­ing that it’s sim­pler to buy soft­ware than write it (Word­Press, Flickr), using hackably-open tech­nolo­gies instead of truly open ones (WMA Loss­less sans DRM), and a gen­eral aban­don­ment of open source prin­ci­ples in favour of vastly improved pro­duc­tiv­ity (Pho­to­shop, Pre­miere, Office 2007, royalty-free stock).

It’s cer­tainly paid off in terms of pro­fes­sional devel­op­ment and enhanced cre­ative poten­tial… but there’s some­thing lost in not being able to hack visu­al­i­sa­tions hooked up to a web­cam together on a command-line any­more. Admit­tedly, that sort of thing only comes around half a dozen times a year! But no mat­ter, it’s all good fun. Given more friends who were into that sort of thing and some good music, I’d so live in the party house. I’ve not fig­ured out how to do the same command-line video tricks using Win­dows just yet, so next time I’ll prob­a­bly use Win­dows for visu­al­i­sa­tions (woo par­ti­cle emit­ters!) and a sep­a­rate Linux-powered lap­top (maybe?) for web­cam trick­ery. Then I’ll take web­cam stuff straight out into Win­dows cap­ture and skip my vis mixer alto­gether for once… I gotta learn to travel lighter anyway!

Illustrator workflow

I offi­cially don’t get it. Mind you I’m work­ing from a CMYK file at some bizarre res­o­lu­tion and it’s just not scal­ing prop­erly at all, so it’s prob­a­bly not entirely my fault… the usual print-web mind­set prob­lem methinks. Only this is extra frus­trat­ing coz it’s due by this evening and I’ve got a Shake­speare scene to work­shop this evening also… so I’ve basi­cally got 3 hours left to build an entire web­site. Crap.

# by Josh Street on March 29th, 2007 Tags: ,
| 1 Comment »

Adobe Production Studio. Just breathe.

Okay.

For what­ever rea­son, I wasn’t pay­ing atten­tion when I bought CS2.

I some­how failed to realise that Pro­duc­tion Stu­dio Pro has nearly all the same things (ex. DTP stuff that I don’t really have much of a use for, but it’s nice hav­ing any­way) and more (Pre­miere, After­Ef­fects) for… not a lot more money at all.

*breathes deeply*

On the plus side, Cre­ative Suite 3 is launch­ing later this month though I don’t know if that means the next ver­sion of Pre­miere just yet. So I’ll wait til that’s an option before pur­chas­ing Pro­duc­tion Stu­dio, which means I get CS3 ver­sions of the stuff I actu­ally use — Pho­to­shop & Illus­tra­tor — and still have CS2 of non-essentials, like InDe­sign, GoLive, etc. Acro­bat is going to be alright for a while coz I’ve already got Acro­bat 8 because of relatively-late acqui­si­tion of CS2. Dreamweaver… I don’t par­tic­u­larly care about, though I’ve hap­pily used it for var­i­ous things.

And yeah, I’m still going to uni and doing all that sorta thing, so it’s cheaper. I’m just vaguely annoyed I didn’t drop $200 more for Pro­duc­tion Stu­dio when I could’ve if I’d read a bit more, but it’s done now. Hope­fully they’ll launch a new ver­sion of that along with CS3 so I can pick it up soon after the end of this month.

One day I might even make a decent amount of money out of this :P My rea­son­ing is that liv­ing at home & study­ing = good time for doing loss-running, skill– and network-building, moderately-expensive-but-just-within-means geeky things.

At the minute I’m not los­ing money on it, but it’s not some­thing I’d be able to afford to do if I were depen­dent on reg­u­lar income for rent, or what­ever. Speak­ing of reg­u­lar­ity, John C & I ran job inter­views yes­ter­day and decided to get one of the appli­cants onboard for CYIADA! So now that enters the build phase & we’re actu­ally going to be Mak­ingStuff™ that’ll become more directed and sta­ble — not in a finan­cial sense, but just in a number-of-hours-a-week kinda way. At the minute my hours have fluc­tu­ated a bit depend­ing on what I’ve been able to think of/motivated to get done, but that’ll obvi­ously sta­bilise a lot as I move back to cut­ting code and actu­ally see­ing it develop!

Any­way. Can’t wait.

# by Josh Street on March 22nd, 2007 Tags: , , , ,
| 5 Comments »

Adobe Production Studio: Back in Mac

I dis­cov­ered this today. It upset me.

SAN JOSE, Calif. — Jan. 4, 2007 — Adobe Sys­tems Incor­po­rated (Nasdaq:ADBE) today announced that the next ver­sion of Adobe® Pro­duc­tion Stu­dio, the inte­grated video and audio post­pro­duc­tion tool set that is part of the Cre­ative Suite fam­ily, will be avail­able for both the Mac­in­tosh and Win­dows® plat­forms. Film, video and web pro­fes­sion­als cur­rently using Adobe After Effects®, Adobe Pho­to­shop® and Adobe Illus­tra­tor® on the Mac will soon be able to har­ness the power of com­pletely new Mac­in­tosh releases of Adobe Pre­miere® Pro, Adobe Encore® DVD and Adobe Soundbooth™ — all key com­po­nents of an upcom­ing mile­stone revi­sion to Adobe Pro­duc­tion Stu­dio. The soft­ware will have its first pub­lic demon­stra­tion dur­ing the Mac­world 2007 Con­fer­ence and Exhi­bi­tion at The Moscone Cen­ter in San Fran­cisco, Jan­u­ary 9 – 12 (Booth 901). The next release of Adobe Pro­duc­tion Stu­dio is expected to ship in mid-2007.

Are they try­ing to con­vince me to buy a Mac? Ever since some­one showed me what you can do with Objec­tive C and Quartz to any video source on a Mac I’ve been wish­ing it were prac­ti­cal to buy one and use it for every­thing I wanted to, but couldn’t bring myself to con­sider FCP on account of lack of snazzy inte­gra­tion. Ah well. I’m sure some­thing else will crop up before the elusively-dated “mid-2007″ to help me reconsider…