Unless you have your image data already available as some internal format in memory, and pixel extractions are relatively infrequent, then possibly you'd be just fine with plain substr. For example, for a 8-bit non-aligned image: 

sub get_pixel($$) 
{
      my ( $x, $y) = @_; 
      substr ( $image, $y * $height + $x, 1);
}

[download]

I know this is over-simplification, but I use these direct memory hacks once in a while, f.ex. $image = ~$image for images of cardinal pixels is as valid and fast as any other image negation. Your pixel extraction problem might just as well hit the same area.

Otherwise, of course, a number of libraries provide generic image access, as mentioned above.

In reply to Re: Extracting pixel values by dk
in thread Extracting pixel values by redbeard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.