CMYK thumbnailing of JPEGs with Gmail/Google Mail

I peri­od­i­cally freak out when review­ing emails that I’ve sent, par­tic­u­larly to print­ers, using Gmail’s (hosted apps) web­mail inter­face. It has this habit of con­vert­ing CMYK JPGs to RGB thumb­nails really badly — but with­out appar­ent corruption.

Gmail getting CMYK thumbnails wrong

The blue in the image above is actu­ally a deep red!

Accord­ingly, while the colours are totally out of whack, there are no other arti­facts in the image. Nor­mally this just looks weird — some­times, in the case of logo vari­ants, it looks plau­si­ble but utterly incor­rect! My guess is they’re using an older ver­sion of PIL (we all know how much Google loves Python) prior to this March 2009 patch. Sounds like the same phenomenon.

Still, those peo­ple email­ing CMYK JPGs has to be a lit­tle bit niche, so I’m not heaps hope­ful of this get­ting fixed too soon! The main rea­son I care is because web inter­faces are so much faster than retriev­ing large attach­ments from IMAP stores.

# by Josh Street on September 16th, 2009 Tags: , , , , , , , , , , ,
| 1 Comment »

More on supplied graphics for the web

I ranted about crappy sup­plied cre­atives a lit­tle while back, and I’m doing so again.

Only this time it’s clue­less mar­ket­ing peo­ple, not graphic design­ers. The prob­lem is they’re not even both­er­ing to ASK for qual­ity. If I get another badly com­pressed JPEG or GIF image too soon, I might just go com­pletely postal in the gen­eral direc­tion of the per­son respon­si­ble. So what, it’s the web/video? Video, in case peo­ple hadn’t noticed, isn’t exactly low-resolution any­more (even if you’re broad­cast­ing in, erm, “pre­tend HD”) so it’s hardly as though a 200 pixel-wide GIF image is always going to suf­fice there, either.

Irre­spec­tive of how crappy your broad­cast com­pres­sion is, the qual­ity of some JPEGs that come through is infi­nitely worse.

This isn’t just me being a purist. It costs real time. Every time I cre­ate some­thing that uses one of these mon­sters, I’ll prob­a­bly spend at least half my time clean­ing up the crap. Why? Because I’m about to com­press it again and it’s impos­si­ble to edit loss­lessly, so even if it looks accept­able in Pho­to­shop, if I’m going to get it con­sis­tent with the rest of the graphic and/or com­press to a rea­son­able level, it’s going to suf­fer. Bleh.

Peo­ple are stu­pid. Vec­tor for­mats aren’t that hard. They’re eas­ier, it’s so much harder to break a vec­tor graphic. I’ve tried using Illus­tra­tor to trace logos in stu­pid for­mats in the past, and that works quite well. Just that my PC at work has a pathetic moth­er­board, and so I can’t have Hyper­Thread­ing enabled or it con­stantly crashes (yeah, tried new BIOS, etc. No luck.). And so Illus­tra­tor is nearly impos­si­ble to use, feel­ing heav­ier most of the time than Pho­to­shop does.

I love com­ing home and cre­at­ing things for here. Fir­ing up the GIMP in about 5 sec­onds, launch­ing Inkscape instantly. Open-source rocks.

Mmm rant quota filled for a cou­ple of days. I feel bet­ter now.

# by Josh Street on May 5th, 2006 Tags: , , ,
| No Comments »

Disable reading layout in MS Word

Arguably the bane of my exis­tence (along­side JPEG logos and Home & Away DVD-cover design), Microsoft Word’s insis­tence on open­ing crap Out­look feeds it in reading-layout can in fact be dis­abled. There’s an Office Assis­tance arti­cle on how to do this.

I hate it because it effec­tively pre­sumes no-one writes doc­u­ments any­more. Under­min­ing MS Office’s awe­some col­lab­o­ra­tion fea­tures (I’m being seri­ous), etc. Not that I ever write any­thing in MS Office myself, of course (except for proof­ing stuff other peo­ple send) — but still, it bugs me. Espe­cially the way things wrap dif­fer­ently, copy dif­fer­ently, etc. Yuck.

# by Josh Street on March 3rd, 2006 Tags: ,
| No Comments »

Sony’s DSC-P93 sucks

UPDATE: Maybe I was wrong. See the bot­tom of this arti­cle for more.

The sen­sor on this must be an absolute piece of trash. It hasn’t even got the excuse of a slowly dying sen­sor due to a man­u­fac­tur­ing defect/humidity… it’s just really poor quality.

One image highlighting its posterization-type effects

The above image has just been scaled, and care­fully com­pressed so as not to exac­er­bate the prob­lem (in actual fact, JPEG com­pres­sion arti­facts reduce the sever­ity of it). It looks as though it’s had a pos­ter­ize fil­ter applied to it (reduc­ing the num­ber of colours in the palette, sim­i­lar to what indexed GIF pho­tos look like), but it hasn’t. That’s straight out of the cam­era… so far as I can tell, no other soft­ware has touched it.

Maybe it just looks worse to me than it is because I’ve got three sets of images here, the other two of which come from a Canon EOS-300D — or Dig­i­tal Rebel in US-speak — (or maybe a pair of them, judg­ing from time delay between shots, but last I heard they were junky con­sumer ver­sions of the EOS-10D with plas­tic cas­ing, and “spe­cial” lens options, so why any­one would buy two of them is beyond me). I don’t know, I was just pretty appalled this was com­ing straight of a cam­era — ANY cam­era, regard­less as to the brand. It’s not over­ex­posed, or blurred, or grainy (well, it is, but you can’t see it par­tic­u­larly well in the scaled ver­sion and that’s not what I’m com­plain­ing about — I under­stand low-light does that to pho­tos), it’s just really bad colour. Inci­den­tally, it was shot as a JPEG. So, it’s not like I or any­one else has screwed up RAW pro­cess­ing — the cam­era has done that for us.

Oh, and inci­den­tally, what’s with 3:2 ratios? I think it’s nicer than 4:3, but it bugged me to look shots from the Canon before I fig­ured out what was going on!

Update: Per­haps they have been processed a lit­tle. One or two of the Rebel’s pho­tos are exhibit­ing sim­i­lar qual­i­ties, so that leads me to believe some­one was being a tool with sat­u­ra­tion in Pho­to­shop or the like. And unhelp­fully left the EXIF data intact so I thought it was unchanged. :-( I guess I’m often guilty of much the same thing with the GIMP, but oh well. Doesn’t hurt to be wrong once in a while!

Another image effects, this time from Rebel

# by Josh Street on October 20th, 2005 Tags: , , ,
| 2 Comments »

Computer screen DPI myth and other misconceptions

Or, an arti­cle denounc­ing the “web is smaller” graphic design mantra. Appar­ently, it’s all about size…

Today I received an email from a graphic designer we’re [base10solutions, that is] col­lab­o­rat­ing with in build­ing a web­site, and this com­ment about source images and com­puter screens came up:

I know we said to make the flash ones a really hi res pic­ture… but you cant view more than 72dpi over the net anyway.

It’s not as though peo­ple who say this are just stu­pid: the whole “72DPI” myth has been prop­a­gated for… a bloody long time. It’s one of those things stuck in the col­lec­tive uncon­scious­ness of the world’s graphic design­ers, espe­cially those who have flirted with design for the screen only occasionally.

The designer we’re work­ing with is great… this isn’t in any way against her, but her email pro­vided an oppor­tu­nity to jump up and down, and there are two rea­sons for that.

Firstly, mon­i­tors don’t all dis­play the same num­ber of DPI, or, more accu­rately, PPI. I think the emer­gence of a plethora of dis­play tech­nolo­gies, as well as falling costs in recent years of all kinds of dis­plays, has meant that we’ve seen a huge move away from 15″ screens being stan­dard (I’m hard­pressed to find any 15″ CRT mon­i­tors new, and even the LCD mar­ket is shift­ing towards 17″ screens) — and “sen­si­ble” res­o­lu­tions on these (1024x768, max) have sim­i­larly been aban­doned. This means, of course, that the com­mon wis­dom regard­ing dis­play res­o­lu­tion has become irrelevent, and ulti­mately false.

Let’s do some maths for a sec­ond. I hate this as much as the next per­son, but… well, it’s required.

I’ve got a 1280x1024 screen. It’s roughly 13.3x10.6 inches in size (17″ diag­o­nally), which equates to about 96dpi. Try this:

1280÷13.3=96.2dpi
1024÷10.6=96.6dpi

It’s not hor­ri­bly com­pli­cated maths, but appar­ently much of the graphic design world hasn’t even both­ered to do that much for some time, instead accept­ing what Pho­to­shop or ImageReady says in all its wis­dom when it advises that “72dpi” is for the web. Yeah, okay.

Hav­ing said that, an image 600 pix­els wide will (in 90% of cases) always be 600 pix­els wide when pub­lished to the web. This means that it’ll always take up about 58% of an 1024 pixel wide screen… it also means that it’ll take up only 46% of a 1280 pixel wide screen. An image’s embed­ded res­o­lu­tion has absolutely no impact unless it’s being printed and the soft­ware spool­ing it to the printer under­stands this.

So, I sup­pose you could say I’m get­ting hung up over words (again) — but I’m not really. There’s a per­fectly valid rea­son to pro­vide higher res­o­lu­tion cre­atives to your web peo­ple (if you’re a graphic designer) — they want source res­o­lu­tion just as much as you print junkies do. For the web­site we’re build­ing, we were going to con­struct a Flash ani­ma­tion that had a spin­ning image in it. If we’ve got higher res­o­lu­tion source, it’s pos­si­ble to do more funky stuff with that (because, in this case, it really is purely about eye candy), just like it is in print (though with­out the sta­tic nature).

It’s worth remem­ber­ing (espe­cially when a web team are devel­op­ing end-to-end cre­ative deliv­er­ables) that the client is ulti­mately respon­si­ble to some extent for the qual­ity of the fin­ished prod­uct. An eye for design isn’t nec­es­sar­ily their sphere of influ­ence, but pro­vid­ing resources to facil­i­tate good design is. And good design is best achieved with good resources.

There’s a com­mon mis­con­cep­tion, it seems, that web design­ers only want cre­atives sup­plied in PNG or GIF for­mat. Most print design­ers realise JPEG images are fairly lossy, so that hasn’t ever been too much of a prob­lem (for me)… but cer­tainly the PNG/GIF thing is. At any rate, just so the world knows, us web peo­ple don’t mind more than sin­gle layer ras­terised images or mock­ups when build­ing sites.

And we cer­tainly don’t need you to splice the web­site up for us… that’s been another con­cern in the past. I’ve spent two hours piec­ing a sup­plied web­site design back together before I even start pulling it apart (again) for CSS treatment!

In fact, in my expe­ri­ence (such that it is), it seems that the less graphic design­ers think about the fact that the cre­atives they sup­ply are ulti­mately end­ing up on the web, the hap­pier every­one is. So here’s my rec­om­men­da­tion: don’t think of it as web any­more. Any web devel­op­ment agency worth their salt should know what to do with what­ever source mate­r­ial you throw at them, and if they can’t use it then it’s their job to say, not the designer’s to guess.

Mt. Buller panorama

A 14424x407 pixel panorama from Mt. Buller

Just to get band­width util­i­sa­tion back to nor­mal, or some­thing ;) The file is 14424 pix­els wide, and 407 high. It’s been man­u­ally stitched, and isn’t too bad, given I shot the sequence in under two min­utes with no great degree of accu­racy. 623KB JPEG. Click the image above to be taken to a full size ver­sion of the photograph.

If you do hap­pen to click through, note the cloud of smoke spread­ing from the bush­fires! It looks even cooler in these photos:

Clouds spreading horizontally
This one reminds me of the spread­ing cloud of dark­ness around… that bad place in Lord of the Rings (I’ve read it, but only endured the first movie – no, I’m not a fan, sorry world). Only it’s not quite so dark. But it reminds me of it any­way. Pic­ture Lord of the Rings with an ugly damn and some sheds in it, or some­thing (I couldn’t sat­is­fac­to­rily crop it, sorry!)…

Clouds of smoke rising from behind mountains looking like it's come from an explosion.
I’m con­vinced it looks like there are mush­room clouds in this one… but… there’s not. Looks like explo­sions in the dis­tance, but the colour (once tweaked a bit) comes out nicely in the photo, in my opinion.

# by Josh Street on July 19th, 2005 Tags: ,
| No Comments »