Slashdot Mirror


Pixel Inventor Goes Back To the Drawing Board

lawpoop writes "Russell Kirsch, inventor of the square pixel, goes back to the drawing board. In the 1950s, he was part of a team that developed the square pixel. '"Squares was the logical thing to do," Kirsch says. "Of course, the logical thing was not the only possibility but we used squares. It was something very foolish that everyone in the world has been suffering from ever since.' Now retired and living in Portland, Oregon, Kirsch recently set out to make amends. Inspired by the mosaic builders of antiquity who constructed scenes of stunning detail with bits of tile, Kirsch has written a program that turns the chunky, clunky squares of a digital image into a smoother picture made of variably shaped pixels.'"

7 of 304 comments (clear)

  1. Re:Invented the pixel? by Tetsujin · · Score: 5, Funny

    Jeebus!! Invented the pixel. I'll be damned. :-P

    That's nothing. What about the guy back in the 40s that invented the color blue!

    No, no... They didn't have color in the 1940s. Just look at the movies from back then...

    --
    Bow-ties are cool.
  2. Without benefit of square pixels, by GungaDan · · Score: 5, Funny

    I would never have known that the Japanese have blurry genitals.

    --
    Eloi are stupid, throw morlocks at them!
  3. Re:Huh? by Sycraft-fu · · Score: 5, Insightful

    But those are pretty easy to solve. The most complete solution is simply to increase display resolution past what the eye can perceive. Have small enough pixels, no jaggies can be seen. We are working towards that bandwidth of the interconnects and cost being the only hurdles, and those are going away slowly. As a quite effective stopgap, anti-aliasing can be applied. It is very easy to do on modern GPUs for little cost.

    Now, take a variable size, variable geometry pixel grid. Tell me how your process that, how you store it in memory, how you rasterize images to it. Sound like some complex problems? They are, very complex. So solve all that, and in such a way computers can process it in realtime with cheap hardware (if it is even possible). Then you get to tackle the REAL hard part: Building a physical display that can display said pixels.

    So, you can do all this, which I am unconvinced is possible, OR, we can simply work on making displays with more pixels. Get displays up in the 300-400PPI region and none of this is a problem anymore. While that will take more bandwidth than our current interconnects provide, engineering higher bandwidth interconnects is a well understood problem and there are a number of solutions (such as simply running more channels in parallel). It will also require working on ways to bring the cost of high density displays down but again, we've had a great deal of success with that. LCDs went from VGAish resolutions that were quite expensive and small to massive HD displays in about a decade.

    To me, it seems like we have the solution to the problem. This new solution sounds far, far more complex and likely impossible.

  4. Re:Huh? by thodelu · · Score: 5, Insightful

    Pixel was probably loosely used in the article. The link talks about image formats and how they use square pixels; not the physical pixels on display devices - which are rectangular generally.

  5. Favorite graphic designer story by jollyreaper · · Score: 5, Funny

    Working in the web division of a semi-fine jewelry retailer.

    graphic artist: Do you know computers?

    me: I should hope so. Do you have a question?

    graphic artist: Yes. It's with Photoshop.

    me: Ok, I might be able to help. What's the problem?

    graphic artist: Ok, let me zoom in here. You see what I have here? (zoomed in so that the pixels were big blocks on the screen.) Everything is really blocky.

    me: Understandable at this view level.

    graphic artist: Well, it's not working for me. I need to be able to get a smaller shape in here but it's all too blocky.

    me: Let me get this straight. You want to get a shape in the image smaller than a pixel?

    graphic artist: *beaming* Exactly! How do I do that?

    me: I'll look into it. *slowly edged away*

    And she was getting paid three times what I was. Things like this make me want to lock myself in the server room, trip the halon and wait for the blackness to take me.

    --
    Kwisatz Haderach
    Sell the spice to CHOAM
    This Mahdi took Shaddam's Throne
  6. Re:Huh? by gotpoetry · · Score: 5, Funny

    Would someone tell me how this happened? We were the fucking vanguard of displays in this country. The Sycraft-fu Mach3 was the display to own. Then the other guy came out with a 300 Pixel Per Inch display. Were we scared? Hell, no. Because we hit back with a little thing called the Mach3Turbo. That's 300 PPI and an aloe strip. For moisture. But you know what happened next? Shut up, I'm telling you what happened--the bastards went to 400 PPI. Now we're standing around with our cocks in our hands, selling 300 PPI and a strip. Moisture or no, suddenly we're the chumps. Well, fuck it. We're going to 500 Pixels Per Inch.

    Sure, we could go to 400 PPI next, like the competition. That seems like the logical thing to do. After all, three worked out pretty well, and four is the next number after three. So let's play it safe. Let's make a thicker aloe strip and call it the Mach3SuperTurbo. Why innovate when we can follow? Oh, I know why: Because we're a business, that's why!

    You think it's crazy? It is crazy. But I don't give a shit. From now on, we're the ones who have the edge in the PPI game. Are they the best a man can get? Fuck, no. Sycraft-fu is the best a man can get.

    What part of this don't you understand? If 200 PPI is good, and 300 PPI is better, obviously 500 PPI would make us the best fucking display that ever existed. Comprende? We didn't claw our way to the top of the display game by clinging to the 200 PPI industry standard. We got here by taking chances. Well, 500 PPI is the biggest chance of all.

    Here's the report from Engineering. Someone put it in the bathroom: I want to wipe my ass with it. They don't tell me what to invent--I tell them. And I'm telling them to stick 200 more PPI in there. I don't care how. Make the Pixels so thin they're invisible. Put some on the stand. I don't care if they have to cram the 500th pixel in diagonally to the other four hundred, just do it!

  7. Exceedingly silly by Virak · · Score: 5, Informative

    First, here's the actual paper, since it clarifies what exactly he's suggesting and doesn't seem to be linked anywhere in the article.

    It's not a suggestion that we start using non-square pixels for displays or cameras or scanners or what not, though he's certainly not being very clear about anything and the reporting on this is just making matters worse. What the paper proposes is a method where:
    1) The image is split into 6x6 blocks
    2) For each block, you go over the four rotations of the two following two-section masks:
    The triangular mask:
    ABBBBB
    AABBBB
    AAABBB
    AAAABB
    AAAAAB
    AAAAAA
    The rectangular(ish) mask:
    BBBBBB
    BBBBBB
    BBBAAA
    AAAAAA
    AAAAAA
    AAAAAA
    for a total of eight effective masks, and average the values under each section, resulting in two values, A and B.
    3) For the mask and rotation that has the largest difference between A and B, you output the mask, the rotation, and the A and B values, resulting in 19 bits from a 6x6 (288 bits) block.

    Though he talks of non-square pixels and whatnot, it's really just a compression algorithm. A really stupid one. Basically it's a bad variation of vector quantization, with lots of baffling details. Why 6x6 blocks? Why those specific masks? Why are you maximizing contrast instead of minimizing error like any sane person would do, WHY? There's no rationale given for any of these choices, not theoretical, not empirical, not even subjective.

    The same sort of rigor extends to his comparison, where he compares his compression algorithm to, instead of, say, another compression algorithm, the image apparently simply downscaled and then scaled back up. And not even with a halfway decent resampling algorithm, but with nearest neighbour. Not to mention that the "non-square pixels" version has 2.375 times as many bits to work with. If he'd done a comparison to a reasonably modern compression algorithm like JPEG, the results would be much less favorable to him.

    tl;dr Some old guy put together his My First Compression Algorithm kit and it's being treated like a revolution in graphics by ignorant reporters. Nothing to see here, move along.