[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: imread / imwrite status?
From: |
Stefan van der Walt |
Subject: |
Re: imread / imwrite status? |
Date: |
Fri, 9 Sep 2005 21:57:17 +0200 |
User-agent: |
Mutt/1.5.9i |
Brendan,
I have (fairly) recently posted patches which use libpng and libjpeg
to read images, instead of ImageMagick. I havn't had the time to
merge in these changes, though. You will find them in the mailing
list archives.
Regards
Stéfan
On Fri, Sep 09, 2005 at 10:59:31AM -0600, Brendan Drew wrote:
> Appologies if this is going to the wrong list -- there's a maintainers
> list but no devel list, which is where I'd usually send this sort of thing.
>
> I am presently using Octave 2.1.64 (SuSE binaries) and Octave-Forget
> 2004.11.16. Looking through the release notes for Octave and
> Octave-Forge, it appears that imread and imwrite (my bread and butter,
> so to speak) are both implemented by forking off an ImageMagick
> (convert) process. This gets to be intolerably slow when reading large
> sequences of images (my C++ png reading / writing code is roughly a
> factor of 10 faster on my system, which when you multiply out by 6000+
> images is quite the savings). Are there any plans for a C++ version of
> imread / imwrite? If not, I'd be happy to take a weekend or two to start
> hacking one together if there is sufficient interest.
-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
Octave's home on the web: http://www.octave.org
How to fund new projects: http://www.octave.org/funding.html
Subscription information: http://www.octave.org/archive.html
-------------------------------------------------------------