I've done TIFF handling in C as well, and it's always going to take time to process images. The free "libtiff" may be over-engineered for your task however, and you can probably find some shortcuts if your problem is narrowly constrained.
The problem with many TIFF libraries is that in order to support all possible TIFFs, there's a lot of overhead in their parsing and encoding which may not apply to you.
I recommend you do some calculations of the bytesize of the image, versus the bandwidth of harddisk->memory->harddisk. If the software itself isn't killing you by being stupidly redundant, the hardware is going to be your bottleneck.
--
[ e d @ h a l l e y . c c ]
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
